Art-J

@paveway248 Just for the future note - yes, that's how all modules in DCS work. "Game/Easy" controls table applies only to game flight & avionics mode, while "Sim / Real" table applies only to full sim mode. Whenever installing a game or a new module, double check what you have or not have ticked in gameplay and special options menus.

+1 for Bozon's advice. 2 or 3 taps of L/R brake will do the job during a couple of seconds of initial roll when rudder doesn't work, but when it does eventually, nothing else is needed. I tried playing with differential throttles when the module was released, but it caused more harm than good and is not really necessary. I never do it nowadays. It comes in handy while taxiing, though!

Good attempt. The only drawback I'm seeing is it makes letters on the central panel barely visible when they're covered by any shadow. Other than that, however, it's a workaround for us.

Il-2GB implemented a similar system some time ago. Apparently It tamed online "rodeo riders" quite a bit . And although the whole physiological limits simulation has been a subject of heated debates in that sim, it still was a step forward compared to having no limits (apart form G) at all. Your request sounds reasonable. There's always some "gaming the game" involved in competitive MP community, however, and I gather it's not the first, nor the last loophole in the simulator to be exploited by some guys.

^ Did you try changing "messages font scale" in game options?

Adding to what was written above, gunsight view options you probably remember (cruise view / gunsight view / combined toggle-view-when-clicking-on-gunsight) are selectable in game special options menu. Options for having a flare gun or not and for rear tank content (MW mix / fuel / empty) are selectable in your airplane properties tab in the mission editor. Recent Issues compared to a year ago? Well, fuel cutoff lever cannot be left/right mouse clicked anymore like it used to be (has to be mouse-dragged), same problem used to affect fuel pumps lever (it doesn't anymore on my PC, but I don't remember if it's because of official fix, or modded .lua file I've been using for months). Other than that, situation with known minor bugs and glitches seems to be stable for years ;).

They're shown correctly on my rig. Both for AI and player's plane, on both Spit variants. Do the usual stuff - disable mods, run repair&cleanup, etc.

We've had it since release, though (if we both mean the same thing). That's how I originally had my THW throttle unit set up: throttles for L/R boosts, grey slider for RPMs combined. Didn't work well in the long run, though. For some reason, even though virtual RPM levers moved together (obviously), the RPMs were always a bit desynchronized in cold start missions and well synchronized only in air start ones. Still don't know if it's a bug, or intended simulation of lever imperfections in real airplane. Doesn't matter now anyway - bought second throttle quadrant in the end to control RPMs individually.

First of all, don't forget it's possible to convert/switch any stable install into OB (or vice versa) via running dcs_updater.exe with relevant parameters. Either doing it manually, as explained here... ... or, in more convenient manner, by using SkateZilla's DCS Updater GUI Utility. During conversion process, the updater only downloads files which are different betwen both current versions and it retains all your modules and settings. That's the solution I would choose. However, if you still DO want to have two separate physical installs on your computer for one reason or another, then the rest of your questions apply and the answers are as follows: a) If you're into MP, then yes you should. I'm not, but from reading the forums I believe most, if not all, popular servers run OB; b) OB installer should detect you already have stable version on your PC and copy/paste as many files from it as it can to your new OB, saving plenty of time and bandwidth. That's what it used to do years ago before module manager became a thing, so I'd hazard a guess it still does and thus your existing modules should transfer automatically; c) Separate DCS install creates a separate folder with your personal content and settings in Saved Games location (it will be called "Saved Games/DCS.openbeta"). As a result, it will be completely fresh and empty folder at the beginning. You can, however, just copy your own missions, settings and options from stable Saved Games to OB Saved Games; d) I wouldn't recommend doing it because of b); You can uninstall the stable later, though, if you decide you don't need it. e) again, see c). They will not, but copy your whole Config/Input folder from stable Saved Games to OB Saved Games and you're done.

Well, this Stang/109/Dora pit retexture happened in December 2018, so "not long ago" is a relative term . That being said, for DCS standards they're indeed quite "new" and I wouldn't expect any work done on them anytime soon, at least not until everything's gonna have to be redone for Vulkan anyway.

Although I don't think fiddling with trims in a turn is a good idea, let's establish if they work at all. Do they in level flight?

Yeah, they're supposed to be and used to be springloaded when operated by keyboard or mouse, but the mouse mode got messed up along other controls back when DCS 2.7 was released and hasn't been fixed ever since. I actually find this "stuck switches" bug useful when I'm on the ground and just want to open the flaps all the way, but I understand it might be annoying in the air.

^ I think the problem is not that master bearing failure has been implemented, but that it seems to be happening sooner than it should when there have been period documents posted in other threads indicating that the engine was rated to rev up to about 3050 RPM (IIRC) in emergency situations. We, on the other hand, are stuck with hard-scripted 2750 redline, exceeding of which during windmilling kills the engine in about 12 seconds every time. By the way, it's the 190 Anton that has the same mechanics implemented, although bearing failures in dives are a non-issue here, because its Kommandogerat decreases RPM together with throttle. I wouldn't say the engine is made of glass. On the contrary, it's a sturdy beast as long as charge and oil temp limits are kept. One can even get away with overboosting to 72 inches all the way until water tank runs dry... but these temp limits are a pain with all coolers being manually adjusted.

@peachmonkey - OK, you don't care, but others do. As long as there's N.20 runnig along 4YA, there's something for everyone. In some of the recent posts You really seem to be seeking for attention and problems where there aren't any.

Make sure oil pressure and temps are OK before taking off, manage the oil cooler doors accordingly. DCS P-47 tends to kill its engine on takeoff easily when these are not within rated limits.

I think he meant Silver Dragon's posts on page 13 of the other thread:

What convergence was used in RL and what is used in DCS are not always the same, though (pattern vs point in US planes is primary example). Unfortunately, ED have been tight-lipped about what they have programmed in most of their warbirds.

Careful - with AI's simplified flight models and their tendency to do neverending loops, competitive performance might actually be more important than you think. Here Dora is the hotrod down low, while the Anton is somewhat underpowered brick, and with both loosing energy in vertical maneuvers rapidly, at least the former can make up for it with its power, while the latter cannot. The only time I could see Anton shine was on Phil Style's SoW server vids, where Phil's teamwork with wingmen made the Anton effective. As other mentioned, free trial is the only way to see which version suits you better.

Fuel problem maybe? With this convoluted mess of tanks, gauges and valves, I would check that possibility. Post the mission file, I won't try it it 'cause I don't own Channel map, but others might.

To add what guys said above, popular comparison to manual car gearbox is a bit dangerous and misleading, 'cause it only applies 1:1 to our 109, 190 and P-47 when they're switched to manual prop mode (the only mode in which you control blade pitch directly). In all other cases governors do the physical blade adjustment, not the pilot, who is rather rpm- or power-manager. If we wanted to compare constant speed props to cars, I guess the only cars that fit would be old DAF variomatics, which could accelerate/decelerate/drive at different speeds while maintaining constant engine rpm.

For ED-developed modules, unless there's some core game update affecting multiple aircraft together, or there's a major overhaul of old flagship product (A-10C, Ka-50), it's pretty much "fire and forget" indeed, with only minor fixes and tweaks implemented occasionally. For 3rd-party-developed modules, it's a mixed bag and depends on developer and module really.

Remember to plug controllers into the same USB ports every time you do so. Switching ports changes port ID number and that can mess up / reset controller settings again.

Why M4? I'd presume it's because it was the last and the most widespread-used variant amongst USSR-allies, still operated today and the easiest one to get reference data about. If OP and Octopus lived without internet and never heard of each other it's obvious for me both would choose the M4, as any other 3rd party most likely would for aforementioned reasons. I really don't see any conspiracy here. Besides, even IF (and that's a big "if" at this moment) Octopus model is intended for DCS: a) anyone is free to develop any aircraft he wants and push the project either towards free or commercial side; b) if Octopus guy decided not to contact OP (it seems?), well, he might have his reasons, that's his decision and he's also free to do so.

If repair and cleanup don't help, the next step is temporary renaming/removal of the whole Saved Games/DCS folder (because it's not affected by repair&cleanup) and checking out how the game runs when it creates itself a new one. If it runs better - you know the culprit of the problem was located somewhere there and you can start restoring sub-folders from your Saved Games backup one by one to narrow down which files cause the issue. For example, your log says the game struggles (and fails after many minutes) with loading CH-53 collision model. It's a custom helicopter mod I think? Get rid of that one - it might just not be compatible with latest DCS version (or see if the updated mod has been released by its creators). Generally, turning off custom mods should be THE first thing to do as troubleshooting, even before repairing and cleaning up.

@lazduc In a couple of weeks stable version number will catch up with current beta and you will be able to install SA map on it if you're just a little patient. I'd wait instead of spending money on a new drive only for second copy of DCS, but in the end it's your decision. Draconus is right, though. Nowadays beta releases are less frequent but more polished and only marginally more buggy than stable. I've been using strictly beta only for at least 4 years now and never had my controls wiped out by the update. I do know it happens every now and then to some guys but I believe it's related to something else in their systems than DCS itself and thus stable version is neither less nor more subjected to such risk. In both cases, keeping controls backups is mandatory.