Burchard Eye Problem...Anyone Have This Happen? --SOLVED--

melaniemelanie Posts: 793
edited November 2022 in The Commons

Before I put in a ticket, I'm just wondering if anyone has had any problem getting Burchard to load without an error message that an eye texture is missing. The "missing" texture is there, but for some reason, it won't load with Burchard. I found the file in the correct place, but my DAZ Studio can't seem to find it. If I click through the error messages, he loads and his eyes seem to render all right, but I'm just wondering if anyone else had had this problem. My sister has the same problem with her Burchard on her computer as well. I even tried to uninstall him and reinstall him, but this continues to happen. I've used him in the past, and I don't remember this happening. I haven't seen any other threads here in the forum about this. The missing file is:  runtime/textures/Emrys/Burchard/BurchardEyesB_1006.jpg

If I locate it and find it, it still gives me the message, but he will lead and his eyes do render all right, but that's a lot of work to get him to come in.

Post edited by melanie on

Comments

  • NorthOf45NorthOf45 Posts: 5,533
    edited November 2022

    Sounds like another "//Runtime" syntax error in the character preset and/or one or more of the materials presets. It was either ignored or undetected before DS v4.20 and has occurred a number of times with certain PA's. Yes, it wil ltake a ticket to get an official correction. You can correct it yourself with a few quick edits of the .duf file(s). Replace the "//Runtime" with "/Runtime" and save.

    ETA: Confirmed. Three occurrences each in "Characters/Burchard.duf" and "Characters/Burchard/Materials/Burchard All Maps.duf"

    Post edited by NorthOf45 on
  • melaniemelanie Posts: 793

    Thank you. I'm not sure how to edit a .duf file, so I think I'll put in a ticket. I just wondered if anyone else had the same problem.

  • NorthOf45NorthOf45 Posts: 5,533

    They are simple text files, sometimes compressed. These are not, so just use your favourite text editor to replace the errant code. Put in the ticket anyway, it's the only official way to get it changed for everyone else.

  • melaniemelanie Posts: 793

    I've never worked with these files, so I don't know where to find them. I did put in a ticket a few moments ago.

  • NorthOf45NorthOf45 Posts: 5,533

    In the Content Library, right-click on the .duf file icon. Select "Browse to File Location". This will open a file explorer window, in a folder where you can find the actual files. Just right-click and select "Open with..." or drag it onto a notepad session (or whichever editor you prefer), or whatever gets it into the editor. Search for the "//Runtime" string and change it to "/Runtime". Save and you're done.

    It could literally take weeks or months for the ticket to be actioned.

  • melaniemelanie Posts: 793

    NorthOf45 said:

    In the Content Library, right-click on the .duf file icon. Select "Browse to File Location". This will open a file explorer window, in a folder where you can find the actual files. Just right-click and select "Open with..." or drag it onto a notepad session (or whichever editor you prefer), or whatever gets it into the editor. Search for the "//Runtime" string and change it to "/Runtime". Save and you're done.

    It could literally take weeks or months for the ticket to be actioned.

    Well, I tried this, found the line with the double slash, deleted the extra one, and saved it, but it didn't work. I even rebooted my computer in case it didn't recognize it, but nothing. It's still giving me the error message. Bruchard does come in, but not iwthout that error message looking for that file, even though it's there. So I don't know what the problem is. I did put in a ticket for it, so I guess I'll wait until they get around it.

  • NorthOf45NorthOf45 Posts: 5,533

    melanie said:

    NorthOf45 said:

    In the Content Library, right-click on the .duf file icon. Select "Browse to File Location". This will open a file explorer window, in a folder where you can find the actual files. Just right-click and select "Open with..." or drag it onto a notepad session (or whichever editor you prefer), or whatever gets it into the editor. Search for the "//Runtime" string and change it to "/Runtime". Save and you're done.

    It could literally take weeks or months for the ticket to be actioned.

    Well, I tried this, found the line with the double slash, deleted the extra one, and saved it, but it didn't work. I even rebooted my computer in case it didn't recognize it, but nothing. It's still giving me the error message. Bruchard does come in, but not iwthout that error message looking for that file, even though it's there. So I don't know what the problem is. I did put in a ticket for it, so I guess I'll wait until they get around it.

    You are on the right track. There are three occurrences per file, not just the first one. One more try, you'll get it...

  • melaniemelanie Posts: 793

    Okay! I found two other occurrences in that file and fixed those. IT NOW WORKS! YAY! Thank you, NorthOf45!!! You were a great help!

  • NorthOf45NorthOf45 Posts: 5,533
    edited December 2022

    Great! Now, the "Burchard All Maps.duf" will have the same problem, if you ever apply the texture separately at some point in time.

    Post edited by NorthOf45 on
  • melaniemelanie Posts: 793

    I guess I'll worry about that if it ever comes to that. I'm just glad that annoying error message is gone. smiley

Sign In or Register to comment.