vray VFB vanishes

[Jacob Hutson]

okay, we've dipped our toes in design 2009 and dont like it so far.
Main issue that will prevent us moving foward is the Vray frame buffer vanishes when the material editor is displayed.
you have to right click where the vfb was to get it back and then its only there for second
close mat editor VFB comes back
frustrating yes

using
xp64bit, max 2009 design, hot fix and sp1, vray sp2

anyone else replicate this
its bad, it happens on all our workstations

[vlado]

I'm aware of the issue; my guess is that something changed because of the viewcube/steering wheel. I'll have to look into how I can work around the problem. I was under the impression this only happens on Vista though.

Best regards,
Vlado

[DrJan]

I had the same problems. But I can't recall if it has happened recently.
It could be that I no longer have this issue because I renamed the viewcube file ,AutoCamMax.gup, to AutoCamMax.gup.BAK in the stdplugins folder.

I'll see if it still happens to me, else that might be a (temporary) solution.

[digtlpete]

I'm having the same problem. I am using max design 2009 on Windows xp x64.

-Brian

[Erik de Graaf]

Same here, im on Vista 64 bit with max 2009 design vray 1.5 sp2

[vlado]

Do you guys also have the problem of the 3ds Max Help window disappearing in the same way?

Best regards,
Vlado

[cashgrow]

same problem here. XP 64 MAX 2009 Design. This is also when im rendering. if i click any other place on screen the VFB vanishes, but stays as long as I dont touch anything else.

no problem with help window.
Also problem with renderslaves that do not update if you not resave the scene after you did any changes. but thats another story..

[gfa2]

Just had this happen for the 1st time. It's only in one file too. I'm on max 2009 (not max design) XP64. When I click render the frame buffer goes away, the rendering happens, I just can't see it. I have to manually pull the frame buffer back up after the rendering is done.

[cecofuli]

Now me too:

XP 64 + 3ds max 2009 + SP3.

(*). Simply scene: plane + teapot + VRayLight = all one material.
(*). I open render dialog + Medit. all work fine. Now I change the material to Arch&Design. Puff... VFB Vanishes.

(*). Change the mat to VRayMat: VFB Vanishes.
(*). Change the mat to Arch&Design : VFB Vanishes.
(*). Save and reset.
(*). Load the same file and I open render dialog + Medit: VFB Vanishes.
(*). Change the mat to VRayMat and I open render dialog + Medit: VFB Vanishes.

(*). Now I save with VRayMat in the Medit.
(*). Reset 3ds max and load the same file
(*). I open render dialog + Medit: VFB OK!

and this is always. This bug is reproducible. So, the problem is the Arch&Design?

[simmsimaging]

I'm having this problem with 2010 Design, also in Vista (64 Ultimate). Did anyone figure out how to get around it? It's not happening all the time, and not always when the mat editor is open so I don't think it's the A&D material.

I do not have the viewcube enabled in any viewports.

b

[themaxxer]

does anybody here use HCG Asset Browser PRO ?
if so, try to close it while working in max. I have noticed, that this can cause similar problems.

best regards
themaxxer

[themaxxer]

I have also noticed that windows 7 has some strange problem with its focus. I think it's has something to do with directx. because if I change to opengl everything works fine. we work with nvidia x2xx...

[kosso_olli]

I had that problem before. It is caused by the Mental Ray materials. If one of these was in the material editor, the vfb disappears. I solved it by making the vraymat the default for the material editor. You have to be carefull though, if you put an MR mat back in one of the slots accidently, the problem is there again. Working on Max 2008 here.

Regards

Oliver

[simmsimaging]

Thanks.

I have seen it happen with MR materials too, but in this case it the mat editor was all Vray. I disabled the viewcube plugin as per the earlier post and it seems to have stopped the problem.

b

[kosso_olli]

Didn't matter for me if the mat was still in the editor or not. If there ever was one in the editor, the problem showed up.