jonsky7

If you are inputting a trailing zero for the last pair of coordinates in the Viper, then like Blinky.Ben has mentioned, you are looking at the wrong coordinate type in the F10 Map. The default coord system for the F10 Map is Degrees' Minutes' Seconds (DD.MM.SS) N37'25'23 E45'12'17 The Viper users the Decimal Minute system, Degrees' Minutes' Thousands of Minutes (DD.MM.mmm) N37'25.321 E45'12.282 You can change the default F10 coord system in the settings if you mostly fly the 16, or as Blinky.Ben mentioned use LALT-Y in the F10 map to change coordinate type.

No, Master mode does not have to be set to NAV mode for waypoint entry to work .

@Comrade Doge This should fix the Harrier, done a bit of testing, seems to work. I've just commented out some of the ODU Option 2 presses AV8BNA.java

It seems the recent update may have changed something in the way the coordinates are entered in the Harrier and made "TheWay" not work properly. It couldn't enter markpoints or targets points though, only waypoints, and it would not overwrite previously stored waypoints, only make new ones. The Harrier does have the ability to import markers from the F10 map for target points though. edit: Before the update it was necessary to press the Pos (ODU option 2) to switch from latitude to longitude, this seems to have changed to automatically switching to longitude entry when the latitude has been entered on the press of the enter key.

This could quite probably be the wiring, I've had issues with axis skipping and have solved it by replacing the cables inside. Mine was the joystick x-axis on a GFmk2 McG pro. Absolutely nothing visual to see, no visually broken wires etc, but I suspect the constant movement causes the copper wiring to break inside or detach somewhat from the teeny weeny plug pins. At first it made quite a difference when I added a small amount of superglue that secured the wiring to the tiny plugs. Just a drop between the wires and to the back of the plug to secure them. But it came back eventually. After a few to and fro emails, VKB sent a replacement set of cables and the issue was solved, I made sure to add a small amount of superglue to the back of the plugs on the new cables. So far so good.

Thanks Flappie

Sorry, I do not know of any way to do this within DCS. Using Notepad++ to search for EVERY instance of LEFT_MFCD doesn't show any files relating the FC3 planes. So I assume their files are buried in some non-editable code somewhere.

I have not experimented much with this but, in your monitor config file you could try changing the position of the UI main view. _ = function(p) return p; end; name = _('CUBESIM'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 2400; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920 / 1080; } } LEFT_MFCD = { x = 80; y = 0; width = 600; height = 600; } RIGHT_MFCD = { x = 880; y = 0; width = 600; height = 600; } CENTER_MFCD = { x = 1680; y = 0; width = 600; height = 600; } F14_HSD = { x = 80; y = 0; width = 600; height = 600; } F14_VDI = { x = 1680; y = 0; width = 600; height = 600; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center So the bottom lines UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center Are basically saying make the User interface, the same postion as the center view, I believe it it possible to change that to UIMainView = { x = 1680; y = 0; width = 600; height = 600; } GU_MAIN_VIEWPORT = { x = 1680; y = 0; width = 600; height = 600; } And put any values you like in there, as you would have done for the MFDs. I believe UIMainView is the main menu, and map. GU_MAIN_VIEWPORT changed the position of the sights in combined arms hope, you will need to do a bit of testing. hope this helps, please do report back.

I havent done much testing myself to confirm this, but from my experience and from comments I've read: in the past DCS would use the top left of your primary display as x=0 y=0, when I started doing this you could not have negative values, so I placed my secondary monitors to the right of my primary display. It is my understanding that as of now, DCS will use the top left of the total resolution, independent of where your primary display is. I've based this on nothing more than forum posts. So now negative values aren't used but rather a positive offset will be used for the cockpit/gui display. So if you want any kind of multiple monitor setup, and have a secondary monitor to the left of your main display with say a third on the right, it's very difficult to use that secondary display for other apps like Web browsing etc. As while you can tell DCS to display the cockpit view on the main display using the config file, DCS will black out the display on the left and it will still be the "on top" application.

Not all of the exportable "viewports" have two names in them. I've only seen a few with two names.

Thanks for the suggestions everyone, I posted this when the new Integrity Checks came into force and you couldn't change any of the files. As that has now been reversed, I'm all good again. Changing the display names of each export is exactly what I do to have them where I want them for each aircraft. If there is two names in the line like the below try_find_assigned_viewport("ABRIS","RIGHT_MFCD") It searches for the first name first in your monitor config file, if it doesn't find it it reverts to the second name. In this case ABRIS is first, RIGHT_MFCD is second. So instead of modifying the file, you can simply define ABRIS in your monitor config file.

@BIGNEWY Thanks for the pin

You can run it in full screen mode, when it starts and it's all squashed, just left click somewhere on your second monitor and DCS should resize. Or try Alt+Enter twice, or Alt-Tab out of DCS and back in again. I have seen "Some issues with exporting the FA-18 MFCDs are reported to be because the vertical resolution exceeds 1440 pixels." in the forums Depending on the Max resolution your graphics can take, you could try rea-arranging your displays in windows.

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!