Loading character file results in unkown error. [solved...sort of]
...I just tried to load a character I had saved as a scene preset and recieved rhe following eerror message::
So I opened the log file, searched for where the character load was initiatied, and this is what I found
2023-12-26 23:33:53.395 [INFO] :: Begin asset load (open): /D:/DAZ 3D/Studio/Amineh 8.duf
2023-12-26 23:34:23.678 [INFO] :: Json Parser (4614199,26): Unexpected end of file in object.
2023-12-26 23:34:23.706 [INFO] :: Error loading asset: D:/DAZ 3D/Studio/Amineh 8.duf
2023-12-26 23:34:23.706 [INFO] :: Operation failed
2023-12-26 23:34:23.787 [INFO] :: Unlocking viewport redraw...
2023-12-26 23:34:23.787 [INFO] :: Viewport redraw unlocked.
O have no idea what "Unexpected end of file in object." refers to;
Before I shut the programme down I always Save, then click New to clear memory after and then when that is finished I exit the programme (this keeps Daz form languishing in memory for several minutes after it closes). I have never had this occur even the last time I opened this particular character. I tested opening an older version of the same character and it opened fine. The one that fialed to load had a number refinements I made as since thenm I purchased several new shaping and morphing assets which fixed several things that I felt didn;t look quite right.
I really hope there is some way to fix this as I don't look forward to rebuilding the character all over again. Even using the older version would entail a lot of work as I don't remember all the modifications I made and settings they were at so it will be at best a frustrating exercise in trial and error.
Still in the processes of rebuilding characters I lost in a drive crash a while ago which was pretty discouraging and has been real slow going.
Comments
It seems that duf file was more or less corrupted to some extent... ( better partially....) Or it was probably written to a bad sector on your disk I presume...
In terms of syntax check, there's either a bracket(s) (round or square) missing or a comma(s) missing in that Amineh 8.duf, or a full broken starting from line 4614199, resulting from corruption....
Can you open it with Notepad++ ? ( first uncompress it if it's compressed, via Windows - Panes - Batch Convert...) Then go to line 4614199, column 26, check the line syntax there...
PS: If you could not fix it, and if you don't mind, you may PM me with duf file attached. I may help to check and fix it if possible.
PLS BE NOTED: Before opening it with Notepad++, make a backup of this duf file !
...OK have the pane open but there are two choices under where the filename is, "Convert DS[A] to DSB" and "DSB to DSA along wconvert DS[A╏B] to DSE" Are these important just for uncompressing?
Do I Also need to uncheck all the boxes under "File Extensions" except DUF?
No, just keep the default ~~ as below SS
...ran it and received the following error:
2023-12-27 00:58:06.011 [INFO] :: Loading Layout: C:/Users/▉▉▉▉▉▉▉/AppData/Roaming/DAZ 3D/Studio4/layout.dsx
2023-12-27 01:28:59.139 [INFO] :: Error converting the following files:
D:/DAZ 3D/Studio/Amineh 8.duf
( ▉ redacted)
Tried a second time but the same message appeared so likely either the bad character is at the start of the file as it cannot even be opened by the batch converter, or it is totally corrupted. I even tried the conversion in 4.20 (as 4.21 can be a bit flakey at times), but it returned the same results Not sure how this would have happened as I take the same precautionary steps mentioned above before closing Daz down and wait for evey action to finish before moving on to the next.to avoid something like this occurring
Not very thrilled about this as it this as it basically means hours, possibly a couple days of work even building off the older version of the character as I don't remember all the morphs shaping and settings I added since then. That particular version is over 8 months old and is part of a full scene out of which I'd have to save the character again as a new scene subset to avoid starting from scratch.
it's late (02:20 where I am) so just going to leave it for now as I'm rather annoyed and need to turn in.
Thank you for trying to help.
7-Zip can open compressed Duf files (Open as archive)
One reason for getting that error message, is when one has run out of space when saving.
First, can you remember you saved the file with "Compress File" ticked ? Or check the file size as a duf file with 4-5 Mil lines of codes, the file size should be xxMB at least. You may directly try to open it with Notepad++, see if you can open it.
Or as PerttiA says, try to unzip it with 7-zip... see if it works.
...yes, I never mess with that (I leave it checked by default).
The drive still has 671 GB of free space so that wouldn't have caused it. Compressed the file is 89.8 MB due to clothing ,hair, and shaders and the HDRI, but I have much larger scenes in teh Studio folder as well.
7-ZIp won't let me extract to anywhere but the Studio folder. I also am unable to copy it to say the desktop as I get an Windows error message that reads...
...which means its likely on a bad sector as even if it was internally corrupted for some other reason, I could still copy/move it. A bit unnerving if it's the former case as the drive is fairly new.
Bugger.
Thank you all again, looks like I have several evenings of work and frustration ahead of me. At least I don't have to start from square one but it is still a major bother to get the character looking as she did. Wish there was a way to save the parameter settings to a file as that would make it much easier ro rebuild a character when this happens.
I'm sorry to hear that ~~ It is odd that even it could not be copied... Anyway, still 2 points for your ref.
- if you have enough disk space, you may uncheck Compress File before saving next time
- always well maintain the original duf file before saving as any type of "presets" or "scene-subset"
Good luck !
...yeah never had this issue using the compress setting before.
Before I save something as a preset (like for poses or wearables, or surfaces) I first save the file itself.
Again usually when you can't move. copy or otherwise access a file, it means it's on a bad sector as usually any information like location on the disk is lost.
Need to be somewhere today but will run a few more Windows diagnostics when I get home as a "hail mary" effort.
Yes, indeed ~ so we only have to cross fingers - never bring bad sectors on our disks !