SkateZilla

None of the latest modules supported Game Mode Avionics anyway, especially 3rd party modules. Game Mode (Avionics and Flight Models) have been depreciated for a while, Game Mode Flight model is the next to go, as several modules don't use it, and with several modules it doesn't work correctly at all.

Graphics card wouldnt cause the zoom axes to be offset in WHOT/BHOT Modes.

the detail isnt the problem, the GPU Driver's Rendering settings causes shimmering the downsampled textures instead of mip-maps and MSAA. shimmering on lines and edges is a common MSAA problem.

The dev team is aware of it.

F10 Info Bar in Cockpit Option Enabled + GForce Effects on Camera Enabled Problem Solved. We dont need any more fake HUD info Game Mode things in the Sim, no thanks,. That don't stare at the G-Meter Sure,/ But Real Pilots, especially WWII and PostWar before HUDs become sophisticated, never looked in one spot or fixated on one thing, they constantly cycled through looking at everything in their cockpit. (G-Meter, Air speed, engine temps/rpms, etc etc).

note, if you downgrade to 2.7.14, you lose any updates or patches to that module made after that version as well.

We had DX11 in 1.5, which was out before DCS 2.0 by a whole 2 months, Both Co-Existed for 3 years until DCS 2.5. DCS 1.5 Introduced DX11/EDGE, DCS 2.0 Alpha introduced the New T4 Terrain Engine / Structure., DCS 2.5 was the Major Release the Unified DX11/EDGE/T4 That being said, ED has already said the Alpha branch is likely to not happen again, sooooo 2.9.x would likely be something else, new feature or module wise, Vulkan would be ideal for the next major version. Don't be surprised if 2.9.x ends up simply being MT binaries take over, no more ST Mode. But as far as subversions and revisions go. They usually coincide with major modules (Mainly Aircraft). We have plenty of AC in the Pipe that look close enough to be 2.x releases. MT also states that it's a MT PREVIEW on the main screen regardless of branch.

The problem with MisLinked SG Folders was fixed with 7/30/23 - 2.0.0.36 Server that holds version info didn't update, should be fixed now. AFAIK it will always open on primary screen centered., if you open it in a windowed mode, you can drag it to another screen.

if you're trying to install DCS with just the updater.exe then you need to follow new install initialization steps, which is not part of this guide due to complexity. -Create a Folder, ie: \root\DCS World 2.7\ -Place DCS_updater.exe in that folder. -Run: DCS_updater.exe --quiet init EN x86_64 2.7.18.30765@release -Create a dcs_local_source.txt if needed with path to local source -Run: DCS_updater.exe --quiet install WORLD -Move DCS_updater.exe into the \bin\ subfolder -Create dcs_variant.txt w/ name for builds SG Folder

Likely, Scaling may return, but Text Size would likely be dynamically controlled based on scale Once all the components are properly re-docked/anchored and bound by container controls, but it's not high up on the list at the moment.

Odd that you say dedicated server owners are being hit with 30GB of Liveries, When my Dedicated Server Build is < 14 GB Total. I supposed you are running a DCS Normal Stable/OB Build as a Server instead of the Dedicated Server Build.

Ok Guys, NO Need to argue about it now and prove why the rule exists. His intentions were to better DCS in an area that does need some attention, and likely will be getting it. Whether the videos came from another game or not at this point is moot.

Ummm.. DCS 2.0? We are on 2.5. 2.0 was an Alpha of the New Terrain Engine in 2015 As for a completely new title, "DCS II", doubt it, there's a reason developers are flocking to the Base Game as Service w/ new content and features added through patches model. It's easier to maintain and cheaper to maintain. DCS World in 2023 is not the same as DCS World in 2012. Outside of standard legacy code that has no reason to change, and a few UI Elements, there's nothing left of the original DCS world 1.1.2.1 core. We've moved from DX9 to DX11, we've changed terrain and atmosphere engines, new sounder engine, new weather engine, new physics and wake modelling, rewritten core to utilize Multi-threading, soon to have Vulkan as the new graphics API Retiring DX11 and the problems that came with it, Soon to Model the entire globe. This isn't Madden or FIFA, ED isnt' gonna update rosters and put out DCS '23 with new cover art every year. DCS Simulates an Environment on a Scale that No other "Game" out today does.

For Anyone unaware, there is 2 Scaling options in Windows 7,8,10,11. Text Size / General Scaling: This Option, Reduces the Desktop to a Lower Resolution, and then scales it up to the display to make text, apps, icons, etc larger (which is why items look zoomed / blurry), This doesn't affect Games, just Desktop and Non-Exclusive Rendering Programs. This Option can be set per screen. (ie, my Laptop remains at 100%, while I sometimes use 125% on my 4K TV). Windows Advanced Scaling Over-ride: This Option, Increases your Screen's DPI, making everything larger (Mainly Text and Controls) inside Apps, This setting does not play well with non DPI.Aware Apps (which is about 85% of the available apps according to MS). This Option also affects games, as it's a Global DPI Override, as Windows Standard DPI is 96. This Option forces all screens to the same DPI value

v2.0.0.xx Settings are retained from one version to the next until I change the settings protocol (or the user does)

Yeah, the APP is not friendly with Text Zoom in Windows 10/11, nor DPI Over-rides. I use 125% Text Scale on my 55" LG 4KTV, Sometimes, most of the time I leave it on 100% as the only time I need zoom lately is on the web, in which case I just used chromes built in zoom. Windows Scaling over-rides the DPI and screws up a lot of things, which is why MS Notes its not recommended to be used.

07.31.2023.36 - Corrected Several Tool Tips - Integrated DPI.X and DPI.Y Detection for Furture DPI.Aware Functions - Adjusted Sim Scan Function 2 -> Function 3 Link. - Adjusted / Simplified Log Readouts for User Profile Auto Setting.

I wasn't talking about the aircraft's self intake, if there were other aircraft in formation etc. Even then, bashing through the door would risk a lot, Some of the stories are about as fictional as the JAG "lower your Tail hook and I'll push your tomcat back to the boat with my windscreen" story. The Rule Exists to remove arguments driven by comparative posting of videos from other sims, assuming the other sim is correct and DCS needs to change, and vise versa, and yes, those Arguments were happening all the time before the rule existed. Even if the rule didn't exist, real world video evidence and proof would still be required, as basing an engine change off what another sim does isnt proof.

32 was the last version that relied soley on user input for the SG paths, The problem is users were not setting the correct paths for their builds. The Auto Scan function removed the user error variable, but I did not fore see the stable to open beta and vise versa manual conversion of builds being a problem. I assumed when you converted it generated the dcs_variant.txt but DCS clearly doesnt. I am testing an update locally as function 3 was indeed mis-linked. Putting the dcs_variant.txt in your main \DCS\ Folder with contents "openbeta" then renaming \Saved Games\DCS\ to \Saved Games\DCS.openbeta\ will not break your install. That's how open beta is installed natively.

because the app is setting it as dcs.openbeta, as that's the default path for openbeta branch, As when open beta is installed it creates the dcs_variant.txt w/ text "openbeta" which tells the sim to use \Saved Games\DCS.openbeta\ The problem is when users convert installs, this does not happen, Function 2 sets path by branch, so it would set \Saved Games\DCS.openbeta\ and check if directory exists, if not launch function 3 Function 3 sets path using previous user path. and checks if directory exists, if not sets as "Not Configured". I will go through, maybe there's a mis-link in function 2, that's not triggering function 3 properly on converted builds.

I will check those functions, the General Launch should launch without arguments so there shouldnt be different VR On/Off Behavior. \Saved Games\DCS.<Build>\Config\Presets\Preset0x\options.lua

Not sure why I was tagged in this..

\Saved Games\DCS Updater Utility\ED Updater Utility v2.log But I can almost guarantee, you are running windows at like 150% or 175% Zoom.