Art-J

Not a complex missions creator myself I admit, but I keep reading about issues MP guys have when playing old missions after major game updates. Apparently sometimes simple re-saving the mission works, and sometimes more digging and fixing is necessary. Of course it's possible that some new fuel system bug got indeed introduced in 2.9 (bunch of shenanigans with AI crew members were found and reported already). I just haven't flown Hip missions long enough to confirm your findings in 2.9 yet. Still, I'd take a deeper look at the parameters of the mission itself first.

I fly warbirds mostly, so I also notice it, usually on instruments whenever any panel shaking or vibration kicks in. But that doesn't happen often enough to bother me. I don't use DLSS either. Keeping DLAA only is sufficient quality vs performance compromise for me. My biggest issue with old MSAA was that it never fully solved buildings & fences shimmering problems and it was too much of a resource hog for my 3070. DLAA throws all these problems out of the window, so some ghosting is a price I'm ready to pay. Guys who fly jets were reporting ghosting problems on their HUDs and that was apparently mitigated somewhat in the hotfix, so I'm sure these new techs will certainly be tweaked and tuned more, affecting us prop-heads as well.

Why did you choose that folder path? Suntsag's instructions say the mod folder should go into Saved Games/mods/tech/ location. Just checked - then it shows up in Artillery tab allright, as seen below. Haven't tried it it still works in 2.9. It's 3 years old mod after all, so chances are limited.

Upon taking a second look It seems to be just a texture problem indeed, similar to boost gauge one. @NineLine since the latter has been reported, could you please highlight this new issue as well? Maybe the gfx artist will fix both together while he's at it. The instrument animaton logic is the same as it was in 2.8, but kollsman scale texture (apart from being divided somewhat different) is just reversed in 2.9, which results in incorrect operation of the instrument: a) In 2.8 rotating the knob CW rotated kollsman scale CW - towards higher reference pressures (scale increased to the right), which corresponded to CW rotation of altimeter needles as expected (higher airfield elevation above MSL). b) In 2.9 rotating the knob CW also rotates kollsman scale CW - but towards lower reference pressures (scale increases to the left now), which combined with CW rotation of altimeter needles causes incorrect, reversed operation of the instrument (lowering reference pressure cannot cause higher airfiel elevation above MSL).

A good demonstration, but I'm not sure what's the point of it really? This ghosting is known and expected side effect of DLSS, affecting all aircraft in DCS. You might try to mitigate it somewhat by not using DLSS at all and sticking to DLAA only, or combining DLSS with some sharpening, but it's always going to be there compared to very clear but very inefficient MSAA.

That's interesting... and worrying a bit. Simple copy-paste used to be possible and made things easy when restoring from backups or switching between Stable and OB, as long as it was done on the same PC and Windows install. Controls not loading between clipped and non-clipped Spit notwithstanding - that's another issue altogether.

I'd start with investigating mission file as well. Turning off random failures option doesn't actually turn them off if failures are still defined in the mission, in aircraft properties tab IIRC.

Although you're right about the mods of course, I've noticed some guys reporting the same magic framebox showing up on default C-17, Il-76 and C-130. The mod on the screenshot is probably based on one of these. I recall someone already created a thread about it, though (can't find it now with this new forum layout, I hope mods can ).

Yup, that's what I figured, but I just don't see it happening on that map, albeit I haven't tested the Autumn scenery yet. That's why I think some gfx setting or mod conflict might be the culprit. @rhinofilms have you tried cleaning up Fxo and Metashaders folders already?

Uh, so the kollsman scale is different and reversed in 2.9 compared to 2.8 then. Nice catch and quite important one! Could it be the case of yet another different version instrument modelled (or rather textured), just like in case of boost gauge? So maybe in a similar fasion, the coded window rotation logic is OK, but it just doesn't match the new (reversed) texture?

Nah, the QNH vs QFE is currently Spitfire-only issue. Quite possibly introduced with 2.9, but I haven't flown the plane in 2.8 all that often to recall how its altimeter worked then. The altimeters in other Allied planes work correctly and according to briefing window, haven't tested German ones. The instrument being wound to extreme is a separate thing, a feature rather than an issue from my point of view. It's always been the case across all maps really, but that's more of a "DCS'ism" in general, with some warbirds always spawning calibrated to QFE and the other always calibrated to God knows what.

Errr... I'm not a native ENG speaker, but your question doesn't seem to make much sense. Do you mean "become" and "bare"? I can't watch the track, 'cause it requires A-10C and I don't own that one. Could you use one of the free planes or post some screenshots? I haven't personally noticed anything noticeably wrong happening with trees on Normandy in 2.9 and I've "flown" between them using F11 free cam, far and close. Maybe your issue is related to one of new gfx options?

I think your memories might be rose-tinted somewhat . Been flying the plane since 2014 and although I remember the over-priming flames, I'm positive there never was smoke. Can't see it on pre-1.5 videos on YT either. It was wished for / requested since the beginnig, that's for sure! Steam cloud from engine overheated and blown on the ground was there (maybe still is?) The exhaust flames coming and going with updates are a problem for all DCS warbirds, Pony is not the only one. I would, however, play devil's advocate here and say the new prop animations, gun muzzle animation, tracer animation, 2018 cockpit repaint, BTD's sounds, cooling revamp, they all show that some hefty updating effort still goes into the oldest warbird trio (51, K4, D9) every now and then and they were way more important in my opinion than exhaust effects. Wouldn't mind getting proper ones, though, I'll give you that. It's the only area where DCS warbirds visually fall behind other sims at the moment. In 2.9 Spit and Mossie have overpriming flame glare visible (without any flame itself ), plus they have magic eternal flames from two stubs showing even when their engines are dead cold, so there's something going on there in animation department. Not sure If I want to see such shenanigans happening on Pony, though. No flames at all might be a better outcome.

^ Yeah, i saw it. My guess is a good as yours, unfortunately, but it's good to see it reported quickly at least. Since more knowledgeable guys say the 2.9 gauge face is for older gauge model which should not be there on Merlin-66 plane in the first place, I hope they'll give the gfx artist a task of drawing a new texture with old scale. That would do the trick. Texture job should be easier and faster than coding job (for needle movement) anyway, but that's just my speculation.

Then you chose the wrong platform to play videogames, 'cause PC + VR + flight sims combination requires quite a bit of tweaking to make it work best, or sometimes to work at all (especially in DCS, although other sims are no exception) and some basic knowledge of file properties or shortcuts editing will be necessary sooner or later. Practices from other businesses don't apply here. Sorry to be blunt, but that's the way it is. But you're getting there it seems. Your screenshot shows your initial approach was correct, there was just wrong folder involved and some typo errors in "target" window. I gather from your screen you already have a desktop shortcut for Singlethreaded version of DCS.exe, located in Bin folder, 'cause you've shown us the properties of it. OK then. Right click on the shortcut, click properties, go to "target" window again and copy-paste the line Flappie wrote above your last post, with one exception: leave \bin\ in the middle instead of \bin-mt\ (because you're editing shortcut for Bin folder, not the Bin-Mt one). Make sure the rest of the line is typed in correctly. There's a catch, though. Flappie's line was intended for shortcut for Multithreaded version of DCS.exe located in Bin-Mt folder (hence he wrote \bin-mt\ in it). That's because some of the new 2.9 features work in Multithreaded mode ONLY and thus you might need to go that route in the end. So, If you have a shortcut for that version as well, then repeat steps above but copy-paste Flappie's line to the Target window exactly as it is.

Contrary to what one might think about "seriousness" of DCS, I'd bet there are many more players who just fire up their engines and fly to do pew-pew and dakka-dakka ;). We noticed 2.9 boost gauge bug quicker because that one is actually much more important. But yeah, I can confirm the kollsman window bug. I remember reading that Channel map used to have some weird ambient pressure issues (not sure if it stll does), so I tried good ole Caucasus. Screens below show readings taken at Vaziani. Pressure set to QFE (~ 974 hPa) yields approximate field elevation (~1540 ft) instead of zero.

Wait a minute. So was it almost upside down or 30'ish degrees roll as you described in your old thread? Can't be both. I never experienced the former in DCS, I do experience the latter, but it is more of a mild annoyance during gunnery rather than a flight safety issue.

It was at some point, introduced with great fanfare in patch notes and all. Then it got broken some updates later and never recovered .

I still use its predecessor - OvGME, as it's apparently a bit easier to set up than OMM, but have you read through OMM's dedicated thread?

Yes, module licences are tied to your account, not to your physical installs, which you can have many of on your computer. As long as you log into your OpenBeta with correct login and password, and if all your purchased modules were installed in enabled in your Open Beta as well, they will be accessible allright.

^ I use the same combination and it offers relatively the least blurry/ghosty image for me as well (RTX3070 and 1440p monitor here too). Some gfx imperfections do exist, as inevitable side-effect of any "deep learning" technique, but I consider them a small price to pay for otherwise more efficient antialiasing than old MSAA. TAA was not for me, though. Way too blurry. I recommend giving other eyecandy options a try. I think the SSS for example improved forests and vegetation look quite a bit for me, even when put on top of my modest previous shadow settings (medium + flat).

^ Haven't flown that one in 2.9 yet. I guess all V-12 birds need to be checked then.

Can confirm, it's the same 2.9-introduced glitch as one reported in Spitfire bugs section. Screens below.

Ha! Haven't thought about using night mission to highlight the same problem in Mosquito. Good idea. Off to take some screenshots then.

Well, it kind of is. These errors and warnings are "normal / usual" in DCS, you'll find similar ones after using other map and aircraft combinations as well. They don't affect performance in noticeable way (or should I say, they're nothing compared to much bigger hardware and settings related factors) and thus can be ignored. About the Pimax, I'd ask in VR or 2.9 performance section of the forum. There will be many more people discussing these matters over there.