[F4RADAR] Lightweight standalone radar application
-
Again the software can only be used if you are sitting in 3d in a jet that is stationary on the ground. You can’t use it when you go airborne. So no it’s not a cheat tool
If you try and take of once you don’t have weight on wheels anymore Status goes red and all contacts dissapear
https://up.picr.de/39037311zb.gif
Gesendet von meinem SM-G930F mit TapatalkVERY cool!
-
Hi Tumbler31,
I’ve send you a mail because i’m very interested by your app.
It is so precise that we can expect play Atc from RAMP to airborn, and more ( GCI).
So, to do that, the complet airbase diagram in place of single runway will be Nice.
Thanks and i’m impatient to read you.
Wacco -
Thanks for your kind words in your email, great to hear you like F4RADAR and see also the option for ATC incl ground ops.
You and others have asked if it’s possible to add the taxiways. Well yes and no. Plotting it won’t be the difficulty, the program simply draws lines between points. But I don’t have the coordinates defining the taxiways. Contrary to the runway, which is defined by 4 points thus creating a rectangle (check out RunwayDimPt in the editor, the red scribbly stuff in the image below), the taxiway seems to be just a textures positioned at the right place. There are no boundaries of the taxiways. If someone knows an easy way to get coordinates of the outline of taxiways (preferably in BMS x,y format, but lat/long with sufficient resolution will do as well), I’ll gladly let the program draw the lines.
@wacco:Hi Tumbler31,
I’ve send you a mail because i’m very interested by your app.
It is so precise that we can expect play Atc from RAMP to airborn, and more ( GCI).
So, to do that, the complet airbase diagram in place of single runway will be Nice.
Thanks and i’m impatient to read you.
Wacco -
Thanks for you answer, i will try to find a way to get coordonates.
Are you limited by the number of rectangle you can use for an airbase.
Do you have to use rectangles or can you draw polygons
Wacco -
Another update of F4RADAR also using some of your suggestions and bug reports. Keep those coming! The download link can be found in the start post.
Main change is that the 200NM detection radius now also extends from a friendly AWACS. Again within 20NM of a friendly AWACS the detection limit is set to 0ft MSL. Furthermore callsigns for friendlies “outside the bubble” have been added and these callsigns have a trailing dash.
version 0.8 changes (24.09.2020)
- added callsigns outside the bubble, these contact have a trailing dash in their name
- detection range of 200NM also added to friendly AWACS
- fixed saving the minimum detection speed
@wacco: I haven’t tested yet with a large number of lines, but I can’t imagine it will have a big impact on the GPU.
-
Another quick update as there was an error in the detection range, a mix up between km and NM (thanks again Eagle-Eye). To make up for it, I’ve added the option to swap the functions of the mouse buttons. By popular demand the left button now defaults to BRAA-line and right pan, but the option menu allows you the swap this.
version 0.9 changes (24.09.2020)
- added the option to swap mouse button functions (default now right to pan)
- fixed detection range back to 200NM instead of 200km
- removed the trailing dash for “out of bubble” contact, as apparently this refers to NORDO
-
I think i had found a way to give you coordonates, but it’s not friendly user, so i do it ASAP for a first test, if you are stil agree
-
Hi
check gmail
Wacco -
Nice work, it’s promising !!
Little question, I just did some tests and I only see the flight leaders, is it normal? It’s linked to BMS this inability to see the wingman isn’t it ? -
Hi Tumbler31,
We spoke on the Falcon Lounge Discord Server a few days back. Big fan of your software!I was running F4RADAR in the proper way [jet parked on the ramp in 3D etc…] and everything was working great.
Then suddenly, the BMS Status light turns yellow, and the F4RADAR display goes totally blank.
I did not do anything in BMS to make it stop working.Then suddenly, the BMS Status light turns green again, and the F4RADAR display returns to normal.
Again, I did not do anything in BMS to make it start working.This happened about 5 times over 60 minutes.
Do you know what might cause this?Thanks,
Freudi [Felix] -
As numbers of MP player increases F4RADAR seems unstable and goes status yellow several rtimes for several minutes.
Anyway we can provide debug information? -
Freudi, chihirobelmo and others, thank you for your feedback on the issue where the program lost connection with the 3D state of BMS. It should be fixed in this update, but do let me know how it functions for you. I also added the option to use the program when you’re in 3D whilst dangling under your parachute or just having crashed into the ground. In such a way you can be of use to your fellow players without having to find a plane parked on the ramp.
The download link to v0.10 can be found in the start post.
version 0.10 changes (05.10.2020)
- added the option to use the program when you’re under your parachute or dead, thus not parked on the ramp
- added statusbar with program and radar status plus game time
- fixed game by adding days when running longer campaigns
- fixed issue of loosing connection to the 3D state of BMS
@nidray, F4RADAR shows flights but also the wingman. The latter only for those entities present in the 3D-world.
-
Thank you! I’ll check its stability in next time we hold large excercise.
A new request: could it be possible to read .ini file to show STPT lines and SAM WEZ?
-
Thank you! I’ll check its stability in next time we hold large excercise.
A new request: could it be possible to read .ini file to show STPT lines and SAM WEZ?
Thanks for the suggestion, I will surely add it to the wishlist!
-
Awesome tool! Have you considered adding the type of aircraft on the contact info? Or to classify it manually by association?
-
Thanks for your enthusiastic reaction! And yes, I’m working on that for friendlies. For bogeys I’m still trying to find a way without spoiling the party.
-
version 0.11 is out. Main visible change is the table with flight info. You can move the table around and scroll when it’s very long. Bogey info is limited to number of planes for now. Another nice one is that the program now also recognizes other nations.
v0.11 changes (13.10.2020)
- added the a scrollable and movable (click header) table showing flight info, for bogey limited to number of planes
- added support for multination war, neutral, hostile and at war are shown as bogey
EDIT: some weird stuff happened in the aircraft type in the table. A fix is on it’s way.
-
Quite a change, the artificial 5000ft and 200NM detection limits have been removed and F4RADAR now uses the logic of BMS itself. Thus all contacts as visible in the 2D screen are also visible in F4RADAR. And when identified within BMS, the program also gives the plane information in the table, which is now in alphabetical order. Friendly contacts are always shown including their plane and mission information.
Also the latitude and longitude of the cursor are shown in the taskbar, currently this only works for KTO. As usual the download link can be found in the first post and your suggestions, bugs and comments are welcome!
version 0.12 changes (15.10.2020)
- added contacts are now shown when spotted in BMS and plane info is given when identified in BMS, 5000ft restriction and 200NM detection limit have been removed
- added plane info in the table when contact is identified in BMS
- added latitude and longitude mouse position in the status bar
- fixed table is shown in alphabetical order
- fixed plane information in table, previous release showed wrong info for certain contacts
-
thanks for creating this tool and investing your time in BMS but i have a question.
Why a different tool when OSC is already there and has also integrity check and ivc api and F4Awacs screen as proven technologie ?
The creator of that tool is also in the inner circles of BMS so every upgrade to 4.xx could be a support tool for it
Would it not be better to combine forces instead of creating a new tool ground up (demotivating the current OSC dev) and in the end having nothing when you decide to call it quits (assumption)(call it cheating or not, think the mp host decides as in current modern warfare every form of intelligence is a way of cheating to get an advantage over your enemy, spy on the ground/spyplane/AWACS/satellite)
-
thanks for creating this tool and investing your time in BMS but i have a question.
Why a different tool when OSC is already there and has also integrity check and ivc api and F4Awacs screen as proven technologie ?
The creator of that tool is also in the inner circles of BMS so every upgrade to 4.xx could be a support tool for it
Would it not be better to combine forces instead of creating a new tool ground up (demotivating the current OSC dev) and in the end having nothing when you decide to call it quits (assumption)(call it cheating or not, think the mp host decides as in current modern warfare every form of intelligence is a way of cheating to get an advantage over your enemy, spy on the ground/spyplane/AWACS/satellite)
I’ve used OSC plenty of times in the past. It’s undoubtedly a great tool, I like it, and for a long time, it was the only tool to do what it does. Still, some counterquestions:
- If the OSC dev is in the inner circles of BMS, or even active in any part of the BMS community at all, why did OSC not work for the entirety of 4.33?
- How does F4RADAR demotivate Monster, and (pardon my bluntness) why should that ever be a factor in whether or not someone else wants to build a new tool?
While OSC does still have some things that F4RADAR does not (e.g. integrity check, direct IVC integration, importing all theater objects and mission.ini PPTs/steerpoint lines), F4RADAR has already surpassed OSC in others.
I know Tumbler still has plenty of ideas to improve F4RADAR, but for now, most importantly, his tool can show individual aircraft and their type, and it doesn’t use / rely on an entire software suite, making it a lot more user-friendly and reducing possible points of failure. (which raises the question: Why does OSC require running so much software - SQServer, AISpy, Validator, F4AWACS - when F4RADAR can retrieve and show that and more information without it?)Whether or not Tumbler and Monster want to join forces is obviously up to them. It might be great if they did, but I don’t understand why F4RADAR should demotivate Monster at all? If they stay separate: at worst, they see each other’s tool as a threat to their own creation, which would be silly IMO, because this isn’t a competition or commercial market; at best, they accept the other tool for what it is, and possibly use it for ideas to improve their own.