read a duf & an error log
alan bard newcomer
Posts: 2,227
merging an file into a scene .. about 5 seconds to error and then: Check the error log for details.*
------
2022-09-04 11:40:42.376 [INFO] :: Prepare asset load (merge): /00 bldgs 2022/02 2021 rwHouse2020.duf
2022-09-04 11:40:42.396 [INFO] :: Locking viewport redraw...
2022-09-04 11:40:42.396 [INFO] :: Viewport redraw locked.
2022-09-04 11:40:43.444 [INFO] :: Native format content directories: 121
2022-09-04 11:40:43.445 [INFO] :: Poser format content directories: 96
2022-09-04 11:40:43.445 [INFO] :: Other import format content directories: 0
2022-09-04 11:40:43.445 [INFO] :: Begin asset load (merge): /00 bldgs 2022/02 2021 rwHouse2020.duf
2022-09-04 11:40:45.016 [INFO] :: JSON interpreter warning: Unexpected number in array: 83
2022-09-04 11:40:45.034 [INFO] :: E:/00 buildings/00 bldgs 2022/02 2021 rwHouse2020.duf (554536,6): Syntax Error - expected '}' or '"'
2022-09-04 11:40:45.124 [INFO] :: Error loading asset: E:/00 buildings/00 bldgs 2022/02 2021 rwHouse2020.duf
2022-09-04 11:40:45.124 [INFO] :: Operation failed
2022-09-04 11:40:46.712 [INFO] :: Unlocking viewport redraw...
2022-09-04 11:40:46.712 [INFO] :: Viewport redraw unlocked.
-----
022/02 2021 rwHouse2020.duf (554536,6): Syntax Error - expected '}' or '"' IS the (554536,6) an idication of where the error is?
---
I can edit the duf file in NotePad ++ and if I knew where to look I might beable to find the missing bracket?
---
* I successfully loaded an earlier version of the file from the same folder ... so I'm pretty sure it's an internal error in the duf rather than a file path error etc.
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
The numbers are line/co;umn - sadly I suspect theya re the very end of the file, I suspect it is damaged in the middle and so won't decompress correctly, beyond a certain point DS just gets gibberish and so can't find the end of the last block it was reading before the corruption. An archive repair tool might help, but even then there would probably be a missing character at some point (though the rror message might give a better idea of where)
It looks like I dodged any loss because the previous save was essentiallly the same file... and the lost one didn't have anything new ... and it turns out there was a larger file from the same day of 3 buildings and it opened and the one that didn't was a subset out of that one.
---
hmm, but just occured to me that even though I don't actively program it was looking specifically for a '}' and a bet they're supposed to come in pairs. and a script parser might pinpoint that.
"
[ 0, 0, 27077, 27856, 27079 ],
[ 0, 0, 27858, 27859, 27087 ],
[ 0, 0, 27858, 27087, 27083 ],
83 ],
[ 0, 0, 27081 27858 ],
[ 0, 0, 27081, 27858, 27083 ],
[ 0, 0, 27860, 27861, 27091 ],
-----
that looks the line.... and the screen shot shows the one right after the 83 ] is line 554536....
so I will see what happens if I fix that line... the lines above and below both end with 27083 and its an 83 that is floating and the line marked as an error needs a comma and 27083
and the 83] is an unpaired bracket. which is what daz was looking for.
----
interesting that first image doesn't have the line numbers in the notepad++ showing even though they are there in the folder view.
Old eyes.. they're in the clicked view just not in the preview at the bottom on the comment because the preview is limited in width
Image 3 is the repaired duf which has sucessfully loaded.
the corrected line is now 554535 despite the fact that somehow the line above got blueballed by Notepad++
just realized that 35 and 36 are identical and even if that didn't mess up the loading I should probably delete the dup and try again or even better just comment them out. (had to look it up but knew it could be done.