mcadamico said:
Has ANYBODY had success with the offset: offset 0042432a error?
Not that I've heard, sadly.
We're still collating, but TiLT has come the closest as per the note in segmentor's thread.After another reinstall, segmentor went from that offset error to his original, 0018273e, so we're still looking into these offset errors. We've been running ProcMon at various times (at game load until crash, and when reinstalling the patch) which showed us some rather interesting results, although nothing so interesting we've been able to turn it into a useful tactic against the errors.For example, at game load, segmentor's machine keeps trying to reference things it can't find, which return errors. My (working, v1.3) version of the game doesn't have these errors and manages to load nicely. We also discovered the last time he tried installing the patch, it only ran for less than 10 minutes before exiting (but the process brings up the 'Finish' dialog like it
has completed fine). At this stage, we're not sure if this stuff is significant or not, but I'm damn suspicious of the time it's taking his machine to run the patch. It
looks like it tries to modify a whole bunch of game files, but if it's not completing those tasks properly then it would make sense the game's system files would be corrupt or unuseable. Basically, we're still collating our ProcMon results and bouncing ideas back and forth. If you'd like to try running ProcMon, give it a shot, it may flag some commonality between these failures. uh, but don't try uploading or posting the logs, as they can run into the tens of MB.