I posted the question on another thread but the tail end of the thread isn’t opening so can’t tell if my message is able to be read.
Got my V7 today - great!
But, camera is crashing repeatedly when-ever I try to load in an HDRI in the world for either refraction or reflection and render.
I can add the same map inot my reflection channel at the material level and it’s fine.
Any special hand-shake?
I’m not doing any GI - just straight-up raytracing.
Stupid question: Have you tried a different map?
All is working perfectly here…
Ian
Edit! Matt tells me he can reproduce it (even though it works for me) - stay tuned… Are you using the PPC or UB?
The first time it crashes was on your glossy project. Turned off the glossy object and tried to just render the raytraced one with GI turned off - it crashed.
So yes, there was a different image there. Seems if GI is turned on it renders…though not certain.
I’m using PPC.
Yes, activating GI stops the crashing. Turning rays way, way down is a work-arounbd till fixed.
Seems to be one of those last minute miniscule changes that has caused this because I simply can’t get EIAS to crash with the final beta (tried on PPC and Mactel).
I’m sure it’ll be fixed very, very swiftly as Matt can reproduce it.
On v6.5 I can reproduce crashes over and over with image viewer and certain .HDR’s and especially with large file sizes, this was reported by me way back…
can Ian or anyone else confirm that the handling of these files has been improved because the new features are all well and good but if the system can only handle every other .HDR image then its a poor show.
Reuben
I’ve successfully used 6000px wide (9 stop) HDRIs with no trouble at all. The system is pretty robust. The image viewer was improved for HDRI - and a few bugs were fixed.
Ian
I can confirm that a crash bug in the HDR viewer was fixed for 7.0. Larger files would crash Animator. This in no longer the case.
This is all my fault. We isolated a nasty crash bug that dated back to version 6.0 and I included the fix at the last moment. I knew better than to inlcude the fix without a lot of testing, but the bug had eluded us for so long that I wanted to see it taken care of. This “fix” created the bug Paul described as a side-effect.
Our 7.0.1 beta (which includes the Camera and Rama changes for Leopard) has this problem taken care of.
Hey…it’s always going to be your fault!
It’s not a show-stopper as clicking on GI and using 1 for samples doesn’t create any render hit and it works fine till everyone can get the fixed version installed.
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.