|
Tell us what you think of the site.
|
Autodesk Media & Entertainment User Community
|
Autodesk® 3ds Max®
|
|
Autodesk® Maya®
|
|
Autodesk® Softimage®
|
|
Autodesk® MotionBuilder®
|
|
Autodesk® Mudbox™
|
|
Autodesk® ImageModeler™
|
|
Autodesk® Sketchbook® Pro
|
|
Autodesk® Smoke on Mac®
|
|
Autodesk® Entertainment Creation Suite Ultimate®
|
| Finally no display lag with Nitrous... [MIRACLE ?]
|
|
|
Hey Dear Friends!
Two days ago I’ve downloaded and installed new CUDA 4.1 from nVidia, and during work in 3ds Max Design I’ve noticed no lag with Nitrous!!
Can you try it too?
I’m curious if it’s real or if it just seems to me?
kcpr raffaEl
http://www.wizualizacje-3d.eu/en/portfolio
|
|
|
|
|
What does CUDA 4.1 do? I am hesitant to install it since I am happy with the performance of my computer.
Author: pyro777
|
| Replied: 03 February 2012 04:15 AM
|
|
|
|
|
|
|
No effing way?! Really? I have that buffering “LAG” u speak of and been needing an answer for a while from autodesk, but seems others get in the way with their smart a$$ opinions that max works just fine and must be me.... Nope… It has to be Nitrous… It is still in its infancy… So totally expected.... But also expected it to be fixed before v2013 release… But as usual… Autodesk will not fix 2012… They got your money and want more.
I’ll have to d/l those drivers u speak of and see if it works..... Hope it works!
How many video cards do u have and what kind? CPU?
Author: timd1971
|
| Replied: 03 February 2012 04:10 PM
|
|
|
|
|
|
|
|
******************************
WELL...... YES! IT IS A FRICKN MIRACLE!!!! my goodness..and only almost a YEAR LATER!
Thansk kcpr raffaEl for stumbling across this FIX!!! You are NOT hallucinating...it definitly works!!!!
There is ABSOLUTELY NO LAG AT ALL now.... 3ds works very fluidly like it should have!!!!! WHy Autodesk couldn’t even remotely provide this solution, I have no idea… but then again, how in the hell would ANYBODY know? The NVIDIA driver page doesn;t say anything about it, just shows the latest stable version I already had (v285.62) or BETA drivers I don’t touch. How were we supposed to know about this developer CUDA 4.1 page and the driver? Except for kcpr finding it!
Even using the MMB (middle mouse button navigating), it works flawlessly now...INSTANTANEOUS!
Attached is the screengrab for the CUDA 4.1 page of the driver that pertained to my setup that works just fine. I did a CLEAN install of remving the prior (so called latest driver) 285.62...and updated to the CUDA 4.1 developer driver 286.19. (SEE ADDITONAL POST BELOW!)
Author: timd1971
|
| Replied: 06 February 2012 12:54 PM
|
|
|
|
|
|
|
re:"WHy Autodesk couldn’t even remotely provide this solution, I have no idea”
My guess is it is probably because it was a fix in a 3rd party driver. Unless they have explicitly tested the drivers how would you expect Autodesk to know it fixed a specific issue?
-Eric
Author: PiXeL_MoNKeY
|
| Replied: 06 February 2012 03:23 PM
|
|
|
|
|
|
|
hellohru
Author: vinodpal
|
| Replied: 09 February 2012 06:43 PM
|
|
|
|
|
I’ve installed it to check if it impact iRay rendering performance.
But it turned out that it installed new drivers too (286.16, while on nVidia site standard drivers download there is 285.62 available).
I do not know enough to say something more…
kcpr raffaEl
http://www.wizualizacje-3d.eu/en/portfolio
|
|
|
|
|
|
|
There are newer drivers than that available from their “Beta and Older Drivers” page here.
-Eric
Author: PiXeL_MoNKeY
|
| Replied: 03 February 2012 11:41 AM
|
|
|
|
|
|
|
|
yeah, BETA… probably looking for trouble using those. not risking using those.
Author: timd1971
|
| Replied: 06 February 2012 12:43 PM
|
|
|
|
|
Has anyone tried out the Beta drivers with Max? I am reluctant to download because they may not be stable. But if Nitrous performance is improved then…
|
|
|
|
So I tried this too, installed the dev. pack and 286.16 driver that came with it. Nothing dramatic for me (not like 100% performance jump or anything), though I do think there was some solid performance gain to be had. Transparency was better in Nitrous, in that it before I had some glass items that you hardly could see, and now they were more solid looking. Shadows were definitely more accurate too (had them cranked up to Best in preferences). Speed was subjectively 20% better overall.
My scene is not very typical I think: 4 million or more polygons in the view port, 8 area lights, and all surfaces with soft reflections of some sort. I’m not expecting anything like real-time scrubbing of the animation, but having accurate lighting that I can adjust without rendering is huge. I had this somewhat already, but I do think the newer driver makes it much more viable now.
I use a Quadro 4000 for my two primary monitors and a Quadro fx 3200 for my third monitor.
Doug
http://www.dbowker3d.com
New England independent 3D animator specializing in technical, mechanical and medical animation.
System: Dual Intel Xeons E5645 2.4GHz (24 cores), 24GB RAM, Quadro 4000, Windows 8 Pro 64-bit
3DS Max user since r2,…
|
|
|
|
The main difference I’ve noticed was no “lag” - earlier when I’ve tried to rotate view, there was about 0,5 second of “freeze”, and then viewport started to rotate smoothly.
Now, it seems to react instantly - but still I’m not 100% sure if it is only my feeling…
I’ll check it during my work.
I’ve forget to mention my config:
Intel i7 @3.4 GHz
24 GB RAM
2 x GAINWARD PHANTOM GTX 580 3GB VRAM no SLI
Win7 x64
kcpr raffaEl
http://www.wizualizacje-3d.eu/en/portfolio
|
|
|
|
|
|
|
Thanks kcpr.
I installed it on another machine that only had a 9800 gt in case it was screwey. Seemed a little better I guess… But. Really honestly cannot tell as I don’t use this particular machine. When I gt a chance, I will brave installing it on my main work pc’s and see if a difference. I really hope so. I too have always had that initial “buffering” lag before selecting, rotating, moving, scaling etc.... And these are basic scenes...nothin complex a about them where I could understand justifying a quadro. Just a coupl lights and few cameras, basic scenes.. Nothing elaborate.
It’s definitely the way Nitrous has to do whatever it does in that split second before working with objects in the scene. Maybe it’s just a necessary trade off for the wonderful result you get with nitrous viewport?
I wonder if Ken and the team have tried your solution and if they get this same solution or not at all? Reason being seems many don’t admit having this LAG problem we have… Either using the MMB or not. Never did a good solution to all of this...which is important… Just answers like it is too complex to fix in a half a years time basically.
Author: timd1971
|
| Replied: 05 February 2012 07:23 AM
|
|
|
|
|
There are multiple problems that appear as a “lag problem”. We thought there was just one, but now we think there are more than one. We’ve seen many reports of Nvidia or other drivers fixing this problem, so that is one dimension. The only thing we’ve been able to replicate is a lag that comes from picking in complex scenes. For that we are testing new code that uses the hw to do picking. That is looking promising. Not sure if we can release it for 2012 yet.
Director, Visual Communication Solutions
Autodesk
|
|
|
|
|
|
|
well thanks for shedding even more light on a real problem that is actually quite serious. since it is taking a while to fix it and arrive at a solution and actually making a REAL effort too, then that tells me quite a bit of users, if not all, are affected here...not just a small amount of users lead to believe. if that was the case, there would be NO effort being made to rectify such a performance problem with max.... but just to blame the user setup.
I think the users who claim they don;t have this initial “lag”, are users that actually have super high end machines, cpus, quadros etc… so with that kind of cash spent, there better not be any sort of hiccup involved even if the software was the problem. But may be noticeable to say setups with not so high end equipment, (not speaking of low end crap, but middle of the road or close to high end). Maybe this problem is more noticable with those setups… or lets just say the more TYPICAL setups.
Author: timd1971
|
| Replied: 06 February 2012 05:12 AM
|
|
|
|
|
|
|
There are enough users, though still a minority, that experience this that we investigated it. The user setup DOES play a role and there is no way of avoiding that. If you want us to spec 5 versions of hw/os and require all of you to use those 5 versions for a tested experience, then let us know.
I’ve seen many different ways of resolving the problem with zero changes to 3ds Max. So yes, some of the lag is induced by things we don’t control. Nvidia discovered that this can be traced to some Windows code for example that is not working as specified in certain configs. What triggers this seems to vary, but resources of the GPU are also a player in the issue.
Author: Ken Pimentel
|
| Replied: 06 February 2012 09:34 AM
|
|
|
|
|
|
|
|
"”...........
Author: timd1971
|
| Replied: 06 February 2012 01:43 PM
|
|
|
|
|
Hi,
I installed the latest beta drive but it doesnt really gave an improvement. maybe some slight speedchanges and a little bit better on the lags. but they are still VERY noticable.
- Markus
|
|
|
|
My 3dconnexion seems to be the root of my navigation problems...pegs one of the processor and gets all jumpy. Not all scenes and not all the time, but when it does, the CUBE works just fine, so I use that.
3ds Max 9 thru 2013
Windows 7 Enterprise 64-bit OS SP1
Dual Intel® Xeon® 6 core X5650 @ 2.67GHz CPU 36GB RAM
NVIDIA Quadro 4000
450GB HDD (x3) and 2TB HDD
3ds Max 2012 Certified Professional Models to Motion
|
|
|
|
|
|
|
fyi, my 3DConnexion Space Navigator (drv6.15.2) works fine...no CPU pegging or anything. so it didn;t affect my situation. the CUDA 4.1 update certainly fixed it though.
Author: timd1971
|
| Replied: 07 February 2012 05:17 AM
|
|
|
|
|
******************************
Attached is the screengrab for the CUDA 4.1 page of the driver that pertained to my setup that works just fine. I did a CLEAN install of remving the prior (so called latest driver) 285.62...and updated to the CUDA 4.1 developer driver 286.19.
Intel i7 3820 3.6Ghz 8 CORE HT / CoolerMaster Hyper 212 EVO / OCZ Vertex4 256GB SSD v1.5
Nvidia EVGA GEFORCE GTX 660 3GB v314.22 (Nitrous in max) / Dual Dell Professional P2311H 23" Displays
ASUS P9X79 PRO / G.SKILL ARES 64GB 1866 DDR3 / Antec…
| Attachment
|
|
|
|
|
|
Thanks kcpr raffaEl! This pretty much fixed the lag for me. Alt+MMB is now as fast as the Orbit SubObject mode, whereas before they weren’t in the same ball park, or planet even. I also received a significant improvement for scrubbing the timeline for an animated deforming mesh (character).
Opening/closing/minimising/maximising windows in Windows in general is also much faster with Max open.
3ds Max 2013, Windows 7 pro 64bit.
MSI NVidia GeForce GT240, 1GB DDR3 (Driver 286.19).
i7 2.93Ghz , 16Gb CORSAIR Vengeance RAM, DX9.0c.
|
|
|
|
|
|
|
might need to update your driver version in your SIG.
Author: timd1971
|
| Replied: 07 February 2012 05:01 AM
|
|
|
|
|
I have this annoying lag too. What should I install? The CUDA Toolkit or the Developer Drivers?
|
|
|
|
|
|
|
Just the drivers. See my screen grab above. Make sure u get the correct one pertaining to your system. They have several ones, desktop, laptop, xp, Linux, etc.
Author: timd1971
|
| Replied: 07 February 2012 02:19 AM
|
|
|
|
|
