merlin851526

Just looking through the logs and there are a ton of warnings and errors. This one caught my eye as it's the action that will crash the game not the mission mind, resulting in a restart. 2018-03-15 13:42:05.235 ERROR COCKPITBASE: Cockpit: Clickable - Wrong connector name PNT-BTN-RWR-UNK Now of course I might be wrong it might be a myriad of factors and not specifically the above. However it's no less frustrating as it's the only Campaign that will do this. EDIT: sorry just checked it's doing it for all my A10 C campaigns. Press the battery switch and crash.

After yesterdays update crashes game when you activate battery at start of first mission. Yeah gona give this a miss methinks.

Many thanks it was doing my head in.

Im sorry I just cant figure this out. I can start up the Harrier no problem. I move the throttle forward pass the idle indent (so to speak) press the Idle cut off switch on the throttle and when I try to put throttle back to idle to slow for taxi the engine shuts down. I'm sorry I know I'm overlooking something simple but I cant seem to understand it, it's driving me insane.

I have easy rudder on and it still spins Grrr.

For the record this is one of the most beautiful aircraft in the game and my favourite. However I'm getting the above mentioned behaviour as well. Have to go to full burners to take off, feels like a heavy WW2 bomber trying to get into the air. Also the aircraft will yaw like crazy even with the auto pilot stabiliser on at random. Moreover the aircraft has a frightful tendency to roll over while stabilised as well from time to time.

12 Gig of ram and always play as admin.

You guys are lucky keeps crashing to desktop on the first mission for me.

This is happening to me quite a bit as well lately. However it's not the Mig 21 that keeps popping up for activation it's the Viggen for some reason and sometimes the F 5 Tiger as well. I've checked my mods in the manager and all are activated.

Thanks for the reply. My Viggen , P 51, A10's both A and C, Mig 15 and 21, F 86 , Huey, Mil-8 and finally FC3 all work without any major problem in 1.5. The only Third party mod I have running in the background is Reshade both for 1.5 and 2.5 I have since disabled it for 2.5 (no change to the non log crash to desktop sadly). Not withstanding the fact that 2.5 is in Beta it's hit and miss whether or not I can get my aircraft to work in it or Nevada. The only one that I can honestly say is 100% consistent is the A 10 C. Hawk and Mil-8 will fail 100% of the time for me.

So far I can not get my Hawk to work in 2.5 nor it seems my Mil -8 they just non log crash back to desktop. Does anyone have a list of module's that actually work in 2.5?

Cannot do a quick mission with 2.5 in Mil. crashes straight to desktops (non log) every time.

TrackIR works for me one minute and then the next it doesn't. Totally intermittent and very frustrating. Have to restart 2.5 and even then its not guaranteed to work. It's not like there isn't enough bugs in this release to be getting on with sigh. No problems with with 1.5. It's really frustrating because Its next to nigh impossible to have a fly around the Nevada map without some issue like this.

How did you get it to work? I cant assign it to anything other than a mini joystick as the axis is identical to my joystick. When I clear them no matter what I do I cant assign it to anything else. For insistence I want to assign it to slew the target seeker in the A 10 but it wont let me.Any advice would be welcome thanks in advance.

Does anyone know how to assign slew for the A 10C to the mini analogue stick on the Thrustmaster TWCS Throttle? For some reason it wont let me assign it to anything other than pitch roll and yaw. It'd acts like a mini joystick which I don't need. Thanks in advance

I've noticed after the last patch that when I work the engine up to 100% before take off the engine will simply shut down sometimes it will fail into the takeoff run as well. Has anyone else encountered this problem or am I missing something on startup?

I too am suffering from the erroneous request for activation for the Mig 21. Which of course means that I cannot use that aircraft now after I just recently updated. The aircraft is visible in the module manager but when I load a campaign all I get is the map. Same thing occurs in instant action.Does anybody have a fix for this ridiculous bug:mad:.

I've sunk the two ships and attacked the AA and at the end of the mission I got the message fratricide as well.:huh:

Well for me it's simply not working and not just the A10C either. I've tried all the other aircraft and the same result, silence:huh:

No I don't think it's anything to do with any texture mod. After the last couple of updates I've noticed this effect as well. Maybe it was there all along I don't know, but it's certainly more pronounced now and I'm not running any texture mods.:(

Went back to the A10C last night played around with the settings custom easy etc. No matter what I tried I still got the above. Non responsive flight and wingmen and as you say Missile magnets.

Ditto

Well I started the install of DCS steam and it finally allowed to to purchase the mod but now the mod is nowhere to be seen it's not showing up in the queue.May have to wait I suppose until DCS is fully downloaded I suppose:(. Which is somewhat inconvenient as I don't need two DCS's sigh.