FoolTrottel

Altitude? We're still on the ground! ??

Sure, good idea, but... I was not the only one that it happened to... I mean, it's just pressing a button/key twice, without you really wanting to do that... a mishap ...

Cools, Thanks Very Much Perf! And Crash! So, we can now stop testing, and we have a work around!

Well, that did not help. Not even with clean keymapping, as in only Proppitch, Mix and engine start assigned. Can someone please execute this exact simple test: Spawn in a P38. Set Mix to 100, RPM to 100. Then hit the 'Engage engines start procedure / Stop engine' key TWICE. Not just once, but twice, nothing special As if it did not take the first press. And next, see what that 'Engage engines start procedure / Stop engine' does afterwards. As a re-install did not fix it, and I even tried it on a separate computer/install. Now when I wait a while until both engines are running, then stop them, and wait until I see 'Battery off' message, I can re-start them just fine.

Hm, so... I guess I should try a full uninstall- re-install then. Here goes!

Nope, button was replaced. So, you can start engines in P38, stop them - like before they even started - and then restart them again?

On our DF server: P38: Hit start engine button, engine start procedure begins. Hit button again, engine stop procedure begins. Hit Engine start button again: Nothing happens, as if the button is broken or unassigned. Finish mission, start again, and button works. (This occured to me last P38 mission, due to a worn out button.) Tested following twin engined aircaft that have this 'bug': - P38, A20B, Pe2-35 Aircraft tested that do not have this 'bug': - 110G2, P51D, Pe2-87 (!) Is it a bug? Can anybody please test, and confirm/deny, and also test for other a/c?

Yes!

First you'll have to click that EnableErrorReporting.reg file, and then wait for the next crash to occur: It will then have created a .dmp file.

Prop pitch is Engine RPM, and fully forward means at 100%, yes, lever fully forward. Mixture CUTOFF I suppose that's 100%, then when engines are running, set to 70%, which is Auto Rich Coolers are automatic, so - leave them alone

Thanks! Server has been updated as well, both Stable and Open Beta. Server will/can/should hopefully sort its own bindings out ... Fingers crossed!

Me thinks there's a chance the #C Libraries have some corruptions. How to fix? Goto Apps and Features, and scroll the list, for all the Microsoft Visual C++ items: - Select it, it will show a 'Modify' button. If it's greyed out, ignore and move to next one. If Modify button is not greyed out, click it, and choose 'Repair' Do so for all of them listed, there can be a few... it could be a long shot, but ... Here's the list of my PC, and as example a greyed out Modify button...

I don't think there's a better place for it, as we do not have a recycle bin on these forums! 🤑 (Ohh... that was mean!)

Well, I discovered why I had engine start issues: Worn out button: Press it, nothing happens. Press it again, engines on, engines off. Oh well...

Done!

0.97 is now available. It will deleted any of the Excluded skins that may have been uploaded (yet again) by some git who did not update to the latest version, yeah, I really should've provided a version check and autoupdater function - oh well... So, no real need to update - it's under control - well, maybe it's not if it is you that is the one git uploading those invalid skins - because you will never get rid of them, unless you download and install the latest version!

Beautiful paintjob Sid! I wish my masking skills were as good!

like yer reading these forums withe yer silly hat on? pfftt.. you'd be so lost!

Acer Predator XB241H Why? - It's 24" can't fit anything bigger in - It does G-Sync, which I wanted to fix stuttery in il2 1946. That did fix it, too bad we quit 1946 a few months later I think... TN, VA, IPS? Dunno, do not really care. Yes, put them side by side, I may see the difference - but this one looks good. And if I cannot see things in game that others can, I blame my eyesight... that's the quickest "solution"

I think I got into an F14 #326 group on the Supercarrier? I did not, my bad!

Sure, but I must confess... I logged on to DCS on the server, using my own credentials, and thus I could install the Supercarrier module. Next, started the Dserver under the DangerDogz account, and ... yeah, I could spawn in on the deck... (I did not take off in the 14, so did not attempt to land, and thus never asked for permission to land!)

Okay, uuhhmmhm, let me see and have a look at this issue ...

No! Catapults are for Sissies!

Sure! No worries, plenty of runway there ...