Repair bug?

[Deadboss]

There appears to be a major bug during the A10 campaign, not sure if it is isolated to the A10 as it is the only one I have tried thus far.

 

The first problem I encountered is that the plane does not reset itself. For example, if there was major wing damage and I make it to the airfield, refuel/rearm/repair, then go to take off again, the plane will still fly off-center.

 

The second issue was when my plane incurred major engine damage. It was on fire and it burned the entire way to the airfield as I did not know the hotkey for the fire extinguisher. Managed to repair, but when I went to startup the left engine it just hung around 3000 rpm and would not move from there. Tried to force the right engine, would not work.

 

I then took drastic measures and started the right first, let it warm up, then started the left. Unexpectedly the left engine started, but it was still majorly damaged and would not go above 3000 rpm. As such, the plane was rendered useless.

 

These issues span across multiple missions in the campaign, so basically you have to commit suicide to reset your plane. Trimming the wings and rudder is an option, but one that slows you down and should not be necessary. I repaired, I should have a 100% clean plane.

 

I have watched and read several tutorials on the repair/refuel procedures, so I am fairly certain that I am doing everything correctly. However, the lack of any hits on google about these issues raises questions. If you suspect I am doing anything wrong please let me know.

[AtaliaA1]

I looked at the lau. and couldn't find a key command to re-spawn.

 

Maybe a tester can tell you/us. I've seen it for the A10C somewhere but can not remember.

[Deadboss]

So I made a replay of me going to the battlefield quickly, getting shot up (left engine failure), repairing, and attempting to takeoff. Don't want to spoil the ending, but it didn't go so well.

 

Hint: Use acceleration to skip past boring parts.

Repair Bug.trk

[Deadboss]

So... any devs want to chime in on this? Known issue? Working on it? Problem with DCSW or isolated to A-10A module? Possible work-around? Planning to fix it? Et cetera.

 

A simple response goes a long way to letting your customers know you give a damn... :music_whistling:

[Filament]

The second issue was when my plane incurred major engine damage. It was on fire and it burned the entire way to the airfield as I did not know the hotkey for the fire extinguisher. Managed to repair, but when I went to startup the left engine it just hung around 3000 rpm and would not move from there. Tried to force the right engine, would not work.

 

I then took drastic measures and started the right first, let it warm up, then started the left. Unexpectedly the left engine started, but it was still majorly damaged and would not go above 3000 rpm. As such, the plane was rendered useless.

 

 

Deadboss,

 

I'm not a developer, but I've experienced the same thing (engine spools to only 3000rpm). I've learned that if you try to start the port engine first [ALT+ HOME] you'll experience that - and if you then try to shutdown the port engine [ALT+END] and start the 'correct' one first (starboard - CNTRL+ HOME) - the 'damage' is done. The problem will persist.

 

I always make it a point to do the starboard one first (CNTRL+HOME) and haven't seen the problem since. In fact, I make the starboard engine 'priority' for starts and shutdowns - last to shutdown, first to start up.

 

I can't comment on the other things you mentioned, as I haven't seen them.

 

Clear skies...

Edited October 18, 2013 by Filament