Art-J

Unless they decide to dump their current practice of keeping a few older builds on their servers for a while, one should still be able to roll back as usual with relevant dcs_updater command. They haven't suggested otherwise (so far at least), and neither did they say anything about forced updates of the unified version, so let's wait and see before predicting doom and gloom.

Ah, another beauty. I'm off my gaming rig for a couple of weeks, it's going to be painful to wait before I can download and try this one out! A suggestion - since it seems you've started doing more DCS projects recently, have you considered posting them separately in aircraft individual skins section of the forum, like this one... https://forum.dcs.world/forum/446-spitfire-mk-ix/ ... or just move this combined thread to general skinning section? I'm finding your recent DCS skins "by accident", either after checking out user files on ED website, which I don't do often, or stumbling upon this thread here in Military section, where I almost never visit, and which is not intuitive place to be honest when one searches for skins. I suppose I'm not the only one in such situation. Damn, before finding wooden wonder Mossie skin I didn't even know you did any DCS stuff. Your awesome skin releases deserve to be easier to spot!

Yup, some guys have been experimenting with manual replacement of that library file. Results vary between configs, but seem to be comparable or better rather than worse, so it's worth trying, as long as you keep a backup:

The only thing I'm concerned is - has Nineline re-checked the bug thread to notice that the glitch can happen in MT build as well, not in ST only as he thought initially. The thread is still marked as ST problem, which clearly isn't the case.

@Schlingel mit Kringel I agree with you to some extent and I know that unification sounds like a great idea at first glance, but it's just not always feasible in practice. What if 3rd party figures they can develop some feature which is better than ED's one (e.g radar) or is missing in DCS core (e.g. wear and tear)? They can't sit and wait for ED to implement/improve their unified solution, because ED coders might have different, much more important "crucial priorities" to develop at that moment (e.g. Multithreading, Vulkan), so it could be a few-years-wait. Nobody can afford that. What if opposite happens and ED develops a better feature while 3rd party module starts lagging behind? In theory 3rd party should revisit and upgrade their product to the newer standard, but who's going to pay for workload required? Most 3rd parties in DCS consist of part-time workers or volunteers and thus maintenance and upgrading of older products will always be of lower priority compared to new projects which bring new income and keep the teams going. Realistically, I'd love to see unification of "small things" first, like convention of left/right mouse button flipping the cockpit switches up/down in some modules, but down/up in the others. Damn annoying and should be easier / more affordable to standardize by all parties involved in DCS.

I'd hazard I guess it's because this thread is confusingly "hidden" in util/program mods section of the forum where it doesn't belong, not to mention a section which is not visited by majority of DCS players in the first place. I've been wasting waaaay too much time on browsing ED forum for many years and I'm various mods user, but even I stumbled upon this thread only recently and purely by accident. I'm super glad I did, because these extra presets are awesome, but the mod is just neither "visible" nor easy to find.

By the way, thread for this mod is not locked, so go ahead and post there if you have other questions:

Nah, nowhere in that highlighted fragment of article Shamrock suggests additional DX12 support being planned for DCS, he just mentions its internal testing and capabilities in general, next to Vulkan's ones. Even if there were doubts about future plans back in '21 when the article was written, it's safe to assume today based on later ED newsletters that DCS is going strictly Vulkan.

^ It doesn't seem even M3 devs themselves have made a 100% final decision about what they want / can update in the MiG. It will probably depend on time and resources availability related to their other projects. There also is no single place where they listed all planned 2.0 features. Go to their website and just browse through annual and summer updates back to 2021. There will be some info about the MiG posted in each of them.

Now I can indeed see it in the track above, while playing in latest OB and despite using only MT. That's the 1st time, though, haven't seen it in my own missions previously. Could be something in the mission parameters that triggers it, like infamous ground controls reversal of MiG-15 caused by wind. @vgilsoler @Raptorattacker Do you guys see it in no-wind missions as well?

Yes, in theory they sound like unrelated things, but people are grouping them together, because for whatever reason Snap Views option needs to be enabled if one wants to fiddle with default cam position and FOV. Confusing but that's DCS for ya. This reminds me of camera lens effects that must be turned on as well if we want the sun to be rendered fully instead of a simple white dot on the sky.

Well, the last thing that needs to be tried then is temporary removal of all custom mods and apps from Saved Games location, whether they are 109-related or not. You've got quite a few of these, judging from your log. Then launch the game and see what happens. Keep in mind that repair and cleanup procedure fixes the main game folder only, but does nothing to content in Saved Games folder at all, so if source of the problem is hidden somewhere there, it's going to be still there no matter how many times you're executing repair command.

You better look around or ask in VKB section of the forum. I guess the problem might be VKB software-related. https://forum.dcs.world/forum/158-vkb-sim-flight-gear/ "Mainstream" products like Thrustmaster have their axes recognized automatically (I use two throttle separate quadrants from them). I believe VKB requires a bit more tinkering to configure it properly.

^ I presume players are usually OK with current 300 per gun as a weight and performance compromise suitable for various types of sorties, but technically, if ammo boxes in wings could be filled up o 425, we should be able to do so for, let's say, CAS missions every now and then. Granted, MTOW limit would indeed be an important factor, but that's what the sliders in loadout options are for.

It's a bunch of dds files, so just take the ones you need and dump all the rest. For gunsight you need to use mark_II_base and mark_II_tick files, that I can confirm because I use exactly these on my PC. For armoured glass, I don't know, but looking at the filesnames, I'd first try to keep the ones with word "glass" in them and see what happens.

Then stop acting like "believer" yourself. Nobody in this thread said DLSS gives better quality than raw rendering. We all know it comes at a price of some quality. But acceptable or "noticeable" quality reduction from using it is a personal preference and different for everyone, just like acceptable minimum framerate, or acceptable level of stuttering. You seem to be blind to that fact, though.

Yup, looks like this skin's description.lua contains references to bomb fairing and tank files which are not there, neither in coremods, nor in skin folder. Should be easy to fix, unless @sticks_62nd, who is the author of the livery, would like to create and submit to ED custom blue textures for these components?

C:/Users/(your Windows user name)/Saved Games/DCS World (or Openbeta)/Logs/. These are the ones needed for troubleshooting, but the latest ones should be dated according to the last time you played DCS.

BN forwarded the info where needed, but just for the record (figuratively and literally), I've experienced recently an engine shudown sequence which took 38 (thirty eight) seconds of poppin' and bangin' (25+ pops per engine) after pulling shutoff plugs, with extra overpriming fire animation (?!) thrown in as a "cherry on top". Track below, recorded in current Open Beta. It's 28 min long so if anyone's still interested in watching, just fast forward to the end, it plays without desync (on my PC at least). One aspect which is consistent with Nealius' latest video above is the fact that my mission was set to winter conditions, like his. Looks like low temps must affect this problematic aspect of simulation somehow. 2.9_Mossie_test.trk

As Kerosene noted above, it's most likely caused by some custom mod located in Saved Games (remember that repair command checks only the main game folder but doesn't check Saved Games location!)

Post your DCS logs from both PCs. We can't troubleshoot without them.

It's still there to some extent, but honestly, it's visible only when panels are hidden in shadow, so it's not such a big deal really. Thanks for your efforts anyway! Maybe time of day has an impact as well (I do these test flights in default Chanel cold start mission).

Sid, If that's really the case, you're the first guy who reports it for MT then. In either case, devs can't do anything without your dcs logs. Zip and post them here so that they can take a look and investigate further.

Granted, FAQ doesn't literally say naval version (whichever gets chosen) is going to be a separate product, but that's most plausible scenario.

Enable snapviews in misc. options and then use keypad to move and save new cam position. Details here: