rob10

UNCONTROLLED OPTION – using this the aircraft will be visible at mission start - it will not do anything (won’t start or move) until it is given a PUSH command with trigger - these aircraft can be destroyed on the ground at any time from mission start - in AIRCRAFT TRIGGERS (third tab), ADD – PERFORM COMMAND / START - in your triggers, set ACTION as AI TASK PUSH, in dropdown select desired UNIT NAME / 1.START NOTE: UNCONTROLLED AIRCRAFT will NOT perform any Advanced Waypoint Actions until they become controlled (even if these are set on WP 0). For example, an uncontrolled aircraft with an Advanced Waypoint Action of “invisible” on WP 0 WILL NOT become invisible UNTIL they are controlled.

It was fixed, the thread you're posting in is over 3 years old. The current version of this problem is being discussed here:

Set it as UNCONTROLLED and use a trigger to start it when you want. NOTE: currently there is a MP bug where if you have any uncontrolled aircraft clients may get some blinking of objects in game. ED is working on it and I think are hoping that it will be fixed next patch.

Being discussed already here. Which is actually the more appropriate place since this is a supercarrier issue, not a F-18 issue.

1st check that you have DCS excluded from your anti-virus (anit-virus may have caused the issue in the first place), then run a REPAIR on your DCS (can't remember what it's called in STEAM but something like "verify" if you're using Steam).

And they've indicated recently that they aren't likely to mess around with never versions of DLSS until they Vulkan finished up. I think that timing is about resources.

Have you flown it recently? I was really disappointed by it at release, but flew low level in F-18 last night as part of a mission and (while it can always be better) it found it quite good. I know others will have different expectations for a map, but Kola is definitely ticking my boxes these days.

Never had drift with WW. Did with old TM setup. Maybe try some compressed air and see if you can blow it out.

You did get the yardstick. It is strictly DISTANCE and has no bearing information, so the TCN needle will keep rotating around because it has no where to point to. However if you look in the top left corner of your HSI page (or SA if it's not priority) you'll get the distance to your wing.

That's a long term issue that started a few years ago when they updated the way liveries info was saved in their .lua files. ED hasn't updated the included liveries to the new formatting. If you search around the forums you'll find info on this and how you can change (at least the F-18) livery .lua to fix the issue. Here is one thread regarding this

No, the comms menu (when open) overrides whatever the other bindings are. So I have (in the F-18) my weapons selection up/down moves the comms menus up/down and depress enters, but if the comms menu isn't open it works normally as the weapon selection buttons.

Haven't used it to send mouse commands myself, but IIRC it is able to yes. Probably not much different to using Viacom etc, but might be slightly lighter overhead if you're not using it for other things and saves having to fight voice recognition (which has sometimes been a challenge for me ).

Have you tried reaching out to WW yet to see if they'd be willing to do it themselves? Even if they won't for you, you might be the one who pushes them up to enough requests for it that they do do it.

You could also use something like AutoHotKey (AHK) to send the appropriate commands to move and resize the kneeboard to a better spot for you.

I see mention of S-3 lighting update and AFAIK while it was in the changelog, it has been acknowledged that the fix didn't actually make it into patch. Just for those who are looking for a change that didn't happen.

You are using the new deck crew. Either turn them off in the options or read the new supercarrier manual and follow the new procedures to get them removed. Yes the error message makes no sense. ED is aware.

You may have to play with circle orbit and set the speed then mess with the distance between waypoints until you get the angle you want.

3rd party option available. Check out DCS Webeditor.

500 error is typically wrong time on your computer. Check that it's correct.

And unrelated, but unless you're in a mission without GPS available (which you're not by the P/INS advisory in your left DDI) you should turn your INS to IFA rather than NAV after it's aligned.

If 875 kB is too big to upload you likely need to go into you profile and delete some older uploads. You've likely hit the individual limit.

Yes. Just realize the red circle is the theoretical max range and may be overly optimistic in some cases (i.e. just barely inside the red may not get hit)

And since ED many years (decades) ago had someone criminally prosecuted (jailed?) in the U.S. over it, I can almost guarantee that they are pretty freak'en careful about where they tread on that side of things.

Have you checked that your Windows display is set to EXTEND THESE DISPLAYS?

This is the most comprehensive list shared by a user that I've seen. Note that you need to be in c:\users\usename\saved games\dcs\kneeboard\F-16C_50\IMAGES for specifc aircraft (note IMAGES at the end) and the file need to be png format with .png lower case.