Problem with DR's Readables Editor

[grayman]

This is a DR problem, long ago solved, but having just moved files around during my recent upgrade, I'm running into it again.

 

I have an existing readable with an existing text and an existing XData name.

 

When DR opens the readable, it doesn't complain, but when I edit the text and save it, I get this message:

 

"You have imported an XData definition that is contained in a pk4, which can't be accessed for saving."

 

If I give it a new XData name, it lets me save, and I can look in the *.xd file and find both the old text and the new text, under the old XData name and the new XData name.

 

Now, if I open the readable again, edit it, and save it, I get the same message, even though it's using the second XData name. I have to give it a third XData name to get it to save.

 

This has been working fine for years, but something appears to have gotten lost during my upgrade.

 

Any help is appreciated.

 

Thanks!

[nbohr1more]

Here's an old thread:

 

http://forums.thedarkmod.com/topic/14083-trying-to-edit-a-readable-getting-this-error/

[nbohr1more]

Hmm.

 

This is happening in 2.0.2 ?

[grayman]

yes

i can't check atm, but i'm betting the mod base in the xdata setting doesnt get updated when you move the mission and redefine the mod base in the game window to the new location.

 

ack! can't find where that info is kept.

[grayman]

Bugtracker down, so I can't read the supposed fix applied 3 years ago.

 

 

Read the bugtracker issue, problem fixed back then, but I can't tell what's going on now.

[Bikerdude]

Does the issue happen in DR 1.8.1..?

[grayman]

Does the issue happen in DR 1.8.1..?

 

I don't know, and I won't be bringing 1.8.1 up. This was working fine when the mission was on the C: drive a couple weeks ago. Now that it's on the D: drive, and even though I reset the 'game' settings, DR isn't happy about the move.

[grayman]

I reinstalled 2.0.2 and the problem persists.

[grayman]

I moved my mission folder from the D: drive to the E: drive so it would be on the same drive as the darkmod folder (as it was two weeks ago), and the problem went away.

 

There's some type of problem with Mod and Mod Base being on different drives. ??