jonsky7

Have you tried setting the resolution to something like 4340x2680, you can type the resolution into the settings box in DCS game menu, you don't have to choose from the drop down list. aspect, 1.619 that should give you 500 pixels of your monitor 1, I doubt you'll be able to run in fullscreen with that

Would they include TMS Left to bring up the SEAD page on the DED, and TMS right to cycle through the emitters the HTS pod sees?

This works, seems long winded but not too bad to do. If you want the kneeboard to open on your monitor labelled 1 above. Try these values for line 33 as a start. {3840,640,600,800}

@dartagnan Check out this guide

Good to know, thanks

@Munkwolf Don't know where else to post these so here they are. I made custom axis for the Ka-50 Shkval brightness and contrast knobs, HMD and Hud brightness. They are a bit funky as only one side of centre the axis does anything on a couple, but usable. axisCommands = { {action = 3002, cockpit_device_id = 8, name = _('SHKVAL brightness knob')}, {action = 3003, cockpit_device_id = 8, name = _('SHKVAL contrast knob')}, {action = 3001, cockpit_device_id = 7, name = _('HUD brightness knob')}, {action = 3001, cockpit_device_id = 23, name = _('Helmet device brightness knob')}, }

I think the only way to do that right now is a tool like joystick gremlin to combine 2 axis from your physical "joysticks", then output them as a single axis in a "virtual" joystick. When you use joystick gremlin together with vJoy, which you must, you get an additional controller in DCS called vJoy. So you can still set your rudder pedals up as normal for aircraft using the rudder pedal column, and then set the accelerate pedal axis in the vJoy column.

Mouse look externally will also stop working if the F keys comms menu is open, so make sure to exit the menu with F12

No, I think he means the propeller wash kicking up dirt and debris from non concrete/asphalt runways

@Flappie Hello again, well the problem came back So I deleted my saved games folder again and I was moving the files across one by one till I found the culprit when I had a brainwave, which is unusual. I thought "I bet it's the SSAA setting" and you know what, it is exactly that! If SSAA is set to 1.5 the cursor moves up and to the left and gets smaller, and if it's set to 2, it moves further up and more left and gets smaller still. It must not get scaled back to proper size after the super sampling, could you pass it to the team? I guess it's not going to be high on the priority list.

Beyond my expertise I'm afraid

You realise that what GPS was invented for right? Literally the US government put the satellites in orbit for use by the military, there's GPS guided bombs for heaven's sake!

@Cendrawasih TheWay enters the waypoints into the PVI800 in the Ka-50. The PVI800 is this bit The PVI800 will only accept decimal degrees, so there's no real need for the warning and no particular reason to change the units in the Abris other than to have them match. The PVI800 and the Abris are not linked. The Abris is basically it's own self contained unit that uses GPS. So waypoints entered into the PVI800 won't automatically show on the Abris screen unfortunately. The Ka-50 uses the PVI800 for it's navigation info. This info is shown on the HUD, and can be used for automatic route following etc. With the Waypoint button (top left) lit up, pressing 1-6 changes the waypoint to that waypoint for navigation purposes.

@Devrim Firstly, thanks for this. Question, if I put this in the liveries folder in my saved games, the power panel on the right is still in Russian. Anyway to correct it, or should I just use ovgme to overwrite core files?

One thing I miss from earlier versions is the ability to add further steerpoints after hitting the transfer button, in the later versions I have to discard the saved steerpoints to enter any new ones.

Awesome!

Thanks, got it working, it was because Force feedback was set to on in the settings.

I would at least try going back to single monitor configuration and seeing if the problem still exists, if you haven't done so already.

Thanks, I downloaded the latest version of exports scripts and got it working. I had just added the Mi24 lua from the library before but must have needed the whole thing

@AngryEchoSix There doesn't seem to be much wrong there. I have added the GU_MAIN_VIEWPORT, I added that to mine to centre the sights on combined arms, shouldn't hurt but not sure if it will fix your issue. I did test mine and don't seem to have that problem. I'll be honest and say I haven't done much testing with a monitor that is left of the main, you couldn't have it on the left when I did my setup so my second monitor is on the right. Camera + CubeSim_v2.1.lua

I'm not aware of any way to automatically select a different config file per aircraft, but there may be a solution. I don't own the JF17 so you might have to a bit of testing. In your monitor config file where it says LEFT_MFCD = { x = 4490; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 2560; y = 360; width = 1720; height = 1080; } add this beneath it JF17_LEFT_MFCD = { x = 4490; y = 360; width = 825; height = 825; } JF17_RIGHT_MFCD = { x = 2560; y = 360; width = 1720; height = 1080; } adjust the values as you wish. It seems the files for the MFCDs are already setup to look for JF17_LEFT_MFCD and JF17_RIGHT_MFCD in the monitor config file and if it doesn't find them it defaults to LEFT_MFCD and RIGHT_MFCD.

Can you either attach your monitor config file, or copy and paste its contents into your post so I can take a look? And take a screenshot of your display setup from windows. My DCS splash screen appears on my second monitor too, as long as the game runs fine I'm ok with it

EDIT - It has since been found that this "bug" may be due to the SSAA setting. Does the start screen fill the same space? What resolution are your monitors? In your monitor config file saved games\DCS\Config\Monitorsetup\ try replacing UIMainView = Viewports.Center with UIMainView = { x = 0; y = 0; width = 2560; height = 1440; } but change the resolution of width and height to match your main monitor.

Anybody still using this and managed to get it working for the Mi24 Hind? I mean all the gauges are the same more or less. There is a DCS-Export Script for the Mi24 and the gauges even seem to have most of the same IDs Basically I copied my Mi8 profile and renamed it Mi-24P, but Ikarus doesn't want to open it when I launch in a Hind and opening it manually it doesn't read the output from the export-script. Any ideas where I'm going wrong? I can't find anything in the config files that specifically says read the Mi8 output

Hello, Wondering if anyone has DCS-Bios working with the NS430? I seem to have modules working correctly, tried both Mi8 and Hind, but I can't get anything from the NS430, and inputs through the chrome extension don't seem to work. Any help appreciated, thanks