razo+r

It seems it's a mission/server specific issue. I tried it in SP and on two different servers and autorudder was only present on that Wolfpack server. Perhaps contact the server owner/mission designer to help troubleshoot this issue.

Cannot confirm. Autorudder unchecked in special settings and no rudder inputs observed during takeoff. Perhaps it's the old issue where it's secretly enforced in the mission. Can you specify which mission(s) you tried it with? And a track or the mission itself would help to confirm that.

Just a wild guess, but have you also checked the special settings for a custom cockpit livery that you maybe have to select?

The problem is the sequence of the advanced actions. Holding is basically infinite, as you haven't set an end condition to the task "HOLD", so they will never switch to the ROE rule. To fix the issue, give infinite actions an end condition, put actions that are infinite at the last position in the sequence or actions that get completed quickly in first place. In case of this mission: ROE = Weapons HOLD HOLD Disperse Under Fire = OFF Or put "HOLD" at the very end like this: ROE = Weapons HOLD Disperse Under Fire = OFF HOLD

Make sure the default view is in the correct position so that you see the full HUD without anything being outside of the view box. Once the default view is correct, you shouldn't have any issue. Also make a habit to reset your Opentrack view from time to time as it may drift ever so slightly.

It despawned because the parking spots are too small for it. So in that sense that is the expect behaviour as designed.

Make sure you only installed the mod in the saved games folder directory. Also make sure that when you open the F-104 folder in the saved games directory, that there is not another F-104 folder in there. If you open the F-104 folder you should see multiple different folders and some files. The message you see is because you installed it wrong. But to figure out where you made a mistake, we need more infos. Can you attach a screenshot of your explorer with the mod and installation path?

Please attach a short track so we can cross-check with your results.

This condition list requires all units that are mentioned in there to be in the zone all at the same time or else the condition is not fullfilled and the action will not be triggered. Add some "OR"s inbetween each line in order to let the action triggered if any of the units is in the zone. Once- if unit in zone - illumination flare or something like that. Don't forget to add "OR" inbetween conditions.

Is the Fire at Point within Max and outside of the Min range? Have you waited the 3 minutes aiming time required by artillery units? Have you considered spawning illumination flares in a trigger zone instead while the L118 is just there for "dummy" purposes? Can you upload your mission?

Instead of relisting every argument written in the dozen similar previous topics, have you at least read one of them yourself before opening up this one?

Who is the author of your Eurofighter mod? Version 1.1 of DCS was not an Open Beta, so now what are you looking for? A DCS OpenBeta version or a Eurofighter mod version?

Obviously after a repair the aircraft should be brand new, so if it doesn't behave like it should it doesn't sound correct. But now it would be good to know what actually went wrong, so we can figure out if it was actually a bug or something else that went wrong. So, can you replicate it? Do you have a short track?

Hard to say what's going on with so little info. Which glide bombs? What aiming method? Wind? Did you do a full GC alignement? GPS enabled? A short track perhaps?

From my experience, you can just ignore it, it shouldn't affect you in any way.

Do you perhaps have a short track showcasing your attempts?

If you click on one of the links in the first post you'll see some example images of what objects come along with it. It contains much more than just paper targets.

There's the 476th target range mod that has some practise targets. There's also some practise range scripts that tell you how far off you were and how many hits/misses you did.

RCtrl+RShift+Num2 or Num8 should allow you to move your camera up/down. Otherwise you'll find a full list of camera controlls/view controlls in the settings-> Controlls

As a workaround until a "moving" seat is implemented, just move your camera up and down.

We don't know either how to fix it if you don't upload it, as a reference for future issues like this.

Open the script and fix it. Something in there is triggering that error.

No, there is not. But you can copy the group once you are happy with it with the good old fashioned Ctrl+C and Ctrl+V.

Press "H" or switch the HMD switch, one of the smaller switches next to the Laser Switch.

They're already spinning in the KA-50 when the HMD is in use, but nobody complained so far, so...