Corona Proxy Exporter Improvement Request

[shortcirkuit]

Hi Corona team,

Can i put forward an update to the corona proxy exporter?  I would like to suggest that it is updated to ask the user if there is an existing proxy in the nominated directory whether to replace it or use the existing proxy if that makes sense.  That would be super handy.

Cheers
S

[maru]

Do you mean something like this? (see attached screenshot)
If not, please explain what exactly is your idea for the improvement.

[shortcirkuit]

Hi, yes instead of overwriting it, if it could have the option to say "use existing' so it uses the existing proxy along with its materials.

Does that make sense?

Do you mean something like this? (see attached screenshot)
If not, please explain what exactly is your idea for the improvement.

[romullus]

Hmm, don't know about others, but for me it makes little sense. What would be reasoning behind this request? Can you provide some examples when this functionality would be useful?

[shortcirkuit]

Ok - so a lot of the time, i would import a tree, proxy it, then edit its materials and save it into a central location (ie - C:/corona proxies)
Down the track, when i am doing another project months later, i might possible import the same tree again, proxy it and if its in the corona proxies folder and it asks me that it already exists, then i know that ive already done the materiality on it so therefore i would like to use the existing proxy if that makes sense.  Does that make sense?

[romullus]

Not really. Materials are not saved with proxy, so your tree would load without material. Also, unless all of your objects has absolutely unique names, you can't be sure that saved proxy is exactly the same tree. Many times you may end up with overriding wrong asset. But of course, everyone has his own workflow, something that doesn't make sense for me, might be very useful for you.