[FIXED B700ish + DB v436] Missions & Altitude....

[sjadow]

It seems to me that aircraft assigned to missions ignore the altitudes specified when the mission was created. Is this correct and if so why??

Thanks...

[mikmykWS]

Where are you specifying it? In the mission editor or manually by hitting F2.

If you're using a mission correct place is the mission editor and then using the override. If you're plotting use the speed and alt dialog.

Mike

[sjadow]

In the Mission Editor when the mission is initially create..

[mikmykWS]

Could you post a .sav game showing the problem?

Thanks!

Mike

[sjadow]

I will when I next encounter it. Thanks.....

[sjadow]

I tried to attach the save file but when I went to upload it just says "c:\fakepath\the real file.save" is not supported. I dont know where the "fakepath" is coming from... Any idea what I'm doing wrong??

[ComDev]

You need to zip the file first

[Rongor]

Since I face the same observation, I attached a save with this exact problem below. It is easily reproducible here.

Aircraft completely disregard the Speed and Altitude Override values, so both, throttle and altitude. It didn't matter if a/c were attached to that mission while waiting ready at their air base or were already airborne. Speed and altitude settings of the mission were ignored. Manual F2 overrides were inactive.

I put up P-8 Poseidons based at Okinawa to do sea patrols over the south chinese sea. Assigned aircraft were ordered to achieve and keep FL400 while doing the transit and after reaching patrol area. Instead I have one Poseidon transiting at 1500 ft and the one already in the patrol box is remaining on 1000 ft. The latter one is patrolling with cruise setting, although ordered to creep/loiter.

Save was created with B678.3, CMANO is installed and gets patched via steam. I applied the B678.3 files manually.
However, I noticed this issue already before applying 678.3.

[Rongor]

I just noticed while investigating to this thread that Bingo Fuel determination in my case is done by a return flight altitude of 1500 ft. So the a/c reaches bingo a lot earlier to endure the much higher fuel burn at an implausible RTB flying at 1500 ft.

[Rongor]

So apparently the aircraft loadout definitions can override at least the altitude setting. As this may be understandable for the time on patrol station, I don't see how the transiting altitude can also be depending on this.

[ComDev]

ORIGINAL: Rongor

Since I face the same observation, I attached a save with this exact problem below. It is easily reproducible here.

Aircraft completely disregard the Speed and Altitude Override values, so both, throttle and altitude. It didn't matter if a/c were attached to that mission while waiting ready at their air base or were already airborne. Speed and altitude settings of the mission were ignored. Manual F2 overrides were inactive.

I put up P-8 Poseidons based at Okinawa to do sea patrols over the south chinese sea. Assigned aircraft were ordered to achieve and keep FL400 while doing the transit and after reaching patrol area. Instead I have one Poseidon transiting at 1500 ft and the one already in the patrol box is remaining on 1000 ft. The latter one is patrolling with cruise setting, although ordered to creep/loiter.

Save was created with B678.3, CMANO is installed and gets patched via steam. I applied the B678.3 files manually.
However, I noticed this issue already before applying 678.3.

You need to set 'Mission Profile' to 'Use Speed and Altitude override to use manually selected altitudes [8D]

The latest database (v436) corrects the cruise altitude and the P-8 will cruise at 36k ft and patrol at 1500 ft.

Thanks!

[Rongor]

Cool, thank you!