Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Counter-intuitive as it may seem, this is actually false. Raytracing based renderers always need access to scene data throughout the entire scene for each and every point sample taken - regardless of whether the final image is delivered in a tile-based or quasi-random scatterpoint fashion (like Iray.) Remember - raytracing is a process that takes place in the 3D virtual space of the scene itself - not in the 2D final image (of which each tile is a component part.)
They subdivide the scene and methodically plod through it but it's correct all the scene data is needed and subdividing the pieces is how they parallelize it. That's what you're seeing in cycles.
Yes but the vram allocated for the frame buffer is tile based. That is, it's independent from the final resolution. In iray the larger the resolution the larger the frame buffer. Thus for very high resolutions such as large printings you can allocate a lot of vram for that. In cycles the final resolution doesn't matter as far as the vram is concerned. Of course the whole scene needs to be computed for every tile for shadows and reflections, but that's not the point.
Bear in mind, I'm an engineer and know how to install proper drivers, updates and such, much more than most people; so the issue is not the computer setup. I'm running Win10 Pro (fully updated), the most recent BIOS for the machine, and the latest nVidia drivers (as of this week).
Here's the issue ...
I have an older machine I use in another room. It's an HPz820 workstation, with 96Gb RAM and dual E5-2697v2 CPU's (12 core). I also have three Titan Xp GPU's running. I am having the same memory allocation error problems with 4.12 as described above; where with 4.11 none existed. This is rendering a single image. Now sure I render at 2K (16:9) and commonly have multiple fully clothed G3 and G8 figures and props, but I never had this issue before on 4.11 no matter how complex the scene. I've had as many as 8 figures, in a fully furnished room and using large HDRi for lighting. No issues in 4.11 in those cases. In 4.12 most scenes, even smallish ones, fallback to CPU from the get go. I'm not making animations, just single images. With the Titans and 4.11 I never really had to think about texture sizes, furnished rooms or HDRi sizes for most of my rendered images.
Once I cancel the render the memory doesn't clear, it just stays at 11.x Gb on the cards. I have to restart DAZ or sometimes reboot the machine to clear the VRAM. I suspect there is a memory leak or a badly written "memory clear" command line in the Iray manager coding or DAZ port coding. This is really making my workflow on this machine pretty much useless, not to mention my expense on three TitanXp's a waste of money. I bought them for this purpose. I don't game.
I've looked at the log files, the total size of the VRAM allocation being made by Iray manager is always about 7Gb, (scene complexity notwithstanding) which is far below the amount available regardless. Why it's always around 7Gb is a mystery to me. Yet it keeps trying to reduce allocation sizes ... over and over and over. Usually, before running a render the memory being used by the 1st Titan is at most 1Gb mostly from the viewport in shaded texture mode and the other Titans are at zero. Yet while the log says 7Gb, the actual memory usage is the full maximum on all three cards simultaneously. The Titan Xp are called a 12Gb VRAM card (give or take).
I have never run Optix, since I always have the hardware horsepower. I don't run anything in the background on the machine, no browsers or widgets or anything other than necessary Win10 services (and only those needed). I do run MSI Afterburner, but only to monitor GPU usage and custom fan curves, I use no overclocking or overvoltage on the GPU's or CPU's.
On my main machine (see my sig) I don't have this issue, but I'm running three Titan RTX's there with 24Gb VRAM each and memory sharing via NVLink.
If I can't run Iray on three Titan Xp's on a big workstation ... well ... that's a potential problem for a lot of DAZ users.
I have my theories and suspicions that the problem lies in how Iray manager may be looking to do memory sharing (or even full-on memory scaling as in the RTX Titans and Quadros). When it can't find NVLink enabled cards, such as when finding cards like the 2070 and below (and Pascal cards), it botches the memory allocation somehow, goes into an error mode and doesn't clear the VRAM memory; and then moves on to fallback CPU mode. The same would happen when rendering multiple frames of an animation after the first frame is completed; because of the manager allocating memory into some failure mode leading to the VRAM not clearing. But this is just conjecture on my part.
Glad you wrote that. My impression was memory usage had deteriorated with 4.12. But we are also typically upgrading Nvidia drivers too. Did you test with Nvidia drivers that were available around that time? Since your vidcards with issues are Titan XPs that should be less of an issue using older Nvidia drivers? Just curious.
Yesterday I re-ran a saved scene from my early test days on GTX1070 (8gb Vram), 32GB ram, and same CPU, and WIN7 Pro x64.
Now on an RTX2080Ti (11GB Vram) and 64GB system-ram. Hardrives are still 7200 rpm.
Scene consisted of 13x G8Fs all with hair, outfits and one HDRI. Scene was optimized to 2k textures.
Load time for scene was 9minutes and 28 seconds. Do not remember it being anywhere near that long with pre 4.12 versions. Almost 10minutes is a long time. Seem to remember closer to 6 minutes before when my runtime was 1/4 to 1/3 the size.
But that may be because my runtime is alot bigger with many more arrays of characters and morphs that maybe need to be considered on scene load for each character? Just trying to understand how big an impact runtime size is a factor when loading characters.
While re-rendering this scene, it rendered fine.
But if i did more re-renders it soon dropped to CPU. Even had one mid-render drop to CPU, which was a first for me.
This was on 4.12.0.86 with 441.12 driver, which is solid for 3 characters and a heavy scene.
Little reluctant to say this without more hardproof.
But impressison is had less issues with GTX1070 on older Daz pre 4.12/older Nvdia drivers with this scene for load time (separate issue likely) and for rendering.
Would need to setup old system and get older 4.11 DS to be sure. Which is not going to happen. So am just left with this strong impression something changed.
Which is why am glad that post was written.
Killing the Daz Studio Process works for me. Frees up system-RAM and VRAM. Start new DS session. Zero ill effects after doing that for months now.
On the other issue, of "drop to CPU" during Iray preview live with Babina/Lingerie Robe set posted a few pages ago in this thread.
Updated to 441.41 from 441.12.
Found still get drop to CPU with that test setup in 4.12.1.40.
BUT interestingly did discover, if i change to a 2nd camera after initiating Iray preview with the 1st one, all of a sudden I could load that lingerie robe set 16x times and still no drop to CPU. Just stopped trying at 16x.
Need to test this now by creating other varied texture changes over a longer session. As fallback 4.12.0.86 still works fine with newer drivers. Well other than that old 13x G8F test scene.
Have updated my ticket.
Believe it or not, this isn't true either because Iray fully supports using both in-core and out-of-core memory resources for storing output framebuffers. Direct from the Iray design document:
To simplify data access and maximize performance, Iray is not required to support out of core scene data, i.e. each GPU holds a full copy of all scene data. This may limit the size of supported scenes on low-end and older generation GPUs.
However, this limitation does not apply to the outputs of Iray, as framebuffers can be of arbitrary size and there can be multiple outputs enabled at the same time (see Sec. 4.1).
And here's a log file example of what happens in the current DS 4.12 beta if you atttempt to render a scene whose final dimensions require a framebuffer too big to fit on your GPU:
Much like with Cycles, in Iray final resolution doesn't matter where vram going to output framebuffers is concerned.
If by "Optix" you mean OptiX Prime acceleration, then there's your most likely answer. When Nvidia revamped Iray for RTX (the big change that happened between DS 4.11 and 4.12) they decided to replace its core rendering code (a 20+ year old hodge-podge of thrice ported code) with a brand new implementation of the same featureset written using the RTX supporting OptiX API. Since OptiX Prime acceleration is (or at least was at the time of the recode) THE native method of raytracing in OptiX itself on pre-RTX cards, that meant that raytracing in DS 4.12+ with a pre-RTX GPU is now always done with the previously optional OptiX Prime processing method active since there is no longer an alternative method to fall back on.
If the scenes you were rendering successfully in 4.11 wouldn't have rendered without CPU fallback with OptiX Prime enabled then, then it follows that those scenes won't render at all without CPU fallback in 4.12 now.
Nope ... that's not the issue. While I never needed to use Optix in the older version Iray because of my hardware, I have tested this since the new version was released and these issues began. The older scenes run fine with Optix Acceleration either on or off in 4.11. My problem is related to newly created scenes within 4.12. The new Optix Prime implementation should run on Titan Xp. Why I am getting memory errors makes no sense on small scenes on GPU's having 12Gb of VRAM. Like I said, regardless of the scene complexity, the log files show ~7Gb, and the cards show max out at 11-12Gb after rebooting the machine starting DAZ and loading a simple scene. This is even when the scene is simply two naked G8 figures and an HDRi, and nothing else. Not even hair. Not using anything other than default subD, BTW. Clearly a scene that minimal does not use 7Gb of VRAM nor should it max out a 12Gb card.
Now, the identical small scene on my Titan RTX machine running 4.12 uses 3Gb of actual VRAM and shows about the same in the logs. And memory allocation is not equally distributed between the three cards (like it would be in 4.11 or cards not enabled to perfrom memory sharing), which tells me memory sharing is occuring between the Titan RTXs.
I'm sorry but assuming a change in Optix as you describe that would make people use only top-tier RTX graphics cards to insure general reliability is a change I doubt would be implemented. However, I do not think this changeover to Optix Prime is the issue. It's more related specifically to how memory is allocated by Iray manager. In the logs the memory errors begin to occur before Optix does it thing.
Bear in mind, I have a Quadro VCA that I used to run Iray Server with, so I am very familiar with the differences between the older DAZ Optix Acceleration and Optix Prime.
If you go back and look at the people who are having this issue, it is people who have cards that are mostly 2070 and lower, or Pascal cards. The only real difference between 4.11 and 4.12 related to these specific cards is in the use of memory sharing (and memory scaling). And clearly the problem involves memory errors. The 2070 and below (and Pascal) cannot utilize NVLink or memory sharing in general and the apparent errors may lie in this change. I can make this conclusion based on the result and the only factors that have changed related to this subgroup of cards where the problem is arising. I suspect there is something going on between manager allocating memory and a conflict when non-NVLink enabled cards are present, be they RTX or Pascal. If there is this type of bug in the memory allocation routine related to NVLink, these errors could occur whether there is one card or multiple cards.
Oh yes ... I should clarify that using three Titan RTX only two are linked via a NVLink bridge, and the third is operating as a acceleration card. I have been talking with nVidia about how they bridge multiple cards (three and higher) in their workstations, servers and DGX; and there is a NVLink bridge for three cards. It's just not commercially available nor supported in non-nVidia workstations.
Yes, each morph files (and UV set and clone shape etc.) needs to be read in with the figure. The main data, the actual chnages in vertex psotion, is not kept in memory unless it's needed (non-zero value) but the fiel has to be read to see how it relates to other properties (cotrnolling or controlled by) so that DS knows when it will be non-zero.
Different versions of Iray, the newest version always uses OptiX Prime on non-RTX cards which has a memory overhead conmpared to when it wasn't used in older versions for one thing.
That's very interesting, because virtually everyone else who has talked about having issues with this stuff (including myself I have a low capacity GTX 1050 card in my laptop which also now likes to spit out memory errors) has experienced the opposite - scenes that rendered fine in 4.11 fallback to CPU in 4.12.
Are they memory allocation errors (ie. failure because of supposively not having enough memory for the scene) or memory access errors (failure of Iray to find/update things already in memory) in your case? Because I have seen both in play on my machines (a GTX 1050 laptop and a Titan RTX based render server build similar to yours) and have seen others report both/either as well. Obviously if Iray is both using more vram across the board in its current implementation and mishandling memory access operations (my Titan RTX has been failing on relatively small scenes pretty consistently throughout all of this due to the latter type - although I just checked with the latext Driver/DS beta avialable and so far no trouble) a relatively high cpacity card like that is still gonna be susceptible to errors.
I find this very interesting because I don't think I have ever seen my Titan RTX report using less VRAM for a scene than my GTX card does for the same scene. Ever.
This is a false assertion. OptiX Prime acceleration has always been perfectly usable on non-high capacity non-RTX cards (I'd been using it defaulted to on with my 2GB GTX 1050 for years before RTX was even announced.) You just have to very carefully manage your scene asset usage for memory consumption.
Here's an example log file (posted earlier in this thread) from someone experiencing one of these memory errors:
Line #5 is OptiX Prime acceleration attempting to start doing its thing. Lines #7-12 are it subsequently failing. Unless you are seeing very different errors from others here (mind posting a log excerpt?) it isn't true that memory errors occur before OptiX Prime acceleration attempts to initialize on appplicable hardware.
Speaking as someone who has dabbled in non-Quadro based DIY dedicated Iray Server system building for years and was a Titan RTX early adopter, DAZ has never been behind any sort of Optix Acceleration alternative to OptiX Prime since they don't develop physically based rendering software.
Again, there have actually been at least two issues going around - one dealing exclusively with OptiX Prime on non-RTX cards. And the other dealing with all cards (from the Titan RTX on down) relating to memory management. And as anyone who's worked in software development knows, simultaneous issues are a nightmare to troubleshoot. Let alone fix.
Sadly I can not render animation with daz studio 4.12.36 and up, Either beta or full public build I have tried them all. So I have reverted back to daz 4.10 in daz 4.12. Iray renders out 3 or 4 frames and then falls back onto my cpu every time. even the smallest of scenes. I can't believe that having 2.- gtx 1080ti with 11.5 gigs each is not enough gpu to run daz. but apparently not when it comes to rendering animation. I am pretty sure it has to do with the fact I am using a GTX gpu instead of RTX gpu's and the opitex prime being enabled is killing my gpu vram. I been reading all over the daz forums this is a common issue and complaint. So I understand it . but as Daz Studio user that uses daz for animation I am sorely disappointed my two 11 gigs GTX 1080 ti's are obsolete to use in daz studio. so unless there is a option to disable Opitex in the next version of daz studio release . I will be stuck with daz 4.10 for animation. Please dress this issue .
is is what my last 3 second animation look like when i tried to render it out
2019-12-05 12:29:53.926 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 2 (GeForce GTX 1080 Ti): Allocated 1.6875 GiB of work space (2048k active samples in 0.163s)
2019-12-05 12:29:53.926 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (GeForce GTX 970 ): Used for display,
2019-12-05 12:29:54.026 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00001 iterations after 0.484s.
2019-12-05 12:29:54.036 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.036 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2019-12-05 12:29:54.056 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00002 iterations after 0.503s.
2019-12-05 12:29:54.056 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.076 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00004 iterations after 0.528s.
2019-12-05 12:29:54.086 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.106 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00008 iterations after 0.552s.
2019-12-05 12:29:54.106 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.136 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00016 iterations after 0.588s.
2019-12-05 12:29:54.146 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.196 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00032 iterations after 0.644s.
2019-12-05 12:29:54.196 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.276 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00061 iterations after 0.729s.
2019-12-05 12:29:54.286 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.386 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00095 iterations after 0.834s.
2019-12-05 12:29:54.386 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.486 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00128 iterations after 0.937s.
2019-12-05 12:29:54.496 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.586 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00161 iterations after 1.034s.
2019-12-05 12:29:54.586 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.776 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00227 iterations after 1.228s.
2019-12-05 12:29:54.786 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:54.976 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00295 iterations after 1.430s.
2019-12-05 12:29:54.986 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:55.176 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00364 iterations after 1.630s.
2019-12-05 12:29:55.186 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:55.376 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00433 iterations after 1.829s.
2019-12-05 12:29:55.386 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:55.586 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00503 iterations after 2.031s.
2019-12-05 12:29:55.586 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:55.786 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00573 iterations after 2.237s.
2019-12-05 12:29:55.796 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:55.986 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00642 iterations after 2.436s.
2019-12-05 12:29:55.986 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:56.196 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00712 iterations after 2.649s.
2019-12-05 12:29:56.206 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:56.386 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00780 iterations after 2.838s.
2019-12-05 12:29:56.396 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:56.586 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00850 iterations after 3.039s.
2019-12-05 12:29:56.596 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:56.796 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00920 iterations after 3.241s.
2019-12-05 12:29:56.796 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:56.996 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00990 iterations after 3.444s.
2019-12-05 12:29:56.996 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:57.196 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01060 iterations after 3.646s.
2019-12-05 12:29:57.196 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:57.406 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01130 iterations after 3.852s.
2019-12-05 12:29:57.406 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:57.606 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01200 iterations after 4.054s.
2019-12-05 12:29:57.606 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:57.806 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01270 iterations after 4.252s.
2019-12-05 12:29:57.806 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:58.006 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01340 iterations after 4.455s.
2019-12-05 12:29:58.006 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:58.206 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01410 iterations after 4.659s.
2019-12-05 12:29:58.216 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:58.406 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01479 iterations after 4.860s.
2019-12-05 12:29:58.416 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:58.616 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01549 iterations after 5.063s.
2019-12-05 12:29:58.616 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:58.816 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01619 iterations after 5.265s.
2019-12-05 12:29:58.816 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:59.016 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01689 iterations after 5.466s.
2019-12-05 12:29:59.026 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:59.226 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01759 iterations after 5.673s.
2019-12-05 12:29:59.226 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:59.416 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01827 iterations after 5.869s.
2019-12-05 12:29:59.426 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:59.626 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01897 iterations after 6.073s.
2019-12-05 12:29:59.626 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:29:59.826 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01967 iterations after 6.275s.
2019-12-05 12:29:59.826 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:00.026 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02037 iterations after 6.479s.
2019-12-05 12:30:00.036 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:00.236 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02107 iterations after 6.681s.
2019-12-05 12:30:00.236 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:00.436 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02177 iterations after 6.881s.
2019-12-05 12:30:00.436 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:00.636 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02247 iterations after 7.089s.
2019-12-05 12:30:00.646 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:00.836 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02316 iterations after 7.288s.
2019-12-05 12:30:00.846 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:01.036 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02384 iterations after 7.482s.
2019-12-05 12:30:01.036 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:01.236 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02455 iterations after 7.687s.
2019-12-05 12:30:01.236 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:01.446 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02525 iterations after 7.899s.
2019-12-05 12:30:01.456 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:01.636 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02593 iterations after 8.090s.
2019-12-05 12:30:01.646 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:01.846 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02663 iterations after 8.296s.
2019-12-05 12:30:01.846 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:02.046 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02732 iterations after 8.495s.
2019-12-05 12:30:02.046 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:02.246 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02802 iterations after 8.697s.
2019-12-05 12:30:02.256 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:02.446 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02872 iterations after 8.899s.
2019-12-05 12:30:02.456 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:02.656 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 02942 iterations after 9.102s.
2019-12-05 12:30:02.656 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:02.856 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 03012 iterations after 9.304s.
2019-12-05 12:30:02.856 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:03.056 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 03082 iterations after 9.511s.
2019-12-05 12:30:03.066 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:03.256 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 03150 iterations after 9.708s.
2019-12-05 12:30:03.266 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:03.466 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 03220 iterations after 9.914s.
2019-12-05 12:30:03.466 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
2019-12-05 12:30:03.666 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 03290 iterations after 10.115s.
2019-12-05 12:30:03.666 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported.
Wait for bug fixes. I've had even a top of the line Titan RTX die repeatedly due to memory allocation errors while attempting to render trivial animation sequences on recent DS/Nvidia driver versions. You can always tell there's a lot of "stuff" (aka ongoing attempts to fix bugs) going on on the development side when software updates are fast and heavy, and both Daz and Nvidia have been quite busy lately.
it doesn't help when temporary solutions cannot be discussed
There's something odd though. In my system 4.12.0.86 works fine for animation and I have one 1060. Full specs in the signature. At this point I'm inclined to suspect it's the double card that gives issues to the drivers. You may try removing one card and see if this works fine. If that's the case it's not a solution of course but may help others as well.
Well in my old laptop I did have issues with the frame buffer but it was DS 4.9 so it's not the same iray version as 4.12. Thank you for the info it's very interesting that iray supports out of core frame buffers. I'll do a simple test and let you know the result. In any case my point was that cycles is designed to be independent from the final resolution as far as vram is concerned. While you say optix prime is not thus iray is not.
https://www.daz3d.com/forums/discussion/157401/iray-failed-to-allocate-device-frame-buffer-solved
Whilst earlier reporting that I was not experiancing CPU fallback
I have been away from DAZ since then, only to return yesterday, and discover I too was now experiancing the problem
nothing changed, the PC hasn't even been powered on since that comment, so go figure
With so many people suffering from these CPU fallback problems WTF hasn't DAZ already provided a facility to rollback both the Pro and beta to versions where this was not a problem
instead they would rather that we all suffer until they find a solution
which may be soon, but most likely will be later, either way they are not coming forward and keeping us users informed about where they stand in the solution
we get total silence, as if the problem does not exist
Whilst DAZ for me is a hobby, I have great sympathies for people relying on DAZ for their income, they must be tearing their hair out right now
Thanks for the suggestion, I unmounted the second 1080ti but it didn't work. i didn't save a copy of daz 11 so I can't try that version. I have 2 gtx 1080ti's ina external drive box. and 1 gtx 970 to drive my 2 monitors which has nothing to do with rendering or daz.
Just running on just one gpu was the same & I am using the same test scene with just Isle g8 character and a 4k hdri i can render it straight out as a still render but trying to render more that 4 or 5 frames my gpu ram becomes maxed out and it falls back to my cpu . like i had mention I don't appear to have this issue with the daz 4.10. Just versions of daz 4.12.36 & up & i was dumb and did not save the 4.11 installer. which i should have and usually do .. am I the only GTX card user having this problem with fall back?
I did warn you
before you updated in another thread
contact customer support
Then I did a little test just to compare cycles vs iray for high resolution renderings. The scene only has a sphere and a plane with no textures, then I render it at 10K resolution that's 10,000 by 10,000 pixels. This way the scene itself takes almost nothing, while we will have the working buffers and fame buffer allocated. Below there's the task manager, first iray then cycles, where windows itself takes about 2gb ram. What's interesting is that iray takes about 8gb ram and 4gb vram to render a simple sphere. While cycles takes about 2gb ram for the frame buffer and almost no vram as expected.
You may want to use CPU-Z instead of Task Manager, as the latter isn't very reliable.
My evga gpu's comes with precision x monitor system. with its own gpu, over clocking & monitoring software i can manage everything in my system from the one control panel. I can click the top tab for each gpu or cpu mounted for specs running and management of them . plus is give me my cpu system spec running as wells as conflicts with a log file that records everything going on. I found this more intuitive than cpu &gpu z
this is a screen shot of it .. though i don't have anything under load if you need ia log file of my issues I can save it and post it
this is my system specs, they are older but still top notch
yes you did and i was dumb wasn't i?
too trusting
Could you provide a link to where Blender's developers themselves make that sort of claim? Because based on some (admittedly) quick searching around, I can't find any mention of such a thing. If anything, the official documentation appears to indicate the exact opposite. Do a word search here for "BHV". BVH in this context refers to the memory-hogging step 1 of 2 that makes up the raytracing (technically pathtracing) process. The overall size of a scene's pathtracing BVH is going to be intrinsically tied to final resolution (since a larger field of distinct pixel points is going to neccessitate a more detailed/complex BVH to describe the scene objects behind it.) And that isn't something that tile vs. full-frame progressive rendering has any effect on since all tiles need access to all parts of a scenes BVH (otherwise the final image would be subject to screen space reflection type visual anomalies.)
The thing is, you are severely oversimplifying the difference between Cycles and Iray both in terms of what they are capable of achieving visually as unbiased renderers (Iray is a much more powerful piece of software - see this document for the juicy technical details) and the system resources required to accomplish those things.
For example - load balancing. One of the main reasons why Iray seems to be such a memory hog is because it purposefully duplicates all working data (with the exception of output framebuffers) to each and every render-capable CPU/GPU (with the exception of NVLinked GPUs on Linux systems) linked together for rendering a specific job. So that if one of those devices fail, the rest can carry on rendering the scene to completion without having to start over. As far as I can tell, Cycles has no such capability.
@RayDant I'm not going to start a cycles vs iray war here. But honestly any test I can do shows me that iray is a resource hogger compared to cycles. Also the denoiser in cycles is by far better since it requires very few iterations to produce good results, and that's the most important feature for animation. Not to mention the classic iray flaws that anyone can find around here in the forum. First of all the character eyes having issues far from the scene center, that simply means iray is not production ready at all.
Then I do appreciate the links you post and your opinions and I find them very interesting. Thank you.
Because many of the changes that may be contributing to these issues would require DAZ to stop updating to newer versions of Iray and the changes that are being made to it, most likely.
Right now we have people who didn't upgrade from 4.11, those who are using 4.11 for some renders and a 4.12 beta for others, some who took the plunge and upgraded so have a 4.12 General Release and still others who have both the 4.12 GR and one of the beta versions. Add in to that confusion the fact that there have been several NVidia driver updates since 4.12 hit the scene and some users with GTX cards and others with RTX ... I mean, it is a nightmare.
Yup.
12 GB Titan X and Titan Xp Pascal cards. (Win 10, i7-8700K. 64GB). Consistent problems with fallback to CPU using 4.12 GR and betas. Nvidia drivers 430.86, 431.86, 441.08 and 441.28 - no change. Very frustrating. Only solution was to revert back to DS 4.11.