Art-J

Is such "static" mission time even a thing in DCS? Just curious - I've never experienced sun not moving in my 9 years of playing this sim.

^ It's all correct, of course, but... mostly off-topic and irrelevant for OP's issue. Which is - how both 190s, as equipped and simulated in DCS can (or cannot) be used against its AI or human adversaries in DCS. Whatever happened in real life about front lines, fuel, pilots training etc. in '44-'45 doesn't apply here. The intermittent engine failures problem of Dora is being investigated in its own thread in bugs section. The only thing we can do is more testing, posting tracks and hoping for the issue to be looked at by the devs. Same about AI simplified FMs and weird damage model symptoms.

Looks like the same thing Reflected did in his "V for Victory" campaign, which is: clever use of scripts, triggers, custom voice recordings and tons of time spent in the editor to make all this stuff activate and work in correct order, moments and locations.

^ Honestly, I kept my settings as they were and haven't looked for a fix anymore. The pixellation shows only in specific lighting conditions, with specific cloud presets and only when my plane is rolling/pitching fast. All and all, it's not noticeable enough for me in majority of the missions I fly to be bothered by it. It's certainly less noticeable than the problem of micro-jumping cloud layers anyway. IF it's caused by DLAA maybe (which I use), then so be it. Pros outweigh the cons in such case. Granted, I haven't experienced patterns as ugly as shown on pavelpilot's screenshots yet. These must be more somwhow related to cloud preset he used in his mission, but I don't know which one it was.

Finally had a chance to fly a bit yesterday. Not sure how I feel about factory-fresh-black faces of the instruments. They show a lots of contrast agains panels, especially the trim indicator. They tend to look a bit lighter on photos, albeit it might just be a question of reflections in real life vs lighting and shading limitations of DCS gfx engine. Other than that, not being a rivet-counter and RLM colours expert I like that mod a lot already and will certainly spend more time with it.

^ Cuesta brothers I'd hazard a guess. Maybe they want to implement similar solution in their flyable mods.

I recall Steam guys did have numerous issues with making the update work correctly when it was first released. Maybe you did buy it but something didn't "click" right. In either case, hey, if it works it works. Glad you've got it sorted.

Not experiencing it either. Maybe it somehow depends on options 'cause I see on your video you've got lowered gfx settings. Although I've no idea how textuer quality could possibly affect animations - it shouldn't. Also, keep in mind that repair doesn't work on files stored in Saved Games location. Perhaps there's something there (some custom mod you use?) which affects the 109.

Size and number of files and folders is correct. As razo+r pointed, that's Normandy "1.5" you're looking at. All the detailed stuff that comes with version 2 is just hidden/locked until its license is purchased and activated.

Looks very nice. I use Massun92's repaint now, but I like some extra details in your version. Can't wait to try it!

I think when 2.9 was released and broke boost gauge, altimeter and compass, players were just more concerned with getting these critical instruments fixed in timely manner. Gear indicator was only a cosmetic nuissance by comparison. Still, now that we've got instruments sorted, it's worth reporting indicator well. Tried to look at various known onboard videos of restored Spits being flown, but they all either have the indicator inop, or use different type of it. Googling for the indicator itself seem to confirm this version should most likely be red over green indeed.

Yup, it's been reported multiple times years ago (albeit not always in dedicated bug threads) and allegedly acknowledged by Nick as something to be improved in the unspecified future, but looks like it got buried under other issues to fix. Nothing wrong though about bringing it to attention again.

Whoa, that's some psychedelic s..t right there . I don't own either Apache or AMD card so can't advise. I do recall people being not quite happy with 2.9 FSR implementation, though. Multple posts on the subject in October, scattered over bugs section, but didn't follow them much after settling with DLAA. You better search and ask around over there.

^ Still, if vastly superior newer spec variant is available at the same price, that's the one OP should get when purchasing a new unit from authorized source, not an older, less-capable unit, which has been gathering dust in a warehouse since Autumn 2022 (if not earlier). Or, they should at least offer it at a slightly lower price - they know exactly which serial numbers are older spec after all. They'd still find customers for it, 'cause not everyone needs slew control (I, for example, don't use it in my Warthog at all).

Zach (or anyone familiar with description.lua mumbo-jumbo), could you guys help me with an issue? I gather TF- version of Mustang borrows some textures from the P- one. I've noticed that after applying reworked textures to P-, two liveries in TF- list don't seem to be working corectly: a) Bare metal one has missing canopy and windscreen textures; b) 364FS 357FG one has missing all but tyre textures. Pics shown below. I'm a bit puzzled by it, cause I've always thought Zach's textures are just replacements on one-by-one basis and thus TF- should find them and load them as well? Not quite it seems. How can I fix that? Does it require editing relevant description.luas of aforementioned liveries in Coremods, TF- folders? EDIT: - Ouch, I missed the quoted post above, already referring to the canopy issue. Sounds a bit voodoo for me, but will try to decipher it and fix the canopy at least. Wouldn't mind advise on the other skin though!

It's going to be the only post-1960's era Red side full fidelity fighter module available in DCS in forseeable few years future. Yes, I know Mag3's MiG-21 Bis is a 1972 plane, but systems-wise it's not different from older versions. Plus, it's a bit of a shoddy module compared to today's DCS standards, in dire need of a thorough overhaul, which might never come. Beggars can't be choosers in full-clickability department, and so the -23 is going to be a critical addition to DCS no matter if it was a good airplane or not.

The particular issue shown on the video above was fixed two patches ago. But, as Nealius mentioned, gyro alone is pretty good (probably more than it was in real life), so you'll probably rely on it more anyway.

You must've misinterpreted something. DLSS and DLAA in 2.9 require an RTX card to work, but are not dependent on ray tracing or reconstruction otherwise. DCS doesn't use these and is still DX11 title. Vulkan version is being developed in the meantime. Why have you posted this thread in the bugs and problems section if you're not reporting a bug here anyway?

^ Nah, Normandy 1944 had these three sets as well. I remember it well, cause only Autumn scenery looked kind of allright, while Summer and Spring had hoplelessly oversaturated cartoon greens everywhere. Not sure how Normandy "1.5" works now (N 2 user here), albeit I suspect it inherited most of ground and foliage textures from N 2. In either case, it seems winter scenery was never part of the devs' plan indeed. Nothing wrong with wishing for it, though!

^ ...which is completely irrelevant, though. Channel is Channel and N2 is N2. From DCS code point of view they're independent addons with airbases which might carry the same names but are separately programmed by a different company and that's it. As you might have noticed in this forum section, quite a few of new airbases introduced with latest N2 update suffer from various hardcoded bugs which limit their usability. The only thing one can advise is to post bug reports here. Ugra guys are usually not very active on English side of the forum, but there's hope they noted this thread and will submit fixes to ED for one of the next OB updates.

You can still run ST mode of DCS by launching it off dcs.exe directly, but since ED is slowly phasing out this version anyway (as shown by the aforementioned new updater shortcut behaviour introduced with v2.9), sooner or later you'll have to get used to MT, warts and all. As for the best upscaling and AA methods, well, simply put, all these AI-driven, "smart" technologies will always cause visual side effects (usually various forms of ghosting) as a price to pay for increased FPS. "There is no free lunch" as they say. Whether you're willing to pay this price is up to you, and hugely depends on your hardware, framerate-vs-eyecandy expectations, aircraft you fly, if you use 2D or VR etc. I, for example, as pancake user with NVidia card, skipped DLSS completely (still have sufficient performance without it), but happily adopted DLAA (ultimate shimmering killer without murdering FPS like MSAA does, at a price of some ghosting here and there - an acceptable tradeoff for me). For this reason, I don't hink there's a single thread anywhere on the forum with full description of pros and cons of each mode, because pros and cons are different for different people. You'll just have to browse through multiple threads which popped up when 2.9 OB was first released, and/or take a look at comparison vids like the one Jabbers did (picture is worth thousand words after all).

As you probably figured it out, these two white protruding thingies on both sides of the cockpit are pistons responsible for canopy jettison. As razo+r said, double check if you ain't got this function assigned to anything on your HOTAS or keyboard.

There's not enough info in your post to answer your question, but, to cover general DCS comms "peculiarities" you might not be familar with, please keep in mind that: a) There's easy comms and realistic comms to choose from in DCS. The former doesn't require setting up radio channels, frequencies etc. in mission editor correctly while the latter does. The choice between two is done by ticking the relevant box in gameplay or realism options (I don't remember which one now); b) It's possible to communicate ONLY with planes, ATC and ground crew of airbase which belongs to the same coalition colour as you (blue on blue, red on red); c) "\" key by default (communications command) is supposed to mimic pilot shouting out of the opened cockpit. Thus, if realistic comms is selected, you can use it to "shout" to ground crew or even ATC, but only while you're on the ground, with canopy open. In every other circumstance you're supopsed to bind and use push-to-talk command - "Alt+\" by default, which mimics using the actual radio equipment of your airplane. d) Various offline or online missions created by someone else can override your own realism & gameplay settings. So the question are: do you use easy comms and which mission exactly you're having problem with (is it one of stock ones available in game or a custom one you made for yourself?)

Never experienced anything like that in any DCS warbird either (unless proper warm up was not done), but I only do singleplayer I admit. I do recall, however, that MP server settings override your own, so who knows what the admins have prepared for you.

I haven't used Reshade in DCS for years, so I don't remember its config files anymore, but I do recall profile file which stores your settings was just text files really with fancy extension. Thus, Instead of re-doing your old settings from scratch I guess you should be able to edit the old file using windows notepad or Notepad++ app, typing in new folder path (pointing to Bin-MT) copy it to Bin-MT and maybe that should be enough? Explanations you've read related to MT and non-MT version of DCS still apply. You can still play "standard" version of course, 'cause MT is still a bit rough around the edges. But since DCS will be moving to mandatory MT for good sooner rather than later whether we want it or not, I'd say it's time to start getting used to it. The only things which 2.9 added were all the new graphics features (DLSS / FSR, SS Shadows and whatnot), some of which can only be enabled in MT mode, so - that's one extra reason to switch.