jonsky7

Two things you can try to solve/minimise the jitter, the first is free, and that is to either use the software to disable the backlighting LEDs, or turn them up to full, anything else seems to increase the jitter. The second is to use a powered USB hub, not too expensive. I even had a custom HALL effect sensor made for the "zoom" slider but it didn't fix it. A powered USB hub did though. Which I learned from somebody else with the same problem. I had the same issue whereby it didn't seem to be saving my preferred FOV when I saved a new snap view. What you can do is set a User Curve for the Zoom slider. If you adjust the centre "button" you'll see that the FOV changes when the slider is in the detent, put that where you want it. When you first get in a new plane, the FOV may be the default, just wiggle the slider out of the detent and back again. Then I did a bit of maths to figure out what the other buttons should be. eg my centre is 30 from centre to either end is 5 steps, 30/5=6, so each step up to the middle is increased by 6, (0 6 12 18 24) 70/5 = 14, so each step from the middle to the right increases by 14, (44 58 72 86 100) Downside is that you need to do this for each aircraft, but it's saved in your keybindings, so you should really only have to do it once. This gives a linear change in either increasing or decreasing FOV from the centre, obviously different in each direction from centre but it's not noticeable.

I think this happens when all 3 of your monitors are not the same resolution. I haven't done a lot of testing to be honest as I don't have 3 monitors to set up like this. Does it still do it if you use Nvidia surround or AMD Eyefinity to make 3 monitors act as one monitor?

Just posting this here as it may help someone else The setting is called "Scale GUI" in DCS

Amazing, lovely models, thanks for sharing them with us

Did the other one work?

I've packaged the above file a bit differently, I'm not very good at this stuff, but I got it to work, but I may have downloaded the Java SDK or something. I think the above looks for the jre folder instead.

Did you put it in the same location as TheWay.exe? Try this one, It should go in a folder, alongside the folder called "jre" basically in the same location as your original TheWay.exe but it doesn't have to replace it. theway-slower m2000 and ka50_3.1.exe

Not having an issue myself, Apu running ? Fuel cut-off valve switches set to run, middle-ish of right panel? Are you remembering to disengage the rotor brake ? Black knobbed handle under the red fuel cut-off levers.

The file below is a replacement exe for the way, using Comrade Doge's source code, it works with the Ka50_3 I've also modified it to have a slighly longer delay between button presses in the M2000C Feel free to try if you wish, or wait for Comrade Doge to do an update. (see two posts down for file)

Do you have a really high framerate? I looks like it's trying to enter it too quick. I limit my fps to 60, I don't need more than that for DCS and it saves a little on energy.

I think they are "mini-spade" female connectors, you might have to check the size, but anywhere that sells automotive connectors should have them. https://www.ebay.co.uk/itm/274709665319?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=yqyWTh8pQi-&sssrc=2047675&ssuid=85vtfCFVQLa&widget_ver=artemis&media=COPY https://www.ebay.co.uk/itm/282902935585?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=YRTmJau9QrW&sssrc=2047675&ssuid=85vtfCFVQLa&widget_ver=artemis&media=COPY https://www.ebay.co.uk/itm/275448415442?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=yqyWTh8pQi-&sssrc=2047675&ssuid=85vtfCFVQLa&widget_ver=artemis&media=COPY

Got a picture?

Are you in VR? I don't think it works in VR. and Are you in the Jet already, you have to be in the jet when selecting waypoints. Well I started in a hot jet, I'm not very familiar with the M2000C as of late so don't really the full cold start procedure. Clicked start selecting on map, selected some waypoints clicked begin transfer watched the waypoints get entered My cursor is modified, so it's not a pink dot,

Just tested with M2000C, still working as intended for me.

This guy was having the same issue But his was offset to the left/right, he didn't get back in touch to say if he managed to fix it, maybe you could drop him a PM. Are the monitors you have shown above the only monitors you have connected to your computer? Would you consider aligning your monitors in windows like this? Even just to test it.

Cubesim is just the manufacturer of some displays made for MFCDs, I've seen other people have this issue when using them. I was just going to suggest searching for cubesim in the forum.

Which monitor is set to your main monitor in windows display settings? It needs to be the top one! Have you entered 5120x2880 in the DCS settings menu? I haven't done much testing with multiple monitors for the cockpit view, but both your Top and Center are currently set to display the same thing. I'm not sure if that stops DCS rendering it twice however. Anyway, you will need to change the value of ViewDy in your Center viewport, that changes the cameras view up and down. I'm not sure if you need positive or negative value to make it look down more. tried with fullscreen set to off?

@Comrade DogeNot sure if you have the BS3, so I made a file and tested ok. More or less exactly the same as BS2, but it didn't like the instant input, just had to add some delay to the keypresses Ka50_3.java WaypointManager.java

I think you need a capital V in mainview UIMainView { x = 0; y = 0; width = 2560; height = 1440; }

@Flappie We would appreciate it if you could mention this to the team please, thank you.

I don't know of a definitive list, but that's not to say there isn't one. Below is a list of at least all of the modules that I own that have exportable displays by default. A-10C, A-10C_2 LEFT_MFCD, RIGHT_MFCD AH64-D LEFT_MFCD, RIGHT_MFCD, TEDAC AV8B LEFT_MFCD, RIGHT_MFCD F-16 LEFT_MFCD, RIGHT_MFCD, EHSI F14 F14_VDI, F14_HSD, F14_TID, F14_DDD, F14_ECMD, F14_UHF_ARC159, F14_VHF_ARC182 Pilot upper display, Pilot lower display, RIO lower display, RIO upper display, RIO right display (by right knee), Radio Freq displays x2 F-18 LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD F-5 RIGHT_MFCD JF-17 JF17_LEFT_MFCD, JF17_RIGHT_MFCD, JF17_CENTER_MFCD, JF17_CLOCK_WIN1, JF17_CLOCK_WIN2, JF17_RADIO, JF17_UFCP_1, JF17_UFCP_2, JF17_UFCP_3, JF17_UFCP_4 or LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD, CLOCK_WIN1, CLOCK_WIN2, RADIO, UFCP_1, UFCP_2, UFCP_3, UFCP_4 (if you have JF17_LEFT_MFCD defined in your config file, the LEFT MFCD of the JEFF will be displayed in that position, otherwise it will be shown in the LEFT_MFCD position. The upper line here takes priority over the lower line, this enables you to have the display export a different size or location to the LEFT_MFCD position, helpful because the JEFF screens are not square.) Ka-50 and Ka-50_3 Shkval, ABRIS or LEFT_MFCD, RIGHT_MFCD (again, if you define ABRIS in your config file, the ABRIS will be shown in that position, otherwise it will be displayed in the RIGHT_MFCD position.) M-2000C VTB displays in RIGHT_MFCD position FC3 LEFT_MFCD, RIGHT_MFCD (can not be changed) Want to export any other digital display? See Note or hint If you have notepad++, you can use the Search - Find in files tool. Have notepad++ search for - try_find_assigned_viewport filters - *.lua Directory - DCS world/Mods/Aircraft

bump

Thanks for showing your appreciation, that makes writing the guide even more worthwhile. I use my "right" monitor to bring up the kneeboard, how to change the opening position is on the first page IIRC. Though it may break integrity check on servers with pure scripts set to on (not very many at the moment but hoggit is one of them) Also if I'm using the NS430 GPS I'll drag into the right monitor and make it larger. I also use the right monitor for the TEDAC screen in the Apache, the lower AMPCD from the F18, The EHSI from the F16, the shkval and abris from the ka-50, the TID from the F14 (RIO screen), as well as some other custom exported displays. To set these up is the same as left and right mfcd but with additional entries called TEDAC CENTER_MFCD EHSI Shkval ABRIS F14_TID eg

Well they're certainly doesn't look like anything is wrong with your config file. Are your 3 other monitors cubesim ones?

Can you post your monitor config file?