Sorry for the mistake in my previous post. I thought you said renders were taking you 3-4x as long on a Mac Studio - not your old iMac.
To that point - you could also grab a Mac Studio and try it in your workflow. Apple gives you 14 days to return it. Restore some of your current projects and see how it suits you
Think im going to wait for the M4, to do a complete revamp simplification of my kit next year, when its out
Hopefully I can get by with what I think is a faulty rtx6000, ā¦ let me explain what happens maybe this is normal, ā¦ using 2024 with another 2 months bookings to go, ā¦ not too sure but when im using 3dblur with a custom kernel for a defocus, ā¦ (this is just one example.) whilst rendering my screen goes all grey with a bit of image detail for a number of frames, sometime my sdi out goes grey or my display, or both, and sometimes it shows up in the render sometimes it does not, sometimes I notice something slightly odd in the the render on the frames the grey appeared, resource manager shows only half or less of the VRAM used.
Shell sometimes shows the matt input of the blur node was not used or something like that when I dont need a matt, or I dont have permission to access "httpā¦;Autodesk6:com on this server ā¦
So im getting by pre-rendering and using my iMac. Any ideas I think its a faulty cardā¦
Have you tried reinstalling the DKU?
Echoing Adam - Iām assuming that is the correct driver for this version of Flame, and that in more recent versions thereās no mention of a bug fix that sounds like what youāre seeing?
Also, Iām not sure if there are any diagnostics utilities to do a self-test on the GPU to see if itās actually faulty. Isnāt there a nvidia-settings tool on Rocky where you can set driver settings like display, etc. It may also have some diagnostics.
ahh I just realised thereās a hot fix released beginning of the month, ā¦how come I wasnāt notified,ā¦ nevermind hope fully this will fix it 2024.2.2
So just checked on my system (which is A5000, not RTX6000, should be immaterial).
There is a /usr/local/bin/nvidiainfo command which just outputs basic info on the GPU on your system. A few health values, but no diagnostics.
There is the /usr/bin/nvisia-settings, which primarily sets the X11 display config. But it also has some hardware elements. Most pertinent it will show you if ECC (memory error correction) is enabled on your GPU, and if so, what the error status is.
If you have in fact a faulty card, and ECC is not enabled, that might be a good step to get you by for a bit longer until M4 comes out.
Lastly, there is /usr/bin/nvidia-bug-report.sh which is a script NVidia describes as their log collector for any RMA. You can run it, it will create a log file that you can look at. A lot is useless info, but towards the end there is useful summary of stats about your card.
by default its not enabled
Might be worth a try? I donāt think it comes with performance penalties, though not certain about that.
ECC Memory is one of the things that sets the workstation cards apart from the gamer cards.
[quote=āallklier, post:26, topic:10665ā]
So just checked on my system (which is A5000, not RTX6000, should be immaterial).
[/quote]
(Help)
interestingā¦ ive gone from grey frames to highly saturated
ECC show no errors
Anyone actually tested an ADA version of the rtx a5000?
just for info as weāve not used it for Flame yet, but we bought a Macbook Pro last week (M3, 12core, 36gb ram), loaded up a Cinema 4d project that we had made on the 2019 Intel MacPro (12 core, 96gb ram).
Rendering on the MacPro took 20mins+, on the Macbook Pro it took 3mins. Impressive speed improvement with the M3 chip.