4.12.2 de-bugging

[KG26_Alpha]

Originally Posted by Genosse

First of all I'd like to say that you've a stunning job on the 4.12 patch. Thanks a lot for your efforts TD!

Here are some points I came across ...

After returning to the QMB the national markings are messed up: once set up enemy USAAF aircraft appears to be VVS after getting back into QMB.

Another thing is the behaviour of the AI planes on takeoff in the QMB. In the attached QMB mission I assigned another P-38 to take off as my wingman in order to interecept incoming Japanese aerial forces. After spooling up all engines my AI wingman seemed to bounce up and down with the result that he bent his props. Maybe you can re-experience this situation flying this QMB mission.

Thank you in advance,

Genosse

Just tested

Results

A bit random >>>

Sometimes there's a bounce and a prop is damaged

Sometimes he only starts the port (left) engine.

This usually happens if you start both the engines quickly to scramble whilst the AI behind you is still in the engine start procedure.

?






.

[Soldier_Fortune]

First of all: Thanks TD for your great effort mantaining this amazing sim alive.

Second: a minor bug in the Go 229... its AFN-2 instrument doesn't work.

S!

[Baddington_VA]

Maybe somebody mentioned this already.

Took off on a mission, course was 270.
But all the time the AI flight leader announced vector 090.
I noticed this throughout the mission, that the vectors given
were the reciprocal of the intended.

This is a mission I built in FMB.
So I am certain of what the true course vectors are.

[ElAurens]

I've had the same issue in the Hawk 75 Campaign.

Radio directions do not match course at all.

[Sapper]

On several occasions when firing at right hand engine on Beaufort II, the undercarriage will fall away leaving the covers in closed position.

[FC99]

Originally Posted by Baddington_VA

Took off on a mission, course was 270.
But all the time the AI flight leader announced vector 090.
I noticed this throughout the mission, that the vectors given
were the reciprocal of the intended.

This is a mission I built in FMB.
So I am certain of what the true course vectors are.

Post the mission, please.

[Pfeil]

I've spent a good two hours figuring out the following bug(that's existed since the introduction of beacons in 4.10 AFAIK):

When a carrier with a YE(Hayrake) beacon(USS Carrier Generic, etc..) is added to a mission, any player aircraft on that team without an appropriate receiver("Only USN, USAF, RN and RAAF planes carry ZB receivers") can no longer jump from "beacon: None" to the last beacon in the list.

I.E. wraparound scrolling is broken, but only in reverse. When going down the list using the "beacon next" key, it simply skips over the YE beacon to "Beacon: None".
When using the "beacon previous" key, it's still possible to go back in the list after using "beacon next", but it gets stuck on "Beacon: None" when you reach the start instead of going through the list in reverse order.

[Baddington_VA]

Originally Posted by FC99

Post the mission, please.

Here is the mission that was giving reciprocal course headings

[Aviar]

Originally Posted by Baddington_VA

Here is the mission that was giving reciprocal course headings

I ran the mission through the FMB. After takeoff, the flight leader called out a heading of 270, which was correct. Is there a different way you want it tested?

Aviar

[Baddington_VA]

The mission was flown via 'Single missions' when the wrong heading was given.
I'm going to try it again. See if it is a continuing problem.


Tried the begining of the mission a couple of times.
At the take off the heading is 270.
This is followed by just after take off by a 'where the hell are you ? course 060'
even after the next waypoint, the course is not 060.
Unfortunately haven't had time to check if this is happening in other missions.

Had a look in FMB thinking I might be hearing the bombers.
They also turn to head 270.