UltraScenery - new territory [Commercial]
This discussion has been closed.
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
Maybe better; sliced bread is fattening.
Is there going to be an update to fix the black stones? I have no idea what to do to fix this. Ultrascenery is useless to me right now. Blackness surrounds all water.
Black stones is not a universal problem. We need to figure out what is different about your configuration.
What version of Daz Studio are you using and what version of UltraScenery are you using (look on the Build tab)? Are you using the accelerator? If so, what version? Is the problem limited to a particular ecology or all ecologies?
Here is a render I did just now with DS 4.20.0.6 Public Beta, UltraScenery 1.3.3.1, and Accelerator 1.0.2.4, Harpwood 1 Ecology, and Bridge 1 Feature.
I have Studio 4.20.0.2 Ultrascenery 1.3.3.1 and Acellerator 1.0.2.4 and I have added the nvidia 1.7.0 vMaterials. I have only noticed this since update to Studio. I will get the latest Beta and see how that works.
People have reported incompatibilities between nvidia 1.7.0 vMaterials and DS 4.20. That may be your problem. Try removing nvidia 1.7.0 vMaterials and see if that resolves the problem. You may need to use nvidia 2.0 vMaterials instead with the current version of Iray. I currently do not have any version of nvidia vMaterials installed.
I updated Beta and now everything seems to be working correctly using it. I made a few new scenes and also opened files I was working on. Stones and rocks by the water look as they should. Thanks for the help!
I love UltraScenery and have added most of the support products for it. It is a great tool.
Did you have to remove or update the nvidia vMaterials, or is it working in the beta with nvidia 1.7.0 vMaterials installed? Or did you even install nvidia vMaterials into the beta?
I did not uninstall the vMaterials 1.7. I did not add them to the Beta. I did not know that they needed to be added to both. I need to learn more about them.
NVIDIA vMaterials is complimentary, it is not a requirement. However, if you do use it, install v2.
The issue with vmaterials depended on the version of Daz Studio, prior to 4.16 the problem was with the version of the Nvidia Materials Exchange that came with vMaterials v2.0.. And you had to go back to the Materials Exchange that came with vmaterials 1.70 to stop the weird rendering issue.. However after Studio 4.16 and up the reverse happened, and you had to reinstall the Materials Exchange that came with vMaterials v2.0 to stop the rendering weirdness with certain products..
Can't you just set the render to use Dome Only?
To keep the headlamp from being used in the render? - probably. I'm not a headlamp expert at all. I'm not sure how all those settings play together. Thanks for adding this suggestion.
I guess the downside would be if you really wanted to have some scene lights. I hardly ever use them with USC so using Dome Only works in this case. And you can also set Auto Headlamp for each camera too, in case you have a special Render Cam. Lots of options...
Greetings all,
I was using UltraScenery perfectly fine for a while. However, I recently uninstalled and reinstalled Daz studio along with all my content and now US freezes or lags to the point of being unuseable. I am wondering if this is related to reinstalling all my content, or to the recent Daz updates?
I have a RTX 3090, and am already aware of the following suggested workarounds: setting optimization settings to "memory" and making sure Iray is not on in the preview viewport. Before I reinstalled everything, setting optimization to "memory" solved my issue, however that is no longer the case.
Also: I have checked all my hardware and all my drivers are up to date.
Is anyone aware of what might be causing the freezing issues? Thanks in advance!
The very first posting in this thread has some trouble shooting tips. Please check and see if any of those suggestions apply to your situation - e.g. having Octane Render installed has been reported as a source of problems.
Thanks for the tip. I should have mentioned that I did take a look at the first post in the thread and that unfortunately the method of install as well as removing octane also do not resolve the issue. The first time that I used US I installed through Daz Central and it worked perfectly fine after setting optimization to memory, but unfortunately I am not having any such luck this go around. I am a huge fan of this product and would love to know if anyone else is having these same issues over the past few weeks or if this is just an anomaly on my end?
Be sure you are using the Studio drivers, If I recall i had a similar problem when i got my RTX360 12GB. I had to remove my other GPU in order for the correct drivers to be installed on the RTX360.
I went back to 472.84 to get studio working properly. Also be sure to set rendering to GPU only. With the faster cards somehow GPU+ CPU combo slows doen the render sometimes.
Thanks for the tip on the unchecking the CPU and switching to studio drivers. I went ahead and tried those and unfortunately it hasn't really solved the issue.
I am able to navigate the scene if I hide most of the instances (which still seem to be generating at a crazy high leve still). However, just a few weeks ago that wasn't necessary and i could navigate the scene immediately after it was built without hiding anything.
Edit: Tech support helped me figure out the solution to my issue. Apparently having viewport set to filament was the problem. Changing it to "texture shaded" has resolved my issue.
Some screenshots of the viewport and the Scene pane showing how many instances are being generated might help.
Attach a sample scene (duf file) that you have built so other people can try it and see if there is something strange happening to them, with that scene, too.
I've been playing with UltraScenery and the new decal product Ground Decal Materials. I posted some images and techniques in my thread. I like the ground decals. They can add extra variety to UltraScenery renders.
Is there an easy way to add an ecology such that the script picks it up as an option?
I'm sure it's been mentioned at some point over the last few hundred posts, but... ;)
For the script to see an ecology, the ecology folder needs to be placed in the same folder as the other UltraScenery ecologies and have all the supporting files like preview, thumbnail, and material.
I meant the first thing you said, which I had done but somehow didn't notice the entry. Duh.
The rest of it I can work out, thanks!
UltraScenery always opens to Grassland 01 ecology, so anything with an alphabetical name that comes earlier requires scrolling up. That tricks people, including me, from time to time.
Can I ask. Is it possible to use a custom depth map and scale the US ground plane?
I had an idea to use Andrey Prestriakov's ancient ruins and try to use US to create a fully planted landscape for the grasses. I used the ground plane to create a depth map successfully. However, it didn't seem to work as the ground plane didn't seem to scale, and you can't scale after planting if making it smaller as the planting will be too close - and I needed it to be 58.7%.
Does anyone have any ideas how to get this to work?
Regards,
Richard.
By depth map I think you mean height map, right? Could you creat a new square image in an image editor, where your ancient ruins height map fills just 58.7% of the square image and the rest of the image is black? I haven't tried this, but it seems like it might work. Then remember to turn off Noise in US by adjusting brightness/contrast to black.
Simple UltraScenery made together with Cloudscape Creator
https://www.daz3d.com/cloudscape-creator-volumetric-clouds-bundle
Really like the look of it.
Love the painterly look, USC is amazing!
Thanks a lot, @Paintbox.
Have added UltraSceneryXT, but need to experiment more on mixing both systems.