jonsky7

Try replaciing GU_MAIN_VIEWPORT = Viewports.Center UIMainView = Viewports.Center with GU_MAIN_VIEWPORT = { x = 0; y = 0; width = 3440; height = 1440; } UIMainView = { x = 0; y = 0; width = 3440; height = 1440; } This will definitively set the bounds of the UI viewports.

Unfortunately I don't think there is, or I havent been able to figure it out. I have seen that sometimes DCS uses the top left of all the displays as point x=0 y=0 but mine has always been the top left of my main display. I don't know what the correlation is, whether it's graphics card related, or which ports the monitors are plugged into, or something else. The only solution I have for you is to set your large display as the main display. You should then still be able to have your smaller display on the left in display settings and be able to use it for whatever you like. Tbh though I havent done any testing with this in mind.

Have you checked the "special" option tab for the Hind? On one update my trim option changed to FFB mode. Which made it very weird. Just a suggestion.

Sounds good to me

There's no terrain data of any kind showing at the minute, just a black display with airfield icons

Yes, that is the same. Anytime I load in any jet with modifications to the files in cockpit scripts folders, whether in single player or multiplayer, and then go back to the server list, my IC check shield icon is red and I have to restart DCS to get it to go green again. I may have misunderstood when you wrote as you being kicked from the server as soon as the jet loaded in. Agree, pain in the butt to have to restart to switch servers even when the servers have this setting to off. In fact I went down the list of the most popular servers by player count, about 20 or 30 of the top ones, and only found one guns only dogfight server with this option set to on.

I have noticed that if you make the display slightly larger, then the brightness will return to normal. AND.... if you make the display really small, the screen starts flickering like mad. The video below doesn't really capture the speed of the flashing, but you get the idea. Just adding this for info, obviously would also like this fixed please.

The refresh or update rate of the NS430 is now very slow in DCS 2.8.0.32066. The unit display now only updates once every 3 seconds. Not sure if this was intentional or not as no mention of it in the changelog track attached NS430 rate.trk

I have the same files modified as you do here, except the PFLD one. I can join and play on servers with "Require pure scripts" set to no. I was able to join and play on the GS server you showed. Maybe try without the PFLD export? Having to quit the game every time you leave a server is a monumental PItA

There is a way yes, it will require a little bit of editing a file though. If you go to DCS World/Mods/aircraft/FA-18C/Input/FA-18C/joystick and find the file called default.lua Add this line { down = hotas_commands.THROTTLE_SPEED_BRAKE, up = hotas_commands.THROTTLE_SPEED_BRAKE, cockpit_device_id = devices.HOTAS, value_down = -1.0, value_up = 1.0, name = _('Speed Brake Switch - EXTEND, else RETRACT'), category = {_('Throttle Grip'), _('HOTAS')}}, You will have a new keybind option called Speed Brake Switch - EXTEND, else RETRACT The speed brake will extend when the button is pushed, and retract when the button is released. I have modified the file for you, so can paste it into the folder listed above. >>>>>>> default.lua You will have to re-copy the file after every update, and it will break integrity check on servers that have the new "REQUIRE PURE SCRIPTS" enabled, but I haven't seen many that do yet. Alternatively, for the Warthog, there is an excellent script for the TARGET software than changes the way the buttons work slightly.

Still working fine for me.

@BIGNEWY I did notice that if you fly in single player with any modification to the DCSWorld/Mods/aircraft/<MOD_ID>/Cockpits/Scripts files, then the IC fail flag is shown as soon as you open the multiplayer server list, before even attempting to join a MP server whether they have this setting to enabled or not.

What server are you trying on?

The patch notes are simply saying that a server, if the operator should choose, can set the server to require completely standard/vanilla files in the cockpit/scripts portion of DCS. And if they do then anything other than the original files in there will break IC check, whether it's some super cheat, or simply exporting a display. So it's now up to server admins to allow this or not. I'm certainly hoping many servers do not turn this setting on, as I too export my displays to another screen.

You might need to load up DCS in 2D mode first and set a key for "recenter VR Headset" I think the problem you have is that the menu screen floats in a fixed position, and from your screenshot I think it's behind you. You could always try just looking behind you and all around to see if you can see the menu screen.

Is it just me or can't you assign a moving trigger zone to a train like you can other ground vehicles, it doesn't seem to work? Also setting the train to broadcast a radio message for direction finding purposes doesn't seem to work either. Am I doing something wrong?

Yes, haven't noticed an issue with any other rotary knobs.

In the air, you must use the "Comm Push to Talk (call radio menu)" assignment. The argument goes: The comm or Communication menu (\) button is just you talking out loud, so in the air nobody would be able to hear you. The push to talk button is you keying up the radio to talk to whoever. You can usually also use this command on the ground but power to the radio system is required. For the Mossie you must open a window to talk to the ground crew using either keybinds. It's a standard ED have adopted for a while, but it's confusing because not all modules adhere to that standard.

@Flappie Sorry to be a pain, but could you possibly have a look at this, and report it if you find the same? I did confirm with a friend that it works this way for him too now. Cheers

@SUNTSAG Hi Suntsag, I recently watched a Youtube video by Tactical Pascal where he was flying one of your missions, The Shipping Fjordcast. I was wondering if you would be so kind as to reveal how you got round the limitation which is the topic of this post, so that the "Navigator" would be able to set up the DF radio while you the player occupy the pilots seat. I'm able to set up the triggers to can get the navigator to do all the required steps, just only from the navigator's seat. The switches etc won't respond from the pilot's seat. Thanks Jon

Sure can, create your trigger, use the condition X: Cockpit argument in range Argument "123" is the rotor RPM, engine RPM is 122 The full range of the gauge goes from 0 to 1, I used 0.8 in this example, it triggers slightly too early, you may need to adjust it a bit to your liking. DCS BIOS has a list of nearly all the output numbers from DCS Huey file here UH-1H.lua Here's an example

+1

You can't directly export an analogue gauge (gauge with a needle), or light panel from DCS. You will need a third party program like Helios, or the older and now not supported, iKarus.

Can somebody please just confirm or not this is how it is for them?

Am I the only person seeing this issue?