razo+r

Unload all gun ammo? Force them to use a specific type of weapon with the advanced waypoint options?

Uh, that's weird. It works just fine for me, and I haven't changed anything. Are you trying to rearm from the start of the mission or did you fly and land and try it that way?

No, I mean mods, not modules/DLC's. Mods like for example the A-4E, Grinellis F-22 etc. In the new launcher go to the "files" tab and on the right side you should get the "repair" option.

If there are no winds, the HUD shouldnt be offset. There is also no reason why the offset is caused by the map, unless you have a corrupted install or are doing something wrong. If there was truly a bug, more people would complain/report it. Make sure you remove all of your mods and run a full repair, and then try to reproduce it and save the track. Thats the easiest way to see what it could be.

A track is more helpful than a screenshot. HUD being offset is usually because of wind, unless you mean tilting due to INS drifting, be it due to no GPS available or the NAV switch being in NAV instead of IFA. But yep, we'll only be able to tell for certain if we get a short track.

Where's the track? What aircraft? You mention carrier and Caucasus. Do you see the same behaviour on other maps? What about airfields on Caucasus? What's the wind setting? Are you intercepting the Glideslope at the correct distance/altitude ratio? Upload a track. So many questions...

Glaub schon. Ist an der gleichen Rumpfseitenstation bzw unter dem Rumpf zu finden. Ja es sind 2 verschiedene. Stell sicher dass der historische Filter (Armbanduhr unten im Editor) ausgeschaltet ist.

The radar has different modes, doppler being one of them. But it also has non-dopplers modes that don't filter out static targets. And by reading the linked topics, PAL seems to not use doppler, making locking onto ships possible.

A carrier broadside has a bigger RCS than a flanker headon. It makes sense that the radar picks the one with the bigger RCS. Some more info:

Not modeled. Icing on airframe is module dependant. Most only have pitot icing, and like 2 only have icing on canopy/airframe.

Can you confirm all these actions are correctly performed ingame?

Move your head back, you basically glued your eyes to the dashboard. RCtrl+Rshift+zoom button on the numpad.

Remember, if you are having issues, add as much detail as possible. We cannot guess what buttons you use or what procedure you use. A track generally also helps depending on the issue.

Can you upload a track or at least the mission?

A very descriptive post...

Do you have a track?

Got a track?

You need to press and hold it. I think it needs to be pressed for 3 seconds before it turns off, for obvious reasons.

P-35 instead of Su-35 or F-35! - Why jumping to 5th or 4th generation with a big gap in ... 0th generation aircraft - For years we've been waiting for decent P-planes - No documentation suddenly no issue Blah blah joking blah blah. This is just ridiculous... I mean the arguments...

You could try doing an offset waypoint from the bullseye steerpoint, manually add a waypoint with the help of the F10 map or use the TGP/FCR in snowplow, move the cursor to the range and azimuth and then create a markpoint that way.

The clock is the historical filter and limits aircraft and equipment to the year you selected, 1939 in this case. The rockets were not around until 1943, thus making them not available.

There are many ways to do it. If you get range and azimuth from a waypoint, you can create offset waypoints. If you get coordinates, you can manually add a new steer/markpoint. If you get range and azimuth from bullseye, use the HSD/FCR. If you get range and azimuth from you, turn to the heading and use SP on your FCR/TGP.

Got a track or mission to showcase the issue?

Im englischen Teil gibt es zig-Menge an den gleichen Fragen.

Any windows update or keyboard layout changes or something similar? Do the F keys still work outside of DCS?