jeroen79

The speed of sound changes as airpressure decreases. And there is a difference between indicated airspeed and true airspeed. This difference will increase as airpressure decreases. If your airspeedindicator says you're doing 1200 kmh and you are very high then you could be doing 1800 kmh or more. And be sceptical when you read somewhere that plane X did mach Y. Under what circumstances did it do that? Was it a standard aircraft or a special version stripped of anything unnecessary? Is it normal operational practice to go that fast or did they destroy a set of engines to get a record? And what sort of flightprofile was used? M1.0 on the deck is more impressive than M1.5 at 30000ft.

He doesn't call "wings falling off AI". He wants to know if AI controlled planes/helos/thingies will have a more detailed damagemodel. Instead of speaking of "AI controlled planes/helos/thingies" he just calls them "AI", which is a bit shorter. But his message is clear to me.

Correct. While there may be many addon 2D cockpits for Falcon 4.0 these are just a graphical mod. All aircraft, from B-1 to A-10 to Su-27, still use F-16C avionics.

http://www.mapblast.com You can search for countries, cities, rivers etc.

Why should padlock work only if you have a radar lock? Padlock is intended to make visually tracking something easier and to compensate for the awkward viewcontrol that the PC offers. It has nothing to do with radar. I could see some merit in a function that padlocks the radarlocked target (when within visual range) but restricting padlock to the radarlocked target is almost like throwing padlock out entirely. Radar works only in the frontal arc and by the time padlock starts to play a role (the close fight) you may not have radarlock all the time.

That was exactly what I was meaning. Rather than sitting on one point (no translation) the camera would sit on a sphere. The simplicity would be in the controls for the player. Instead of having to control x,y,z translation manually (add two hats) it is done automatically with the x,y panning.

How about putting the camera slightly in front of the pivotpoint? That would translate the camera as it is rotated and it would keep controls a bit simpler. In the same place: http://www.geocities.com/jeroen_huijben/noparallax.txt Camera move forward: http://www.geocities.com/jeroen_huijben/parallax.txt (links will open as pictures)

On the Su-27 and MiG-29 (in LO 1.0x) you can see what navmode you're in on the HUD and which waypoint or airfield is selected on the MFD on a map. With [`] you can cycle through the waypoints/airfields. The F-15 and A-10 show the navmode and waypoint on the HUD. You can cycle through waypoints with [`] but you cannot change the selected airfield. It is not indicated which airfield is selected but it seems that it is either the airfield with a land-waypoint in the flightplan or the closest airfield at the begin of the mission. On the Su-25 there is no indication of the navmode or the selected waypoint/airfield. The only way to know what is selected is by knowing your current position and reading the bearing and distance off the HSI. You can cycle through airfields and waypoints with [`]. Will 1.1 change this? Can we change the selected airfield in the F-15 and A-10? Will the A-10, F-15 and Su-25 give a clear indication of the selected waypoint/airfield? Waypoints could be identified by their number and each airfield could be given a code (radio frequency?). This number/code could then be displayed somewhere. How do the real planes handle this? I know the US uses TACAN and I assume the Russians have a similar system.