I have absolutely no idea why it choses to MAV, I almost scrapped the project it happened on when i stumbled on the cause.
I suspect its something to do with how memory is protected between win98 and winXP.
Also, I beleive something in the way blitz works doesnt like it when the VEH.Vehicle type gets modified, so when NEXT is issued, it gets confused and chucks up.
I can't think of anything else. Getting a MAV on a NEXT line should never happen anyway :/
I really hope it can be fixed man. Your demo totally kicks ass!
[edit]
and Nope, it doesn't sound like this is a problem, Just make sure all the Types that your functions are using have them set to local wherever possible.
I suspect its something to do with how memory is protected between win98 and winXP.
Also, I beleive something in the way blitz works doesnt like it when the VEH.Vehicle type gets modified, so when NEXT is issued, it gets confused and chucks up.
I can't think of anything else. Getting a MAV on a NEXT line should never happen anyway :/
I really hope it can be fixed man. Your demo totally kicks ass!
[edit]
and Nope, it doesn't sound like this is a problem, Just make sure all the Types that your functions are using have them set to local wherever possible.