Usually, it does and I still think it must be something somewhere in my settings but I wouldn't even know where to begin to look. I'm happy I got it working and it looks fabulous! And thank you lol!
So, I'm a bit confused.. there are mentions of a scene, yet all I see are 5 render settings, 3 props (the your object here, the volumetric light cube, and the ripple), and 1 iray mat?
And none of the render settings have that sandy ground from the promos, no matter what I try to do with the camera. Is that a prop not mentioned in the "other products used" section?
Here's what I see with the sample camera, placing a sphere at 0,0,0 (attached).
Changing the dome mode to finite sphere w/ ground, infinite sphere w/ground, or box w/ground basically produces the same effect (except the shadow is a bit different perhaps).
...am I missing something? o.0?
I'm using DAZ 4.9.4.117 on Win 10, in case that clears something up...
So, I'm a bit confused.. there are mentions of a scene, yet all I see are 5 render settings, 3 props (the your object here, the volumetric light cube, and the ripple), and 1 iray mat?
And none of the render settings have that sandy ground from the promos, no matter what I try to do with the camera. Is that a prop not mentioned in the "other products used" section?
Here's what I see with the sample camera, placing a sphere at 0,0,0 (attached).
Changing the dome mode to finite sphere w/ ground, infinite sphere w/ground, or box w/ground basically produces the same effect (except the shadow is a bit different perhaps).
...am I missing something? o.0?
I'm using DAZ 4.9.4.117 on Win 10, in case that clears something up...
Thanks!
@Dolbomir I am looking over the released package and it appears that you are correct. There are no scene files but only Render settting files (plus the props). I'm not sure why this change was made in QA, but when I double-click on the Render file, it does appear to load a complete scene for me.
In your case, the HDRI does not seem to be loading for some reason. Have you tried double-cliking on one of the Render files?
Usually, it does and I still think it must be something somewhere in my settings but I wouldn't even know where to begin to look. I'm happy I got it working and it looks fabulous! And thank you lol!
IDA,
I think I see now why you were having those issues. As Dolbomir pointed out above, there are no actual "Scene" files in this product. They are "Render" files instead. I'm not exactly sure why this was changed, but it sounds like this is the root cause of why you were having problems loading this skydome but not my other skydome.
If you continue to have problems with this, you may need to submit a support ticket (and reference this thread), so QA can address it.
So, I'm a bit confused.. there are mentions of a scene, yet all I see are 5 render settings, 3 props (the your object here, the volumetric light cube, and the ripple), and 1 iray mat?
And none of the render settings have that sandy ground from the promos, no matter what I try to do with the camera. Is that a prop not mentioned in the "other products used" section?
Here's what I see with the sample camera, placing a sphere at 0,0,0 (attached).
Changing the dome mode to finite sphere w/ ground, infinite sphere w/ground, or box w/ground basically produces the same effect (except the shadow is a bit different perhaps).
...am I missing something? o.0?
I'm using DAZ 4.9.4.117 on Win 10, in case that clears something up...
Thanks!
How are loading this? Are you double clicking or are you merging with the scene?
Usually, it does and I still think it must be something somewhere in my settings but I wouldn't even know where to begin to look. I'm happy I got it working and it looks fabulous! And thank you lol!
IDA,
I think I see now why you were having those issues. As Dolbomir pointed out above, there are no actual "Scene" files in this product. They are "Render" files instead. I'm not exactly sure why this was changed, but it sounds like this is the root cause of why you were having problems loading this skydome but not my other skydome.
If you continue to have problems with this, you may need to submit a support ticket (and reference this thread), so QA can address it.
Seems to work fine as long as I don't try to merge it with the current scene. But it is odd that they would change that, and I wonder if that has something to do with it.
@Dolbomir I am looking over the released package and it appears that you are correct. There are no scene files but only Render settting files (plus the props). I'm not sure why this change was made in QA, but when I double-click on the Render file, it does appear to load a complete scene for me.
In your case, the HDRI does not seem to be loading for some reason. Have you tried double-cliking on one of the Render files?
-P
Ack! I saw water and for some reason assumed it was the HDRI component of your scene... now that I look closer, it's completely different... I wonder which one of my HDRIs my DS has pre-loaded on first scene creation!
Seems to work fine as long as I don't try to merge it with the current scene. But it is odd that they would change that, and I wonder if that has something to do with it.
I think, my double-click is set to merge into scene, so that's probably what was happening to me as well.. So far, using my current settings, I was able to load it, but only if it is the very first thing I load into the scene or if I deliberately choose 'Open as New' via right click.
Typically, I can apply other similar HDRI render settings by merging into the scene (via double-click) without issue... I wonder if this is different because the preset also includes other items in a group or something?
Thanks
*EDIT*: I tried loading one of the presets, then re-saving it as Render Settings asset... The saved asset merges as HDRI-only without issue. I wonder if this is all due to the original assets really being a Scene type (or a Scene Subset at least) but classified as a Render Settings type of asset (which seems to be expected to only include General and Iray render settings in it)? Maybe that confuses DAZ studio and it opts to load the scene elements, but omits the settings as a trade-off?
... I mean, sure that sounds backwards, but still...
*EDIT2*: Actually, why are these assets showing up as Render Settings to begin with? They're scene assets, not preset_render_settings o.0
@Dolbomir I am looking over the released package and it appears that you are correct. There are no scene files but only Render settting files (plus the props). I'm not sure why this change was made in QA, but when I double-click on the Render file, it does appear to load a complete scene for me.
In your case, the HDRI does not seem to be loading for some reason. Have you tried double-cliking on one of the Render files?
-P
Ack! I saw water and for some reason assumed it was the HDRI component of your scene... now that I look closer, it's completely different... I wonder which one of my HDRIs my DS has pre-loaded on first scene creation!
Seems to work fine as long as I don't try to merge it with the current scene. But it is odd that they would change that, and I wonder if that has something to do with it.
I think, my double-click is set to merge into scene, so that's probably what was happening to me as well.. So far, using my current settings, I was able to load it, but only if it is the very first thing I load into the scene or if I deliberately choose 'Open as New' via right click.
Typically, I can apply other similar HDRI render settings by merging into the scene (via double-click) without issue... I wonder if this is different because the preset also includes other items in a group or something?
Thanks
*EDIT*: I tried loading one of the presets, then re-saving it as Render Settings asset... The saved asset merges as HDRI-only without issue. I wonder if this is all due to the original assets really being a Scene type (or a Scene Subset at least) but classified as a Render Settings type of asset (which seems to be expected to only include General and Iray render settings in it)? Maybe that confuses DAZ studio and it opts to load the scene elements, but omits the settings as a trade-off?
... I mean, sure that sounds backwards, but still...
*EDIT2*: Actually, why are these assets showing up as Render Settings to begin with? They're scene assets, not preset_render_settings o.0
That's exactly what happened to me and I think I agree with you I think Daz messed up his files by changing them, because I know how meticulous he is with his stuff. And it is set up different than Cloud Haven.
That's exactly what happened to me and I think I agree with you I think Daz messed up his files by changing them, because I know how meticulous he is with his stuff. And it is set up different than Cloud Haven.
Yup, it seems like some kind of DAZ bug dealing with scene assets including render settings... or something.
For now, I just re-saved each of the scenes as separate Render Settings asset, so I can load the HDRI by itself or re-add it into the scene.
Kinda wish I had that sand as a shader... looks so good @.@
No, this is not working correctly. Although DAZ shows the four files types as "Render", these are actually loading as scene subsets with no render settings at all. Also, the scene subsets load with the cube at XT:-418.9406, ZT:-2461.479 and YR:-37.23406 (see attached). There is a sphere called "your object here" at XT:-67.01296, ZT:-2004.860. Nowhere near 0,0. Attached is the view through Sample Camera 1. Until this gets sorted out with DAZ, can you please provide some guidance as to how this should actually be loaded and parameters set?
No, this is not working correctly. Although DAZ shows the four files types as "Render", these are actually loading as scene subsets with no render settings at all. Also, the scene subsets load with the cube at XT:-418.9406, ZT:-2461.479 and YR:-37.23406 (see attached). There is a sphere called "your object here" at XT:-67.01296, ZT:-2004.860. Nowhere near 0,0. Attached is the view through Sample Camera 1. Until this gets sorted out with DAZ, can you please provide some guidance as to how this should actually be loaded and parameters set?
Artistb3,
When you switch the viewport over to Iray, you should see this image (see attached) through the camera, with the large sphere in the center. Note, the sphere is just an example of where and how you can place your object. Since it is in the distance, this is why it is not at 0,0. (For most shots, it is true, you can keep your object at 0,0 and just rotate the camera to position it. But if your object needs to appear like it is far away, then it is necessary to move it).
The elongated cube is the volumetric light cube, which passes through the sphere.
No, this is not working correctly. Although DAZ shows the four files types as "Render", these are actually loading as scene subsets with no render settings at all. Also, the scene subsets load with the cube at XT:-418.9406, ZT:-2461.479 and YR:-37.23406 (see attached). There is a sphere called "your object here" at XT:-67.01296, ZT:-2004.860. Nowhere near 0,0. Attached is the view through Sample Camera 1. Until this gets sorted out with DAZ, can you please provide some guidance as to how this should actually be loaded and parameters set?
No, this is not working correctly. Although DAZ shows the four files types as "Render", these are actually loading as scene subsets with no render settings at all. Also, the scene subsets load with the cube at XT:-418.9406, ZT:-2461.479 and YR:-37.23406 (see attached). There is a sphere called "your object here" at XT:-67.01296, ZT:-2004.860. Nowhere near 0,0. Attached is the view through Sample Camera 1. Until this gets sorted out with DAZ, can you please provide some guidance as to how this should actually be loaded and parameters set?
Artistb3,
When you switch the viewport over to Iray, you should see this image (see attached) through the camera, with the large sphere in the center. Note, the sphere is just an example of where and how you can place your object. Since it is in the distance, this is why it is not at 0,0. (For most shots, it is true, you can keep your object at 0,0 and just rotate the camera to position it. But if your object needs to appear like it is far away, then it is necessary to move it).
The elongated cube is the volumetric light cube, which passes through the sphere.
-P
Well, alright, this is something that will need to be played with in order to get something useful. Can you see how this might be confusing when the .pdf states "So the easiest way to begin playing, I have found, is to leave my object at 0,0", yet the "your object here" is default loaded at an offset that would appear to be perhaps the ship in the promotional image? If that is the case, since there are no actual render presets, what is the rotation, etc. of the environment map? Certainly, during your testing you must have tried many different options to obtain renders for promotion. It would be most helpful if you could share some of those with us (as presets) so that we would have some useful examples and ready scenes to plop a object/figure in for render testing.
Well, alright, this is something that will need to be played with in order to get something useful. Can you see how this might be confusing when the .pdf states "So the easiest way to begin playing, I have found, is to leave my object at 0,0", yet the "your object here" is default loaded at an offset that would appear to be perhaps the ship in the promotional image? If that is the case, since there are no actual render presets, what is the rotation, etc. of the environment map? Certainly, during your testing you must have tried many different options to obtain renders for promotion. It would be most helpful if you could share some of those with us (as presets) so that we would have some useful examples and ready scenes to plop a object/figure in for render testing.
Hmmm, I do see how that might be confusing. I'll be sure to clarify in my PDF's that leaving an object at 0,0 only suffices for near-camera shots. Also, I am thinking of changing the text "your object here" to "example object" (just to avoid the impression that you HAVE to put your object there in that location only).
Well, alright, this is something that will need to be played with in order to get something useful. Can you see how this might be confusing when the .pdf states "So the easiest way to begin playing, I have found, is to leave my object at 0,0", yet the "your object here" is default loaded at an offset that would appear to be perhaps the ship in the promotional image? If that is the case, since there are no actual render presets, what is the rotation, etc. of the environment map? Certainly, during your testing you must have tried many different options to obtain renders for promotion. It would be most helpful if you could share some of those with us (as presets) so that we would have some useful examples and ready scenes to plop a object/figure in for render testing.
Hmmm, I do see how that might be confusing. I'll be sure to clarify in my PDF's that leaving an object at 0,0 only suffices for near-camera shots. Also, I am thinking of changing the text "your object here" to "example object" (just to avoid the impression that you HAVE to put your object there in that location only).
-P
Okay. Since the Render Setting Presets do not actually set render parameters I would still request that you provide here any dome settings (e.g. Dome Rotation, Dome radius, etc.) that we need to be aware of. Thank you.
Okay. Since the Render Setting Presets do not actually set render parameters I would still request that you provide here any dome settings (e.g. Dome Rotation, Dome radius, etc.) that we need to be aware of. Thank you.
The presets should load the render parameters. I just tested the final release product on my computer and it seems to load ok. I'm not sure why its not working for you.
Anyway, here are the non-default settings;
-Env. Mode: Dome and Sphere
-Env. Resolution: 4000
-Dome Rotation: 270
-Draw Ground: ON
Honestly, I still have to load my own re-saved Render Settings asset to apply the actual render settings.
The original Scene assets with the props + render settings flat out do not work when merged into an existing scene--at least in DAZ 4.9.4.117. The fact that they show as a Render Settings asset type in the Smart Content pane, but load as a Scene Subset asset type with no render settings is still a thing. Even though they're clearly Scene asset type, which is neither.
I don't know if it's a general bug with scenes that contain render settings or a specific bug with these particular assets. Some playing around seems to suggest the former, since any attempt I tried at saving scenes with iray render settings makes them not load properly when merged into another scene (just like this one). The only thing I can't reproduce out of this problem so far is the scene showing up as a Render Settings asset in Smart Content.
Good luck with this... I'll just use the pure render settings re-saved version, since it works well :)
Daz did not change the files. They were saved as and are scene presets. Daz did set the metadata type to render-settings because they are more reflective of that type of content. Metadata types (the tag displayed on teh thumbnail) and file types are two different things and the metadata type does not affecet how Studio reads the file.
Scene files have their render settings ignored when merged with an existing scene. Which does have the issue of tending to set up the environment last not workign with these files unless the user saves their scene, loads one of these presets then merges their scene back in.
ThePhilosopher could submitt an update which added render setting presets which would set the render settings but not load the extra props. And those would work loaded or merged.
Daz did not change the files. They were saved as and are scene presets. Daz did set the metadata type to render-settings because they are more reflective of that type of content. Metadata types (the tag displayed on teh thumbnail) and file types are two different things and the metadata type does not affecet how Studio reads the file.
Scene files have their render settings ignored when merged with an existing scene. Which does have the issue of tending to set up the environment last not workign with these files unless the user saves their scene, loads one of these presets then merges their scene back in.
ThePhilosopher could submitt an update which added render setting presets which would set the render settings but not load the extra props. And those would work loaded or merged.
That's interesting, I did not know that. It is good to know that the best and easiest workflow then would be to load the scene then add whatever I want to. I have a couple of light sets that work this way as well (not his, from other vendors) Its a small adjustment to make for these awesome products.
The first time I loaded this, I got the same type of render that Sonja did where the hdr didn't seem to load. I'm not sure why as it loaded fine the second time around. Same file and everything. I've included my render. I have a strong DOF on this render but it still turned out very nice. I'm definitely going to play with this some more. I love the cove and rotating the dome gives it lots of background options. I love your skydomes.
Gorgeous! I don't know why its being weird on mine. Certainly not anything that will stop me from using this. I love all three of them but I think this one may be my favorite so far...
Daz did not change the files. They were saved as and are scene presets. Daz did set the metadata type to render-settings because they are more reflective of that type of content. Metadata types (the tag displayed on teh thumbnail) and file types are two different things and the metadata type does not affecet how Studio reads the file.
Scene files have their render settings ignored when merged with an existing scene. Which does have the issue of tending to set up the environment last not workign with these files unless the user saves their scene, loads one of these presets then merges their scene back in.
ThePhilosopher could submitt an update which added render setting presets which would set the render settings but not load the extra props. And those would work loaded or merged.
I kind of figured it was something like this. I guess, one could argue this is a feature rather than a true bug. That being said, this "feature" causes confusion. This is a scene and should be classified as such. If DAZ is "smart" enough to auto-classify it as a Render Settings asset, it should also be smart enough to load said render settings. Seeing as that is not the case, it should have classified the asset as a Scene, which is what it is.
In this particular case, a "last loaded asset wins" strategy would make some sense. In that case: merging a scene with render settings would override the prior render settings... Maybe that should be a configurable preference?
Given that this is not an option right now (as far as I know so far), saving a scene with render settings should strip said render settings and never classify a scene as a "Render Settings" asset. The way this is handled right now is downright misleading. Notice that none of this confusion is due to the author's choices. It's all due to how DAZ team chose to implement the resolution strategy for the render settings conflict between merged scenes vs. the way smart content auto-classifies said scenes :P
Anyone care to file a change request ticket for DAZ or somesuch? :P
Comments
Usually, it does and I still think it must be something somewhere in my settings but I wouldn't even know where to begin to look. I'm happy I got it working and it looks fabulous! And thank you lol!
looks great! bought :)
Hiyas...
So, I'm a bit confused.. there are mentions of a scene, yet all I see are 5 render settings, 3 props (the your object here, the volumetric light cube, and the ripple), and 1 iray mat?
And none of the render settings have that sandy ground from the promos, no matter what I try to do with the camera. Is that a prop not mentioned in the "other products used" section?
Here's what I see with the sample camera, placing a sphere at 0,0,0 (attached).
Changing the dome mode to finite sphere w/ ground, infinite sphere w/ground, or box w/ground basically produces the same effect (except the shadow is a bit different perhaps).
...am I missing something? o.0?
I'm using DAZ 4.9.4.117 on Win 10, in case that clears something up...
Thanks!
@Dolbomir I am looking over the released package and it appears that you are correct. There are no scene files but only Render settting files (plus the props). I'm not sure why this change was made in QA, but when I double-click on the Render file, it does appear to load a complete scene for me.
In your case, the HDRI does not seem to be loading for some reason. Have you tried double-cliking on one of the Render files?
-P
IDA,
I think I see now why you were having those issues. As Dolbomir pointed out above, there are no actual "Scene" files in this product. They are "Render" files instead. I'm not exactly sure why this was changed, but it sounds like this is the root cause of why you were having problems loading this skydome but not my other skydome.
If you continue to have problems with this, you may need to submit a support ticket (and reference this thread), so QA can address it.
-P
How are loading this? Are you double clicking or are you merging with the scene?
Seems to work fine as long as I don't try to merge it with the current scene. But it is odd that they would change that, and I wonder if that has something to do with it.
Ack! I saw water and for some reason assumed it was the HDRI component of your scene... now that I look closer, it's completely different... I wonder which one of my HDRIs my DS has pre-loaded on first scene creation!
I think, my double-click is set to merge into scene, so that's probably what was happening to me as well.. So far, using my current settings, I was able to load it, but only if it is the very first thing I load into the scene or if I deliberately choose 'Open as New' via right click.
Typically, I can apply other similar HDRI render settings by merging into the scene (via double-click) without issue... I wonder if this is different because the preset also includes other items in a group or something?
Thanks
*EDIT*: I tried loading one of the presets, then re-saving it as Render Settings asset... The saved asset merges as HDRI-only without issue. I wonder if this is all due to the original assets really being a Scene type (or a Scene Subset at least) but classified as a Render Settings type of asset (which seems to be expected to only include General and Iray render settings in it)? Maybe that confuses DAZ studio and it opts to load the scene elements, but omits the settings as a trade-off?
... I mean, sure that sounds backwards, but still...
*EDIT2*: Actually, why are these assets showing up as Render Settings to begin with? They're scene assets, not preset_render_settings o.0
That's exactly what happened to me and I think I agree with you I think Daz messed up his files by changing them, because I know how meticulous he is with his stuff. And it is set up different than Cloud Haven.
Yup, it seems like some kind of DAZ bug dealing with scene assets including render settings... or something.
For now, I just re-saved each of the scenes as separate Render Settings asset, so I can load the HDRI by itself or re-add it into the scene.
Kinda wish I had that sand as a shader... looks so good @.@
No, this is not working correctly. Although DAZ shows the four files types as "Render", these are actually loading as scene subsets with no render settings at all. Also, the scene subsets load with the cube at XT:-418.9406, ZT:-2461.479 and YR:-37.23406 (see attached). There is a sphere called "your object here" at XT:-67.01296, ZT:-2004.860. Nowhere near 0,0. Attached is the view through Sample Camera 1. Until this gets sorted out with DAZ, can you please provide some guidance as to how this should actually be loaded and parameters set?
Artistb3,
When you switch the viewport over to Iray, you should see this image (see attached) through the camera, with the large sphere in the center. Note, the sphere is just an example of where and how you can place your object. Since it is in the distance, this is why it is not at 0,0. (For most shots, it is true, you can keep your object at 0,0 and just rotate the camera to position it. But if your object needs to appear like it is far away, then it is necessary to move it).
The elongated cube is the volumetric light cube, which passes through the sphere.
-P
No, this is not working correctly. Although DAZ shows the four files types as "Render", these are actually loading as scene subsets with no render settings at all. Also, the scene subsets load with the cube at XT:-418.9406, ZT:-2461.479 and YR:-37.23406 (see attached). There is a sphere called "your object here" at XT:-67.01296, ZT:-2004.860. Nowhere near 0,0. Attached is the view through Sample Camera 1. Until this gets sorted out with DAZ, can you please provide some guidance as to how this should actually be loaded and parameters set?
Well, alright, this is something that will need to be played with in order to get something useful. Can you see how this might be confusing when the .pdf states "So the easiest way to begin playing, I have found, is to leave my object at 0,0", yet the "your object here" is default loaded at an offset that would appear to be perhaps the ship in the promotional image? If that is the case, since there are no actual render presets, what is the rotation, etc. of the environment map? Certainly, during your testing you must have tried many different options to obtain renders for promotion. It would be most helpful if you could share some of those with us (as presets) so that we would have some useful examples and ready scenes to plop a object/figure in for render testing.
Hmmm, I do see how that might be confusing. I'll be sure to clarify in my PDF's that leaving an object at 0,0 only suffices for near-camera shots. Also, I am thinking of changing the text "your object here" to "example object" (just to avoid the impression that you HAVE to put your object there in that location only).
-P
Okay. Since the Render Setting Presets do not actually set render parameters I would still request that you provide here any dome settings (e.g. Dome Rotation, Dome radius, etc.) that we need to be aware of. Thank you.
The presets should load the render parameters. I just tested the final release product on my computer and it seems to load ok. I'm not sure why its not working for you.
Anyway, here are the non-default settings;
-Env. Mode: Dome and Sphere
-Env. Resolution: 4000
-Dome Rotation: 270
-Draw Ground: ON
Everything else is default.
-P
Honestly, I still have to load my own re-saved Render Settings asset to apply the actual render settings.
The original Scene assets with the props + render settings flat out do not work when merged into an existing scene--at least in DAZ 4.9.4.117. The fact that they show as a Render Settings asset type in the Smart Content pane, but load as a Scene Subset asset type with no render settings is still a thing. Even though they're clearly Scene asset type, which is neither.
I don't know if it's a general bug with scenes that contain render settings or a specific bug with these particular assets. Some playing around seems to suggest the former, since any attempt I tried at saving scenes with iray render settings makes them not load properly when merged into another scene (just like this one). The only thing I can't reproduce out of this problem so far is the scene showing up as a Render Settings asset in Smart Content.
Good luck with this... I'll just use the pure render settings re-saved version, since it works well :)
Daz did not change the files. They were saved as and are scene presets. Daz did set the metadata type to render-settings because they are more reflective of that type of content. Metadata types (the tag displayed on teh thumbnail) and file types are two different things and the metadata type does not affecet how Studio reads the file.
Scene files have their render settings ignored when merged with an existing scene. Which does have the issue of tending to set up the environment last not workign with these files unless the user saves their scene, loads one of these presets then merges their scene back in.
ThePhilosopher could submitt an update which added render setting presets which would set the render settings but not load the extra props. And those would work loaded or merged.
That's interesting, I did not know that. It is good to know that the best and easiest workflow then would be to load the scene then add whatever I want to. I have a couple of light sets that work this way as well (not his, from other vendors) Its a small adjustment to make for these awesome products.
The first time I loaded this, I got the same type of render that Sonja did where the hdr didn't seem to load. I'm not sure why as it loaded fine the second time around. Same file and everything. I've included my render. I have a strong DOF on this render but it still turned out very nice. I'm definitely going to play with this some more. I love the cove and rotating the dome gives it lots of background options. I love your skydomes.
Gorgeous! I don't know why its being weird on mine. Certainly not anything that will stop me from using this. I love all three of them but I think this one may be my favorite so far...
I kind of figured it was something like this. I guess, one could argue this is a feature rather than a true bug. That being said, this "feature" causes confusion. This is a scene and should be classified as such. If DAZ is "smart" enough to auto-classify it as a Render Settings asset, it should also be smart enough to load said render settings. Seeing as that is not the case, it should have classified the asset as a Scene, which is what it is.
In this particular case, a "last loaded asset wins" strategy would make some sense. In that case: merging a scene with render settings would override the prior render settings... Maybe that should be a configurable preference?
Given that this is not an option right now (as far as I know so far), saving a scene with render settings should strip said render settings and never classify a scene as a "Render Settings" asset. The way this is handled right now is downright misleading. Notice that none of this confusion is due to the author's choices. It's all due to how DAZ team chose to implement the resolution strategy for the render settings conflict between merged scenes vs. the way smart content auto-classifies said scenes :P
Anyone care to file a change request ticket for DAZ or somesuch? :P