FoolTrottel

In the end, it looks like the complexity of all the items listed is giving us some challenges. Indeed. And the one that bother me the most, is the restart-mission issue. The fact we cannot seem to easily restart a mission ... We will never prevent issues from happening with that number of pilots in a multi-engined a/c, spawning in a parking spot with engines off... Whatever we do to be prepared, the chance something bad happening is always there. Not saying we should ignore the technical issues, control issues, pilot errors. No, for sure we should test, and test and be focused ... be prepared. I'd like to figure out why these PWCG mission restarts are so prone to failure - I mean, we have plenty restarts in normal coops, which are run from the same Dserver - only one difficulty settings was changed for PWCG - and I can't seem to remember any restarts being that troublesome - Some do fail, but mostly due to operator error : Generating a mission too late, while it's already loading in the Dserver, pressing the wrong button etc. To test this, and draw some conclusion is nearly impossible. I can run one server, and have two clients connected... tops... lol.

Me too ...

In this circumstance, you may want to dial back the instrument lighting a bit, it might get too bright!

Noobs!

What I learned from this: Second spawn (the one where I let the mission rotate, ie. not re-loaded on the server) the in-cockpit view was incomplete, had to wait until a/c left and right showed up. And that was when some high pingers lost connection. As this did not happen on 1st and 3rd time: any mission restart in this campaign will now mean the dserver.exe needs to be stopped and started. And, if Fen keeps on using the 2.PWCG Mission icon on the server, then the large .mission file will also be deleted -> much faster loading ... Cool stuff, I mean the mission flying itself was. And nice. And thanks!

I am sorry, but this makes me think of a tip like 'Make sure your engines are running, as it makes for a much easier take off run' ... Instrument lighting has been like the first thing I switch on when in cockpit, like forever, and ever !

No need to do this. This one time was a special occasion...

+1

Should be for each and every a/c that has a radio ... well ... See here: https://docs.google.com/spreadsheets/d/1tzd996zJ1t0heZ-t1PpL7vNUIZbXl7pI6De0GThN1Qw/edit#gid=1869108790 So, after reading that, I still do not know...

Technical support for moving a slider? You kiddin'?? How old are you then?

Check what sound device is selected when you right click speaker icon and select Open Volume Mixer. Try with as many devices disconnected as possible: Maybe one is acting as a mouse wheel? Can you lower the volume? Any sound effects activated? Dolby, or ... Atmos? Check device manager, remove all sound devices, reboot and let windows discover and install them again? In other words: Basically, I have no idea!

It takes your current age into account, and thus it tries to prevent you from suffering further loss of hearing ... Windows HearLow (TM) it's called.

Good Show!

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...