anyone experiencing tremendous viewports slowdown using vrayproxy?
I’m trying with a gtx570 and they are almost unusable if not in box display
Which 3ds Max and V-Ray version is this?
Best regards,
Vlado
sorry I forgot to mention
3ds max design 2011 x64
windows 7 x64 pro
VRay 2.20.03
geforce gtx570 latest beta driver
Hm, ok. It would be useful if you can get us a way to reproduce this - from my tests here it doesn’t seem too slow, but maybe my scene is too simple.
Best regards,
Vlado
here it seems to happen with simple scenes as well
http://www.mediafire.com/?mz8kycj16u34k9m
without proxy (1024 poly) I have 350 fps
with proxy (160000 poly) I have 3.5 fps
orbit in full viewport and smooth+highlights without any degradation
I can add that the proxy was made time ago with a previous vray release
any idea?
Not right away, will have to debug it to see what’s wrong.
Best regards,
Vlado
does it mean that you can reproduce it there?
vlado can you please confirm that it’s a vrayproxy problem? …it’s just to narrow a bit what’s wrong with this new gtx 570
With GeForce 580 and the latest drivers on 3ds Max 2012, I get between 150-200 fps in the Nitrous viewport, about 3 fps in DirectX mode and about 19-25 fps in OpenGL mode. So it does look that proxies draw slowly in the DirectX mode. I don’t know the reason for the slowdown yet.
Best regards,
Vlado
ok, thanks for the infos …let us know if you find a solution, for the moment I can switch to box mode
Vlado, I’ve just found something that could be useful:
importing as mesh one of the old proxies and redoing the entire proxy creation process leads to a scene where the preview from file (edges) option is extremely slow as previous but the the proview from file (faces) is a lot faster, I’ll dare to say tedious but almost usable.
any news about this?
if yes does the fix will come with a future sp or sooner?
managing older scenes with this new gtx its a pain (backface culling and vrproxy slowdown together are an overkill)
We will try to improve this, but it’s a lot of trial and error…
Best regards,
Vlado
gasp! so, no hope?
suggested alternatives?
do you know if does it happen using a quadro 600 or 2000 as well?
I didn’t say that
I just said it’s trial and error, so I can’t get you a quick solution unfortunately.
do you know if does it happen using a quadro 600 or 2000 as well?I don’t know yet; we have to try it out on a Quadro card.
Best regards,
Vlado
As a temporary solution, you may try the following:
- use preview from file (faces) display mode
- select all vrayproxy objects, then from the 3ds max object properties clear the “Vertex channel display” property
The above steps should make the viewport quite usable.
Hi Vasil,
right now I’ve just remember your answer about this issue and wow!!! …I’ve been already using the “preview from file (faces)” trick but I’ve totally forgot about the “vertex channel” one
…that makes a huge difference!!!
thanks a lot for your support
As I’m still with the 2.20.03, is this issue solved in the latest build or this workaroud is still required?
I don’t think I merged the changes in the official builds, so for the moment it’s only in the nightlies.
Best regards,
Vlado
I am experiencing very slow vrayproxy related viewport performance in Max 2013 using a Quadro 4000.
I have narrowed it down to a simple file that contains a camera and 2 vrayproxys. Pressing play I get the following performance:
Both proxys in the scene:
Max 2013: 0.5 fps
Max 2011: 375 fps
Just VRayProxy_B:
Max 2013: 375 fps
Max 2011: 375 fps
Notes:
In both cases orbiting the view gets me around 575 fps
Max 2013 (PU5, vray 2.30.01, nitrous)
Max 2011 (SP2, vray 2.20.03, nvidia performance driver)
VRayProxy_A and VRayProxy_B are created from the same base mesh, some iGrass.
VRayProxy_A was made using a vray version prior to 2.30.01, not sure which.
VRayProxy_B was made with 2.30.01.
I’ve tried the above (use preview from file (faces) display mode & clearing the “Vertex channel display” property) and it has no effect.
Any ideas greatly appreciated! Let me know if you would like a copy of the file Vlado.
Thanks,
Olly
Can you try one of the latest nightly builds and see if it helps?
Best regards,
Vlado