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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
I wonder if the failure to apply Render Settings Presets has to do with switching render engines back and forth between Filament and Iray.
Most likely you are correct. I did some filament rendering as well. Then I just had some tests by switching back 'n forth, Environment is back. But I still think it's a bug.
I haven't figured out a repeatable scenario to recreate the problem, either, but it has happened to me twice in the last couple days.
I feel all the animation tools are left terribly behind... I don't see a single fix on those tools or any related function.
It's easy to reproduce the issue on my side.
1) Clear the scene. Now Engine in Render Settings pane is Nvidia Iray. Load a Render Settings Preset. No Environment path appears in Render Settings pane.
2) Switch Engine to Viewport then switch it back to Nvidia Iray, Environement path appears ~~
I'm afraid you're right ~~ my friend. I'm sorry that usually we have no other option but just wait ~~
Enabling the Iray DrawStyle adds an enviornment settings node, the empty scene won't have one until that or a render are done. No settings node should tie the proeprties to their default values so I am surprised it wasn't an issue before.
Custom actions are about the only bit of DS that uses absolute paths even if the files are in a content directory, check the Custom entries in Window>Workspace>Customise to see if there are any orphans.
Nope... applying a Render Settings Preset has nothing to do with enabling Iray Drawstyle. In DS 4.22, after applying a Render Settings Preset, Tone Mapper and Environment Options nodes are placed into Scene pane, and Environment path appears in Render Settings pane.
In DS 4.23, Environment path doesn't appear in Render Settings pane... even if switching to Iray Drawstyle. The only way to show Environment path by now is to swith options in Engine dropdown list.
How do I check for orphans?
What I meant is the Environment section in Render Settings pane. It's officially named as Path (or Group...), isn't it ? (in ss1) Again, in DS 4.22, after loading a Render Settings preset, I get the result in ss2. In DS 4.23, I get the result in ss3 ~~
Open Customactions.dsx by Notepad++, search by the GUID, you can find the path of script, then check if the script file physically locates there?
I understand now. Thanks for the illustrations!
When I looked in that file yesterday, the file path for the suspect GUIDs was "", so it gave me no clue. I didn't know how to find out what those GUIDs were supposed to represent, so I just deleted those entries. I don't know how I got custom actions with null file paths. I wonder if it had anything to do with Update and Merge Menus?
@crosswind I removed my startup scene file from DS 4.23.1.20 for testing.
What does this have to do with the inability to get applied presets to work? I am still unable to reproduce that on command, but it does still happen to me at times. I also get into situations where the HDRI applied by an Iray render preset does not change the HDRI in the Filament viewport. Sometimes it changes; other times it does not. I have wasted hours and hours trying to understand what causes these issues, and I cannot come to a conclusion. I still don't have enough data to submit a useful help request at this point.
Probably... I never did Update and Merge Menus before so not sure if it would remove somthing in Customactions.dsx. Usually if I lost something in F3 with invalid GUID / action path of whatever, I just removed the items then save the layout.
Same on my side (since 4.15 or 4.16... ?) but this behavior shouldn't have had anytying to do with Loading a Renderings Preset. Why did one have to switch to NVIDIA Iray drawstyle in 4.23 before loading a Renderings Preset ? It works all well in DS 4.22.
However, the most interesting thing is that I cannot reproduce the issue now !! I really don't know why, haha ~ !
Also same on my side... With 3DL engine, the same thing will happen... because those paths / groups are hidden in Viewport / 3DL engine. The moment you switch back to NVIDIA Iray, you'll see them there.
I'll do more tests then...