I get the following error when trying to change the hair color for "Untamed Long Hair for Genesis 9, 8.1 and 8" [ https://www.daz3d.com/untamed-long-hair-for-genesis-9-81-and-8 ]  ... An Error occurred while reading the file. See the log file for more details ... and this is what is in the error file ...

2025-11-03 11:37:02.550 [INFO] :: Prepare asset load (merge): /People/Genesis 8 Male/Hair/Daz Originals/Untamed Long Hair/Materials/ULH Melanin 0.2.duf
2025-11-03 11:37:02.550 [INFO] :: Locking viewport redraw...
2025-11-03 11:37:02.550 [INFO] :: Viewport redraw locked.
2025-11-03 11:37:02.670 [VERBOSE] :: Native format content directories: 8
2025-11-03 11:37:02.670 [VERBOSE] :: Poser format content directories: 3
2025-11-03 11:37:02.670 [VERBOSE] :: Other import format content directories: 0
2025-11-03 11:37:02.670 [INFO] :: Begin asset load (merge): /People/Genesis 8 Male/Hair/Daz Originals/Untamed Long Hair/Materials/ULH Melanin 0.2.duf
2025-11-03 11:37:02.690 [INFO] :: Determining missing assets...
2025-11-03 11:37:02.936 [WARNING] :: Invalid hierarchy for selected node(s) and "preset_hierarchical_material" type; no root(s) found.
2025-11-03 11:37:02.936 [WARNING] :: Error loading asset: E:/DAZ/Public Documents/My DAZ 3D Library/People/Genesis 8 Male/Hair/Daz Originals/Untamed Long Hair/Materials/ULH Melanin 0.2.duf
    Operation failed
2025-11-03 11:37:03.337 [INFO] :: Unlocking viewport redraw...
2025-11-03 11:37:03.337 [INFO] :: Viewport redraw unlocked.

... I tried re-installing it via DIM and manually and I still continue to get this error. I don't have any problems with changing hair color of other hair packages.

EDITED TO ADD : This product also does not appear in the "products" section even though I installed it via DIM

Great renders everyone!! It's fascinating how good everyone is these days.

I have been working now for a few months on a new-ish idea for volumetrics.

Below two renders. I took a scene from a few years ago featuring a fantastic Bryce model made by Dave Savage. The original, posted to my gallery, was even more overexposed than I realized. anyhow, I tweaked the brightness for this compariosn. This render is ideal for this cloudy study for obvious reasons, but also becasue the horizon is exposed. On the right is a new render. A few minor lighting tweaks...still want a slightly overexposed look. The main difference is the clouds.

Bryce volume slabs have always had a horizon problem in my view, gathering too much at the horizon and never accounting for planetary curvature. The version on the right doesnt curve either, and for that reason it does eventually end. Still this seems more natural to me than everlasting clouds into oblivion.

But I could be wrong.

Bryce cannot import nor export Open VDB files. I've always wanted to bring volume simulations from other apps into Bryce, so in this case I've taken a few months to find a way to model cloud planes with real geometry in Blender, and bring them into Bryce. I ensured that the bases were soft and flat, and the tops were crisp and dynamic in a way not really feasible with slabs in my experience.

Needless to say the polygon statistics are insane, but I've planned carefully.

So my questions are:

1. Do the clouds in the second version look more "natural" than the clouds I accomplished with the regular volume slab? What drawbacks do you observe visually that make one or the other more convincing to you?

2. If these cloud models were made available to the public, would anyone use them?

Generally speaking, they would only be appropriate for intermediate to advanced users. The meshes also are typically just under 2 million triangles per mesh, occupying about 470mb of scene ram each. To accomplish the view we see here, I used two unique cloud planes, instanced them into a grid of 9 plates, and then a third mesh is needed that fills in the distant areas closer to the horizon. There are just as many clouds out of view as there are visible. The three meshes together occupy some 1.5GB of scene ram, and with instancing of the meshes, the scene holds roughly 29 million triangles. With LAA, I still have about 2GB of available space before running out of memory, so still plenty of room for more stuff..trees. grass, etc if I desired.

Feedback is greatly appreciated. Thanks for your time.

@TheMysteryIsThePoint
So, I’d like to share my impressions of working with Sagan.
First of all, I want to thank you once again for such a useful tool. Now that it’s possible to work with Daz hairstyles through the new Hair Geometry Nodes in Blender, it opens up some really cool possibilities for fine-tuning and customization — all without having to do any grooming. 
So far, I’ve only tested the plugin in Blender. I’m not yet sure how it can be used together with MD, but I’ll be looking into it.
1. Working with classic Alembic seq (without hair curves)
Everything works great here — it bakes without issues, and with proper tessellation imo the hair looks identical to the Daz render. That’s perfect if you don’t want to mess with nodes and just bake the simulation directly in Daz, then import it into Blender.
2. Working with hair curves
This one is definitely a game changer for me. It takes some practice to understand how the node system works, but the flexibility is impressive. At first, I used the .blend file shared by @TheMysteryIsThePoint and extracted everything I needed from it, but later I refined the setup a bit — added fuzz and other details.

Thank you — it’s an amazing tool. I’ll keep actively participating in this thread, so feel free to share your thoughts as well.
And apologies if my review seems a bit “surface-level” — I’m not great with technical stuff, so this is more about general impressions. I might add more details later.

P.S. Haven’t encountered any bugs so far :)
Here is few quick tests with hair curves + sim:
https://youtube.com/shorts/3-Rg2OZyawo
https://youtube.com/shorts/vjvTFr47NnA

My external drive (D) comes under New Content Set 2 and has CMC cluster box ticked, and other import formats box ticked.

Richard Haseltine said:

wsterdan said:

wsterdan said:

Richard Haseltine said:

wsterdan said:

Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.

2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder  to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file. 

I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?

I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.

Thanks Richard; I can't seem to access the logs at the moment, but I thought I saw reference to the Mac camera last night and I'm not sure what the computer's camera would be used for other than for some sort of facial or lip sync. I'll try again later to confirm that it wasn't my (almost always) overblown imagination. 

 

Found it:
"Added camera usage description on macOS"

So, if not facial or lip sync, what might this be pertinent to?

I beleive that they come as a pair, I don't hav a Mac but presumably at some point you get a permissions pop-up and I beleive that is where the usage description will come in - which may well say that this is just ancillary to the Microphone.

Thanks. That could be it. No worries, I'm not getting my hopes up. I'm just glad I'm able to import video again in the latest Alpha. 

wsterdan said:

wsterdan said:

Richard Haseltine said:

wsterdan said:

Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.

2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder  to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file. 

I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?

I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.

Thanks Richard; I can't seem to access the logs at the moment, but I thought I saw reference to the Mac camera last night and I'm not sure what the computer's camera would be used for other than for some sort of facial or lip sync. I'll try again later to confirm that it wasn't my (almost always) overblown imagination. 

 

Found it:
"Added camera usage description on macOS"

So, if not facial or lip sync, what might this be pertinent to?

I beleive that they come as a pair, I don't hav a Mac but presumably at some point you get a permissions pop-up and I beleive that is where the usage description will come in - which may well say that this is just ancillary to the Microphone.

wsterdan said:

Richard Haseltine said:

wsterdan said:

Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.

2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder  to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file. 

I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?

I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.

Thanks Richard; I can't seem to access the logs at the moment, but I thought I saw reference to the Mac camera last night and I'm not sure what the computer's camera would be used for other than for some sort of facial or lip sync. I'll try again later to confirm that it wasn't my (almost always) overblown imagination. 

 

Found it:
"Added camera usage description on macOS"

So, if not facial or lip sync, what might this be pertinent to?

Richard Haseltine said:

wsterdan said:

Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.

2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder  to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file. 

I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?

I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.

Thanks Richard; I can't seem to access the logs at the moment, but I thought I saw reference to the Mac camera last night and I'm not sure what the computer's camera would be used for other than for some sort of facial or lip sync. I'll try again later to confirm that it wasn't my (almost always) overblown imagination. 

Keysha is a Premier exclusive shape for Kayla 9 - you must let daz Studio log in to your account and update its metadata, then it will appear in the install pane or the All or Available install state filters of the products tab of Smart Content (probably near the end if you sort by purchase date).

wsterdan said:

Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.

2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder  to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file. 

I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?

I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.

As Richard explains, the DAZ EULA doesn't allow to transfer assets among users, so all the developers working on the same project must purchase the same assets set to own the personal licences, then you can share the scenes.

About converting DAZ assets for Unreal or any other game engine, as others noted there's a lot of work to do to by hand to optimize the meshes and the materials, plus you have to purchase the interactive licenses apart for game development, for each single item you use unless there's bundles. The main tools DAZ Studio provides to optimize a figure are the texture atlas, included in daz studio, which will merge textures into a single one, and the decimator plugin, that you can purchase apart.

https://www.daz3d.com/decimator-for-daz-studio

As an alternative you can import in blender then use the blender tools to optimize and export. Another issue worth noting, is that jcms don't work in a game engine, as dual quaternion can't be supported for performances sake, that means you lose the figure deformations unless you animate in blender then export the fbx with baked jcms.

p.s. For the EULA, may be you can work around it if you connect to your client workstation, this way DAZ Studio and its asset library is installed in a single workstation shared among users. The owner of the licenses is the owner of the workstation, while the other users act as "consultants" payed for their work for the owner. Not sure this can work though you better ask DAZ.

Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.

2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder  to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file. 

I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?

Iray 2025.0.0 beta, build 387700.770

Known Issues and Restrictions

• Iray Interactive (IRT) is now considered deprecated. While we may not delete it directly in the next major revision, only extremely critical bugfixes may still be done.
• The minimum NVIDIA driver branch version in order to support the new CUDA toolkit is R575 (Windows 576.57).

Added and Changed Features

• General
  • Updated general libraries:
    • OpenImageIO 3.0.8.1 (includes libPNG 1.6.50 and OpenEXR 3.3.4)
    • CUDAToolkit 12.9 Update 1
    • Boost 1.88.0
    • Embree 4.3.3
    • OpenSSL 3.5.0
  • The hash map implementation from robin_hood has been replaced by its successor project unordered_dense. The latter supports heterogeneous lookups used for performance improvements.
  • A rare race condition related to names of DB elements marked for removal has been fixed. The corresponding section with the heading "Re-use of names of DB elements eligible for GC" onIDatabase has been removed from the API reference documentation.
  • Improved performance when accessing DB elements by name.
• Iray Photoreal & Iray Interactive
  • From now on, future GPU generations (at the point of writing: e.g. Rubin based GPUs) will automatically work without having to update the Iray SDK. This comes at the price of a one-time cost when first launching Iray GPU code (longer delay, plus memory peak), plus potentially less efficient execution (compared to specialized code).
  • Added support for crack-free displacement (between different subregions of the same object), introducing two new object attributes: crackfree_displacement which allows duplicate/similar points in a mesh to be detected and displaced to the same positions, by averaging their displacement values (and normals), and crackfree_displacement_point_tolerance which controls an epsilon by which points are considered equal, when detecting these duplicate points (the default value will usually work well in general though).
• Iray Photoreal
  • Auto instancing mode can now be configured to more aggressively optimize for scene size. The existing iray_rt_low_memory option (which previously had no effect on Turing+ GPUs) now also affects auto instancing decisions. If enabled, instancing will be performed if there is any memory saving at all, not only if the savings correspond to a significant fraction of the overall scene size.
  • Added a render context option memory_limit which allows setting a limit for any (possibly remote) CUDA device for the amount of memory that may be used for rendering workspace on that device.
  • Added a transform parameter to volume blackbody emission.
• Material Definition Language (MDL)
  • The new context option "filename_hints" provides more flexibility when exporting nameless resources. See documentation on IMdl_execution_context for details.
  • Added "export_requested_functions" HLSL backend option allowing to export generated functions in DXIL libraries.
  • Improved HLSL code generation resulting in less PHI variables.
  • Implemented version promotion for default arguments: As default arguments are hidden to the user, they are now not only auto imported, but also version promoted. Especially entities that uses deprecated functions in its default arguments are not filtered out anymore, if they can be promoted.
  • Improved generated debug information by the core compiler, especially fill in debug line information in several corner cases which were not available before.
  • API change: built-in module have now there absolute module name stored as their file name. This allows to have better debug information for code originated from the built-in modules, especially for code from the base module.
  • Introduced epsilon for the constant detection in the CPU baker.
  • Increased epsilon for the constant detection in the GPU baker.

Fixed Bugs

• General
  • Slightly reduced memory requirements for some postprocessing pipelines.
• Iray Photoreal & Iray Interactive
  • Fixed potential illegal memory accesses on sm9.X (Hopper) and sm10.X (Blackwell) class GPUs.
  • Fixed texture/environment baking on SM versions greater or equal 10.0 (all Blackwells).
• Iray Photoreal
  • Fixed regression introduced in 2024.1.4: If instancing_shift_camera and instancing are enabled in scenes that feature decals, and certain scene options were then toggled (e.g. spectral rendering) along with camera movement, then the decal placements could have been offset.
  • Handle switching from local- to cluster-rendering properly, was an issue if e.g. a cluster was only populated after local rendering had already started (nvbugs 5391882).
  • Fixed various issues with failing network hosts (e.g. during processing of longer batches of rendering work).
• Material Definition Language (MDL)
  • Fixed several auto-import problems, for instance caused by default arguments of struct elemental constructor. As a consequence, it is now always an "internal error" if the compiler was not able to do the auto-import, not only an assertion in debug builds.
  • Fixed declarative property of struct constructors, the declarative property of struct constructors must be inherited from the struct type definition.
  • Added missing decl_cast calls related to the use of default arguments.
• MI Exporter
  • Export HDR textures with alpha channel to tif rather than exr to retain alpha channel.

Well, I'm glad it's here. I wasn't paying the significant monthly increase in Photoshop. It just could not be justified. I tried Paint Shop Pro as I had it many years ago, but after several weeks I finally uninstalled. I just couldn't stand it. I was always lost. Affinity is as close as I'm going to get to a Photoshop likeness and I've already been playing around with it. I wish it had smart layers options unless I'm missing this feature. Scratch that, it has Live Filters which is pretty close to the Smart Object feature in Photoshop. So far I was not able to import any PSD file with smart layers and keep those layers intact. I need to play with it more and get used to the options, tools, etc, but so far it does almost everything I need it to do. Lordy, it's so much faster than Photoshop and doesn't have a dozen or more tasks running in the background. 

And as hjake has noted, you do not need to be connected. I don't know what I did. Maybe it was denying data sharing during the setup process, but I've tested it and it works as expected. I don't sign out, I simply close the program as I would any other.

I made a post earlier but we didn't reach any solution so I try another go with more information. 
Out of the blue a few weeks ago Daz "crashes" for me. Its not a blue screen crash because things in the background are still going. E.g if I'm listenting to a Youtube podcast I can still hear it going on and light is still being emitted from the PC and my peripherals. It just turns off the monitors. Only way to fix it is by doing a hard-reset on the PC. I've seen some similar threads were people say its a VRAM issue. Yet why would this happen to me out of the blue? Sure I only got 10gb of VRAM but that has always been enough and these aren't resource intensive scenes we are talking about. I've even done close-up 6 charachter renders before and it have worked fine. It can even occur during me playing around in Filament. I've been using Daz3D for a couple of years now, so I don't really get why this issue have popped up. I can't really troubleshoot the issue cause the screen turns black so I can't tell if Daz is giving me an error message or not. This issue is Daz exclusive. Meaning it doesn't happen to me when I render in Blender. I'm thinking its software based yet the only thing that's new is me downloading assets and updating Daz3D. But it happening out of the blue makes me think it must be something related to that but I don't know and I don't want to give up on my main 3D software. I read some other post about people saying that XTransfer plugins or OOT hair assets causes crashes, I have both of them.
Specs:
AMD Ryzen 5600X 6-Core Processor, 4200mhz
Corsair 16GB (2x8GB) DDR4 3600MHz CL18 Vengeance
ASUS GeForce RTX 3080 10GB TUF GAMING OC
PSU produce 900W, maybe a bit low for this spec but it has never been an issue in the past.
What I have done: 
Updated to the latest version of Daz3D
Did a fresh install of the latest Nvidia driver with DDU
Benchmarked and troubleshoot both CPU & RAM (which are stable at 50c)
Cleaned the PC
Checked temps during load and they are about 70-80 at their most intense
Here is a example log: 

2025-10-20 17:03:20.254 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 194 textures, 0 lambdas (0 unique)

2025-10-20 17:03:20.255 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Emitter geometry import (1 light source with 2 triangles, 1 instance) took 5.900 us

2025-10-20 17:03:20.255 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating compiled material code.

2025-10-20 17:03:20.255 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating material textures.

2025-10-20 17:03:20.258 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating BSDFs.

2025-10-20 17:03:20.258 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating volumes.

2025-10-20 17:03:20.258 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.

2025-10-20 17:03:20.258 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.

2025-10-20 17:03:20.258 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.

2025-10-20 17:03:20.260 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.

2025-10-20 17:03:20.260 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer

2025-10-20 17:03:20.262 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using interactive scheduling, caustic sampler disabled

2025-10-20 17:03:20.263 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):

2025-10-20 17:03:20.263 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3080)

2025-10-20 17:03:20.263 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

2025-10-20 17:03:20.263 Iray [INFO] - IRAY:RENDER ::   1.14  IRAY   rend progr: CUDA device 0 (NVIDIA GeForce RTX 3080): Processing scene...

2025-10-20 17:03:20.302 Iray [INFO] - IRAY:RENDER ::   1.15  IRAY   rend info : Importing lights for motion time 0

2025-10-20 17:03:20.302 Iray [INFO] - IRAY:RENDER ::   1.15  IRAY   rend info : Initializing light hierarchy.

2025-10-20 17:03:20.302 Iray [INFO] - IRAY:RENDER ::   1.15  IRAY   rend info : Light hierarchy initialization took 493.200 us

2025-10-20 17:03:20.305 Iray [INFO] - IRAY:RENDER ::   1.14  IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3080): Scene processed in 0.042s

2025-10-20 17:03:20.306 Iray [INFO] - IRAY:RENDER ::   1.15  IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3080): Allocated 11.616 MiB for frame buffer

2025-10-20 17:03:20.307 Iray [INFO] - IRAY:RENDER ::   1.14  IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3080): Allocated 2.094 GiB of work space (2048k active samples in 0.000s)

2025-10-20 17:03:20.307 Iray [INFO] - IRAY:RENDER ::   1.14  IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3080): Optimizing for cooperative usage (performance could be sacrificed)

2025-10-20 17:03:20.329 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00001 iteration after 62.666 ms.

2025-10-20 17:03:20.330 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

2025-10-20 17:03:20.374 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00002 iterations after 102.712 ms.

2025-10-20 17:03:20.375 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

2025-10-20 17:03:20.418 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00003 iterations after 142.999 ms.

2025-10-20 17:03:20.419 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

2025-10-20 17:03:20.462 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00004 iterations after 182.830 ms.

2025-10-20 17:03:20.464 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

2025-10-20 17:03:20.507 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00005 iterations after 226.756 ms.

2025-10-20 17:03:20.550 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00006 iterations after 268.478 ms.

2025-10-20 17:03:20.592 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00007 iterations after 309.906 ms.

2025-10-20 17:03:20.634 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00008 iterations after 352.121 ms.

2025-10-20 17:03:20.675 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00009 iterations after 393.723 ms.

2025-10-20 17:03:20.717 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00010 iterations after 435.476 ms.

2025-10-20 17:03:20.759 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00011 iterations after 477.231 ms.

2025-10-20 17:03:20.801 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00012 iterations after 519.387 ms.

2025-10-20 17:03:20.857 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00014 iterations after 575.434 ms.

2025-10-20 17:03:20.925 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00017 iterations after 643.529 ms.

2025-10-20 17:03:21.006 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00021 iterations after 725.229 ms.

2025-10-20 17:03:21.101 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00026 iterations after 819.348 ms.

2025-10-20 17:03:21.194 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00031 iterations after 912.875 ms.

2025-10-20 17:03:21.287 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00036 iterations after 1.006 s.

2025-10-20 17:03:21.382 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00041 iterations after 1.101 s.

2025-10-20 17:03:21.539 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00051 iterations after 1.259 s.

2025-10-20 17:03:21.724 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00063 iterations after 1.442 s.

2025-10-20 17:03:21.919 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00076 iterations after 1.638 s.

2025-10-20 17:03:22.117 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00089 iterations after 1.836 s.

2025-10-20 17:03:22.311 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00102 iterations after 2.030 s.

2025-10-20 17:03:22.506 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00115 iterations after 2.225 s.

2025-10-20 17:03:22.701 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00128 iterations after 2.421 s.

2025-10-20 17:03:22.898 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00141 iterations after 2.616 s.

2025-10-20 17:03:23.093 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00154 iterations after 2.812 s.

2025-10-20 17:03:23.288 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00167 iterations after 3.007 s.

2025-10-20 17:03:23.483 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00180 iterations after 3.202 s.

2025-10-20 17:03:23.679 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00193 iterations after 3.398 s.

2025-10-20 17:03:23.875 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00206 iterations after 3.593 s.

2025-10-20 17:03:24.071 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00219 iterations after 3.789 s.

2025-10-20 17:03:24.266 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00232 iterations after 3.985 s.

2025-10-20 17:03:24.461 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00245 iterations after 4.180 s.

2025-10-20 17:03:24.656 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00258 iterations after 4.376 s.

2025-10-20 17:03:24.874 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00271 iterations after 4.593 s.

2025-10-20 17:03:25.084 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00283 iterations after 4.802 s.

2025-10-20 17:03:25.258 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00294 iterations after 4.976 s.

2025-10-20 17:03:25.445 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00306 iterations after 5.164 s.

2025-10-20 17:03:25.634 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00318 iterations after 5.353 s.

2025-10-20 17:03:25.820 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00330 iterations after 5.539 s.

2025-10-20 17:03:26.017 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00343 iterations after 5.736 s.

2025-10-20 17:03:26.218 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00356 iterations after 5.937 s.

2025-10-20 17:03:26.420 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00369 iterations after 6.139 s.

2025-10-20 17:03:26.621 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00382 iterations after 6.340 s.

2025-10-20 17:03:26.815 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00395 iterations after 6.533 s.

2025-10-20 17:03:27.012 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00408 iterations after 6.730 s.

2025-10-20 17:03:27.207 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00421 iterations after 6.926 s.

2025-10-20 17:03:27.404 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00434 iterations after 7.123 s.

2025-10-20 17:03:27.606 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00447 iterations after 7.325 s.

2025-10-20 17:03:27.812 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00460 iterations after 7.531 s.

2025-10-20 17:03:27.997 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00472 iterations after 7.716 s.

2025-10-20 17:03:28.193 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00485 iterations after 7.912 s.

2025-10-20 17:03:28.393 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00498 iterations after 8.111 s.

2025-10-20 17:03:28.597 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00511 iterations after 8.316 s.

2025-10-20 17:03:28.786 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00523 iterations after 8.505 s.

2025-10-20 17:03:28.973 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00535 iterations after 8.692 s.

2025-10-20 17:03:29.159 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00547 iterations after 8.878 s.

2025-10-20 17:03:29.356 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00560 iterations after 9.074 s.

2025-10-20 17:03:29.553 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00573 iterations after 9.272 s.

2025-10-20 17:03:29.751 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00586 iterations after 9.469 s.

2025-10-20 17:03:29.948 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00599 iterations after 9.666 s.

2025-10-20 17:03:30.145 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00612 iterations after 9.864 s.

2025-10-20 17:03:30.348 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00625 iterations after 10.067 s.

2025-10-20 17:03:30.717 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00651 iterations after 10.435 s.

2025-10-20 17:03:31.418 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00703 iterations after 11.137 s.

2025-10-20 17:03:32.514 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00785 iterations after 12.233 s.

2025-10-20 17:03:33.760 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00876 iterations after 13.479 s.

2025-10-20 17:03:35.072 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00974 iterations after 14.790 s.

2025-10-20 17:03:36.543 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01084 iterations after 16.261 s.

2025-10-20 17:03:38.172 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01205 iterations after 17.891 s.

2025-10-20 17:03:39.937 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 01337 iterations after 19.656 s.

2025-10-20 17:04:02.889 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.32  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3080): Kernel [13] (MaterialSurface   ) failed after 21.400s

2025-10-20 17:04:02.890 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.32  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3080): unknown error (while launching CUDA renderer in <internal>:904)

2025-10-20 17:04:02.890 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.32  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3080): Failed to launch renderer

2025-10-20 17:04:02.890 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3080): Device failed while rendering

2025-10-20 17:04:02.890 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [WARNING] - IRAY:RENDER ::   1.14  IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 3080) is no longer available for rendering.
Any type of help would be appreciated. Thanks in advance!

Jan_Scrapper said:

I was not going to join in on this sale, however you have made me think twice.  It seems that everything in the scene is included WITH a curved backdrop.  So, I don't think the angles are limiting!  I am going to have to pick up a couple!

Jan_Scrapper,

I took advantage of the sale but didn't buy any of the vignettes. Based on the product image I see that the enclosing curved geometry is used for atmospherics. The backdrop is largely flat, limiting as the OP pointed out. 

Write Idea,

Depending on your needs, an idea is to model the landscape background yourself. Here's a recent discussion about terrain modeling and rendering software (i.e. basic Terragen is free). A few people pointed out that EON Softwares VUE and Plantfactory are now free from Bentley. I haven't used them, but it appears you can export models to OBJ and import those into Daz. Alternately, there's Flowscape, which I used a few years back and isn't too expensive. Blender has a bunch of addons too.

Cheers!

FIXED !!!  Just that unchecked UV import box was driving my nuts....

Richard Haseltine said:

You need Read UV Coordinates checked on the Import options.

AHHHHH !!!  That's a face palm moment.  Thank you so much.  

You need Read UV Coordinates checked on the Import options.

Those attachments are still on their original post, it is images showing the options used for export and import that we wish to see.