Hi again Monster .

Here I'll keep a synthesis topic about our GCIs feedback and other users (pilots with playback for debrief) about the F4AWACS.

All this should be considered just as a sort of big wishlist . People here are aware about the time and energy necessary to developp such a tool, and we also know that everything is not doable...
Anyway, even if only some of our suggestions can be taken into consideration for the further developpement of the tool, everybody here will be happy .

We also made a sort of rating of our wishes, in order to give you an idea of what appears as most interesting/important for us.


So, well, now, , the list :

1- voiceserver connector with IVC, with the possibility to manage frequencies

2- possibility to define floor detection areas
3- possibility to define detection limits, and/or non detection areas

2'-3' possibility at the SQSERVER level to make such detection areas/limits mandatory to any F4AWACS clients

4- track labels permanently reduced with just Callsign and FL (Flight Level) information
5- track labels on demand (with just one click on the track) giving in the following order Callsign, heading, FL, speed (kt and/or Mach), Squawk (if in shared memory...)

6- cursor function improvement in order to get the bearing/distance between point/aircraft, or point/point, or aircraft/aircraft without having to maintain the drag

7- possibility to add some icon types to the area function
8- speed vector on ia flights

9- voice recording (if 1- doable), synchronised to the tape, with mp3 compression

10- possibility to playback a tape from any point of the recording (1.3.3 implemented )

11- OF PPT importation
12- possibility to choose the label track font
13- options to control what precisely is to be displayed in a track label (name, callsign, FL, speed, etc...)
14- option in case 4/5 is implemented to disaply extended information with "mouseover" a track

15- some other map centering possibilities (minimap, cursors)
16- possibility to play on areas opacity
17- possibility to make floating windows slaved to F4AWACS working area

18- possibility at the SQServer level to impose the same track display for human and ia tracks (even if it is just flights for ia) to F4AWACS clients (so that the GCI can't identify human tracks frow ia tracks)

19- possibility to add and record marks on a tape
20- a tape editor (cut, copy, paste)


If you have any questions about these ideas, we'll do our best to give more details with pleasure .

ooohhh my God!!!

Hahaha, just kidding...

Great job. This stuff is beautiful. Great ideas.

I think the most important one is number 1 (IVC). I am working on it and I have made some progress too but I'm afraid I'm not very used to programming in DirectX, so I'm taking it a little slow.

Anyway, I'll let you know in this post the progress of all of these  .

Hi Monster,

Is this IVC communicator meant to replace the current voiceserver.exe ?

No, no replacement. I just want to make a program so that a GCI can communicate with the pilots, through IVC, including frequency support. Think of it as a radio device, independent from Falcon, that allows you (if you are on the correct frequency) to talk with the pilots.

Just a thought about issues number 2 and 3...

I was planning to add the feature to the program to be able to define on SQSERVER specific Radar sites on the map and when you connect with F4AWACS (if it is set on SQSERVER) to be forced to choose one of these sites. When you choose one of these Radar sites, you will have a radar coverage according to the terrain morphology of the current theater (e.g. you won't be able to track a plane that flies behind a mountain) and have a maximum detection range (e.g. 256 nm as modern Radars have).

If the above is implemented, are you still finding the issues number 2 and 3 useful and would want to implement them too, or do you think that they would be obsolete?

With the above implemented, 2 and 3 would be obsolete . That's the idea .

Implemented that way, what I would suggest is to also give the possibility when connecting the SQSERVER to choose either one radar site or one radar set of multiple radar sites. Cos in some air forces, what is displayed to the GCI is a synthesis of multiple radar detections.
Another point, I think it would remain interesting to allow users to define your radar sites capabilities, not only the terrain morphology, to allow more restricted detection capabilities (not only due to the terrain).
Last refinement , if you can implement as radar type a moving one, to modelise an AWACS, you're a master .

Anyway, what you intend to do appears more developped than what we were suggesting, so sure we will be happy with that .

If you do confirm you go that way, and that last suggestions can be taken into consideration in the plan, I'll update the points 2 and 3 .

Yeah, great ideas...

Ok, I'll go that way with the choices of a single Radar, a net of Radars, an AWACS radar (moving) or the combination of all (!). I just have to find a way to make it and at the same time to be user friendly  .

What extra restrictions,in Radar capabilities do you have in mind? Specific areas that the Radars won't be able to see (or from a height and below)? This can be done but I'm not sure how realistic this can be.

Of course, we can implement Radar ECM from hostile ground units, blanking a sector of Radar area, from a certain distance and further...

Ok, please update the first post if you like, and I'll give it a thought, and come back on this...

Of course, any other opinion is highly appreciated...

Awesome .




Yep I was think from height and below, and some defined sectors.




That's part of the idea .





I'll do it later .




I'll talk about all this in the dedicated topic in french. I'll report a synthesis of expressed opinions. This for non english friendly users . Other will react directly here I think .

A litle question Monster .

Are "2D events", for the computer running AISPY, like "Mampo radar struck by X forces" for exemple, in shared memory ?

Never looked for them to be honest, so I'm not sure...

Have you got anything in your mind?

Yes . If such information were in shared memory, we could associate some OSC radars to some F4 "radar objectives". So that in case a radar is attacked, with such a message you could then shut down the OSC associated radar . What would alos bring a new dimension to SEAD missions...

Hi Monster 

I have a important file to give at you ( concerning the voiceserver and your projet )

You can contact me via icq ?

I'm sorry Toopack but I'm in Germany right now and I just got internet...

If the file isn't very big, you could send it to my gmail account


Thanks and sorry for the trouble...

Any news Monster ?

Still in Germany ?

Hi guys...

Sorry for my long absence I really don't have much time.

Yes Couby, I'm still in Germany, and this is where I'm gonna be for the next two years. Unfortunately, I still don't have enough time to make any improvements to OSC. The major problem is that, due to the big size of the program, I need some consecutive time to work with it, and I really don't have it.

I'm really sorry guys, I know that everybody here is expecting something new and I really want to improve my program. The cruel truth is though, that real life comes first (although most of the times we wish it could be the other way around ).

Hi Monster, nice to read you again .

Hope all is working fine for the rest, beside the lack of time.

No way to share the developpement of the tool with someone else for the next two years ?


Wish you the best, and happy new year .

Any news Monster ?