jonsky7

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?

Thanks, I figured I'd give it a go and all is well so far.

How many waypoints have been imported from the mission? The Right LSK3 is showing ?-1, which is what it looks like when you have entered all 50 available waypoints. It usually looks like ?1 or ?10 etc from 1-50. You will not see anything happening in the A10C when TheWay is doing it's stuff, it is instantaneous for this aircraft. All you will see when it's working correctly is the number on LSK3 change.

Hello, Anybody else finding that it takes a considerable amount of time from when the radar finds a target to you being able to lock it up with TMS up? The radar shows the little white square with a line, but it takes like 10 seconds for me to be able to lock it up. Once the contact is a little white square I thought that means the radar has found it. Am I incorrect? Thanks

Hello, I bought the upgrade for my gunfighter Mk2 to make it a mk3 a while ago, only getting round to fitting it. I'm having a problem installing the new circuit board to the side of the gimbal. Basically my clutch is held together with a stud with a nut on it, and the nut is interfering with the installation of the board, have I been sent the wrong board? I did send pictures of the base as requested when ordering the upgrade. Am I supposed to just remove the nut? Please help, the official tutorial video does not show the same Mk2 as I have.

I think what that function does is switch to weapon view on launch. So you're flying along in the cockpit view, if you toggle that function on, when you launch a weapon it will automatically switch to the F6 view. The best I've come up with what you are after is headtracking hardware, and the use of time deceleration. Slow time down, use a headtracker to follow the missile, then speed it back up again in editing, to achieve something like.....

Ah that's awesome, thanks very much for taking the time to leave your message, certainly makes writing the guide feel worthwhile .

Don't think it's supposed to work like this

I dont have the Mig21 but for the Mirage it seems Razbam have used a different file system with regards to the kneeboard. Probably because they have aircraft "controls" embedded in the kneeboard. And so this "mod" doesn't work with them.

So I've noticed that there's been a change to the way the rotary knobs respond to inputs, though it isn't mentioned in any changelogs as far as I can see. Previously the rotary knobs would auto scroll when a key was pressed, and now they only move one click at a time. While I appreciate this change, I made a keybinds mod to do the same thing, I'm finding the implementation a little clunky. Basically a substantial pause is required in between each keypress, or mouse wheel scroll movement, for the next keypress to be recognised. This means that each indent of the mouse wheel scroll does not correspond to a letter/number change whilst inputting data, in fact if you scroll fast enough you can have five or six indents in before the letter changes. Or you have to pause between each press of a keyboard key to do the same. I didn't have that required pause previously but could scroll one letter at a time by simply adding the following to the default.lua in the keybinds and users could use either the fast scrolling method or one step increment method using the mod. {down = device_commands.Button_8, cockpit_device_id = device_id, value_down = 0.5, name = _('Left big knob Increase in increments'), category = _('NS Device')}, {down = device_commands.Button_8, cockpit_device_id = device_id, value_down = -0.5, name = _('Left big knob Decrease in increments'), category = _('NS Device')}, {down = device_commands.Button_11, cockpit_device_id = device_id, value_down = 0.5, name = _('Left small knob Increase in increments'), category = _('NS Device')}, {down = device_commands.Button_11, cockpit_device_id = device_id, value_down = -0.5, name = _('Left small knob Decrease in increments'), category = _('NS Device')}, {down = device_commands.Button_26, cockpit_device_id = device_id, value_down = 0.5, name = _('Right big knob Increase in increments'), category = _('NS Device')}, {down = device_commands.Button_26, cockpit_device_id = device_id, value_down = -0.5, name = _('Right big knob Decrease in increments'), category = _('NS Device')}, {down = device_commands.Button_29, cockpit_device_id = device_id, value_down = 0.5, name = _('Right small knob Increase in increments'), category = _('NS Device')}, {down = device_commands.Button_29, cockpit_device_id = device_id, value_down = -0.5, name = _('Right small knob Decrease in increments'), category = _('NS Device')}, This has also broken my pretty awesome (self admittingly) voice attack profile, though I did manage to fix it by adding a pause between key presses, but it's so slow now Was this an intentional change? or a new found bug? If intentional, any possibility of reducing the required pause between each key press? Thanks

Good point, we can't ask the navigator to do stuff, so I don't see the issue with being able to do it yourself.

shameful bump

Shameless bump

I've not looked into changing the position of the messages, there is a mod to move the controls indicator though, though the George AI target list is then over the top of it when it pops up. https://www.digitalcombatsimulator.com/en/files/3321356/