4.11 General debugging

[FC99]

Originally Posted by Uzin

Does anybody tried to create or change missions for QMB in 4.11?
In my experience, you can build new QMB missions with a full editor - FMB only at the default maps, not at added ones, their name appears in QMB , but they can not run. Even at default maps, you cannot change QMB missions using new take off options - Pairs or Line, because in QMB the planes are wildly scattered around the airfield.

There is nothing in QMB that would prevent missions work on any map, assuming that missions are made correctly.

Take off in pairs or in line in QMB Scramble missions is ready for the next patch.

[CzechTexan]

I've had 4.11 (clean install) for a week now. Today while editing missions in the FMB, I loaded a new mission and it was almost blank - no waypoints, no objects, hardly anything showing but the green waypoint select lines were showing in several places.

I loaded other missions from other folders with the same results.

For the past week I've been editing missions and everything worked fine, til now.

I read a few days ago (on M4T I think) that this happened to someone else.

[Aviar]

Originally Posted by CzechTexan

I've had 4.11 (clean install) for a week now. Today while editing missions in the FMB, I loaded a new mission and it was almost blank - no waypoints, no objects, hardly anything showing but the green waypoint select lines were showing in several places.

I loaded other missions from other folders with the same results.

For the past week I've been editing missions and everything worked fine, til now.

I read a few days ago (on M4T I think) that this happened to someone else.

In the FMB, click on View/Display Filter and make sure you have everything checked.

Aviar

[CzechTexan]

Originally Posted by Aviar

In the FMB, click on View/Display Filter and make sure you have everything checked.

Aviar

Thank you Aviar! It worked when I checked "all". Just strange because this has never happened to me before and i don't know how it got unchecked.
This may or may not be a bug. I dunno.

[EJGr.Ost_Caspar]

Just wanted to push a 'Thank you!' through the rooms. Due to all your reports many small and some larger issues had been found and are fixed by now already. So just keep it up!

[Pfeil]

This could be a known bug, but I think it's worth mentioning as it still occurs in the latest patch:

When selecting one or multiple engines, some changes made to one engine will carry over to any and all engines selected afterward.

As a practical example, in an aircraft with running engines, select #1 and set the magneto's to off, effectively stopping the engine.
If the #2 engine is then selected, the magneto's for this engine will also be set to off, killing this engine as well.

This "carryover" happens with a number of controls. I've tested it with Magneto's and radiator settings(Open/Closed).

Prop pitch has a similar issue: Set #1 prop pitch to 20%, switch to #2 which is at 100% and decrease prop pitch.
Rather then decreasing to 95% as it should, it will switch to 15%. So the value it decreases from is the one last set.
I'm assuming Mixture will have the same problem.

There are exceptions however: Prop feathering and fire extinguishers do not exhibit this behavior.


My conclusion is that the problem occurs only with incremental controls, I.E. controls with more than two settings.
A possible cause for this is the system reading the variable that was last changed, rather than the one for the currently selected engine.

[IceFire]

Two bugs that I did spot recently...

Ki-27 Ko and Otsu

Part of the engine cowling appears in the gunsight and is clipped.

Ki-43-Ia/Ki-43-Ib/Ki-43-Ic

The prop disc appears to intersect with the camera at times creating some clipping. It's particularly irritating when at full throttle as the flickering does get intense.

Apparently not all can see this. I'm running at a customized 1920x1200 resolution. SaveAspect is set to 0. Not sure if that may be relevant.