I think I'm getting this too.
This (~1.8MB) used to work fine on my old system (Duron/GF2MX/DX9c same OS install) it also works okay on a couple of AthlonXP systems (one with a GF4 and the other with a FX5200).
Since I've upgraded however, I'm getting the same symptoms as described by DocFritz.
From the IDE, the program runs fine in debug but errors out with a MAV and points to the scenery collision section if I fly through a 'tight section'. When debug is off or if running standalone I get a MAV as soon as I move.
At first I thought it may be some sort of DEP issue, but it runs okay on my daughters system (A64, XP Pro SP2, Radeon 9800Pro (Cat 5.1), DX 9.0c).
Strange, no?
Is anyone else getting this?
[edit]
oh...The keys...arrow keys to move, Tab for debug, numpad and T.
I wont bother posting code until someone confirms the error as it's rather long and It may just be my flakey install of XP.
[/edit]
[edit again]
BTW...It works on my system if I comment out the ImagesCollide() calls.
[/edit again]
This (~1.8MB) used to work fine on my old system (Duron/GF2MX/DX9c same OS install) it also works okay on a couple of AthlonXP systems (one with a GF4 and the other with a FX5200).
Since I've upgraded however, I'm getting the same symptoms as described by DocFritz.
From the IDE, the program runs fine in debug but errors out with a MAV and points to the scenery collision section if I fly through a 'tight section'. When debug is off or if running standalone I get a MAV as soon as I move.
At first I thought it may be some sort of DEP issue, but it runs okay on my daughters system (A64, XP Pro SP2, Radeon 9800Pro (Cat 5.1), DX 9.0c).
Strange, no?
Is anyone else getting this?
[edit]
oh...The keys...arrow keys to move, Tab for debug, numpad and T.
I wont bother posting code until someone confirms the error as it's rather long and It may just be my flakey install of XP.
[/edit]
[edit again]
BTW...It works on my system if I comment out the ImagesCollide() calls.
[/edit again]