bolek

I think it's the bird strikes. Mission 1 enforces 500% bird strike rate :)

I also had two unexplained engine failures in mission 1. Tried to land in the field but crashed :) Track attached The first failure is at 10:14:43 and the second at 10:23:09 (mission time). I was shot at but not hit (and this was after the first failure). Thanks Battlefield Krasnodar Engine Failures.trk

I just started on this campaign and this is some excellent work! Thank you very much. May I suggest that the messages are shown for a longer time (actually, I probably would need quite a bit longer :-)). When flying at very low level it is very hard to read the entire message before it disappears. Thanks again.

It seems that right now unread threads are automatically marked read after a relatively short period of inactivity. This is a common problem with the vBulletin software but it is adjustable. Would it be possible to change the setting on the forum server from #1 to #3 as described here: http://www.vbulletin.org/forum/showthread.php?t=175423 Failing that, would it be possible to increase the timeout to something like 24hrs? Thanks

Actually, as long as you are conscious you can usually recover. Deploying the air brake helps a lot. It's when you completely black out and loose consciousness then you can't recover (understandably so :)).

I wonder how much of that is the payload/fuel. A lot of people (myself included) have the dubious habit of loading up on 100% fuel and 10 missiles. This is bound to affect center of gravity.

One thing to note is that while you need to purchase additional aircraft modules (except for the two included) in order to fly them in the first person, you DO NOT need them if you just want to control AI units from the mission editor.

I have never seen this. Perhaps your keyboard or joystick is registering double presses? If you use keyboard, try using the joystick button or vice versa and see if it makes any difference.

But I was able to destroy the command post couple months ago, so perhaps at least that has been fixed.

You have to fly fairly level in order to be able to drop tanks.

Here is my entry :-). Very simple: fully loaded plane, push the stick all the way forward. No recovery. departure2.trk

I did not experience this. By "horizontal trim" do you mean trim left and trim right commands? If so, they seem to be working fine for balancing uneven loads. They do seem to be quite sensitive though and it it's easy to over-trim in the opposite direction, so it usually takes me a couple of tries. Also, plane's reaction is delayed so you have to be patient (and again, not over-trim).

Yes, it should happen automatically but see this thread: http://forums.eagle.ru/showthread.php?t=133974

Is it possible that these are contacts received via datalink, not from the radar? I thought such contacts don't show up on the hud (unless radar sees them too)?

I see the roll to the left very often (but not always), in multiplayer as well. As trubrit says, it's not possible to trim out.

Good to know, thanks!

One reason for loosing a lock easier in TWS is the antenna elevation range. In STT radar is automatically pointed at the target. In TWS antenna scan zone is automatically centered in azimuth on the bugged target(s), but the elevation you need to adjust manually as the situation changes. This can be quite challenging, especially at close ranges and high speeds.

It is possible to use ILS in the opposite direction, but you only have localizer (lateral) guidance and not the glide slope (vertical). See also: http://stoenworks.com/Tutorials/ILS%20Back-Course%20Approaches.html

That is some nice flying! Thanks for sharing

See also https://www.youtube.com/results?search_query=LOCK+ON+%28+Flaming+Cliffs+%29+Air+to+Air+-+tutorial+

I have experienced missing sound in Su-27 on mission restart many times. It is actually the in-cockpit engine sound that is missing. External sound seems fine. The missing sound may or may not come back later if I keep flying.

I want a Hawk

Are you sure? I just tested it and when I move the stick forward/back using the up/down arrow keys it stays put after I release the key. It does not recenter by itself. I thought that this was what you (we) wanted?

It is not just a thrust issue. Tires should not be blowing up when breaking at 30km/h. Or should they? Is this how it behaves in RL?

Has this been fixed in 1.2.12 OB? Can anyone confirm? Thanks