Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
For the purposes of the forum it's nude if it shows the groin, or front chest on a woman, with skin coloured textures - lack of detail doesn't help Acceptable Ways of Handling Nudity If you repost your images in Smooth Shaded then people will still be able to see the issue, complying with the forum rules will not hamper your obtaining help.
Well, with a name like commando991, you can't expect underwear.
LOL, I get it, but the name is Military base name for my old position in the service.
Just for INFO
bought her in the 2.99 deal yesterday - the ERROR is still there - intalled via DIM
Starting to wonder if someone has reset something they really shouldn't have, as a result a lot of "fixed" products have been reset back to thier original upload.
Sure would explain why a "broken" product gets "fixed", only to return to being "broken" some time later.
Did a spot of digging through my notes and it turns out one of my lot bought this "Zilpha", and that I had to do a spot of fixing.
A control dial with a value of 1 was only part of the issue, the control dial didn't have any ERC, so it wasn't linked to anything, and a control dial without ERC is a waste of drive space.
The main issue was ERC links in both head and body DSF files, they were pushing a value into the control dial.
Don't have the files to check, but I probably manually coded two ERC links into the control dial, set the value to zero, then removed the bad ERC links from the head and body morphs.
I used the instructions in this conversation to fix the Zilpha issue:
https://www.daz3d.com/forums/discussion/369811/zilpha-hd-for-jenni-8-is-loading-with-all-of-my-g8f-characters
I used notepad to change the value form "1" to "0" and it fixed it.
FIX THIS DAZ! This is so unprofessional to let this issue persist since NOVEMBER 2019. This needs to be posted in The Commons so everyone knows about it.
Novica, according to this post, halfway down the first page, the bug was fixed in December 2019. It seems to have become unfixed again recently.
Either way, it need fixing.
There was a fix in 2019-12-10 (the ReadMe actually documents this, when you can get to it), but the currently available zip is the previous version (released 2019-11-20, package date 2019-10-23). It seems to have crept back in sometime around 2020-10-30 (just before the store change) as an update, which wasn't really an update, but I guess it triggered the update status, since it was, in fact, different. I always compare updates with the previous version to see what has changed and noticed it had reverted somehow, but then Storepocalypse happened, and, well, bigger fish...
DAZ needs to put back the previous (new) version. The only change was to the file mentioned above. Oddly, I have the 2019-12-10 version of the archive in place in my download folder, but DIM accepts it as up-to-date. Something is wonky with the perceived package dates.
Timeline: