At first thanks for testing everyone. And thanks for your feedback.
I will release a much improved prototype soon.
- Altitude indication is incorrect, it showed about 700 ft when the pilot actually reported about 2300.
=> Yes, I had the wrong units. ISO instead of miles, feed and stones. There where more problems with the speed: It was given in relation to the aircraft, so my METAR wind compensation to calculate airspeed was wrong too. This is fixed in the upcoming version.
- Altitude should be displayed by 3 digits ONLY i.e "xx" and not "FLxxxx". The first digit should represent the TENS of thousands, the second digit should represent the THOUSANDS, the third digit represents the HUNDREDS in ft.
i.e: "230" = 23,000 ft
"058" = 5,800 ft
=> adapted, I have added the vertical speed in hundreds of fpm to the radar screen and to the flight strips and location and distance of the radar contact to the flight strip. This should be reviewed. Is propably not available in reality, but useful if you need to see if he lands or starts. Maybe I change to something more realistic, as proposed below.
- Magnetic headings should be shown, and not true (it does show true at the moment)
=> Where can I get the magnetic variation from? Does FG has a file for that?
These are the main things that should get fixed.
Now here are some other stuff that occurred just to me, I'm not sure if these problems really occur for everyone else.
- I can't receive voice through FGcom, sending voice does work though. (Delta server)
=> I can, although if I run many things over my network or on my computer to the same time, I hear it distorted. Try to start it manually using the test frequency 911 (argument -f911) (see fgcom wiki page)
- My messages over in multiplayer chat are not visible to others; Although I can see their messages.
=> This might have to do, that I sent the messages only once and they are sent via UDP protocol. I have changed this to send them for 3 seconds, minimum 10 times. I hope this fixed this issue.
Now a few suggestions from my point of view/feedback:
The targets have way too large "lines" that represent their direction of flight/where they're pointing, I suggest cutting that to about a half or so.
Also, keep in mind that radars in the U.S airspace (issued by FAA), usually do not have this kind of targets at all (except for Center/Enroute positions) , they just show up as different letters with a trail to show if they are tracked, tracked by another controller or no tracked at all.
Yes the lines are too long... They pointed to the projected place, where plane would be in 60 seconds, if it would fly straight. I have changed ot to 30 seconds.
This can give you a general idea of what we're talking about: http://www1.metacraft.com/VRC/docs/doc. ... adar_modes
=> Good page!
Then secondly, the ILS centerlines look too bulky, in real radars they can be represented by just a simple line or a line with distance markings (like those found in euroscope):
=> This is painting the object "only". I have simply drawn, what MP map shows. I like your proposal better