Quest Script Corruption?

[Radioactivelad]

Working on a Companion mod and twice now I've had this bizarre issue where my Quest Script has something happen to it; I don't know what else to call it than corruption.

 

I'll launch in to the game to test features and suddenly find that nothing is working.

Going back to the geck, I'll see that In the Quest Script box, the Script's name will have suddenly become gibberish.

 

The contents of the script (even the name) are completely unaffected, and saving the script under a new name immediately resolves the issue.

 

The script itself is also nothing more than a bunch of shorts I use for condition checks.

 

I haven't really used Quest Scripts extensively before this, so Is this unusual and/or am I doing something wrong?

 

Edit: Forgot to mention the strangest thing: If I revert to one of the automatic backup esps, like hours old, the quest script will still borked.

Edited April 18, 2019 by Radioactivelad

[dubiousintent]

I would suggest you look into the possibility of either bad RAM (Memtest) or Disk space errors (ChkDsk).

 

-Dubious-

[Radioactivelad]

Yeah Memory sounds like a sure bet, given another odd, unrelated issue I noticed:

 

Certain interiors like the Goodsprings Saloon would suddenly this severe microstutter similar to the infamous 64hz bug, wheras earlier in the day there was none.

 

If I unlocked the framerate, it curiously stayed at exactly 75fps, whereas interiors where this issue wasn't presenting itself would be well over that.

 

The Stutter Remover does fix the issue, but given I don't *need* the SR for this problem till later in the day tells me there's an underlying issue.

 

I won't be able to know for sure for a couple weeks as I don't have a spare usb stick for Memtest around at the moment.

Edited April 18, 2019 by Radioactivelad