Jump to content

Recommended Posts

Posted

Hi,

 

 

I play the campaign the second time, so I know the BFT09 is my weak spot.

So I decided to play the included training mission first for some practice.

But every time I got a TERMINATE because of Q- altitude exceeded when on final to batumi.

 

I tried it 5 or 6 times. Every time the same result and I didn't know what's wrong.

Then I fly the campaign mission the check if it is a bug only in training mission and passed it on the first try.

 

Please check if something is wrong with the training mission.

 

 

I love your campaign!

 

 

Regards,

Kal

SYSTEM: Mainboard MSI MEG X570 | CPU Ryzen 7 5800X @ 4.5 GHz | RAM 64 GB @ 3200 MHz | GPU GIGABYTE RTX 4090 | 1 TB SSD | Win 10 x64

DEVICES: ASUS 27" LCD | TrackIR 5 | LukeClip | Quest 3 | PointCTRL | Virpil HOTAS | MFG Crosswind | TableMount MonsterTech

MODULES: To much to list. But I stopped buying more, because of too much bugs in e.g. A-10C(II). @ED: Fix the bugs and I spend money on modules again. Promised.

PROJECTS: OpenFlightSchool: DE / EN

Posted

Training mission bug

 

I have noticed this with the UH-1 training also. I have been trying to learn cold start up. The first time I tried the I opened and closed the cockpit doors repeatedly and the training would not move forward. The second time I tried the engine start buttons would not work including the home key. The third time I turned the radio on and off several times and the lesson would not move forward.

  • 7 months later...
Posted (edited)

I have a bug that forces me to fly for ever to heading 120 after touch and go in Batumi. When I try to deviate from 120 the FE yells at me, that I have to keep the 120 heading. And there is no end to this. Even when there are mountains in front of me.

 

 

Also the FE tells me that I am off altitude when I am perfectly on the ILS glide scope on 2500 feet a few miles away from the runway. What the hell is his problem? Besides the off altitude problem he also complains if you are off course no matter where your actual position is or if you have to compensate for the crosswind. So if you have to change your heading a bit in order to get to a waypoint, then the FE is too stubborn to understand that. Really annoying when this bug terminates the whole mission!

Furthermore in some cases he claims my speed is too high for landing even when my angle of attack is correct such that the green circle turns on. So I am sure now that it is defnitely not my fault. Probably I have really bad luck that I am often triggering those bugs. :D

Edited by Tiramisu
Posted (edited)

I am not sure any more which tacview files belong to which bug, because I tried this mission 15 times, but I think it should be this one: https://ufile.io/01kywipt

Btw. in that tacview replay you can see that I got distracted and missed the first waypoint after takeoff, so I had to turn until I was close enough for the next trigger, but in the end that worked for me without problems.

 

Anyway, one of those bugs I was talking about happens at the end of that trackfile, when I try to get to the second waypoint of the landing pattern after my touch and go landing. I have noticed too late that my heading was not quite at 040, which did not terminate the mission, but it caused me to deviate from the waypoint position. Also I did not make the turn sharp enough after the first pattern waypoint, so in the end I had to fear that I might miss the next waypoint. From my previous attempts I know that if you are too far away from a waypoint the triggers will not work correctly. The FE however only cares about your heading, not about your position.

 

At the end of that trackfile I had to deviate from 040 to roughly 350. Maybe that was not necessary in order to get close enough to the next waypoint, but I wanted to make sure that it will work. Unfortunately this was the reason why the FE terminated my mission, because my heading deviation was too big. I think in real world the FE would also take your position into account like any good air traffic controller would. So I suggest that in this mission either the restrictions of the heading deviation should be lowered or the FE should give you headings dependent on your position to the next waypoint instead of the hard coded ones.

 

 

After a few more attempts it seems like I have finally made this mission, but the FE did not give me a quality rating after saying "let me confirm your shutdown procedure". Maybe it is because I have damaged the gear of the aircraft when I landed too hard. My end score was 100, but still I think that this is another bug, when the FE does not give you a rating after shutdown.

Edited by Tiramisu
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...