- This topic has 29 replies, 10 voices, and was last updated 1 year, 3 months ago by
.
-
Posts
-
Recently, when I loaded a saved scene, the textures seemed damaged. I didn't get any warning message, I just noticed the overall white colour of all the textures in the scene. Then I previewed it in iray and everything showed up in a garish magenta colour(the same colour as the damaged textures I saw after recovering my library - in which I lost most of my assets, but managed to save some, and the rest were damaged) so I quit the scene and loaded one of the scene figures from my library; it was perfectly fine and rendered fine (if a little slower than usual)
Thinking there was some problem with the particular scene, I saved out the figure I had recently checked, then reloaded it. It's textures were missing, and it rendered in magenta, just like the first scene.
I loaded other saved projects - same thing, yet when I load the same figure from my library it's fine. It's only the saved scenes that are damaged.
I thought there was a drive probelm. Checked the drive - it's fine. Did a memory check as well; memory is fine. Checked GPU,no problems there, either.
Can anyone tell me what the problem could be? It kind of sucks if you can't save scenes and have to complete something in one go.
What version of Studio are you using. I see in another forum that folks are having BIG problems with 4.23. Among the problems are those involving saving stuff.
I have 4.24 - the latest version, as far as I know, but I've never had a problem with it until now.
I don't have a problem saving; it saves fine without issue. For example: I'm working on a scene for an hour, but I need to get to bed. I save the scene and close Daz and shut the PC down. When I get a quiet moment, a day; maybe two, or three later, and I open Daz, then open the saved scene, it loads the exact same way in which it did before - no warning message to say that there is a problem - but the models are white - missing their textures. When I preview it in iray, the whole thing is magenta.
Then, I close that scene and go to my library and load the exact same assets as were in the scene, then preview in Iray, and the textures and assets are perfectly fine and render normally - no magenta colour, no missing textures. But, if I save those assets to the project folder and then reopen, the textures are missing and the scene renders in magenta, as with the original save.
I've had this version for a while and I've never had a problem. I searched on the Daz forums, but no one had a similar complaint. Then I googled it, but the best answer I got was in relation to Blender; not Daz. It turned out, in that case, faulty memory was the issue. So, I checked the memory. It was fine. Then decided to be more thorough; I checked GPU and the disk. No problems in either. So, I'm at a loss... I'm entirely baffled, as no one seems to have a similar problem and I can't find a solution anywhere.
It sounds like you've covered all the bases. There are older versions of Studio here, you might try installing one of those as a second install then load your scenes. There's also instructions in the stickies for doing that.
I was thinking of doing a reinstall, but, I'd like to see if anyone has any other solutions first.
4.24 has been showing problems for me - on occasion, if I have more than one figure in a scene and I'm using Filatoon, it'll work fine for awhile, until one of the figures suddenly turns transparent. I then have to reload the scene or restart Studio to make it work.
I've tried updating NVIDIA drivers, changing which textures are used (to see if it was just a sudden iray allergy to a specific skin texture), you name it. I've dragged through the settings to see if it was due to that, and removed everything from the scene except two naked figures w/ no hair, saved it, then reloaded again to see if I was just overloading vRAM (I wasn't), and I still get an issue.
I'm this >< close to uninstalling and reinstalling 4.23, but it only affects Filatoon so far, so I haven't done it yet.
I have experienced the same problem. Could this be a bug in DAZ Studio 4.24? Is DAZ doing anything about this issue?
This is so frustrating. Hours of work lost. This is completely innefficient and inneffective.
What can we do?
@dirtydog You're in the wrong thread. Message one of the mods or read this https://www.zonegfx.com/faq/
From FAQ:
Membership and Renewing your Account
Membership to ZoneGFX is free and while you are asked to renew your account once per year, this is a simple process and your account details including your points total will remain unaffected. There are no fees involved and you will not be asked for any details after registration.
To renew your membership once you have received an email from ZoneGFX simply click on the following at the top of any page: Community>Membership Levels>Renew, and that’s it! All done for another year!Thanks for helping @ulysses but waaay offtopic :p
@reinecarola Is that the main channel or public beta (or 2025 alpha)?
I've been reading similar horror stories in the release threads in Daz forum for all the 4.2x flavors.For the record, I've been messing with 4.24, and I haven't seen anything like the bug you describe. I have however noticed some morph shenanigans, some old scenes with my entire runtime present seem not to know the morphs are present when loaded, and models sometimes appear "wrinkled" or badly morphed. No error messages. Makes me wanna throw spaghetti at someone. >:{_}
This thread over in RenderHub has some interesting information that I believe offers some background to Studio's ongoing problems.
https://www.renderhub.com/forum/10639/daz-is-killing-its-bare-bones-ai-generator
This Thornton James clown is turning Daz into a short term money pit (equity firm). Daz_ Raub, their lead programmer, disappeared shortly after Studio 5 was announced, followed by the failed attempts to generate cash using the next big thing. NFT's and AI are perfect examples. Reluctantly realizing that they HAVE to fix/update Studio, he's now using what little programming capability is left. An attempt to fix the constant complaints about loading ALL morphs are now being felt. I'll just bet that he's trying to use AI to write code.
I've got most versions of Studio archived and won't be playing with any newer ones until it's been shown that they work. I'll bet my next paycheck that he's aiming to put most of Studio behind a paywall. This will of course be hacked in a second, just like every other popular program that tries this.
I asure wish Abad was still around, he'd be all over this.
- You must be logged in to reply to this topic.
