Laurreth

Same thing, the screenshots you posted there are almost completely black on a calibrated monitor. If you blow up brightness so much that you start to see crass banding, that's likely not an issue of the game but of your game or monitor settings. There simply aren't enough gradations between "black" and "almost but not quite black" in an 8-bit render to support that sort of postprocessing.

I'm suggesting that the monitor is set to 100% brightness or some feature like MSI's "Nightvision" that massively overbrightens dark parts and ruins the image.

Those screenshots are almost entirely black, it looks like you're running some crazy brightness boost on that monitor. That would of course introduce extreme banding since colour resolution in those narrow ranges is almost nonexistant. The histogram of the first screenshot looks like this in ACR: You can't really do much brightness boosting with that out of an 8bit source without having a horrible result.

Can you please post a screenshot with the effect? (I still assume the two pictures in the OP are photos taken off the screen.)

Do you see the effect yourself on screenshots? (Do you see any banding in the menu screenshot you posted in the first post?) Could you include some screenshots for a side-by-side comparison with the monitor photos? At that point I'd dig through monitor settings and try to run it as close to "ancient" technology as possible, i.e. 8 bit per component (try forcing wherever it's available, graphics driver and monitor settings) no HDR no "gaming features" like e.g. the "night vision mode" that MSI markets on some of its monitors; there also appear to be "gaming modes" that I'd disable, but then again I'm weird. if the monitor has it, sRGB colour profile (will look washed out AF once you're used to wide gamut monitors) Given the manual of the MSI G27C6: Gaming Game Mode "User" Night Vision off Response Time "normal" or "fast" (I hope that doesn't fudge with colour rendition, but who knows) MPRT off (whatever the hell that's supposed to be) Professional Pro Mode "User" Eye Saver off (that will definitely do weird things with colour rendering) HDCR off Anti Motion Blur off Image Enhancement off Image Color Temperature to one of the presets to avoid having some weird effects from a custom white point

Try removing your monitor profiles entirely and see if that changes things. I've seen some really bad results come out of stock monitor profiles and calibration attempts where weird things happened. If you could attach a copy of your profile that'd be interesting too.

Make sure you have enough space free on your D drive. See if that file already exists and if it does, delete it (both D:\DCS World\_downloads\Mods/aircraft/Mirage-F1/bin/MirageF1CE.dll and D:\DCS World\Mods/aircraft/Mirage-F1/bin/MirageF1CE.dll). If you are using some 3rd party antivirus software, try disabling it, e.g., by setting up an exception for the DCS installation folder.

And then you still need to pray that the mainboard manages to run that stuff anywhere near stable without severe underclocking or overvolting; no, Asus is not a sign of stability in that area, during the DDR3 era I've had several Asus boards that straight up refused to run stable with 8GB sticks without best guess manual adjustments. And you do not want to fill up all RAM sockets because that will make things even slower and worse. The 1050Ti may even be fine for that though; DCS quickly becomes CPU intensive, and that CPU won't be able to throw enough data at it to make it sweat. If at all possible, I'd try to find a cheap DDR4 system with a moderately recent CPU (even a first-gen Ryzen 5 will run circles around the 870!) and throw the graphics card in there. That'll give you much more room to play with.

Drop everything 90° into the break, and you'll quickly get a feeling for how the plane behaves once you level out. I've found it to still balloon quite a bit, but that's nothing a little forward pressure on the stick can't fix. It becomes a bit of a Kata after a few dozen Bolters. (Yes, I suck at carrier landings, sue me.)

Letztens war eine Aktion für Cyclics; melde Dich am besten für den Newsletter an, die schicken solche Rabatt-Aktionen rum und der ist ansonsten recht ruhig, vielleicht eine Mail jeden Monat oder zwei.

Zufällig nochmal über die erste Seite gestolpert und muss doch noch meinen Sanf zum Thema Stick-Rotation versus gute Pedale geben: nimm die Pedale, wenn du Geld, Platz, und den Willen die Dinger ab und zu hin und herzuräumen aufbringen kannst. Am Stick rumzuschrauben nimmt immer irgendwo Präzision raus, oder man kommt in gewissen Stellungen nicht mehr komfortabel an alle Knöpfe. Wenn dann noch etwas Angstschweiß ins Spiel kommt, geht Rotationsachse garnicht mehr.

The one time I try to be inclusive

AFAIK for Apple stuff you'd need to do a native Metal implementation, yet another shade of green. Metal 2 and up may even be suitable for games.

Yeah, I agre with that; it's just a general observation on the choice between Vulkan and D3D12. If you have something that's only supposed to run on platforms supporting both, there's no reason to make it religious.

TL;DR as far as I can tell would be that there are more important construction sites, first and foremost the scripting engine. Hop onto a busy multiplayer server like Enigma, get a whopping 17 to 24 FPS, then check out performance metrics, and the game is stuck with the Lua task eating a tonne of CPU and the rest of the game doing more or less nothing. Vulkan won't fix that. The other thing is of course, why not go DX12, which offers about the same features? In therms of graphics, that gets you on the vast majority of gaming systems (Windows, and current XBoxes) and unless you really REALLY want that 3% Linux Gaming marketshare and maybe target the Switch, Vulkan is a bit of a weird decision from a pure ROI perspective. Apple and PS4 are using their own things again, so there's no gains to be made in those directions.

Ich habe mich zu Virpril breitschlagen lassen und eine WarBRD-Base mit Constellation Alpha Griff, sowie den Mongoos CM2 Throttle am Tisch. Beide sind super Geräte. Die Mongoos-Base ist wohl eher was wenn du den Stick mit Verlängerung zwischen den Beinen haben willst, die Basis hat kleinere Winkel und dafür höhere Rückstellkraft. Wenn du F-16 fliegen willst, wäre ggf. der Mongoos-Griff die bessere Wahl, oder halt ein entsprechender "Replica" von Thrustmaster. Dazu hab ich noch die Tischklemmen von Monstertech mit passenden Platten; Monster lassen sich zwar wirklich fürstlich bezahlen dafür dass sie leicht bearbeitete Standardprofile und Alu-Platten verschicken, aber funktionieren tut das Zeug. Im Vergleich zu den Tischklemmen von VPC spart man auch ein paar Millimeter Abstand vom Tisch und ist etwas flexibler, weil da alles in Nuten verschraubt wird statt dass man nur ein paar vorgebohrte Löcher hat. Die MFG Crosswind bereue ich auch nicht. Bei denen sollte man ggf. die hydraulische Dämpfung gleich mitbestellen, weil die "kaum noch was kostet" wenn man eh schon einen vierstelligen Betrag in Hardware steckt, und dann hast du das Ding halt und zahlst nur einmal Versand.

The ASE circle before you have a lock is a visual indication that you have an AIM-120 selected and does not indicate anything about a fired missile hitting anything useful (it will not). Once you have a lock, it's getting smaller and you need to put the little steering dot within it. The symbology with the big circle on the HUD may be a holdover from the AIM-7 that had a "FLOOD" mode where the plane's radar would continuously radiate out in a small cone straight ahead and you'd fire the missile in the hope of it tracking anything useful that might reflect the emitted energy.

Game capture works fine with DCS for me. If you're on a laptop, https://obsproject.com/wiki/Laptop-GPU-Selection-Windows-10 may help. OBS also has an active Discord for support, usually you should be able to find help there.

Is there any particular reason why you're running either software with admin privileges? Neither needs it under normal circumstances.

The thing is that a lot of the controls are already heavy compromises. I doubt that most people are running around with all the little things that various manufacturers have put into their real birds, e.g., locking 3-position switches, spring-loaded wheel inputs (like is the case here or on the F-16), 4-position toggles in a star pattern (yes, those happen), or MFD frames with 30+ functions on each. Most people will have a number of 4-way hats, maybe some 2-ways, simple buttons, momentary on-off-on switches, axes that don't return to centre (as turning knobs, sliders, or levers in varying forms), or rotary encoders, and IMO it just makes sense to cater what a lot of people have. There's also the other side: many input devices will have a bunch of locking on-on toggle switches that would be perfect to map to stuff in the cockpit, and ED is on average surprisingly bad at supporting those.

Yes, I'd also please like an unrealistic option. It's far more likely to have a surplus axis on a throttle than to have a centring wheel or surplus analogue centring axis. I'm using the slider on a Virpil CM50 with a very strong in-game curve which sort of works because it comes stock with a huge deadzone and a tactile centre, but it's still not great.

Running the game at 2560x1440 ("1440p"), cockpit displays are set to 1024. Graphics card is a Radeon 5700XT with 8GB VRAM, I've seen the issue with both 22.5.x drivers so far, haven't tried 22.6.1. options.lua

Have a thanks, I distinctly remember pressing that button, didn't remember what it did yesterday The manual says that the Recce button on the stick only blanks the HMD (which probably isn't correctly representing the real plane at all); has that changed in the meanwhile, or would it be "safe" to map that button somewhere else for now? I'm using a rotary encoder for HMD brightness anyway, might as well map Recce to the push function of that to make it a bit more intuitive.

Last night I was doing a sightseeing tour of about an hour with a friend; maybe 20 minutes in, the HMD vanished and I couldn't get it back to work. Tried turning brightness to zero to turn it off, waited, turned it back on, attempted the BIT which passed without showing the test patterns at maximum brightness, disabled hiding it when looking straight ahead. Is there something that I could (accidentally) have done that would hide the HMD?

Considering that you can vastly over-G even GA aircraft and still land them somewhat safely (though severely crinkled), the limits on combat aircraft would likely be conservative too, at least as long as they aren't carring twice their empty weight in ordnance on the wings. Apart from "wings snap", the damage would be more on a logistical side, i.e., maintenance reaming the pilot and planes going out of service for a good long while until an antire new airframe can be procured. Disabling repair/refuel for an aircraft that has been strained significantly could work? As soon as it lands, ground crew just runs up to the plane and siphons out all the fuel to make sure nothing worse happens to it