Rongor

Has anybody flying the A-10C II ever experienced a single engine failure after receiving damage? I did so back then in the A-10C module. Yet since we got the Tank Killer update I ALWAYS lose both engines, never a single one in case I receive combat damage.

parking brake was on, you can see it in the pic

Update after today's OB 2.7.15.25026 patch: -TSD wind display seems correct now, also matching windsocks, which are also showing actual wind direction as expected in real world. -PERF wind vector is still opposite direction, 180° offset to TSD -IHADDS is now displaying TAS on the ground, which seems to be correct. In this setting, wind direction was indeed west (as in coming from the west)

That's the L for laser Hellfire. It doesn't even display the channel in this moment, only if I assume Hellfire control

Like this?

in fact none of the pushbuttons 1 to 15 seem to do anything. I guess a is missing and including this test into the training mission and in the checklist without this advisory could prevent confusion.

If it is not simulated, why then did they include it in the checklist? Without marking it with their symbology from page 16 This would save confusion...

Item 20 in the cold start checklist: What's the point of this second test? 1. The LIDS caution already lit up in the preceding LTS TEST (item 2) 2. There is no 'wait' for the LIDS caution, it lights up in the instant you switch the LTS TEST, so what are the 5 seconds needed for? There is no delay, so I assume no circuitry is checked.

Item 39 of the cold start checklist tells me to uncage the SAI 1 minute after power on. Yet it is already uncaged. 12.3.1 Cockpit preparation doesn't address standby instruments, so everybody doing a cold start will have an uncaged SAI right from the start and hence Item 39 doesn't make any sense in this regard.

I did, see my first post. You need the parking brake on for alignment, regardless. I see. Would have been more clear this would be explained in the manual. Thanks

wheel chocks are placed, so no need for them. But as you can see in the pic, they are on, brake pressure is applied

As easy to see in the pic, all necessary data was entered, Lat/Lon, mag var. Turning the dial into alignment lets the "time: 00:00" blink eternally. UFC is blocked, any inputs are ignored... Yes, I have waited several minutes, this is a ground alignment. It just never starts. UFC remains unresponsive until I turn the dial back to off.

Doing a cold start on ramp, I am following the shore based procedures as printed on the manual, beginning on page 280. Step 43 on page 286 is the SAAHS BIT... Described flow doesn't work, as 1. pressing P/B 12 doesn't do anything, there isn't any reaction at this point hence 2. the TEST doesn't appear 3. caution/advisory lights don't illuminate This BIT doesn't initiate and can't be run. any ideas?

Doing a cold start on ramp, I am following the shore based procedures as printed on the manual, beginning on page 280. Step 5 is the Throttle quadrant test... Described flow doesn't work, as 1. the JPTL caution light already comes up in the LTS TEST of step 2. 2. the switch doesn't disengage 3. there is no audible caution JPTL light remains on. JPTL switch remains on. any ideas?

Hey there, regularly flying on MP servers, I love to make use of the Téléaffichage feature. Yet sometimes I wonder what to do in cases there are multiple targets. So sometimes there are OPFOR helos in the area, but in other cases there are F-4 Phantom's coming for me. While it is generally not a problem to determine if the TAF offers a helo or a jet, by simply observing the target's velocity, as a Mirage I obviously see an F-4 as the higher threat. Yet in some cases, the TAF alerts me to go after a helo, while also an enemy jet is nearby, which is of course not desirable. So, by which rules does the TAF decide which contact to send me? Apparently it is not threat based. Is it range or simply the order of appearance? By which rule does the TAF sometimes switch targets, keeping that one for a minute and then suddenly switching forth (or back) to a different target, while the initial target is still alive? Is there any way to let the TAF sort targets? Is there any way to refresh the TAF reception in a way to cycle to a different threat?

my browser can't find that link

I'll try, thanks! I know the "recommended" rotate speeds of the manual, but the bird seems to be reluctant to even raise its nose before reaching the 180s, with a A/A loadout...

I accelerate and when rotating, I always get tires blown. 1.Why? 2. How to prevent?

Maybe all of you failed to read but I was in fact helping him. I even guided him to the page to read it up. After this one I was only responding to the dude critizising me for helping out. Yeah, that's basically what I explained to the OP (btw the symbols appear in fact inside the box). Check page 161 in the manual. These were 2 guys. The OP received my help. My quote you critcized was a response to another guy's reaction. While he certainly wasn't nice, yet I can't see any scolding on anyone's side.

If you don't have the time to read a manual, it means you lack interest. If you're not interested enough to put effort into learning things, don't expect others put effort into teaching you.

That's exactly what it does. With the trimming modes, you shift your curves' center.

zero curves. best curves.

Still confused what he might think of with the Huey rudder option....

This is the ASE footprint. All detected air defense will be displayed along the frame of this box (see the yellow symbols?). If it doesn't appear for you when doing cold starts, you may want to review your cold start procedure as you are clearly leaving something out connected with the ASE. Edit: Oh wow, you didn't read the manual. Check page 161.

Loaded your Gunner.trk into replay. Assumed control the moment you fired the laser. While laser continued, I could switch field of view of the TADS no problem, also changed from FLIR to DTV. Something isn't configured correctly on your end. Maybe try some different binding for the laser, to rule out you are using some odd hardware which is preventing any multiple button input.