Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Daily Builds => Topic started by: rowmanns on 2023-12-13, 09:20:09
-
Chaos Corona 12 for 3ds Max Daily Builds Discussion
You can grab the latest build from: Daily Builds Changelog (https://forum.corona-renderer.com/index.php?topic=41598.0)
-
Something's wrong with colour picker in December 13 build, the swatches are not keeping their colour and overall are acting weird. Also there's that annoying half-checkered thing, but that issue started to happen few weeks earlier, not sure if it's Corona's fault or bug in 3ds Max 2024.2 update.
-
Thanks for the report! We are aware of both things and investigating.
Fun fact: the "transparency" part of the color swatch is expected in some cases. For example, if you create an Autodesk Physical Material and change its diffuse color - you will see that the Corona Color Picker allows setting alpha there. But it should not appear in all color swatches. The fix for this is usually collapsing and expanding the material editor rollout again. So it looks like a UI glitch.
The swatch glitch - (Internal ID=1262704903)
Corona Color Picker stuttering/jumping colors - (Internal ID=1268112830)
There is also picker always sampling black when using multiple monitors - (Internal ID=886677936)
-
Does anybody else experience crashes when using VFB history in Corona 11 and 12? Crashes happens without 3ds max error message and does not generate minidump. Could be scene specific, since it happened to me several times when working with certain scene.
-
I am not aware of this. What exactly do those crashes look like? Is it 3ds Max disappearing completely so that you don't even have time to capture a minidump?
-
It happens when i want to do VFB history AB comparison - try to grab and move divider, but Max freezes for a few seconds and then disappears without a trace. Doesn't happen always, or even too often, but i had few such occasions in V11 which i don't recall to be happening in older versions at all. I don't do any rendering lately, but if it happens next time, i'll try to figure out if it's reproducible and if i can provide you with the scene to investigate.
-
I did not manage to crash it, even in a non-teapot scene ;) , when rendering in various resolutions, IR and production render. If you figure out reproduction steps, please let us know.
-
even in a non-teapot scene ;)
Don't use such scenes, you may encounter bugs ;]
Good Luck
-
Found another colour picker related bug in Dec 13 build - IR is constantly refreshing when one is adjusting tint colour in Corona colour correct texmap.
-
Found another colour picker related bug in Dec 13 build - IR is constantly refreshing when one is adjusting tint colour in Corona colour correct texmap.
Thanks, confirmed also in 11 release.
(Internal ID=1274577117)
-
Hi,
Every time I open a scene (on both PC's) I get the out of core error pop.
Disabling it, or resetting it seems to do nothing.
See attached for details. Max 2024.2, Windows 10. Daily build C12 Dec 13.
-
I don't get that error, but i noticed that even disabling out of core, does not completely prevents Corona from temporarily writing to the disk some OOC related stuff, which is quite upsetting TBH.
-
TBH, This out of core has been nothing but a headache since day one of its arrival.
I don't use it. I don't want to use it. But it still causes crashes, often, and now this annoyingness too.
-
We do use it, Corona is NOT good managing the ram, we have 128gb in all systems and we Need to use it on various scenes in order to render, but the pulze plugin can interfere with the paths.
-
Hi,
Every time I open a scene (on both PC's) I get the out of core error pop.
Disabling it, or resetting it seems to do nothing.
See attached for details. Max 2024.2, Windows 10. Daily build C12 Dec 13.
Hey,
I bet this is really frustrating. I have tried numerous times to reproduce this here, and I have failed every time. Can you provide a list of every plugin you are using and if you are using any render managers?
Cheers,
Rowan
-
Hi,
Every time I open a scene (on both PC's) I get the out of core error pop.
Disabling it, or resetting it seems to do nothing.
See attached for details. Max 2024.2, Windows 10. Daily build C12 Dec 13.
Hey,
I bet this is really frustrating. I have tried numerous times to reproduce this here, and I have failed every time. Can you provide a list of every plugin you are using and if you are using any render managers?
Cheers,
Rowan
Yes, I am using Pulze SM. (Ad RM).
Apart from that it's just Phoenix, I think?
I think one issue is that I cloned my PC... then on the clone changed the user and PC names. It's searching on my old user folder.
However, this only started happening when I upgraded to C12. It worked fine for 1-2 months on C11.
-
I've been playing around with the displacement lister today for the first time.
First thing, it seems quite buggy. If I rename one of the materials that has displacement while the lister is open, it seems to crash. Also if I open the lister, close it, then rename a material and re-open the lister. This is happening in a very heavy file though, so might be hard to replicate.
Second thing; it's a bit strange that displacement has an on/off toggle in the lister, but not in the material settings? Is there not a way to turn off a displacement on a material any other way than the lister? Edit: Ah, I see it's toggle is in the maps list at the bottom of the material properties. Maybe this should also be in the displacement settings area of the material?
-
Apologies, I think I might have possibly led you on the wrong track!
Although this did start with C12 installation, it is also possible that it's Pulze SM causing the out-of-core file location to reset every time I load a Pulze scene. I think perhaps the settings override might have this saved, hence it defaults back to an invalid drive every time.
Worth checking out anyway.
-
hey guys is there something wrong with corona lately? there are certain scenes where the suns position seems to change everytime i re-open the scene? currently on corona 11
-
This and some other issues has been fixed in Corona 11 HF1: https://forum.corona-renderer.com/index.php?topic=41809.0
-
thx mate
-
Small bug in Corona Decal.
In the object include/exclude.
If an object is included to receive the decal. Any object you link in a child/parent relationship to that object will also be included to receive the decal. Highly doubt this is an intended behavior.
-
Small bug in Corona Decal.
In the object include/exclude.
If an object is included to receive the decal. Any object you link in a child/parent relationship to that object will also be included to receive the decal. Highly doubt this is an intended behavior.
Generally, this behavior has to be optional as it's found everywhere in Corona (for example in mask render elements). Please devs, make it an optional per-case thing, it's really problematic in scenes where you just can not change hierarchies, for example in animations. It's a nice feature if you really need it but a real headache if you don't.
-
Not sure if I was experiencing a bug, or if it's a known limitation...but
Today I had a multi-map material with a CoronaLightMtl plugged into one of the slots.
The light worked, but it didn't emit onto itself (ie; the other materials in the same object).
I don't think this is new behavior...?
Will try to replicate if I find time.
Corona 12 Daily Dec 13. Max 2024.2
-
Hi team
i got this error on new daily
-
Hi team
i got this error on new daily
Hi,
It can be caused by various Scatter version installations. From what I observed, it is fine to OK it.
Do you see any unexpected behavior or so in regards to Chaos Scatter after this?
-
Hi team
i got this error on new daily
Had the same error ommediately after installing the 29th daily. So then i installed the previous one and then installed again the latest and the message gone, but the scatter toolbar buttons are gone too.
-
Small bug in Corona Decal.
In the object include/exclude.
If an object is included to receive the decal. Any object you link in a child/parent relationship to that object will also be included to receive the decal. Highly doubt this is an intended behavior.
Generally, this behavior has to be optional as it's found everywhere in Corona (for example in mask render elements). Please devs, make it an optional per-case thing, it's really problematic in scenes where you just can not change hierarchies, for example in animations. It's a nice feature if you really need it but a real headache if you don't.
Decals to not affect the children of included/excluded objects is not reported. It is requested to be as an option.
(Internal ID=1298173053)
-
Hi team
i got this error on new daily
Had the same error ommediately after installing the 29th daily. So then i installed the previous one and then installed again the latest and the message gone, but the scatter toolbar buttons are gone too.
Same error regarding permissions , scatter icons are gone as well and relink bitmaps script now doesnt work until i run 3ds max as administrator.
-
Hi team
i got this error on new daily
Had the same error ommediately after installing the 29th daily. So then i installed the previous one and then installed again the latest and the message gone, but the scatter toolbar buttons are gone too.
Just noticed right now that vrscans materials don't render correctly, sometimes objects appear as transparent or semi transparent...
-
Just noticed right now that vrscans materials don't render correctly, sometimes objects appear as transparent or semi transparent...
Can you share which exact Scans are rendering incorrectly?
-
Hi, the vrscan called rca96517.vrscan which is a carbon, renders semi transparent. Carbon stripes render solid but the rest is completely transparent.
While another carbon called carbon.vrscan renders completely correctly.
-
Hi, the vrscan called rca96517.vrscan which is a carbon, renders semi transparent. Carbon stripes render solid but the rest is completely transparent.
While another carbon called carbon.vrscan renders completely correctly.
The material rca96517 does not render transparent for me. In the attached scene, I placed a rectangular light behind the teapot and it appears fully opaque.
Please provide exact reproduction steps.
-
Hi, the vrscan called rca96517.vrscan which is a carbon, renders semi transparent. Carbon stripes render solid but the rest is completely transparent.
While another carbon called carbon.vrscan renders completely correctly.
The material rca96517 does not render transparent for me. In the attached scene, I placed a rectangular light behind the teapot and it appears fully opaque.
Please provide exact reproduction steps.
Hi Maru, here you can see what's happening. Sorry i reported the wrong vrscan. It was the ccx3300. I tested it in a clean scene and the problem doesn't happen. The scene that has the issue is very heavy and memory consuming so maybe a RAM saturation issue?
-
I can't reproduce it. Which exact version of Corona are you using? Could you send us any scene where this happens? (it can be just one object with the problematic material)
-
I have no idea how Scan Mtl works but maybe they need correct face normal orientation due to the nature of the data (it comes with captured normal info)? In other words, could it be that normals are flipped on that geometry...?
-
I can't reproduce it. Which exact version of Corona are you using? Could you send us any scene where this happens? (it can be just one object with the problematic material)
I'm running Corona version: 12 (Daily Build Jan 29 2024)
Full-speed, Non-debug, MaxSDK 2024
I tried to isolate the object and it renders correctly but unhiding all the things the issue happens again.
I don't think it's a normal issue since with other mats it works.
-
@cgiout I have create a support ticket #216163 for you - you should receive an email notification
-
Creating or selecting a corona camera crashes 3dsmax 2024 with daily march 5
-
Creating or selecting a corona camera crashes 3dsmax 2024 with daily march 5
"Create Corona Camera from view" works, but I can confirm that using the "Create Corona Camera" from the toolbar does indeed cause a crash, even in my basic starter scene. BTW with crashes minidumps are always useful, info on how to find it is here https://support.chaos.com/hc/en-us/articles/4649117083409-How-to-report-issues-3ds-Max
-
Creating or selecting a corona camera crashes 3dsmax 2024 with daily march 5
the same!
-
The camera crash is now reported.
(Report ID=CMAX-838)
-
With the recent Build (chaos-corona-12-3dsmax-daily-2024-03-05.exe) theres something strange with Scatter toolbar
-
Ah the new ultimate in minimalist interfaces! We figured everyone had it all memorized by now so that you could just use it like touch typing.... just kidding, there is a bug here (for me the toolbar becomes text and not icons), ought to be a fix in the next daily.
-
I installed corona 12 in max 2023 and its crashing even in empty scene when I want to create corona camera or try to select corona camera to change parametres...........does anybody have same issue???
-
I installed corona 12 in max 2023 and its crashing even in empty scene when I want to create corona camera or try to select corona camera to change parametres...........does anybody have same issue???
This was discussed a few messages above and it is reported.
-
sorry :-) I am blind and did not see forum pages button, so I chcecked only firts page :-)
-
Hi, I have installed the latest Corona beta. Every time I add a camera (CoronaCam) to a scene, or try to modify its settings, I get an error message about the application closing it. The problem does not occur when using the vray camera.
-
Hi, I have installed the latest Corona beta. Every time I add a camera (CoronaCam) to a scene, or try to modify its settings, I get an error message about the application closing it. The problem does not occur when using the vray camera.
Please see:
I installed corona 12 in max 2023 and its crashing even in empty scene when I want to create corona camera or try to select corona camera to change parametres...........does anybody have same issue???
This was discussed a few messages above and it is reported.
:)
-
Hi, I have installed the latest Corona beta. Every time I add a camera (CoronaCam) to a scene, or try to modify its settings, I get an error message about the application closing it. The problem does not occur when using the vray camera.
This is a horrible bug. I've had to revert to another daily. Will we be seeing an update any time soon?
-
That's the typical risk of using daily builds. And yes, it will be fixed in the upcoming version.
-
I have moved the request for Chinese version of Corona to Feature Requests: https://forum.corona-renderer.com/index.php?topic=42344.0
Please note that this thread is for discussing the newest daily build of Corona. If you have any feature requests, bug reports, or anything else - please use the dedicated forum sections for this. Thank you.
-
No daily builds... even an update for 2025? what's going on?
-
Preparing the 11 HF2 with 2025 compatibility is what is going on :) Should be out on Wed if all goes well (as in, actually out, not daily builds out).
-
Preparing the 11 HF2 with 2025 compatibility is what is going on :) Should be out on Wed if all goes well (as in, actually out, not daily builds out).
Great, Thank you Tom :)
-
Ah unfortunately, things did not go to plan, some issues were uncovered, and the HF2 will now be out next Monday (if all goes to plan...). Sorry for the extra few days' wait!
-
Thank you, Tom, for information. It's good to know something than nothing :)
-
i dont know whats happening today but everytime i create a corona camera, it crashes the scene! latest daily.
-
@shortcirkuit, it's a known issue with the latest daily build. Have been discussed just a couple messages above yours.
-
Perhaps a warning could be added to the daily builds thread stating that there is an issue with cameras?
-
Good idea! On it!
Done: link (https://forum.corona-renderer.com/index.php?topic=41598.msg222636#msg222636)
-
Nice one, cheers Marcin!
-
thanks all - however now that i revert back to the HOTFIX, it still crashes - but not when i select camera - after or during a render now.
Is there some diagnostic tool i can view or file dump to see where and what is causing?
-
thanks all - however now that i revert back to the HOTFIX, it still crashes - but not when i select camera - after or during a render now.
Is there some diagnostic tool i can view or file dump to see where and what is causing?
Did you save a file with a Corona 12 daily build and then load it in Corona 11? Sorry, but that won't work.
You can capture a minidump and send it to us for analysis, but if what I wrote above is your scenario, then there is nothing we could fix: https://support.chaos.com/hc/en-us/articles/4649117083409-How-to-report-issues-3ds-Max
-
hey mate - i reverted to a previous scene, imported models that i did make within the daily, and it still crashes? not sure what to do?
i did submit a ticket - if you could please review?
thanks all - however now that i revert back to the HOTFIX, it still crashes - but not when i select camera - after or during a render now.
Is there some diagnostic tool i can view or file dump to see where and what is causing?
Did you save a file with a Corona 12 daily build and then load it in Corona 11? Sorry, but that won't work.
You can capture a minidump and send it to us for analysis, but if what I wrote above is your scenario, then there is nothing we could fix: https://support.chaos.com/hc/en-us/articles/4649117083409-How-to-report-issues-3ds-Max
-
Thanks, I will check it ASAP.
(note to self: #231699)
-
thanks so much
Thanks, I will check it ASAP.
(note to self: #231699)
-
The crash was caused by the 3ds Max Chamfer modifier and, according to our investigation, was not related to Corona at all.
-
hi team - im still getting that issue when in IR mode, the IR keeps in this motion UNTIL i click off screen (ie another window program) and then IR resumes. It seems to be with forest pack objects.
-
had these a bunch of times, you can hover your mouse over the 3dsmax interface, just not on the viewports for it to restart
-
yeah i know thanks - but we shouldnt have to! its been an ongong issue thats been here before and im not sure what exactly causes it - could it be forest pack?
had these a bunch of times, you can hover your mouse over the 3dsmax interface, just not on the viewports for it to restart
-
hi team - im still getting that issue when in IR mode, the IR keeps in this motion UNTIL i click off screen (ie another window program) and then IR resumes. It seems to be with forest pack objects.
Hi, which version of 3ds Max are you using? I am asking this question because we had some similar reports in the past and it always happened with 3ds Max 2022. If you are using this version, one solution would be to update to a newer one.
Also, did it start happening only after you installed a daily build? It never happens with Corona 11 HF2?
Other than that, I can only recommend submitting a new support ticket and sharing the scene with us: https://support.chaos.com/hc/en-us/requests/new
-
hey mate - im using max 24 with the last official corona release.
hi team - im still getting that issue when in IR mode, the IR keeps in this motion UNTIL i click off screen (ie another window program) and then IR resumes. It seems to be with forest pack objects.
Hi, which version of 3ds Max are you using? I am asking this question because we had some similar reports in the past and it always happened with 3ds Max 2022. If you are using this version, one solution would be to update to a newer one.
Also, did it start happening only after you installed a daily build? It never happens with Corona 11 HF2?
Other than that, I can only recommend submitting a new support ticket and sharing the scene with us: https://support.chaos.com/hc/en-us/requests/new
-
This is a daily build discussion thread. Please only post bugs/feature requests/questions/suggestions related to the daily builds.
-
Woha that's been quet a while since i have been here.
But i am here for a reason, i saw on the road map future Chaos Vantage implementation, so the question is:
Does this current v12 daily build supports vantage or not and we have to wait a bit? If it does i will be able to test it out on insanely huge golf scenes.
Also question is if it will be implemented soon will it have any texture\material\feature limitations, for example such as corona pattern?
-
Hi, it is not yet available in the daily builds. Tom shared some insights here: https://forum.corona-renderer.com/index.php?topic=42118.msg222299#msg222299
Basically, the initial support will be most likely limited (no live link). I am not sure about specific limitations like materials or modifiers. Perhaps Tom can shed some more light on this. :)
-
Great! Thanks for the info.
Sad that it is not yet available to test, i am very tempted to try it out =D
But anyway i will be glad to provide some feedback when it will be implemented to test builds.
-
There will indeed be limitations, same as there are limitations from V-Ray to Vantage, e.g. see here : https://docs.chaos.com/display/LAV/3ds+Max
As a general guide, if it doesn't work for V-Ray, we can expect it not to work for Corona too, and given this is an initial implementation, there may be extra restrictions or limitations for Corona.
And as noted, yes, no live link in Corona 12, this will be revisited after the release of 12 to see what is possible.
-
Any updates form the trello board maniacs ??
-
Nope, I haven't revisited the Trello board just yet, shouldn't be any major changes there though (but will give it a checkover soon).
-
i must say, in all these years, activity around dailies has been abnormally quiet - is something going on?
-
i must say, in all these years, activity around dailies has been abnormally quiet - is something going on?
Agreed! Never seen such a large gap between dailies. Odd...
-
Half-yearly builds :)
-
Just lots of stuff needing doing before a daily comes out, big blocks of code that can't be released in stages; and then in combination with the last week or so being full of statutory holidays meaning things move to next week or so. On the plus side, should then mean a lot in that next update, including the first appearance of "export to Vantage" functionality.
-
Just lots of stuff needing doing before a daily comes out, big blocks of code that can't be released in stages; and then in combination with the last week or so being full of statutory holidays meaning things move to next week or so. On the plus side, should then mean a lot in that next update, including the first appearance of "export to Vantage" functionality.
Holy cow...
-
sounds exciting....
@devs - can i ask something, one thing that has bothered me for years and i dont know the mechanics of what goes on behind the scenes in terms of code. But the heavier a scene gets, the more longer it takes for parsing/IR to work. Sometimes, on repeated IR activation's, it takes over 20 seconds or so on heavier scenes. Now, i assume its taking longer obviously due to geometry/poly count + the increase in textures etc.... if this is the case, wouldnt it be possible to pre-load these (cache) them in so that it starts quicker? & any NEW geometry/texture additions should be calculated from scratch and loaded into cache? again, i have no idea about code and its way out of my depth but i was just wondering if it was at all possible.
Because the thing is this. I moved to Corona many moons ago due to its ease of use. It got rid of the technical aspect that vray had in terms of scene setup/settings. It just works. However, with heavier scenes, i feel as though there is a bottleneck in terms of optimisation. Scenes get heavy and slow, IR works poorly and we are left to our own devices to figure out how to optimise. Scenes tend to feel 'dirty' if that at all makes any sense. Apart from what i mentioned above and ive said this before, it would be awesome to also, in the short term, provide a dignostic tool to help us understand where teh bottle necks are. WHY the IR is taking long - is it a 320MB TIF file? is it loading multiple proxies or a 300,000,0000 polygon item that has turbosmooth set to show only during render (which has a iteration of 5) - a diagnostic tool is somehting that i feel can be achieved relatively easy as its jsut data, data that is currently understood by Corona - we just need it transposed to meaningful and clear text to us, the users....
anyway, hope this all makes sense.
Just lots of stuff needing doing before a daily comes out, big blocks of code that can't be released in stages; and then in combination with the last week or so being full of statutory holidays meaning things move to next week or so. On the plus side, should then mean a lot in that next update, including the first appearance of "export to Vantage" functionality.
-
sounds exciting....
@devs - can i ask something, one thing that has bothered me for years and i dont know the mechanics of what goes on behind the scenes in terms of code. But the heavier a scene gets, the more longer it takes for parsing/IR to work. Sometimes, on repeated IR activation's, it takes over 20 seconds or so on heavier scenes. Now, i assume its taking longer obviously due to geometry/poly count + the increase in textures etc.... if this is the case, wouldnt it be possible to pre-load these (cache) them in so that it starts quicker? & any NEW geometry/texture additions should be calculated from scratch and loaded into cache? again, i have no idea about code and its way out of my depth but i was just wondering if it was at all possible.
Because the thing is this. I moved to Corona many moons ago due to its ease of use. It got rid of the technical aspect that vray had in terms of scene setup/settings. It just works. However, with heavier scenes, i feel as though there is a bottleneck in terms of optimisation. Scenes get heavy and slow, IR works poorly and we are left to our own devices to figure out how to optimise. Scenes tend to feel 'dirty' if that at all makes any sense. Apart from what i mentioned above and ive said this before, it would be awesome to also, in the short term, provide a dignostic tool to help us understand where teh bottle necks are. WHY the IR is taking long - is it a 320MB TIF file? is it loading multiple proxies or a 300,000,0000 polygon item that has turbosmooth set to show only during render (which has a iteration of 5) - a diagnostic tool is somehting that i feel can be achieved relatively easy as its jsut data, data that is currently understood by Corona - we just need it transposed to meaningful and clear text to us, the users....
anyway, hope this all makes sense.
Just lots of stuff needing doing before a daily comes out, big blocks of code that can't be released in stages; and then in combination with the last week or so being full of statutory holidays meaning things move to next week or so. On the plus side, should then mean a lot in that next update, including the first appearance of "export to Vantage" functionality.
The new Pulze SM has an update that does a diagnostic like this. It's nothing special, but for you it might be a good start...
-
very true mate thankyou - it does help but a more indepth one would be beneficial (ie showing what is causing bottlenecks)
sounds exciting....
@devs - can i ask something, one thing that has bothered me for years and i dont know the mechanics of what goes on behind the scenes in terms of code. But the heavier a scene gets, the more longer it takes for parsing/IR to work. Sometimes, on repeated IR activation's, it takes over 20 seconds or so on heavier scenes. Now, i assume its taking longer obviously due to geometry/poly count + the increase in textures etc.... if this is the case, wouldnt it be possible to pre-load these (cache) them in so that it starts quicker? & any NEW geometry/texture additions should be calculated from scratch and loaded into cache? again, i have no idea about code and its way out of my depth but i was just wondering if it was at all possible.
Because the thing is this. I moved to Corona many moons ago due to its ease of use. It got rid of the technical aspect that vray had in terms of scene setup/settings. It just works. However, with heavier scenes, i feel as though there is a bottleneck in terms of optimisation. Scenes get heavy and slow, IR works poorly and we are left to our own devices to figure out how to optimise. Scenes tend to feel 'dirty' if that at all makes any sense. Apart from what i mentioned above and ive said this before, it would be awesome to also, in the short term, provide a dignostic tool to help us understand where teh bottle necks are. WHY the IR is taking long - is it a 320MB TIF file? is it loading multiple proxies or a 300,000,0000 polygon item that has turbosmooth set to show only during render (which has a iteration of 5) - a diagnostic tool is somehting that i feel can be achieved relatively easy as its jsut data, data that is currently understood by Corona - we just need it transposed to meaningful and clear text to us, the users....
anyway, hope this all makes sense.
Just lots of stuff needing doing before a daily comes out, big blocks of code that can't be released in stages; and then in combination with the last week or so being full of statutory holidays meaning things move to next week or so. On the plus side, should then mean a lot in that next update, including the first appearance of "export to Vantage" functionality.
The new Pulze SM has an update that does a diagnostic like this. It's nothing special, but for you it might be a good start...
-
Vray has it ! You can bump this thread for it
https://forum.corona-renderer.com/index.php?topic=41901.msg221336#msg221336
-
Done, cheers mate.
Vray has it ! You can bump this thread for it
https://forum.corona-renderer.com/index.php?topic=41901.msg221336#msg221336
-
sounds exciting....
@devs - can i ask something, one thing that has bothered me for years and i dont know the mechanics of what goes on behind the scenes in terms of code. But the heavier a scene gets, the more longer it takes for parsing/IR to work. Sometimes, on repeated IR activation's, it takes over 20 seconds or so on heavier scenes. Now, i assume its taking longer obviously due to geometry/poly count + the increase in textures etc.... if this is the case, wouldnt it be possible to pre-load these (cache) them in so that it starts quicker? & any NEW geometry/texture additions should be calculated from scratch and loaded into cache? again, i have no idea about code and its way out of my depth but i was just wondering if it was at all possible.
Because the thing is this. I moved to Corona many moons ago due to its ease of use. It got rid of the technical aspect that vray had in terms of scene setup/settings. It just works. However, with heavier scenes, i feel as though there is a bottleneck in terms of optimisation. Scenes get heavy and slow, IR works poorly and we are left to our own devices to figure out how to optimise. Scenes tend to feel 'dirty' if that at all makes any sense. Apart from what i mentioned above and ive said this before, it would be awesome to also, in the short term, provide a dignostic tool to help us understand where teh bottle necks are. WHY the IR is taking long - is it a 320MB TIF file? is it loading multiple proxies or a 300,000,0000 polygon item that has turbosmooth set to show only during render (which has a iteration of 5) - a diagnostic tool is somehting that i feel can be achieved relatively easy as its jsut data, data that is currently understood by Corona - we just need it transposed to meaningful and clear text to us, the users....
anyway, hope this all makes sense.
Just lots of stuff needing doing before a daily comes out, big blocks of code that can't be released in stages; and then in combination with the last week or so being full of statutory holidays meaning things move to next week or so. On the plus side, should then mean a lot in that next update, including the first appearance of "export to Vantage" functionality.
The new error log shows you the heaviest scene items as well as the heaviest textures but possibly only if you run low on RAM. Having this as a diagnostic feature on its own would be good but i totally agree that as clients request higher res images, and we are required to put more and more detail in both geometry and textures to support the resolution we need better ways of optimising scenes. Revit models in particular seem to take an absolute age to begin rendering and ive got no idea why.