Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.Daz 3D is part of
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
I spotted the tower in the woods, the building by the jetty and the little boat - what else did I miss?
Melanie, that first render reminds me of a drive we used to make when we lived in Washington, heading into the edge of the Cascades to Leavenworth.
Great stuff!
Yes, i made a folder in my daz library specifically for it. Have just tried a Full render, and the trees are showing up, they just don't show up in the Iray preview render, is that correct, or is that a fault?
@shedofjoy_a0bca15db4 The trees do not show (by design) in Iray preview. I thought, from a previous message you wrote, that you aleady knew that. Iray Preview does not honor the Instancing Optimization Memory settings and showing all those tree instances in Iray Preview would probably crash your computer. HowieFarkes discussed this earlier in this thread.
So are your problems resolved now?
I got UltraScenery and various add-ons a while back, but never got round to trying it out yet. I know, shocking!
Got USXT on release and thought to throw it all together and see if I could get things to work, fingers crossed. It took a minute, but thanks to all the tips here, it worked.
This just has a basic US foreground with a basic USXT background, with a character in there to see if I could get everybody to play nice. I'm still unsure how to best show the middle distance and give the impression of the overall distance. I think Oso3D gave a nice tip on using matte fog. I'm guessing DOF and just size of the environments used also makes a difference... Still figuring out the basics...
Thanks Howie for a lovely set of products!
I scattered some grass and reeds along the lake shoreline with UltraScatterPro.
Here's one experimenting on height map. This came from real world of an area that i was able to zoom in on and render... Tangram Heightmapper (tangrams.github.io)
I didnt have a sky on this. wanted to see how it would look.
Looks like im good to go now, thanks for your help.
Wonderful! Have fun.
I have narrowed the problem down to 4.12 on a MAC. The shader is not working on terrains, as I documented above.
So lets get specific.
XT works just fine on 4.15 (using an imported file from 4.12 with all of its file/folder settings, so there is no problem where you thought there might be one regarding XT being able to find files, folder restrictions, etc.).
I noticed you DID NOT test XT on 4.12 for MAC. You only tested it on Windows. Why? As everybody knows, 4.12 was and is a critical release for MAC people. You should know that given that you are developing on a MAC.
4.15 works only for CPU renders, which makes XT basically useless on 4.15. And as we know from what you said, you didn't test it on M1s either .... and it also doesn't work on M1s. That leaves a lot of MAC folks out in the rain.
So, the last critical release (4.12) that MAC people with Nvidia GPUs can use was not tested by you.
Perhaps you could compensate this oversight by trying to solve our problems by now testing XT on 4.12?
You are contradicting yourself. First you said XT works just fine on 4.15, and then 4.15 works only for CPU renders, which makes XT basically useless on 4.15.
The new beta version of worldcreator now allows much higher resolution texture map export. The detail is just crazy.
Like I said, 4.12 is a totally critical release for many MAC people -- as are the new M1s -- to counteract Nvidia card/MAC OS/Studio combo limitations. It should have been tested on 4.12 by you IMO. And somebody like Totte should have tested it on an M1 for you. It would have been easy to do that.
NM
If we were to request version 4.12, as an example, through a ticket, would DAZ provide that download? I think 4.12 was the last version I liked overall as far as stability, but they keep updating everything to work with the current version so who knows it it would even work with some products. Obviously not even for USC.
I once asked for version 4.12 through a ticket but the answer was a stern no. It's really sad you can't even request it. You can try it, but that was my experience.
The 4.12 issue I suspect is due to changes in Iray, that made complex shaders working on 4.12 broken on 4.14+ and complex shaders working on 4.14+ broken on 4.12. A recent similar thing is GhostLights.
I'm starting to play with UltraSceneryXT, and it's everything I hoped for, and much more ! It worked fine from the start for me (thanks for the user manual). For everyone experincing difficulties, keep trying, it's worth it.
Of course, now I want more, and since it's spring today, especially blooming trees ! But for now, maybe just a tip : is there a way to have a terrain with grass everywhere and no rocks showing ? The rocks are fine, mind you, but I'm trying to capture the feel of a more luxuriant mountain grass.
This looks great but I've had problems with it. Maybe my computer is a under-powered or perhaps it's some oddity in my setup. I've found a way round it so I'm writing this in case anyone else is having similar problems.
I can render scenes with or without water but if I use a biome I get a box saying Error during rendering! The render seems to be over, the Studio interface is active but if I try to render again it says the renderer is already in use. The way I get round this is to save the scene, exit Studio, restart Studio and reload the scene. Next I unparent the biome group from the terrain, select the terrain, go the the UltraSceneyXt settings and switch off the biome. Then I render the scene and it renders OK, UltraSceneryXT doens't re-create the biome but the one left from before renders OK. I have to unparent the biome from the terrain, if I don't then UltraSceneryXT deletes it before rendering.
Since my computer can render the biome it looks as if there is something in the way the plugin gereates it then launches the renderer that my computer doens't like. The error happens every time I use a biome. I've rendered two test scenes with my work around so far and they both worked.
Sounds likw a low memory issue, but just guessing.
Sounds very likeley. It's a fairly old computer, 12GBytes of RAM and that's the maximum it can take. I'd need to buy a new computer to get any more and that's likely to be rather expensive.
At least you found a clever workaround for the problem. I'm impressed by your ingenuity.
Playing around with creating new biomes. This is just the conifer biome with colors changed in the json, but at some point I might experiment with new plants and whatnot.
Howie,
I have an M1 MacBookPro and I need to point out that just before the release of your product, macOS Monterey updated to v.12.3 which on the internet is reporting a number of problems with 3rd party software.
I downloaded USXT through DIM and when I tried to open it, Daz Studio 4.20.0.2 crashed. I tried the Beta, 4.20.0.8 and it just didn't open. I closed down my computer, reopened it, tried again, this time saving the crash report. Today, I found someone's note that they had a similar problem on page 7 of this thread and I uninstalled both USXT files, closed DIM and rebooted the computer. I was successful in opening Daz Studio. I made a copy of my Help Log from the last time I was on the program to this opening. I also have opened a Help Ticket Request #405385 and asked if they would send you this information, but I will also attach it here for you. Also, all files for UltraScenery are downloaded by DIM and I never mess with the file structure.
I have two other computers Win 10 with it on, so I am able to wait while you figure this out.
Mary
Created my first non-test scene, I'm enjoying this. I added a small amout of 4.20's Matte Fog to add a sense of distance. I had to switch off the limits on Matte Fog visibility and turn it up to 100,000 metres.
On the technical side, it's behaving differently today. The only changes I've made are to disable the Octane plugin (it kept telling me it was finishing doing stuff even though I wasn't using it) and not running Chrome at the same time to try and save memory. It isn't crashing on render which is great. Also, it isn't creating a group of instances for the biome parented to the terrain. In fact I can't find the biome instances anywhere in the scene tab which is really confusing me. Anyway, technical matters are not important, I made a picture that I'm happy with.