I’m noticing a difference how Vray 2.0 handles proxy objects from 1.5. Please see attached. The first thing I noticed is how the proxy mesh looks. I do not have a screen shot of the 1.5 mesh, but the 2.0 proxy mesh is different, perhaps heavier looking. I’m also noticing a drop in view port performance. The other thing I noticed is when I assigned a material to the proxy object, it changed the appearance. In 1.5, this did not happen. The 1.5 Proxy looked more like the proxy without the material. Now… all the proxy objects rendered just fine but working with the 2.0 proxy in the view port is somewhat painful. Is this normal for 2.0?
What method are you using to view the proxy in the viewport?
It sounds like you may need to switch the proxy to “preview from file (faces)”. With most game video cards, they have LOTS of issues with displaying wireframe objects. Switching to faces can make a major viewport performance increase.
What Troy said, try the faces mode. There must be a dozen ways to draw stuff in the 3ds Max viewports, all of them with varying performance in the various viewport modes (OpenGL/DirectX/Nitrous). The proxies in 2.0 are supposed to draw faster in Nitrous. If you still have issues, it would be good to send us the proxy along with some more information on the Max version, the video card and the driver.
Thank you for the response. Switching to "Preview from file (faces) help some. At least now in wire frame mode, the proxy objects look correct. Still a bit sluggish when zooming in and out in real time. It freezes just for a spilt second…my guess the geometry is re-drawing itself. I think the video card is having a hard time keeping up with the re-draw. I guess this stuff can happen when you upgrade to new software and you run it on old hardware. My current video card is a NVIDIA Quadro FX 4600 and I
m running on XP64, Max 2010. In the next couple of weeks, I’m going to re-building my workstation. I’m looking at a Quadro K5000 card. Maybe this will remedy the problem or create a new set of issues…details at 11:00.
Please keep us updated about this proxy issue. We will do our best to find a solution.
Note that you can always use our support mail to send us scene files for investigation.
I’ve got a Quadro K5000 card, if you have a particular proxy that is creating issues, can you post it up? I can do some testing here. Max 2012-2014 here. Unfortunately I no longer have 2010 installed.
I do remember our older machines having Quadro FX4500 cards, but I don’t recall having the slowdown issues you are describing. Maybe we created our proxy files with a much lower face count for display?
I don’t think it is a face count issue. I just upgraded from 1.5 to 2.0 and problem happened after the upgrade. I did not have this issue in 1.5. So there must be conflict between how 2.0 handles proxy objects and my video driver or system config. I understand it is impossible when writing software to take into account everything. There are to many variables. Like I said, when I upgrade my system from the stone age to the 21st Century, perhaps this will no longer be an issue. I will keep you posted.
Troy, not to get to off subject but I was curious how you liked your K5000? I was also looking at the K6000 but it is almost twice the price and I can’t imagine the card has twice the performance. At first glance, it appears the K5000 has a good price to performance ratio. Your thoughts?
Proxy Issue: Have you tried recreating the proxy in VRay 2. I believe there were some improvements in the proxy creating system.
K5000: Love it. When I built our new workstations, I tried to get by with a GTX 680 and it was just unworkable for us. We do arch viz, product development, engineering visualization, so we need to be able to work with body objects in 3ds Max and the game cards just couldn’t do it. I even tried a Titan for almost a month, but sent it back due to poor performance in our workflow. The K6000 is an incredible card if you need the huge amount of memory, otherwise your money is much better spent on the K5000.
Now having said all of that, many people here have great luck with the GTX 6xx/7xx cards, including the Titans. You may want to try one of those first before jumping up to a K5000, they are NOT cheap! I use a Titan at home and really like it, until I have to do work stuff at home, then it struggles a bit. YMMV.
Creating the proxy in 2.0 was the first thing I did…same problem. You will love this one…when I created the proxy…it looked fine but when I assigned a material to it…the object color turned black in shaded mode and in wire frame, it was white. It drives me nuts because I can not tell if the object is selected or not. For now. switching it to “preview from file” (faces) will work for the short term. The other thing is, when I merge a proxy object into the scene it looks just fine but as soon as you click on it or navigate in the view port, it gets funky. I think everything is related to video issues. I hoping the system re-vamp will fix it.
As for the k5000…I was looking at Amazon and the price there was around $1,700.00. Have you had the chance to test drive the K6000? It’s to rich for my blood but it would be fun to play around with it…like driving a high performance sports car.
Yep, we gave the K6000 a go. It was nice for RT due to have a LOT of memory, but other than that, I didn’t notice too much difference between that and the K5000. Bunkspeed definitely like the K6000 a little more due to memory as well. Probably not a lot of Bunkspeed users here though.
