All,
I’m curious if this also fixes your “fans spinning up” problem? It seems very related, but it’s possible this is just another problem found and has overshadowed the original problem mentioned in this thread…
Does starting Rhino and letting it stand idle still cause the fans to spin up?
Thanks,
-Jeff
My fans-problem is solved since i changed the nvidia settings. Thanks!
Just a wild guess: The NVidia driver considers Rhino as a game and therefore switches on the high performance mode by itself.
If this should be true, then there must be a reason why it is so with Rhino and not with Photoshop etc.
Fan is quiet for my XPS9650 with GTX1050, but battery drain seems a bit fast.
Also, GPU seems to think Rhino is still up and running even if Rhino is exited.
Anyone else see this problem?
----->Pls ignore the GPU thinking Rhino is still up, was ok after reboot of windows
It really isn’t as complicated as that… The drivers aren’t looking at specific vendor applications and making any kind of intelligent decisions…
What happens is that when an application creates a graphics context for the first time, it is then when the drivers get loaded into that application’s process space… During the loading of the drivers, they take a look at the process in which they are loading, and then look up in the their profile dictionary to see if there is a profile entry for that specific executable (.exe)… If the drivers can’t find a profile entry, the defaults are used, otherwise the found profile settings are used. If an application never creates a graphics context, then this process is never done. If PhotoShop uses shaders for any of its filtering (which it does), then I would expect some kind of context to be created, but it may not create that context until you actually filter something for the first time…
However, what you probably aren’t aware of are “hidden profiles” … NVidia can create profiles that you can and will never see… This is mostly done by request of the ISV… Adobe may have requested that any specific profile settings that exist, be hidden and locked down so that users cannot change them…or as I said above, simply starting PhotoShop isn’t enough to get a graphics context created…whereas starting Rhino, it’s the first thing that is needed to be able to see anything.
-J
What makes you think the GPU thinks Rhino is running? What makes you think Rhino has anything to do with this if Rhino is not running? First thing I would do is bring up the task manager and see if Rhino has indeed shutdown…you may have a zombie Rhino running for some reason.
-J
The nvidia task manager? A small icon that shows up if any program is using nvidia gpu was showing rhino as running program even after closing all windows of rhino.
But, after reboot of windows, seems to be working fine now. Yup, should have checked task manager before rebooting.
What happens is that when an application creates a graphics context for the first time, it is then when the drivers get loaded into that application’s process space… During the loading of the drivers, they take a look at the process in which they are loading, and then look up in the their profile dictionary to see if there is a profile entry for that specific executable (.exe)… If the drivers can’t find a profile entry, the defaults are used, otherwise the found profile settings are used. If an application never creates a graphics context, then this process is never done.
I tend to agree to all of the above, but…
I have an own OpenGL-using app.
It draws curves and meshes.
2 OpenGL viewports are created and used on program start, more do come later.
This program will not be known by NVidia for sure, so it will use the driver’s defaults.
The GPU core clock raises on program start and falls down to ‘nothing’ on idle.
Seeing this, I assume there is something special with Rhino.
Or/and the driver makes an intelligent (= thumb) decision.
I remember slow performance in V6 before it came out.
This was with Intel HD xxxx graphics on MS surface devices.
It was solved by not loading shaders from the beginning or so, I don’t know exactly.
Ask @BrianJ.
When you look in the NVidia control panel do you see a Profile entry for Rhino (rhino.exe)? If so, then that’s the reason why your GPU clock spins up and remains… The profile setting for “Power Management” for Rhino is most likely set to “Maximum Performance” which is NOT the default setting for NVidia drivers. I don’t know why at the moment that setting is set the way it is, but that’s the cause of this problem. Changing it to something else will solve the issue. Your OpenGL application has no profile and therefore the default settings are used when your application creates the graphics context.
There is no magic going on here, I assure you.
-J
Hi Jeff, all - I wonder if that setting is there because on dual card systems with low power on-board video and a card, it may force the Nvidia to do the work when Rhino is running.
-Pascal
I’m not sure if this should be a new thread, but is there any info on what the recommended NVidia settings should be? Specifically, in regards to Rhino 6 and antialiasing?
To clarify, I am referring to the settings in the Nvidia control panel->Program Settings->Rhino.exe
I would like to know if there are additional settings for antialiasing that should be set/changed?
For the Global Settings, I am using Workstation App - Dynamic Streaming, as recommended here:
https://wiki.mcneel.com/rhino/nvidiainfo
Video Card info:
NVIDIA Corporation
Quadro M2000M/PCIe/SSE2
OpenGL version: 4.6.0 NVIDIA 389.08
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 2-27-2018
Driver Version: 23.21.13.8908
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24bits
Stencil depth: 8bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 4 GB
If a Profile already exists, then the recommendation is to not make any adjustments, as they have been determined by McNeel to be the “best” or most optimum values… Except of course the Power Management setting…but I’m pretty sure McNeel did not request that setting be part of their profile, and it will be addressed with NVidia.
If there is no Profile present for Rhino.exe, then my best recommendation would be not to create one…but if you do, then any time there is a feature that has “Use application setting” or “Application controlled” as a choice, then that’s the setting you should use.
-J
Perfect. Thanks for the clarification! Just to be sure, I clicked the “Restore” button on the Rhino.exe profile to get all the settings back to default.
That will get you back to Rhino’s Profile defaults, yes… But remember, one of the defaults is wrong… the “Power Management” setting discussed in this thread should NOT be set to “Maximum performance”… So make sure that after resetting to the defaults that you go back make that change to that setting.
-J