Error Opening File

Comments

• Richard Haseltine Posts: 108,149

  July 30

  That looks like a compression issue, possibly due to a file system glitch. You may be able to recover it with some kind or archive repair tool (by default scenes are compressed, usinf GZ format I believe) but nothing is certain. I would suggest making sure the compression option is off when saving scenes.
• IceCrMn Posts: 2,319

  July 30

  7zip can decompress daz studio files

  go here and selct the version you need Download

  Most likely the 64 bit Windows version https://www.7-zip.org/a/7z2500-x64.exe
• wondergracyanne Posts: 29

  July 30

  IceCrMn said:

  7zip can decompress daz studio files

  go here and selct the version you need Download

  Most likely the 64 bit Windows version https://www.7-zip.org/a/7z2500-x64.exe

  Hey man, I really appreciate you going out of your way but I think this file is cooked. 

   

  When I extract it, it says "unexpected end of data." and when I open it, same problem.Expects a comma or ] but doesn't find one. I tried your method on other files, though. So, I can pocket this as a method in the future.

  Suuucks that this had to happen though.
• wondergracyanne Posts: 29

  July 30

  Btw, I opened the file with Notepad++ 

   

  `Json Parser (1685915,30): Syntax Error - expected ',' or '}'` 

   

  Was a line that stuck out.

   

  I went to that line and I did not see a ',' or a "}" out of place.
• RuudL Posts: 226

  July 30

  While in Notepad++ goto menu Language>J>Jason  On the leftside, where the linenumbers are, you'll see fold and unfold symbols ('-' and '+') You can check the validity of each segment by closing and opening it using those symbols.

  The last line of the file must be a line with only a closing bracket.
• Richard Haseltine Posts: 108,149

  July 30

  IceCrMn said:

  7zip can decompress daz studio files

  go here and selct the version you need Download

  Most likely the 64 bit Windows version https://www.7-zip.org/a/7z2500-x64.exe

  Yes, but what is needed is a tool to repair them (if possible).
• Richard Haseltine Posts: 108,149

  July 30

  RuudL said:

  While in Notepad++ goto menu Language>J>Jason  On the leftside, where the linenumbers are, you'll see fold and unfold symbols ('-' and '+') You can check the validity of each segment by closing and opening it using those symbols.

  The last line of the file must be a line with only a closing bracket.

  Depending on where the file breakage lies there may be any number of close brackets/curly brackets missing - and just adding them wouldn't fix the issue, and might well not even alow the file to be opened.
• IceCrMn Posts: 2,319

  July 30

  yea, 7zip I don't think can repair them just decompress them. I really don't know as all I've ever used it for was comperssing or decompressing files. I've litteraly never had the 7zip file manager open in all the years I've used it.

  I never compress my Studio files anymore. Iearned the hard way many years ago that it leads to lots of issues so stopped doing it and just bought ever larger storage. The 4TB Westerndigital "My Book" is great for this hobby.

  If the OP is on Windows, there is a file backup buitin to it that can make iterative backups of folders. Maybe that can be an option for backups?

  I don't use it myself, but I hear good things about it.
• wondergracyanne Posts: 29

  July 30

  RuudL said:

  While in Notepad++ goto menu Language>J>Jason  On the leftside, where the linenumbers are, you'll see fold and unfold symbols ('-' and '+') You can check the validity of each segment by closing and opening it using those symbols.

  The last line of the file must be a line with only a closing bracket.

  There was no closing bracket at the end, so I put one in. Oddly enough I got the same error, same line.

   

  This is line 1685915 and 2 subsequent lines after: 

  "label" : "Metallic "current_value" : 0,

  "enum_values" : [ "PBR Metallicity/Roughness", "PBR Specular/Glossiness", "Weighted" ]

  },

   

  Everything honestly looks fine. I don't see where a comma is needed unless there needs to be a comma between Metalic and current value.
• crosswind Posts: 9,579

  July 30 edited July 30

  From the coding you posted above,  at least there needs to be a comma in between "Metallic" and current_value, i.e.

  "label" : "Metallic ",
  "current_value" : 0,
  "enum_values" : [ "PBR Metallicity/Roughness", "PBR Specular/Glossiness", "Weighted" ]
  },

  Edit: yeah, and that " I missed !

  Though these codes still looks weird to me (Metallic should be Base Mixing) ...,  you can give it a try firstly. But be noted, in my experience of fixing corrupted file, you might further see next syntax error then.... Just see what will happen.

  Post edited by crosswind on July 30
• RuudL Posts: 226

  July 30

  "label" : "Metallic",
  "current_value" : 0,

  All strings (labels and textvalues) must be quoted with double quotes. Numerals unquoted.
• wondergracyanne Posts: 29

  July 30

  Hi Crosswind, I had chatGPT write a script to replace the "Metallic" with "Metallic", but at the end of the file I ran into this : 

   

  "

  "channel" : {

  "id" : "Metallic Weight",

  "type" : "float",

  "label" : "Metallic""c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "c "

  }

   

  I thought it was trying to write "current file" so I replaced it with : 

   

  {

  {

  "channel" : {

  "id" : "Metallic Weight",

  "type" : "float",

  "label" : "Metallic","current_value": 0

  }

                          }

                          ]

                          }

                          ]

                          }

                          ]

                          }

   

  Syntax was accepted by JSON editor online , opened it and... Nothing. Daz log won't even give me a reason anymore, just "Operation failed"

   

  Tried reloading Daz and opening, nothing.

   

  Even had chatGPT give it a look. 

   

  My interpretation is that there were other surface texture data settings that didn't make it in and the malformed string at the end was a sign of that.
• wondergracyanne Posts: 29

  July 30

  Thank you both for your help, but I'm just gonna remake the render. 

  This file is cooked. xD
• crosswind Posts: 9,579

  July 30 edited July 30

  Yup, that is like what I mentioned, the file might be further corrupted... The codes above seems incompleted. Is it possible that you attach the DUF file down below ? so that we may help to check ~~

  Post edited by crosswind on July 30