Stug engine bug - please answer if possible

[AHWULF]

If you get this error (where StugG or Daimler or other engines gets stuck starting).

(1) Speed/type of your CPU (ie Intel i7 2.8)

(2) Status of engine when you turned it off before getting the bug next start up (in gear, high revs, reverse) or say you get it on spawn

(3) Type of vehicle (StugG, etc)

(4) Did it happen more than once in a row during one run of the client or does it just happen randomly

(5) Keyboard control or joystick

(6) During gameplay, anything unusual you did right before the bug happens

(7) And FPS oddity during the engine start sequence.

(8) Were you ever hit at all (even a bullet) before the bug happens.

I think there is something we are missing that helps trigger the bug. It isn't as easy to reproduce by mashing keys or multiple engine start settings. It appears to be more common online during gameplay rather than offline testing. It's not common but sometimes you get it over and over and then never again. It can happen on both PC and Mac so it's not platform or compiler related.

It's possible it has to do with a physics loop being skipped or going over (physics in the game runs every 20ms) or something. For this to happen something unusual must have occurred though since it doesn't happen to everyone all the time.

This is like the concussion bug, two unrelated things coming together to form the bug.

It appears that the engine becomes stuck with the starter running but the engine has either not caught yet or gets into a caught/uncaught endless loop. The starter is running when you see the starter smoke clouds.

Edited September 6, 2011 by BLOO

[dotsie]

Im thinking the following might be important too.

- Is your engine start, on a secondary keymap.

[dotsie]

(1) Intel E8400 clocked to the brink.

(2) I always just engine off from a high gear, then brake.

(3) Only StugG for me

(4) Seems random, I dont tank much anymore but got it twice in a few hours the other day when i did stug.

(5) Jstik for levers, pedals, gears. KB for engine, reverse and views.

(6) Nope, often not near combat, just spying a town from afar with comm, hit driver, start and locked up.

(7) This game is one big oddity.

(8) No usually far and unengaged. But thats how a stug should be IMO so thats what im ding 90% of the time.

(-) I use a secondary keymap to start my engine (DELETE)

PS.

I thought i saw someone post the 3B and 3G had the same engine. Would it not be prudent to just swap the 3B code into the 3G.

Edited August 25, 2011 by dotsie

[murhis]

(1) E6600

(2) Normally I hit the gears/break down and turn off the engine. Though this have happened right after I've spawned and turned the engine on.

(3) Stug3G mostly, Stug3B and Tiger as well, but very rare.

(4) It have happened 3 times at the most on the same game session.

(5) Keyboard + MB. Engine related stuff on the keyboard.

(6) It varies from spawning from AB to trying to get the engine on in heat of the battle

(7) Can't be sure. Nothing that I've noticed.

(8) No

Edit: btw. one thing to add: My ping is over 200 most of the time. Being a finn down sides.

Edited August 26, 2011 by murhis

[AHWULF]

I found I can alter 1 line of code and get this bug to happen in any engine. Beginning to wonder if it's like the concussion bug, somehow one piece of engine data is corrupted or written over.

[noons]

Totally random and only the DAC for me being allied.

I have a e6600 ping over 200. Can't remember shifting down gears I think I just shut engine off. Use keyboard for engine and joystick/mouse for other control.

I always thought it was engine damage (enemy) that caused it but after reading this thread and others I felt compelled to post.

[petie]

i5 760 at 3.6 Ghz

sometimes get it on spawn, some when engine off whilestillin gear(no revs)

mostly stug g, happens on all vehicles to me on the spawn in bug type

never had more than once in row,have in same gaming session though

keyboard for engine, joystick for rest

not sure

no

no

and my ping always above 200 also

[monsjoex]

(1) Speed/type of your CPU (ie Intel i7 2.8)

Intel Q66600 Core Quad 2.4Ghz

(2) Status of engine when you turned it off before getting the bug next start up (in gear, high revs, reverse) or say you get it on spawn

All times i got it in the laffy were at spawn.

Stug g at spawn and in field.

Ehm i press E then i go full W then i go a gear up.

Stopping procedure is pressing S to break hard and gas down. At the same time i press E to turn off engine.

(3) Type of vehicle (StugG, etc)

Laffy, stug g that i can remember

(4) Did it happen more than once in a row during one run of the client or does it just happen randomly

Randomly

(5) Keyboard control or joystick

Keyboard control.

(6) During gameplay, anything unusual you did right before the bug happens

No.

(7) And FPS oddity during the engine start sequence.

No

(8) Were you ever hit at all (even a bullet) before the bug happens.

1/2 the times were on spawn, the rest of the times maby, probably not.

And i'm from europe so high ping.

[AHWULF]

Not likely ping involved directly as you can get it offline. However if there is a random component that triggers the bug anything could change the environment.

[monsjoex]

As i said in my PM ahwulf:

The method of keymapping the engine button to keyboard and mouse and then pressing them at the same time gives repeatable results without any random factor.

However the ingame problems are random. But they might come from the same problem: the key inputs get messed up and make the tank go into a loopmode. Ping/packet loss could be a problem then no?

[ghost]

1: amd athalon 64 x2 5000+ @ 2.98ghz

2: in gear

3: stugG

4: random

5: both. kb controls position select, engine start/stop, and transmission. js does the rest.

6: no

7: no

8: not that i know of.

[AHWULF]

Thanks for the inputs. I know what's wrong but fixing it is tricky. My first attempt at a fix created a tank running at 6 Billion RPM which caught fire and blew up. An R35 is not a dragster :-)

[ghost]

My first attempt at a fix created a tank running at 6 Billion RPM which caught fire and blew up. An R35 is not a dragster :-)

i bet that was fun to watch lol

did it do a wheelie? or, err, a trackie?

[petie]

Thanks for the inputs. I know what's wrong but fixing it is tricky. My first attempt at a fix created a tank running at 6 Billion RPM which caught fire and blew up. An R35 is not a dragster :-)

LMAO

Bet you could make some really funny Video's getting the equipment to do some weird stuff

[AHWULF]

It starts in top gear, does a bit of a trackie then drives like mad for a bit before it blows up. One time I got an A13 to fly straight up when it hit an obstacle. Simulating reality is a fine line between a reasonable approximation and insanity.

[GOPHUR]

This is noted as FIXED in Beta. Awaiting confirmation.