看到晴空 629 跳出错误的解释现在解决了吗?

FDCSKING

the smart_map 629 error

I got the smart_map 629 error that several posters described and decided to see if I couldn't fix it. I was a programmer for a number of years, and

though I'm very rusty and no nothing about Python programming languages all follow the same basic logic so it was possible to parse what was happening.

The function in question in smart_map is part of a series which determines how far your character is from his current main objective. It's that little

number that tells you that you're X meters from your target destination, the one we probably all ignore. Unfortunately, the function that results in the

629 error isn't isolated; it runs constantly and is called from another function. I tried a few tricks to get it to stop counting the distance, but they

all ended up breaking other interdependent smart_map functions. They *really* want a valid number for the local job variable, and won't accept anything

else, including a command to return out of the subfunction - the fix that Raven usually uses. That subfunction *has* to produce a valid number because

it's comparing the value mathematically elsewhere.

It might be possible to turn off the distance meter altogether to avoid the mess, but I didn't try that out. As rusty as I am, that would've been too

much work.

I did, however, determine that the job (current main quest) is being passed a nil value from the savegame file. In other words, instead of a valid value

being saved, no value is being saved. This essentially corrupts the savegame file. Even if you don't save it can still result in a crash, since the nil

value is in memory (which will later be transferred to your savegame, unless you crash first).

The 'fix' is to go back to a previous save (one prior to accepting the current main quest) and install Raven's scripts. You might only have to install

the smart_map script, but I erred on the side of caution and dumped the entire lot in. After installing his scripts, go and get your main quest again.

Everything should play normally from that point on - at least until something else in this incredibly buggy game breaks. Raven apparently corrected the

'nil job' bug in some other part of his scripts when he was trying to fix something else - or, more likely, fixed something up the chain which means the

'nil job' bug doesn't come up anymore.

Note that installing Raven's scripts *after* you get the corrupted save won't work. At least, it didn't for me. The savegame has a nil value for the job

value, and that results in a nil map location which the game doesn't know what to do with (can't measure distance when you only know one point on the

line).

In my game this was 100% reproducible and testable, which tells me that something else in my save is probably already corrupted as well, leading to a

completely predictable set of events.

觉得大致意思是因为出现 975 错误 打了那个scripts补丁之后造成了存档破损等等等..好象之间还有很复杂的关联,不知道哪位有什么办法可以解决吗? 为了进第二张地图好不容易杀了N多的人才刷到增援,没想到刚到商人那里没多久就跳出了,郁闷......

呕心沥血

装阵营MOD……

我就就是靠那个解决掉629错误的……玩爆机了现在