Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
You might almost be there. Try turning OFF all Filter options Noise/Bloom, and any Optimizers that may be enabled. Also, turn off Spectral Rendering, and give it another go.
@fdsphoto - thanks for the suggestions - but still no love from DAZ Studio even after turning off all the filters I'm able to -
Reads off for : Caustic Sampler, Firefly Filter, Post Denoiser, Bloom Filter, Spectral Rendering, Tone Mapping, and Environment Lighting Blur
I can't shut off 'Pixel Filter' - have that set to Gaussian with Pixel Filter Radius 1.5
Nor can I 'shut' Spectral Conversion Intent (set to Faithful) or spectral Observer (set to cie1931)
Environmnet Mode is set to Sun-Sky Only
Dome Mode to infinite sphere
CPU still goes to 100 on all cores while GPU stays at 0 or 1%, though CUDA cores go to 100% (visually in task manager, no number/% is given)
Temps stay fairly low as well, so I don't think throttling of any sort is a factor/
Other suggestions from anyone?
I have not tried an earlier driver from nVidia or the Game version (currently using the Creation version, which is touted as being better for applications other than games).
Thanks
Driver 430.86 is the best to use at the moment according to some postings. Later drivers have reported problems. YMMV
Again, I wonder whether that 441.66 fix also applies to GTX cards. I notice from your previous posts that you have an RTX GPU.
And this was a good day
Yes I agree Driver 430.86 is the best one i had found as well
This is what your task manager should look like when rendering the viewport.
HI - I'm trying to get my RTX 2070 Super working with DAZ Studio. Can you clarify on that screenshot above: CUDA is close to 100% but the GPU is only at 1% (though it does look like there's a spike on the right side). My task manager does look similar to what you're showing above, except that the CPU will peg at 100% unless I uncheck the boxes under advanced settings for nVidia to try to avoid fallback to CPU. Thanks.
The Spike on the right in the "3D" performance is normal, that's when it's writing parts of the image to viewport (it's your viewport updating). You'll see a simalr spike in the CPU as its flushing parts of the image that are complete.
@fdsphoto - so is it normal for the GPU to stay mostly at 0 or 1% if things are indeed working properly?
My CUDA stays around 100% most of the time and CPU goes to 100% unless I use the beta and uncheck CPU as hardware option under advanced options for nVidia, in which case CPU runs around 10% instead.
Yes, that's the processing of the current "3D" envoirnment being displayed (viewport and/or aux viewport).
- if you grab the orbital and change your viewport angle, you'll see the "3D" stats ramp up and reacts as it updates the current displaying of your "3D" Enviornment in the viewport.
When rendering, all you should care about is your Cuda Cores.
Use the Beta, and always uncheck the CPU. We want to see a render now!!! lol
Any feedback? any of you guys get your setups working?
I think I'm making some headway. Doing some experiments with current DAZ vs current DAZ beta with and without CPU enabled.
Also reading through various posts about Iray - trying to see if I need to load specific procuts / shaders to take full advantage of iray.
Will try to post back in a day or two after learning a bit more and doing some experiments.
I'd just been working under the assumption that GPU in task manager should be closer to 100% as opposed to 0-ish% when rendering. But as long as it's just the CUDA that matters, that's running near 100% so guess it's working as expected.
I agree that for still pictures the cpu may be an option, especially if you are fine rendering overnight. Personally I can't wait for a render more than a few minutes so the gpu with the denoiser is the only way. Also exporting to a real time engine is a very good option for animations. Then we have iray interactive that may be good for limited quality animation too. And I do agree that the vram usage of most daz assets is too much, mostly because of 4K textures. That's why iray is unusable without the scene optimizer addon. That's why some optimization addons as standard inside daz studio would be fine to have.
Back to the topic just for the sake of completeness I'd add that my system seems to work fine, with none of the issues described in this discussion, apart the extra vram for optix that I used to turn on anyway so no differences for me. Specs in the signature.
BTW all. The new beta was released yesterday. It amazingly fast, and you can turn of CPU fallback. Just test drove it yesterday, works fine on my rig.
I wish they could do it like blender and combine both the power of the CPU and GPU, 16K HDRs are insanely fast !
Now that brings up a question for me. How much GPU VRAM should one have in order to easily work, and get renders done with the GPU only? Have the RTX GPUs been around long enough to ensure we have proper performance? I get an impression that the RTX drivers are unreliable. Would it be better to go wtih a GTX card with adequate VRAM?! Is that even possible? Are the GTX cards still easily available?
@Ron I rather would question if staying with nvidia makes any sense at all .. Blender does great with amd and imports daz assets quite fine. For my next rig I'm evaluating to go with amd and blender for production and use the cpu for little iray tests only.
I second that opinion. I can't keep afford to keep paying those prices. For me it'll be worth the extra few minutes to convert to Blender and adjust a few materials. AMD offers plenty of GPU bang for the buck and they're alot more generous with VRAM.
Padone & Kitsumo, I understand that Blender is easy for you. I just want to work with DAZ and get the job done.
I keep seeing these claims about how simple it is to render DAZ Studio scenes in Blender but when I tried it I didn't find it simple at all. Firstly you need to figure out the best method of getting the scene from DAZ Studio to Blender - some use Casual's Teleblender, some Diffeomorphic, some FBX, etc. I tried the first two and was disappointed with the results - clearly that step "adjust a few materials" is a bit of an understatement. Again, knowing how to adjust materials probably means a big learning curve while trying to figure out the Blender node system (obviously, for experienced Blender users, this will have been acheived already). Yet I suspect that tweaking materials is not a trivial task for anyone - even when I do so in IRay (which I am finally getting the hang of but have a lot to learn), it takes a considerable amount of trial and error.
I would appreciate any links to renders of DAZ Studio scenes done in Blender with a comparison of the total time taken, including material tweaking. I suspect that IRay renders of DAZ Studio scenes will be of a higher quality for a given total time taken. Obviously, the VRAM issue is a big motivating factor for looking for alternatives so, for me, the question is: do I try to optimise my scenes sufficiently to allow them to render in my seemingly meagre 8GB VRAM or do I plunge into learning Blender and Cycles in order to remove the VRAM restriction on my scenes. I honestly don't know the answer to that yet.
I tried the scene optimizer and that in itself takes a very long time to run as well! I wish Nvidia offerred an affordable graphics card with 48 or 64 GB RAM. I am sure many people want to render more than 1 character in the scene and just two characters appear to max out the 11GB of my 1080 ti. So I don't know if even 64 GB RAM would be enough. Sure I can hide some charcters and then render them later but if all the characters will be casting shadows on each other you can't do that because the missing shadows would make the image look fake.
Unfortunately, it's gotten to the point where it's expensive to work with DAZ Studio. I want to create a scene, and render it. I don't want to fiddle with or optimize it. I'm not sure if I'll ever gather enough money to build an ideal PC. In the meantime, I might just stay with the earlier Genesis versions, and look for simple scenes that don't tax my system too much.
I'm not sure how affordable a card liek that could be - the memory used in GPUs is priciey than standard memory, as far as I know, and 64GB of regular memory for this machine was somewhere around £350 on its own as I recall.
As the saying goes — and nowhere more appropriately than rendering — "Better; Faster; Cheaper: Choose Two"
Trust me I'm a newbie at Blender. I'm barely able to transfer a scene over from DS and get it working. As long as Blender requires memorizing keyboard shortcuts, I'll probably never learn it. And at my age, my memory's not getting any better. But the new 2.81 interface is a lot more user friendly - it's easier to find things by clicking around.
When it comes to modeling things, I still use Hexagon.
I prefer my eggs sunny side up!
That's really the problem with Blender in a nutshell. Even if the keyboard shortcuts are no longer required, the tidal wave of options, features and techniques facing a new or occasional user is so daunting. Hexagon is not simple but it is manageable and after a few sessions one could get used to where to find the essentials. Blender, on the other hand, requires a solid committment to learning the interface, the tools available and how to use the dozens of modifiers, just to name a few requirements. The latest versions are a huge improvement and I'm pretty sure that I would have just as much difficulty finding my way around ZBrush or Maya if I could afford such software but my memory and my powers of concentration are also on the wane as I approach my seventies.
I'm still having this drop to CPU problem in the latest 4.12 beta (4.12.1.55), even very small scenes do it (GTX 1070 - 8 GB VRAM). Same scenes as well as much larger scenes never do it in 4.10.
Driver is latest Studio driver (441.66). Are there any older drivers that will fix this?
AMD has a 32 GB GDDR5 card that cost less than most RTX 2080ti, so NVidia could probably have offered a 32 GB GTX for a similar price if they had wanted to:
https://www.amazon.co.uk/AMD-100-506048-Radeon-GDDR5-Video/dp/B072HTFZM4/ref=sr_1_4?keywords=amd+radeon+32gb&qid=1580728797&sr=8-4