well, i think i found the problem.
SpySweeper (perhaps the memory shield)
combined with some unnecessary collision detection
every 10-15 seconds or so, spysweeper shows up in task manager taking up 15 percent of processor. disk makes a head moving sound, and blitz pauses for a split second.
It's very interesting that it doesn't happen for other people's setups.
jhocking: i wrote a game a long time ago in AMOS that used the mouse, it was good that way, and i might do it that way. on the other hand, you can see where you are aiming because the bullets go there, and you just stream them out. it means less to think about - aiming the car *and* the crosshairs turns out to be a little more cumbersome, at least for mouse/keyboard combination. for joystick/mouse, it's a little easier.
thanks for trying it and your help!
SpySweeper (perhaps the memory shield)
combined with some unnecessary collision detection
every 10-15 seconds or so, spysweeper shows up in task manager taking up 15 percent of processor. disk makes a head moving sound, and blitz pauses for a split second.
It's very interesting that it doesn't happen for other people's setups.
jhocking: i wrote a game a long time ago in AMOS that used the mouse, it was good that way, and i might do it that way. on the other hand, you can see where you are aiming because the bullets go there, and you just stream them out. it means less to think about - aiming the car *and* the crosshairs turns out to be a little more cumbersome, at least for mouse/keyboard combination. for joystick/mouse, it's a little easier.
thanks for trying it and your help!