Volumetric light and reflections

[Madman]

Hi Jesse,

Your new volumetric light feature is a fabulous, albeit difficult to control, new feature to M3D. I am having issues with the combination of volumetric light and reflections, however. Calculating selections does seem to freeze M3D in an infinite loop. If I calculate reflections for the complete render, it freezes the first time, but if I stop the calculation and restart it, it seems to work fine. Can you have a look at this? Thanks!

[Jesse]

Hi Madman,

i have not seen this issue yet, so if you got some sample parameters, please post or send per pm.
Thank you!

[Madman]

OK, this is weird... I have this issue with three totally different sets of parameters (m3i files). But... if I rerender the same parameter sets from scratch, reflections work fine... Sorry to have bothered you. Must have been a crooked bit in my PC   

[Jesse]

Just a thought:

because Jeremie got this issues too, but couldn't repeat them as well, it might be due to a memory limitation!?
Especially when the renders were huge in size.
Memory limitations can always lead to unpredictable issues... but i would expect more that rendering would stop rather than loop forever.

Nevertheless, if someone got repeatable params with this issue, please tell!

[bib]

I don't think this has to do with memory (at least from an available memory standpoint, I have 16GO, more than enough). Difficult to reproduce indeed but I've seen similar issues, yes, however not while using "calc selection". It had more to do with passing params back and forth between the navi, the main window, the animation editor.

Since VL I noticed that the navi crashes (whereas usually it's very stable) but again, I can find a step by step way to replicate. Not sure if there could be an issue for example when using VL together with DE Combinate....

I think the navi crash has a good probability to be the same issue as Madman: rendering time growing infinitely in the main window (I saw that a couple of times recently)

[Madman]

I don't think it is memory either. I'm not doing anything exceptional (rendering mainly @ 3600 X 2400). It's interesting that you mention DE-combinate, bib, because two of the three parameter sets that have this issue are DE-combinates. That was the first link I made, but the fact that one of the parameter sets that misbehaves is a "normal" alternate set, threw that thesis overboard... If I find anything reproducable, I'll let you know.