/-/S'pht-Translator-Active/-/ |
Re: Heart of Fusion (user error after all) | ||
Posted By: patrick | Date: 12/18/07 12:02 a.m. | |
In Response To: Re: Heart of Fusion (Forrest of B.org) : Were you the same person who reported this problem over on the Pfhorums? Have
Forrest, No, I've no account at the Pfhorums, I've been following the relevant thread there to be certain that I'm only contributing unmentioned issues/corroborating uncertain issues. However, I've traced this behavior to my non-virginal ~/.alephone --specifically an Eternal_Preferences file tainted by references to Alpha 5 environment data. The problem remains on Heart of Fusion regardless of method of arriving at the level, and there are other (obviously) odd artifacts on a few other levels so far. I assume I'd keep finding odd things happening through out the scenario--but none of it is applicable to the current build. Deleting the prefs file and generating a new one solves the problem. I've checked out another level where I noticed an oddity (a phantom untouchable hunter on May The Pfharce Be With You) and it's returned itself to normalcy as well. I should have recognized this for what it was immediately, as I had encountered this phenomena in the past when installing newer builds of Eternal X next to older ones, assuming that the prefs file would take care of itself in the background. Previously the problem was much more acute--weapons and the like would be unpredictable from the beginning. I had forgotten about it, and this coupled with minimal symptoms in the carry over from Build_Five to Build_Release_Candidate (i.e. the only glaring 'problem' being the breakdown on HoF) meant I misidentified the root of the matter. So, the HoF issue is caused by a 'corrupt' (conflicted, rather) Eternal_Preferences file. Delete it, and one is good to go. I suppose this issue is endemic to *NIX Aleph One's centralized configuration directory coupled with no real version control when one is downloading and playing multiple test builds of the same scenario--a situation unique for end users of your project. I have no reason to doubt that this is the source of the other two user reported instances of this problem. I apologize for muddying the waters needlessly, both for my verbosity here and for my unrigorous investigation that led to my earlier 'bug report.' Regards,
|
|
Replies: |
|
Problems? Suggestions? Comments? Email maintainer@bungie.org Marathon's Story Forum is maintained with WebBBS 5.12. |