SASE Jazz - missing file?
Taoz
Posts: 9,971
Just grabbed this yesterday, however I get an error about a missing file: /Textures/SASE/Jazz/SASEJazzEyesB_1007.jpg
It does say it requires Sahira 8 which I currently don't have but it doesn't look like it has anything to do with that. Anyone else getting this error?
Post edited by Taoz on
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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
OK, thanks!
Is this ever going to be fully fixed? Some SASE products are fine, but Tillie, Jazz, Sprout, Karma–and possibly others–from the DAZ Store still throw up errors, especially with the eyes. Rendo products, like Lillian, Lena, etc. also. I tried reisntalling them with freshly downloaded zip files but no fix.
The error has to be corrected in every asset that contains the "//Runtime" in the path for a texture bitmap file (or any other file, for that matter). The files are present, it's just that Studio can't resolve the path to find it. So, it throws an exception. This all started with 4.20 being more strict with the syntax, but has probably been lurking for years.
It's not just their products, either. I've found the problem in Emrys's products, too.
To me, this is rather disappointing. IMHO it really comes down to a quality control issue and Daz not enforcing proper path structure. What's even more disappointing to me is that they haven't fixed the issues yet. They have programmers on staff, it should be a fairly trivial task to develop a quick script/program that when a ticket is submitted with this pathing issue, the program is executed by someone at DAZ pointing to the proper files and they are automatically fixed.
I may be over simplifying things, but I don't believe it would be that difficult to do. The result would be providing content that works as intended instead of customer complaints. Seems like a good reason to me to fix things, but what do I know.
I'm not sure what the hold-up is, but only two (2) characters out of the many of Sabby's characters that I own have been updated. This is not a good thing, since people are still receiving characters with this problem when they purchase them today and they won't load properly.
On the bright side, while it's annoying, I've not found it to seriously affect characters in practice.
That seems to be a DAZ issue. All affected products i have bought at the other store have already been fixed.
A few of my Sabby characters from Rendo have been fixed within the last 3 year, some in March this year, according to the "Updated" data. Since I only own a fraction of her characters and these are all older than 2 years there are probably many others that have been updated.
Currently not keeping track up DAZ updates though.
What exactly needs to be changed in the files?
// instead of / in paths - every instance I have seen has had a path starting //Runtime, from using a bad template for materials.
One of the two "/" characters before the word "Runtime" needs to be removed in the eye colour duf files.
OK, thanks. If it always is //Runtime to /Runtime or just any // to / in the files it should be fairly easy to write a script or an app that automatically fixes the files.
There might be a vendor website link that has "http://"; so I wouldn't globally replace "//" with "/", but "//Runtime" with "/Runtime".
Not all Rendo products have been fixed either. I just checked this yesterday. But at least now it only seems to affect the eyes.
You can fix them yourselves and stop waiting for the vendor and Daz to do something about it. I posted a fully illustrted set of instructions here to fix the files on Windows with Notepad++.
Notepad++ can do this. (And is a great text editor in its own right.)
... and I should have read the enire thread as Barbult already stated as much.
Over the course of several weeks earlier this year, I took on the task of removing "missing file" errors when they were thrown. Sometimes the duf file had the double forward slash error before Runtime, but more often than not for my "problem" files, it was something else such as
The correction (fixing the path description needed to locate a file) is simple but tedious. Usually, there were several lines in a single file that needed correction. Once a file is corrected (I used Notepad.), it's corrected for good. I'm aware of Notepad++ but have never explored it.
Notepad++ can change all of your //runtimes in multiple files at once. It is not tedious at all. Look at the instructions I linked to. Don't waste your time editing one by one with old Notepad.
barbult said:
Notepad++ can change all of your //runtimes in multiple files at once. It is not tedious at all. Look at the instructions I linked to. Don't waste your time editing one by one with old Notepad.
Most of my file correcting did not involve //runtime errors but the other three bulleted items in my earlier post. In any event, all of that correcting is weeks behind me now and I've not had an occurrence since then, although it will likely occur with some product that I haven't tried to load. Always willing to learn something new, I've got the Notepad++ web site bookmarked.
Those other types of missing file errors would have always thrown an exception. What is particularly annoying is that this new "//" didn't cause problems before 4.20, and now there are dozens of broken products that used to work properly.
OK. Regex can take care of that and other exceptions though.
@barbult This worked great. I was dreading having to download and reinstall all my many, many Sabby characters with the updates, which would have taken half a day. Thank you very much!
@barbult,
I encountered an issue yesterday with some content that comes with Poser 11 Pro wherein the content loads fine in Poser but Daz Studio couldn't find some of the needed files - usually textures and, occasionally, an OBJ file. This is not the case for all Poser content; some load fine in Poser and in Daz Studio. For the content that Daz was having issues with, the case almost always was that the content was installed where the package files were supposed to be installed but there was a reference path mismatch in the loading file; for example, referencing a path to a folder titled UrbanDecay when the files were properly installed to a folder titled Urban Decay, or vice versa sometimes. I discovered a while ago that Poser can easily accommodate such errors and find all of the needed files whereas Daz Studi cannot.
So, remembering advice from you (and others), I downloaded Notepad++ and used it to make the needed changes in files - even all opened files in Notepad++. For example, I opened all of the prop files for one product that had a file path mismatch error and had Notepad make the needed changes to more than 700 instances across all of the files at one time. That would have been a nightmare to accomplish using Notepad.
Why didn't the collective world get me to use Notepad++ sooner!! :)
It's always great to find a new tool that solves a pesky problem!