jonsky7

Check out the guide I made for setting up MFCDs, I think that doing it the way you want to will cause some issues in DCS, nothing major, things like the controls indicator might not appear where you want them, then you'll have to decide if it's better for you to have your desktop behave as you want it, or DCS. You shouldn't need to change your centre viewport, just the y position of anything you want to display on the 2nd monitor. Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; } } DCS will render things within the resolution you give it, whether or not you have any part of a display to actually show it. So similar to the examples in my guide, yours will look like this. Anything DCS renders in the red area, you won't be able to see it as there is not any part of an actual display there.

I might have misunderstood your question. If you really want to have your displays setup like you have, then you need to adjust the resolution in DCS. You will need to add some vertical resolution in the DCS settings menu, by as many pixels as your 2nd monitor is below your 1st. You can type a resolution in the box in DCS, you don't have to pick one from the drop down menu.

In windows display settings, try and grab monitor 2 and align it with monitor 1, rather than trying to align 1 with 2. A bit of back and forth and you can normally get them aligned perfectly.

If I understand the question correctly then no, doing this will pass integrity check.

They definitely do test them to destruction, edit: but on the ground, then from the data gained they draw up the flight envelope limits. The problem with sitting in your chair at home is that there's no way to simulate the force needed to yank the stick back. Even with hydraulic powered flying controls, the feel of the stick can be changed by increasing or decreasing the load of a centring spring using an actuator, or other device, this is called q-feel nowadays. (I have no idea if an F14 or Harrier had a Q-feel system) Then there's the amount of G you'd be pulling to break the wings off. In most cases the pilot would probably black out due to G-LOC before the wings came off, but yanking back on the stick with all one's might at supersonic speed might. It's probably one of the reasons fly-by-wire is the go-to choice today, the flight computer system will limit controls surface deflection to prevent the wings snapping off. Not a fighter but a stress test to destruction

I'm sorry, I have absolutely no idea.

Oh, just remembered, you might need Combined Arms to control units in game, Probably should have led with that, sorry mate If you have combined arms then you should see this in game map And the option to set it is in the mission editor here:

I dont seem to have too much trouble navigating using it. I can enter an airfield ICAO code and get directions, and use position entry to get to a desired coordinate with reasonable success. I have seen the issue regarding true/mag heading, but maybe I don't suffer from it as much as I mainly use it when flying heli's, and they're normally flying sideways anyway . It's a picky bug yeah, i was just curious why they would put the extra digit in there in the first place.

And what?

Yes, well depends, in game you can go into the F10 Map, click on any unit in the Hawk site group, in the bottom left you get the unit location info, and depending on mission settings you also get a control menu, this menu lets you set ROE and ALERT STATE (it's the same menu box for moving vehicles etc) So the "it depends" is dependant on: 1. The unit is visible in the F10 map (ie not hidden) 2. Server/mission settings allow control of ground forces. (I'm not very knowledgeable about which setting it is)

Yes, it seems hawk sites do not track enemy planes unless their alert state is set to RED.

Crucially the real thing does not. There's a difference between the real thing and DCS, The picture above is from the Garmin manual The game looks like this There is an extra 0 after the N in the position box, the latitude coordinate. In the real thing there is a blank space.

That's the point, it's in the Wish List section.

As I previously stated "It was a single player mission with Easy communication off in both the mission and settings menu." It is a mission I set up with every module I own set as client, so I can choose any, and either practise or test changes. So the settings were exactly the same for the modules where the menu would open, and for those that wouldn't. So other than "that's the way is" and "it's a good system, just read the manual", if ED were to reverse it to opening the menu anytime the / was pressed, would that negatively impact your gameplay in any way?

Correct. Good for you, thanks for sharing.

Actually NO, you're very condescending aren't you? It was a single player mission with Easy communication off in both the mission and settings menu. Which was exactly my point, it is NOT consistent between modules. As in the same mission, I also tested the 18, the 16, the ka50, the Huey, the Spitfire, the Mustang (paid), which DID NOT open the communication menu when using /

You're very welcome. Not sure about re-arming, I didn't try in game, should not be any reason for it not to though. You need to own the Ka-50, Are you sure your folder structure is correct in OvGME? like: OvGME Mods\Mod APACHE JGSME\Coremods\aircraft\SA342\xxxxxxxx and OvGME Mods\Mod APACHE JGSME\Mods\aircraft\Ka-50\xxxxxxx google traanslate Necesitas poseer el Ka-50, ¿Está seguro de que la estructura de su carpeta es correcta en OvGME? como: Mods OvGME \ Mod APACHE JGSME \ Coremods \ aviones \ SA342 \ xxxxxxxx y Mods OvGME \ Mod APACHE JGSME \ Mods \ aviones \ Ka-50 \ xxxxxxx

Are you playing the same game? Communication menu opens in air using \ in: A10C Harrier Mirage Viggen F14 Gazelle and those are just the ones I own, annnnd one of ED's own modules is in that list. Why is it that there is always someone protesting against a change that would not effect them in the slightest?

Well obviously there is if posts like these keep popping up. They keybinding is called "communication menu" and not "ground crew communication" or "easy communication menu" The problem is that is not consistent between all modules. Some modules it works all the time, some it doesn't work in flight. You've either got to have it completely realistically implemented or not. eg, on the ground in a hot helicopter, you'd still have to use a radio for the ground crew to hear you. Whether that be via intercom, which in some cases, like the Huey, you would have to select that, or by radio transmission. My vote is just have the menu open when I press \, if I'm not on the correct radio, then the receiver doesn't hear me.

@Ice Rhino I've never had a monitor to the left of my main monitor in windows settings, so I'm interested to know how it turned out.

@Si45Might be the issue that your mod manager is adding the folders to the saved games folder, rather than the DCS core directory. I know there's a long post saying to put your mods in the saved games folder, but I've never done that, all of my mods are written to the DCS core directory, hence the mod manager.

It seems that while doing a repair the engines are not fixed after having an engine fire, caused by excessive vibration, likely due to the fact that I occasionally *cough* push the bird to the max. In fact, the repair sequence won't start with only damaged engines, I had to do a hard landing and snap the tail off. But the engine wasn't fixed.

Please visit this thread for a more up to date version of this guide

@Ice Rhino Try this monitor config file, copy it to Saved Games\DCS\Config\Monitorsetup\ Main plus 2 cubesim.lua Then in DCS System settings menu Set your resolution to 2560x1680, if that is not a selectable resolution, you can type it in the box. Set your aspect ratio to 1.5238095238, can also be typed Choose the config file, name is Main Cubesimx2 Click "OK" DCS should restart

Why does the Latitude Coordinate have 3 digits for degrees? It's not possible to have a Latitude above/below 90 degrees. from the Garmin Manual https://static.garmin.com/pumac/GNS430_PilotsGuide.pdf