Tyrant07

How do you disable to constant "altitude altitude" warning when passing 20,000 ft?

Since the 2.9 update the JDAMS in the A-10C 2 do not align after a cold start. They constantly say ALN UNS in the DSMS. I have tried all the different alignments and re-loading the DSMS before and after alignments. Nothing seems to fix this.

When I install the 214 Day skin, its exhausts are jet black, almost like its missing textures from that show in the screen shots. Any idea on a fix?

Can we get a dark tinted visor for the pilot and CPG? I've seen multiple IRL pilots say there is advantages to using the visor and the IHADS FLIR during the daytime. Right now the FLIR is pretty washed out in during the daytime and I feel this would be a nice addition to the module.

With the PERF page not being accurate right now, has anyone created a PPC calculator yet?

Thanks for the reply. The OAP function works close enough for what I was looking for. Thanks for the writeup on how to do it.

In the harrier for example if I want to ingress on a 250 heading to a target waypoint, I set a course line on the 250 radial and it displays off the waypoint on the EHSD. The F/A-18 has something almost identical. The A-10 and F-16 have something similar in their analog HSD's. But the JF-17 doesn't seem to have this customizable course line.

Does the JF-17 have a course line function (like all the NATO jets have) on the HSD or in the jet at all? I have tried looking through the documentation and don't see any reference to one.

Is there an existing roadmap for the Hind, similar to the one for the Viper and the Hornet? Just curious when some of the missing features like the R-60 will be on the way to the game.

it sounds like you had retreating blade stall. This happens when you go over 350kph in the Hind. You need to be careful when doing descents at speed as the Hind gains speed quickly.

I just cold started with no issues on the latest open beta. Could be an issue on your end.

What is the elipse?

I'd also like to point out the pattern of impact n that video. Notice how its kind of spread and not a straight line laser like we currently have.

Step 9 is the major change with JDAM's. Make sure you are holding the pickle button for that 1.5 seconds, or it will not come off the jet.

For the point track it is dependent on what FOV you are in, how much zoom you are using and contrast of the vehicle. Select what you think looks the best, then toggle to point track and place your crosshair in front of the vehicle's path of travel. Once the vehicle passes through the crosshair, the point track should grab it and track the vehicle. If it does not acquire, adjust your zoom settings and/or switch camera and then try placing your crosshair in front of the vehicle once again. Rinse and repeat until you establish a track.

Sounds like a miscommunication as its clearly not correct. What good is a North arrow that never points North?

The North arrow in the TGP does not point North ever. The aircraft can be facing north while having the TGP in the boresight position and the TGP will be showing North in a completely different direction. Because of this, it is very difficult to figure out what direction stuff is when looking at it through the TGP.

Still an issue

SSS depress twice in quick succession enabled TPOD control with the TDC.

When entering UTM coordinates into the CAS page the system seems to convert the UTM into LAT LONG upon hitting the enter key on the UFC. The entered UTM coordinates in the scratch pad visually change to something different as Line 6 is populated on the MFCD. This inaccuracy makes the created Target points inaccurate for GPS weapons and also for target acquisition in general. Additionally. When creating a waypoint via the EHSD using UTM. The system does not allow the user to edit the elevation for the waypoint that you have created and the elevation it chooses does not match that on the F10 map. Update. Seems the elevation the system is choosing might be meters and not feet, which is causing this error. This can be replicated on all maps by creating a target point via the CAS page or the EHSD. Steps taken on CAS page. 1) Selecting the EHSD created waypoint that is in the same UTM grid square as the target as the IP on line 1 2) cycle down to line 6 for target location entry and hitting clear on the UFC and then entering in the 10 digit MGRS/UTM coordinate from the TPOD/F10 map/JTAC/FACA and hitting enter on the UFC 3) the entered coordinate on the UFC scratch pad changes as the LAT LONG on Line 6 populates 4) Hit save and use on the CAS page and designate it as a useable Target point 5) Slave TGP to that target point and see if it actually on said target Edits: Added more information

-28 to -30 in the special options seems to center the stick

The lowest FM I have been able to get is 31.00. To do this, on your UFC scroll wheel to the channel you want to change the FREQ on (in my case it was M on radio 1) type 31 and hit enter. The freq should then be 31.00 FM

Both radios work pretty flawlessly with SRS integration. You can change freq's, preset channels, modulation and crypto settings via the UFC and the ODU. There are also keybinds for radio 1 and 2 PTT to use the in game pop up radio menu's for non easy comms functions.

Since the update alot of my control bindings are showing orange and no longer work. These include all the OSB pushbuttons, the fuel probe, countermeasure dispense, kneeboard page cycle and finally I am no longer able to bind my warthog pinky lever as a modifier as the Harrier doesn't register it for some reason, but it works flawlessly on all other modules.

The way I posted is the only way I have managed to get a successful countermeasure reload after exhausting my starting loadout. If you try to rearm them by simply using the AN/ALE-39 menu you WILL NOT get a reload. I understand what Ironmike says should be the correct way to reload them, however right now that simply does not work and has not worked for all of 2020.