Quote:
|
Originally Posted by legs37
Also, as Markus suggested, I submitted my League .dat files to him and apparently he was able to sim without a hitch. So he suggested updating DirectX and video drivers (did it), turn off sound (did it), turn of 3D (did it), set to OOTP Browser (did it) ... damn near cried when the game died immediately upon clicking 'sim' !
|
Well that's frustrating even to hear. I'm no PC Tech and unfamiliar with the game's engine process, but the fact that another user (in this case Markus) had success using your .dat file certainly points to something user/location specific.
What I'm wondering (for those of you who know operating systems) is whether there is any kind of .log - like the bootlog for specific program operation where the sequence and order of processing could be examined to determine at which point - command-related - (not just the fact it's when SIM is selected) the function breaks down. Is there such a record, or could any sort of script be created to record the processing?
And the thought crossed my mind that somewhere in that sim-selection the mouse click or some oddity like that may trigger an IRQ interruption or such. I remember having a problem awhile back with another game that everything was fine until I actually clicked with the mouse or pushed a controller button. Certainly a remote relationship, but looking into all the corners.