Mr_Blastman

I stand corrected. The "drag a box" after pressing magnifying + glass allows zooming to resume afterwards. Weird. Still a bug. Hope they can fix this. Thank you for the workaround.

Nope. Does not work in single player missions where this occurs. Completely stuck. One in particular where this is observable is the Nevada F-16 RUS SAM HARM mission.

Sadly my TH Cougar throttle pot has started to go bad, I fear, after 18 years. At maximum forward deflection the POT is now walking backwards at times, endlessly. I could try cleaning, or I could finally swap to better sensors. My halls in my Uber II NXT stick base are awesome, but I never bothered with the halls at the time because the installation for them in the throttle was a bid odd, and Cubpilot has moved on to another existence. Emailed the OP today. I hope this project is still alive.

So I get this bug often in multiplayer where this is easy to fix - I click on dynamic slots and the map unlocks and I can zoom out of a spot. HOWEVER In Single Player such as Instant Action, if I get this bug, I'm stuck. There's nothing I can do to unlock the zoom. Basically I am stuck fully zoomed out, and none of the zoom/unzoom icons will work, keyboard commands, or even the mouse wheel will allow me to zoom in/unzoom. Everything gives me the middle finger and laughs at me. This is a serious bug. This does not affect common aspect ratios such as 16:9. I only began experiencing this at 32:9 and my native display resolution is 5120x1440.

Where? There is no such "fog" option in the graphics settings. There's no way to alter this value for multiplayer servers I join... I have heard this is mission specific setting, but that doesn't help when 99% of time is spent online.

This has probably been mentioned before, but I'm going to mention again: George and Petrovich are practically useless after the most recent update, unable to spot targets. You command them to search for some and they never produce a list of targets to select for them to fire at. This needs to be fixed, ASAP, as this affects both multiplayer and single player.

Yep, looks really great now. Also, thank you to ED for coding DCS so well, and with strong, easy to understand structure that is coherent.

Edit!!!! I did it!!!!!!!!! Haha! So the two files that need to be edited for 32:9 and 21:9 users to get both the Command Interface and the Server/Game Messages centered in the screen are: gameMessages.lua - for game/server messages, edit Line 54, use some math to figure out the 16:9 area of your 32:9 screen, divide the X axis by 1/2, then set that number close to that value, so in my case 5120x1440 = 5120 / 2 = 2560 for a 16:9 screen, then 2560 / 2 = 1280 for 1/2 that, so my Line 54 reads: "local offsetLeft = 1300" (exclude the quotes) The second file, as mentioned above, is: CommandDialogsPanel.lua Line 182: do the same formula as above, and on mine now reads: "window:setBounds(screenWidth - menuWidth - 1300, 0, menuWidth, height)" (exclude quotes again) Formatting is important! Both of these files are located in the X:/Eagle Dynamics/DCS World/Scripts/UI with the second, CommandDialogsPanel.lua, being X:/Eagle Dynamics/DCS World/Scripts/UI/RadioCommandDialogPanel X: being an arbitrary value for whatever hard drive or mount point of your drive. These files have to be updated after every patch. Back them up after editing and either make a batch file to replace or do so yourself, manually. Thanks to MadKreator for pointing me in the right direction. Thank you Sir.

Excellent. So that fixes the input dialogue box, thank you. Now the remaining issue is the game/server messages, how do I move them? Here is an example where you can see them on the far right:

Interesting... Those seem to be Y values, however. How do I move the position to the left on the X axis?

DCS is great on 32:9 ultrawide displays, with added immersion that one who simmed in the 1980s only dreamt of. There's only one minor flaw with the way DCS implements this: the comms/GCI/AWACs messages and interaction box are stuck on the far right side of the screen, near the edge. For a normal 16:9 monitor this is fine, but for a 32:9 monitor that is 49 inches in diagonal... these messages appear at the edge of our field of view and to read them requires turning our head. If we are flying 550 knots at treetop level, this could cause us to crash! Here's an example of what this looks like. Pay attention to the location of the little grey box, and imagine how far we have to turn our heads to read. You my have to fullsize this to see on a normal monitor. Could we have a way to reposition these UI elements? Maybe there already is one in a config file?

I solved the problem by setting ["launcher"] = false in the /users/documents/saved games/dcs/config/options.lua DCS then let me log in, since that information was missing after the upgrade. I think the launcher was panicking? Seems like a pesky bug ED needs to fix.

I am going mad and about to delete this entire program. This is insane. I've spent way too much on DCS to have this go fubar like this.

I did a repair. Not the fullest deep repair though. renaming the folder did not help. The launcher remains "frozen" when I start up. No buttons can be pressed.

This is bad, real bad. When the launcher box does open up and I click on a button, the entire launcher goes black. Firewall rules are allowing inbound and outbound connections.

Swapped CPU and Motherboard yesterday, same windows install, same game install, nothing has changed for years, and I get this error from the launcher: I cannot press any buttons in the launcher. Nothing works. Help.

Definitely _not_ screen tearing. Imagine panning the mouse around your parked aircraft in 3rd person view, and suddenly seeing the screen pause for a moment, then jerk free and your view has been teleported.

So I inadvertently discovered what was causing my huge stuttering and framerate hitches. I have not flown DCS in 10 months because I have traveling. When I jumped into the sim I was concerned about the stalls/pops in framerate. I tried turning off background process, changing graphics settings, etc., deleted shader caches, but nothing worked, until... I saw that in DCS Graphics Settings the "Max FPS" was defaulted to 180. Well, that shouldn't be an issue, right? WRONG I lowered Max FPS to 60 and poof, the hitching went away. Buttery smooth DCS followed. Is this a bug? If not, this should be stickied to help others.

So I finally got a 32:9 monitor--a Samsung G9, which is quite a step up from my former 16:9 1920x1080 display. I recall that in the past, to use a 32:9 display, one had to manually input values, etc., to get DCS to render on them properly. Not anymore! Needless to say, I am stunned at the difference. Here's what the game used to look like on my 16:9 display: And here's what stuff looks like now... Thank you, ED, for all your efforts!

There is a nasty bug with the F-15E on hotpit servers, where if you spawn in a hot jet then you cannot transmit at all to AWACS, despite correct settings. Your requests simply will not leave the jet and go to them. The weird thing is you can hear other players make AWACS calls. Switch to a cold jet and ramp start and the problem goes away.

OP you should always fly open beta if you are interested in multiplayer. You will not find many release servers. Most are open beta.

I think the BLU-107 is also available on the Mirage, as it is a French designed weapon, after all.

I set my 97s to 1200 ft. Burst altitude and then aim for the center point of say a dual ripple release and they hit smack dab where they should. This is wrong, because that means I have to lead a single 97 by quite a fair to ensure a hit, but works for now, nonetheless. I have accommodated for wind by setting up missions with zero wind, but still they are off slightly.

This begs the question... what is the manual engine restart procedure in flight? I had this happen yesterday but could not crank the engines like I would in the Viper...

Kill them well before they get close or be prepared to run...