>Additional features: The ability for the server to restrict which airports a >client can use based on wether the client is RED or BLUE. This
>way the ATC console cannot be used to look at aircrafts that are near an >airport that you supposedly cannot use.
>On the server side, make it possible to lock the ATC onto a specific airport or >list of airports - this can be done via a config file, thus >locking RED and >BLUE side into different airports.
I try my best to implemente these features.
>Add the ability to use an object or multiple objects named in a special way as radar - the object name(s) should be specified in the config >file for each side. This way a SAM site radar could be used for the ATC console. This combined with the ability to list only some or NONE of >the airports for ATC capability makes it possible to have in-game destroyable radars.
btw LOTACT is more look as a Awacs than asimple radar.
>Add the ability to calculate real intercept vectors ... ie. not vector for just 'nose on' capability but a heading and speed to fly at in >order do a lead collision course.
OK, but not ugent.
>Add a config value to allow only a certain IP or list of IPs (with wild-cards) to connect to the ATC console.
Possible by why ?
>The server needs to be able to start after LOMAC has started - this is important for starting it on HL.
You can already do this whitout pb.
>Please let us choose larger fonts for the display
Ok donne.
>The ILS screen should also be zoomable
This view will change in new version ;-)
>The application window cannot be maximized to fit the screen well. Enabling -that would be very nice
Sorry not now. Because of the border :tongue:
>Contact airspeed is not displayed
OK donne.
>Need to be able to choose imperial units, too
OK donne
New version last week. ( in ED time based :tongue: )
