RubberDogSh1tOutOfHKG

Can we at any point expect to get system failures implemented? When I look in the Mission Editor I can't find any option to fail random or specific systems. Is it planned for the future?

They stay in the pattern. Only way to get them to land, that I have found so far is to take off myself. Im thinking there must be some logic that triggers them to hold until I am gone. I just wonder where that logic triggers?

Im in an F16, waiting at rwy27 Gutersloh. Ai aircraft I have tried both AJS37 and AV8B, both goes into a holding pattern

Hello! Im working on a mission where I want the player to hold short of the runway while AI Aircraft comes in to land. However the AI just goes into a holding pattern. I haven't crossed the Runway Hold Short Line at all. What to do?

I've tested a bit too myself. Never flown the F16 IRL, but I do fly A330 for a living. I've switced from from the Thrustmaster Warthog to the Winwing F16 set with the MFSSB set (no movement, only force sensing). Have flown the F16 in game since launch. The F16 used to feel very easy to takeoff in, but lately has felt very heavy and sluggish. Spurred on by this post I also did some testing myself. And have to agree if you follow the numbers you do get a takeoff as advertised. For me the main take away is that I am not as strong as I thought when adjusting the power sensing sensor inside Winwings Simapp. After some more sensible tuning, and starting rotate around 150ish I can get the aircraft off the ground around 180-190. Watching the replays I note that the first few seconds after liftoff doesn't really register in pheripheral vision, then as you get out of ground effect you get a more sharpish pitch up moment (which is odd as when in Ground Effect you have less drag than when above - perhaps an IRL F16 thing or a DCS thing?) So what I conclude is that there is a smaller pitch up on initial rotation and lift off, but it does actually happen. Before FM change the initial still in ground effect pitch up was more pronounced. So yeah, feels a bit scary zooming towards the end of the runway but flying by the numbers will get you up in the air.

Really love the map! Please add Værløse Airbase on Sealand, it is well within the Phase 2 and 3 area. And had F16 Shelters!

Thank you for the great mods! Does anyone have a solution to this: I'm working on an intercept mission, where I would like the TU160 to open its bomb bay doors. But not shoot straight away, as that would be the ROE change for the Player. I found the argument and value to look for, but can't seem to trigger any action to actually open the doors. If it can't be done with triggers can it be done with scripting? I tried ChatGPT but none of the solutions offered worked Again, thank you for the great mods!

Can I use this to get an Ai Helo to pick up a downed AI Pilot?

Thank you! Then I will have to change my story a bit

I need an AI Aircraft change behaviour if it has been locked by Radar. How do I do that? Its a QRA Intercept Mission, and I would like the AI to change Waypoint when locked by the Players Radar Thank you!

In the free version you cannot zoom out that much, how much can you zoom out in the standard version? Thank you

Yeah, I think I just should have been a bit more aggresive in getting down fast to avoid the missile. One thing the Mig31 isn't famous for is its agility

I got him on my 3rd try. Again didn't really do anything fancy here either, it was just good luck I got him fast on the radar this time. The first 2 times I didnt get him on radar in time to fire off a missile. Situations like this almost makes me wish for the ability to save a mission state!

Both my attempts at the Glorious Dawn mission have seen me shot out of the sky by the Mig31. I cant seem to shake his missile, even though I turn on ECM, drop Chaff, and drop to the ground. I do not get a Radar Lock before him.

Damn keybinds! (Keybind was set to VOIP and not Radio Menu) Thank you so much for your help and again, what a fantastic Campaign!

Stupid question as I've always used Easy Comms. I do have the transmit button mapped to my HOTAS, so I just press it (then I can see the UHF on the DED having a Yellow Background) and then I bring up the Comms menu press F6 at the same time? So I have to press those 2 buttons simultaneously?

Make a Swedish Splinter Camo!

An explainer on how to use all those tables would be great, as is now its just gibberish without any introduction

I cannot find that described in the Manual, do you have any guide to this? Thank you!

Is it correct that the Glideslope is the small White Triangle then, on the side of the ADI?

-----EDIT!---------Would be nice to have in the Manual ----------- It Is In The Manual! SORRY! I just had a look at the Landing section, but I see the Buttonology is in section 3.3.4 If I may suggest to perhaps link to that from the How to Land section? Again thank you Zabuzard for answering my questions!

Glad to see your response Zabuzard! Sometimes its hard to know wether its a Feature or a Bug

If you look at the attached pictures you will see that ILS is acompletely independent system, no VOR needed. You will also note that the Course is defined by the Beam transmitted from the Ground Installation. Why then do you then need to set the Course of the Localiser in the Cockpit. Should be completely irrelevant.

Well, the screenshot would be of the 2d Monitor. So no use. My gamma is set to almost 3 to be honest. Never needed to adjust it in other modules. And Global Illumination is on. Ill have a look, thank you

I tried it in VR, just toggled it on and off. Didn't see any change to standard view. I'm probably doing something wrong