razo+r

Usually if your stick is not centered perfectly, you cannot engage BAlt. Check your stick and add a deadzone if necessary. Otherwise slightly nudging the stick around if you know it is always offcentered can also help.

Have you already tried changing the country to an english-speaking one or also making sure you are part of the blue coalition?

Which training mission? What is the "dial top left cockpit number"? Do you mean the trim gauge/indicator? Did you check your controls? Are the keys you are being told to press the correct ones for whatever you are trying to achieve?

Because of the ARI like Nealius mentioned above.

Hast du auf der Website von DCS geschaut? Falls es das Handbuch dort nicht gibt, schau trotzdem in deinem Rechner nach (Installationsverzeichnis von DCS, Dcs World/Mods/Aircraft/XYZ/Doc). Du kannst es ja auf dein iPad laden/schicken/schieben.

No, wings level and rudder only after touchdown.

Why make it easy when you can make it complicated. After you touch down the aircraft will straighten itself so then you'll just do a normal aerobraking and rollout. There is nothing additional you have to do in a crosswind landing with the F-16.

Answer is here:

Are you 100% sure that is the Navigation Target Point? To me it just looks like you are designating your waypoint 1 as a SPI. I mean, the waypoint is labeled as "1" on the HSD, you have waypoint 1 selected on your UFC and that Navigation Target Point that is supposed to be bottom right of waypoint 1 isn't shown on the HSD. In both pictures the point is exactly 18.7 miles away while there should be a difference in distance between wpt 1 and NTPoint. They are also at the same bearing from you but as you show in the picture, the NTPoint is more to the east than WTP 1. So I don't think you are actually targeting NTPoint 1, but your ordinary WPT 1. It is weird though that it jumps to ground level. You did not press any other button, right? Otherwise I guess "auto" mode automatically puts the point at ground level. I will try it out once I have the opportunity to see myself what is going on. But so far, you just seem to target your normal waypoint 1, while the NTPoint 1 you added does not exist in your flight plan because you did not give it a name, so the point is not recognised and not added.

Sorry, what exactly do you mean by that?

That is not the name, that is just the number of navigation target points you have placed down. The name for that point goes into the comment field below.

I don't have the files but you can download youtube videos and convert them to audio files, if you have the time for that.

Its basically the same, just one method is for more singleplayer and the other is better for multiplayer. But you can set PP# any time, either in the editor if you are there, or via the F10 map if you didn't or couldn't place any in the editor. It depends on what you name it. If you name it WPT#, it should appear like any normal waypoint (at least in multiplayer). If you name them RP# or PP#, they will appear as "markpoints" that are not connected to your route. It does work, if you give it a name. I have never tried it that way so I cannot comment on that.

You need to give it a name in the comment field, like PP# (# being the number) RP# or I think WP#. Simply placing down a navigation target point is not enough. It will then populate your DST waypoints accordingly. So if you place down RP's, they will appear as waypoint 36-39 (I think, I am not 100% sure anymore. Consult the manual/quick guide to see which ones populate what DST waypoints), WP as their number and PP as 31-35 or something.

V1 launch sites are static only.

Static objects don't snap to airport slots. They can be placed anywhere, unlike actual AI aircraft.

G warmup ist nur nötig, wenn du viel G ziehen willst. Falls du immer viel G ziehen willst, ist ein G warmup immer sehr empfehlenswert. Und das ist bei allen Flugzeugen implementiert.

Cool, thank you very much for taking a look and fixing it. I also tried various ways and came to about the same conclusions as you. @ex81 Looks like something weird was in your mission together with embarking and hold interfering each other...

When you slew your SPI with let's say the TGP or FCR, it will create an offset or delta. This offset is then kept and applied to any steerpoint you select. If you want to delete that offset, you have to press CZ. For example if you select steerpoint 3 and slew the SPI 5 Units up and 7 Units right, that will be your offset. If you then select steerpoint 4, the system will apply the same offset onto that steerpoint, so again location of steerpoint 4 + 5 Units up and 7 Units right. If you select steerpoint 1, the same offset will still be applied. Now if you press CZ, the offset will be deleted and all steerpoints will be on their true location again. Basically, after you are done targeting something, it is a good practice to press CZ to remove the offset from the system.

I guess when you employed weapons, you slewed one of the sensors around, which in turn slewed your SPI around, and then you forgot to press CZ to reset the steerpoint (deletes the offset created by slewing the SPI around). Can you confirm? If not, do you have a short track of it happening?

Are you sure it's RCtrl+9 and not RCtrl+F9? Usually cameras in DCS are the F# keys.

The line is tilted that way because you are using high drag bombs from a relativly high altitude with strong crosswind blowing. Get lower and the line becomes more straight. Fly from a different angle to limit effect of crosswind on your bombs. What you also see is a bug, the F-18 in DCS does not distinguish between High Drag and Low Drag settings for high drag bombs. The computer always applies High Drag into its calculation.

There can be many reasons for that. You will have to provide more info for us to figure out why.

That's because the other variants have been added in the December update last year, without updating the manual of course.

You have to move your head closer to the HUD. The HUD cannot zoom itself, it's likely you moved your view or your TrackIR was not centered.