Recently I’m experiencing frequent and serious 3ds viz 2008 crash during vrfb drag and drop or zooming and panning, anyone else? … is it a known bug?
In the beginning it happened (well, I noticed it) during render time but now I can simply render something at large res then move around the screen my vrfb window and Viz exits without any message.
I’m running on Quad, 4 gb, quadro fx1500, vray sp1
it happens with maxtreme and direct 3d as well
any suggestion?
thanx in advance
upd 1: max frame buffer work as expected, no crash or whatever
thanx vlado for your ultra fast answer but to me it doesn’t seems related with focus, I mean not only with that.
Just for test I re-opened my scene and click render, after a few buckets are gone without issues I had started to grab the VFB moving it fast around the screen to stress it; after a few seconds everything went away; no other apps running, no focus on anything else; it happens via backburner as well
In the meantime I’m considering to switch back to max FB to avoid any risks forgetting about this issue.
Well, I don’t seem to have the issue under max 2008 64bit and VRay 1.5 sp1, under XP64bit SP2.
NVidia 8800 GTS 640mb, latest release drivers, no maxtreme, Direct3d, macro-recorder enabled (there’s no output whatsoever in it related to the vray vfb).
the past days the issue appears frequently
now it seems less frequent (but probably it’s me and my focusing on that)
actually I’m not able to reproduce it in a consistent way, sometimes it happens sometimes it doesn’t
I don’t know how to check the macrorecorder thing or the maxscript.dll one, anyone who knows how to do it?
edit: definitely it’s not anyway related with the scene: I just test with an ultra simple scene (array of teapot), everything default except GI ON, vrfb ON, show calc phase checked; start render, grab the vrfb to move it fast around the screen… after a few seconds everything is gone
Well, the macrorecorder is on if you see commands spit out in the tiny pink window on the bottom left of the max interface.
It’s off by default, anyways.
As for the bug being related to the specific dll, you’d likely have to have debugging tools (as a standard error simply quits you out with too few infos given).
Could you post a test scene, with correct size and features used at the time of crash?
I really don’t seem to be able to get it to happen here.
It’s not doing that here, no matter what i do.
Max redraws when the window goes on top, sure, so that is somewhat intensive, but it never crashed on me, while max was windowed or fullscreen.
I had winrar open as well, and the VFB was redrawing that too (which is odd).
Still, no issue here (config as of my previous post).
Lele, thanx for your time..
…mmm, let me guess… it begins to appear as another great gift from autodesk related with the useful differences between max and viz?
I’m thinking that because it’s the only common item (other than vray sp1, of course) on my 2 PC and it differs from yours
could you try stretching hard the vrfb window as well, to see what happens?
anyone running Viz 2008 would be so kind to test it?
I’m getting the same crashes inside Viz2008 when I either scale or move the vfb around the screen during the render or even after it’s complete. It’s a pretty hard crash with no error boxes (everything pretty much instantly closes and I lose the render
Just wanted to chime in and say I’m getting the same problem.
thanx alias_marks for you info, it proves I’m not crazy
to Lele:
my “d3dgfx.drv” seems to be older than yours, it’s 9.0.0.36 that make sense according to the different max/viz update scheduling; viz 2008 was released a few months before max 2008.
nope,
using sw display the vrfb works as expected but I can say that in the beginning I tested max frame buffer with D3D and it works too; so it could be something related with that specific version of d3d driver and vray
are u able to confirm what we found about this issue?
Is it really an obscure alchemy among that Viz 2008 release of D3D driver and VRay SP1? any workaround to suggest? (in addition to roll back to max frame buffer, of course)