Recent Posts1
[Max] Daily Builds / Re: Chaos Corona 12 for 3ds Max - Daily Builds Discussion
« Last post by shortcirkuit on Today at 01:14:00 »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.
@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.