Monster Truck Stunts PC simulator

Hello everybody =) We have finished coding a little driving game with great car dynamics, break-into-pieces crashes, etc. I was wondering if anyone would bother checking it out and give us impressions and suggestions for a future release. http://www.3impact.com/Monster_Truck_Pc_Game/index.htm Steve

"Steve" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (11 lines)

> Hello everybody =) > > We have finished coding a little driving game with great car dynamics, > break-into-pieces crashes, etc. > > I was wondering if anyone would bother checking it out and give us > impressions and suggestions for a future release. > > http://www.3impact.com/Monster_Truck_Pc_Game/index.htm > > Steve

Looks fun, but the win98 demo version locks my PC solid every time I try hit the "configure controls" button. It goes right past a screen (probably the assignment screen) and immediately to the "success" screen and locks up there, requiring reset/scandisk. I can shut it down via the task mgr if I run it in windowed mode. Running 98SE with DX9.0b and all background progs shut off except explorer, systray, zonealarm and point32 (MS optical mouse), with a GF4 Ti4400 & 45.23 whql drivers. Can it not handle DX9? SB

"Steve Blankenship" wrote... > Looks fun, but the win98 demo version locks my PC solid > every time I try hit the "configure controls" button. > It goes right past a screen (probably the assignment > screen) and immediately to the "success" screen and locks > up there, requiring reset/scandisk. Not quite, try pressing your throttle a little and hitting alt-tab... I was able to exit full screen mode and kill it via taskmanager (WinXP) > I can shut it down via the task mgr if I run it in windowed mode. > Running 98SE with DX9.0b and all background progs shut off except > explorer, systray, zonealarm and point32 (MS optical mouse), with > a GF4 Ti4400 & 45.23 whql drivers. Can it not handle DX9? It can't handle split axis and even with my MOMO pedals set to combined it doesn't recognise them (but I can configure something else instead). Controller configuration does appear to be rocket science(*). I'll comment on other aspects when I've played it some more. Jan. =--- (*) Rem.: You reading this Ash? -You could make a nice buck consulting on this subject methinks.

> "Steve Blankenship" wrote... > > Looks fun, but the win98 demo version locks my PC solid > > every time I try hit the "configure controls" button. > > It goes right past a screen (probably the assignment > > screen) and immediately to the "success" screen and locks > > up there, requiring reset/scandisk. Thank you for your response :) There is a possible explanation for the problem you encountered. Control configuration system works as follows: 1. check if any input device (keyboard or joystick-like) is sending input 2. if so, assign that input to the currently edited control (steer left, steer right, etc) The problem raises when you have an input device that is constantly triggered, for example the throttle pushed. As soon as you enter the config panel, the always-triggered control is assigned to steer left, and the 'success' screen is displayed until you release that control. You should be able to unlock the system by finding the always-triggered control in your attached devices, if any.

"Steve" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (26 lines)

> > "Steve Blankenship" wrote... > > > Looks fun, but the win98 demo version locks my PC solid > > > every time I try hit the "configure controls" button. > > > It goes right past a screen (probably the assignment > > > screen) and immediately to the "success" screen and locks > > > up there, requiring reset/scandisk. > > Thank you for your response :) > > There is a possible explanation for the problem you encountered. > > Control configuration system works as follows: > > 1. check if any input device (keyboard or joystick-like) is sending > input > > 2. if so, assign that input to the currently edited control (steer > left, steer right, etc) > > The problem raises when you have an input device that is constantly > triggered, for example the throttle pushed. As soon as you enter the > config panel, the always-triggered control is assigned to steer left, > and the 'success' screen is displayed until you release that control. > > You should be able to unlock the system by finding the > always-triggered control in your attached devices, if any.

Thanks for the response, but no luck here, using a Logitech Wingman Formula non-FF wheel (w/4.11.30 drivers only; no profiler). No matter what I try (all controls released, or slight pressure on the throttle or wheel), it locks solid when I try to configure the controller. As for it "sending input", I tried both combined and separate axis for the pedals, and used DXTweak to increase the deadzone of all axes to ensure nothing was getting activated at rest, but it still locks up. Logitechs are common wheels, and I've used mine with LOTS of different games/sims. While some simpler games don't recognize the pedals on separate axes, they work fine with the axes combined, and none (until now) have locked up my PC when configuring the controls. I looked for a controller settings file to see if I could edit it pre-start and thus bypass the problem, but didn't find an appropriate one. You might want to rethink your controller assignment routines. For what it's worth, it's very common for sim-drivers to have their throttle and brake on different axes, and also to have zeroed out the deadzone of all the axes for added precision, particularly the X-axis used for steering. So you should be able to accommodate some constant input and more than just the X & Y axes; Logitech uses Z and Rz for the pedals when they're separated, for instance. I've deleted the demo for now; let us know if you get it sorted and I'll have another look. Thanks, SB

This was my problem as well. As long ass I found what axis was off nuetral position I was able to calibrate my tsw2. > > The problem raises when you have an input device that is constantly > > triggered, for example the throttle pushed. As soon as you enter the > > config panel, the always-triggered control is assigned to steer left, > > and the 'success' screen is displayed until you release that control.

We have found that some wheels actually send output as if a control is triggered, even if it is neutral. For example a Logitech Wingman Formula FF may be seen by the system as if the reverse pedal is pushed. We'll try to add a timeout to the config system, so that some controls can be excluded/ignored if necessary... Any opinion about the game itself? Physics, playability... Thank you again for your time.

I have MS SideWinder Wheel Force Feedback and Logitech Wingman Extreme Joystick and everthing worked perfectly. Just letting you know. As for car physics and crashes I must say they are G-R-E-A-T!! VERY nice game! Too bad evaluation time is two hours only... -- Magher