Kid18120

+1000000000 but i would't get my hopes up, nothing about the TAD has been even remotely mentioned about the upgraded features for A10C-II

I plan to replace the TISL panel with the HMCS control head and sneak the ARC210 somewhere by the other radios by doing some resizing in Helios. I'm confident the parts that are the same will remain equal with exports and what not

SAS currently DOES provide turn coordination, not sure what you guys are talking about

I can confirm it's as described by Snoopy. You can see your own lights remaining steady, whilsh other's remain on the flash mode no matter the switch setting. The only way to see other's lights steady is for them to go pinky switch forward

Hi, i've come across a bug with the TAD. If you set the BULL/CURS mode, it should show the bullseye readout of whatever place you have the cursor on (not necessarily a steer/mark/mission point but also just the map itself). It doesn't. The one workaround i found is to set the BULL/CURS mode, then "lock" yourself with TMS UP on the TAD and only then you'll be able to get the BE readout. I'm not sure if this is intended or a bug as i couldn't find any details on how the TAD should work on manuals i have access to. Thanks

Very nice analysis, hopefully this will push ED to implement the necessary changes to correct the behavior, though this might be due to contract agreements made when the A10 module became a thing. It might be intentional.

Getting rid of the carriers seems to actually solve the issue. Some new code slipped in by accident? :music_whistling:

So far all the bridges i've bombed were destroyed. Sometimes they are a bit too tough IMO but still destroyable.

Is this before or after yesterday's hotfix for 2.5.6?

That's because of bad server admins. You can enforce trees but that's through the mission files not through server settings

The TAD is indeed showing all the correct info on my end

I had the same issue with my HOTAS Warthog. I use the throttle slider axis as zoom but as long as there's any kind of LED turned on it gets the jerky spikes. The only solution was to disable LEDs completely. Can you do the same on the Saitek X52?

Not sure about "why" it is like that, but that's the official answer ED gave long time ago. You can notice it over Vaziani. Just put the A10C on the ground on Vaziani airbase, you'll see that with zoom level at 5nm you'll only see the black background. As soon as you zoom back to 10nm and above you'll get the map background

Not a bug, some areas of the TAD map are not available at 5nm zoom

The RIO is just following the Pilot's position so if the pilot has the collision model enabled, the RIO would "stick" to it.

Just select the desired steerpoint that you created from a markpoint, go to the STEER page on the CDU and then click on the relative OSB for the '> Waypoint' function. You'll find all the relevant steerpoint data in there.

Though something like an F16 weights around 8 times a Ferrarir F458. There's weight to take into account, brakes temperature, runway surface conditions, wind. I think brakes work just fine especially if you compare the size and weight of any aircraft compared to the size of its wheels and brakes

The rotary switch is working as intended i think. If you picture yourself rotating it, to go from OFF to MAN for example, you'll be rotating clockwise - so to the right. Right click makes sense.

Some of these features will probably come with the dynamic campaign, or at least i hope so!

Yeah the clunky sound when bombs get released is barely audible right now, it most likely has to do with the ongoing work on the in-cockpit sounds. Maybe adjusting one of the sound volume sliders is going to "fix it". I'll give it a go when i get a chance :joystick:

If what you mean is to use a secondary touchscreen for a cockpit export using tools such as Helios, then a 21'' 1080p is going to work perfectly. I use a 'Hanns.G HT225HPB' 21.5'' touch screen display via Display Port. I then just exported my A10C cockpit using Helios and the job's done

True, the same goes for the AV8. There's something on Navy's way of thinking about HOTAS that doesn't really make sense to me

In the A10 AFAIK the triple-MAV rack isn't used because the inner MAV would potentially cause damage to the landing gear. I also read that the TGP should be set to standby mode while launching the outer MAV on the same wing to avoid damaging the optics

I'm one of those who said no to the F16 simply because it's an aircraft i don't have an interest for right now. I also don't have an interest in the super carrier so i probably won't buy it either. The difference (possible) is that i don't need the F16 to join a server but i might need a Super Carrier to join. If i won't need a SC to join a server, i'll be happy. As simple as that. :joystick:

Hey think positive! At least you won't find yourself without fuel in the middle of nowhere without a Boomer if thre's a Droguer around :D