Hi,
I got a rather annoying problem here.
This scene worked more or less fine for several weeks, then more and more crashes started to occur. Tried it on different 3 PCs (similarish hardware, all intel CPUs, NVIDIA GPUs, one most recent driver, other two older drivers), same result.
The scene crashes approximately 75% of times when you hit the render button with an unhandled exception.
It’s a fairly simple scene, several hundred VRayProxies manually placed around in the scene, and two smallish multiscatter systems. Apart form that fairly small modifier stacks (<7) on some 10 or so objects. Nothing fancy. It is very polygon-heavy (>50 million) when rendering, but since the awesome VRayProxies do their job pretty good usually the scene stays at around 10-12GB at render time on 6k
It’s annoying since I cant really work with the scene and I am in the final stages of testing highres renders and tweaking shaders and rendersettings.
I am also not 100% sure if this is a VRay or Max issue since when I got unhandled exceptions in the past they didn’t crash max but only VRay.
My system:
Intel Core i7-4930K @ 3.40GHz (not manually overclocked)
64GB RAM
GeForce GTX 780 (also standard clock)
If I get an E-Mail adress, I can mail you support guys an ftp link containing the screenshot of the error aswell as the zipped scene file with all assets (~1.1GB).
Also, this scene is also the one in which this issue is happening.
Please send the link to support@chaosgroup.com
Let us know if we have to follow any specific steps in order to reproduce the issue.
Please include links to both related forum-threads into the email in order to track where the scene comes from.
Please include the versions/service packs of V-Ray/3DSMax/Multiscatter.
In a last desparate attempt to fix the scene I converted any and all geometry to VRayProxies (except the multiscatter systems) and had no crashes so far (about 6h working). I don’t have the time to go through each object one by one to find out who’s causing the issue at the moment. This is an inconvenient but acceptable short-term fixthough. Luckily we’re in last stages of production where not much changes anymore. But if I imagine this happens on an earlier stage…
We have already replied on your ticket with details about crash and how you can fix it.
To help any other users that may experience this issue, it turned out that the crash was due to a specific arrangements of modifiers.
Most probably it is a bug in 3DS Max 2014, which is already fixed in the latest version and Extension packs.
Thank you very much! I am hesitant to upgrade the SP on max though since I heard several reports of f****-ups after SP3. Never touch a running system. And I think I can live with collapsing stuff for now. Thanks for solving this issue!
