Feature suggestion. When trying to export big number of objects at once, exporter gives warning and an option to temporarily turn off undo. I think it would be good if it also would give an option to cancel operation
Me again :] I noticed that if i export proxy with replace source objects turned off and then save the file, its size gets much higher than before export. At first i thought that it’s some garbage left after export, but cleaning the scene doesn’t reduce it’s size. I’m attaching screen with simple test.
On the file size issue. Apparently it has something to do with mesh normals, if i try to export object as OBJ after proxy conversion, then it takes very long time for OBJ exporter to prepare mesh normals. Trying to reset normals with edit normals modifier, gives no result, however selecting all polygons and detaching them to new object, solves file size issue. I think this should be fixed, there’s no reason to leave unnecessary information in object after proxy export. Maybe exporter could make a copy of original object before conversion and then delete it after it’s done its job?
Well, now there shouldn’t be any changes of the original geometry anymore, meaning that there should not be any difference in normals or anthiny else before and after. The proxy exporter does make a copy before collapsing and deletes it afterwards.
I can’t reproduce the issue here. The car file you sent me saves exactly the same size after exporting a collapsed proxy and is only a few mb if I let it replace the original.
I tested it on simple teapot primitive, converted to mesh and it consistently saves almost twice as bigger files after export as before it. I tested it with v0.07, but i first noticed that on v0.06 Is there something else i could provide, to help you identify the issue?
Can’t reproduce it with a teapot either. Maybe you can record a short video of what exactly you do, maybe I’m missing something. Apart from that, the usual “send the file” thing always helps 
Sure, will record a video and send you a file. Many thanks for prompt response!
Ok, got the same effect here. However, here this also happens when you create corona proxies manually, can you confirm that? If so then it’s a corona or max bug.
Hmm, probably a stupid question, but how to create proxy manually? :] Nevermind, i got it. Yes, i can confirm, it’s the same file size issue after manual proxy creation. Should i report that on mantis as a bug?
Yes, would report it. Doesn’t sound right to me.
In my opinion, Corona is the best renderer of today even without the Proxy exporter for Cinema 4D r 19 for OSX \o/
Corona will crash if some special caracter is in the name for example (21 Louis Poulsen PH 3/2 wall lamp) or if i has this symbol "
That may very well be the case. You can’t save files with those characters. I should probably add some checks but quite frankly, this is something you should not do anyways anywhere 
Well, no program or script should crash, no matter what. So reporting this is totally justified and appreciated. I should “sanitize” those string before trying to save (and not crash the script).
I agree, the bug report is still entirely useful.
Proxy Exporter script aside, I think it not a good practice to use those symbols in naming conventions, and I strongly suggest learning not to use them.
I hope this can also be useful. 
Hi all!
I am trying to export a very heavy geometry (44.000.000 polys) and I am getting an error a few seconds after I click the export button, I attached the error image below.
Usually I never had any issues with heavy geometries but today yes.
I use Win 10 and Corona 6 latest daily build.
Do you know what it could be?
Thanks in advance and happy new 2020 from my part as well.
Dionysios -
Hmm… that’s a tough one. Can’t really tell you anything helpful I’m afraid. There’s no reason for it to fail code-wise so I suspect it either being a max problem or a problem with the corona proxy object itself. Can you try exporting it the “old school” way via the proxy object?
Happy new year to you too
Thanks for getting back.
Unfortunately the “old school” method doesn’t work either. I think the object is way to heavy and crashes everything during the process.
I’ll try to detach some elements and create 4 smaller new object and try again.
Thanks,
Dionysios -