Art-J

Yes, and it was clearly explained in patch notes that brought new model back in December. Mossie first as a tech demo, the others to follow. Yesterday we got it in Mustangs and Thunderbolt. There's no going back, only tweaking. I haven't tested the Mossie yesterday on Normandy Manston, though, to see if tailwheel strut is still as fragile as in previous version.

Was indeed implemented for a while, then either got removed, or, more likely, broken. Gotta do it manually again.

Does the P-47 workaround "fix" of defueling and disarming the plane first work in case of Mossie as well? Seriously though, it shouldn't happen in either case.

Pic quality is crappy indeed, maybe it's just old and was shot during Gulf War (hence the sandy background?). I'm not THAT knowledgeable I admit. Can't advise about the scheme I'm afraid, haven't tried this particular mod. I'm sure, however, when AviaStorm release their full fidelity Tornado, all iconic schemes will be there allright . EDIT: have you tried asking on VSN discord channel? They seem to be more active over there so someone will know if such scheme was made for the mod.

It's a pic of a real bird, from No. 2 Sqn.

Their lead artist and lead programmer, so not just ordinary "some people" indeed. Which is their prerogative - whatever the real reason, if they don't feel like doing contract work anymore for whichever company was supposed to pay them, then they won't do contracts for that company and that's that. Simple. I do consider it a non-trivial problem, though. One could say 3D and texture artists are dime a dozen (albeit I've heard this particular person is one of the very best amongst 3rd party devs in fligth sim business), so his replacement could be found sooner or later. Coders competent in flight and system modelling, however, well, they don't grow on trees to put it VERY mildly. And even IF ED does have access to source code of Mudhen (which allegedly isn't even the case), taking someone elses code and figuring out how it works is the very last thing any sane software developer wants to do. Espeicially when ED is not the most efficient entity in fixing their own modules, to be honest. To sum it up, even if ED and RAZBAM come to some settlement and fire is put out, if two key staff members decide to quit anyway, maintenance of the current RAZBAM modules is going to be much more difficult, let alone development of any new ones.

Description doesn't give us enough data. Please save a replay track with this loss of airspeed happening and post it here so that we can take a look. The shorter the better, "free flight" mission should suffice. It's difficult to advise otherwise.

When installing a new module, DCS auto-assigns multiple controls to every damn USB device plugged to your PC. Duplicated assignments are an unfortunate "norm" in such situation and the very first thing you need to do is to browse controls table carefully and delete duplicates indeed.

Thunderbolt is much more pitch-sensitive than either of both Fw-190s in DCS, so I'd actually expect you to have similar problems with former rather than the latter. Something ain't right. Do you use game flight mode by mistake instead of simulation one? You probably have reset many options after getting back to DCS after a while. You already seem to be using easy comms rather than realistic ones judging from training mission woes you deccribe.

Tinker with special options and see what combination of these might work for you. More info here: Mind you, it's a bit old thread so something in the Grom code might've been changed permanently during one of recent patches.

You might take a look if you've got folders called _downloads and _backup located in your root DCS folder and if there's any trash left there (leftovers from failed update process and from modded files being replaced with stock ones respectively). Other than that, however, 228 GB is pretty small size for DCS and not unusual if there are any maps amongst these "3-4 modules" of yours.

As noted above, there has been a way, available for a few years now. Details here: Apart from that, just like in case of F-4 Phantom, some form of Steam pre-order will happen, it's just going to happen closer to release compared to standalone users. What's the hurry? The map won't be released faster on Steam anyway.

WTH indeed. Have you actually fully read the post you quoted, or read that drivel you wrote yourself for that matter? 1) Zach started making Anton skins 3 years after the livery competition took place. If he was around back then I'm sure some of his skins would've been included. 2) He scratch made a whole Anton skin pack literally posted in this very thread and and even more detailed Mustang skin pack as well, available in Mustang section, so looks like he indeed can create some custom content for DCS warbirds. What about you?

It wasn't. Oldschool gyro AHs have been modelled incorrectly in DCS for years, however, and that issue carries over to module after module after module after module etc. There have been many threads reporting the problem, these ones for example provide more info:

Oh, I agree 100%, but experience shows that maintenance and fixing of training, instant and single missions tends to be on rock bottom of devs' priority list in DCS, so I'm afraid fixing them yourself (if and when possible) is a faster solution.

It has been clearly explained in Thursday announement and FAQ, but I've noticed many people tend to NOT read announements and FAQs thoroughly (I'm not calling you out, mind you). Granted, I haven't checked if that info is easily available in game store as well.

"Yes" to both questions. I wouldn't count on the latter, but the former can be dealt with by creating fixed/modded copies of stock missions (as you did) and enabling/disabling them at will during update day using any mod manager of your choice (JSGME, OvGME, OMM).

Turning broken game flight mode off is mandatory for Mossie, so it's good you've got that sorted. After next failed takeoff attempt, exit mission and save a replay track (It's one of the buttons on the bottom of post-mission screen). It will be saved in your C:\Users\[your user name]\Saved Games\DCS\Tracks folder. Post it here as an attachment to your message. The only way for us to help is to watch it and see what's going on there.

Check out suggestions mentioned in this thread:

Go to your Saved Games / DCS / Config / Input folder and remove everything (diff.lua files you created when you were making changes to stock assignments). That should restore all controller settings back to default next time you start the game. Also, wasn't there some sort of load defaults button in ctrl options screen? I kind of recall seeing it but not at my PC right now to check.

^ What Trigati said. Stock missions can not only override your realism & special options but snap view settings as well. Some of them do, unfortunately, which requires manual "fixing". The good thing is all should work as intended in your own custom missions.

The old map (technically called "1.5" as it contains all new areas and assets, just in lo-res version) is theoretically supported as long as you keep your DCS up-to-date. I'm not experienced in deciphering dcs.logs, but there doesn't seem to be anything strictly Normandy related in yours. There are, however, a bunch of DX11BACKEND errors in them indicating more general issue with how your Vega gfx card tries to run. You say drivers are updated, is the card overclocked, though? If it is, can you clock it down and try again? Does the crash happen if you launch the game restored back to "square one"? I mean with Saved Games / DCS folder temporarily renamed/removed and after doing slow repair and cleanup procedure. You might also try to post in general crash section of the forum, there are just many more experienced poeple lurking around there, or tag @Flappie and hope he'll find your thread. https://forum.dcs.world/forum/482-game-crash/

@statrekmike Read BN's reposnse a couple of posts above yours. The rest of the country will follow later. EDIT: Sniped by NL

Business practices from mainstream area of production and distribution don't quite apply in our very specialized and niche software segment. 1) Guys who are crazy about PTO and Corsair will buy it no matter what; 2) Guys who have sub-zero interest in PTO and Corsair will not buy it no matter what; 3) Guys who are possibly so-so maybe kinda sorta half-interested in PTO and Corsair will: a) wait for release and buy it (or not) only after reading and watching reviews from early adopters; b) wait 3-4 years to buy it when it's on sale. In all of these cases, devs' interaction with community in pre-release and pre-preorder phase is irrelevant and unnecessary, as it will not affect aforementioned buying decisions in any way. I agree with Lionel that it would be nice to read more frequent updates on this project, even short ones, but that's my point - it's a "nice to have" item rather than "must have" one and this is where our opinions differ. Introduction of preorder changes things, obviously, but we're not there yet.

Other option - the last time I've read about such symptoms in Mossie, user had game flight mode turned on.