Problem with Tacview RealTime Telemetry and OpenRadar
-
Hi guys, I’m trying to get OpenRadar v0.1.4 working on my second monitor, but I can’t get it to work with v4.7.37 build 3062. Here’s what I’ve done so far:
- I have put the following in my Falcon BMS User.cfg file:
set g_bTacviewAcmi 0 set g_bTacviewRealTime 1 set g_nTacviewPort 42674- I have tried changing the g_bTacviewRealTime option to 0 and 1 with no results.
- I have tried recording the session -in flight- as well as activating ACMI from the launcher.
- I have run the program normally and also as administrator, both Falcon and OpenRadar.
- Thinking it might only activate on a specific flight type, I’ve tried everything, except multiplayer.
- I have verified with netstat -an | Select-String “42674” and the port does not appear to be open in any of the tests mentioned.
- I’ve enabled debugging and haven’t found any mention of it… maybe it would be good to put something confirming that it’s running and on which port.
What am I missing or doing wrong? Is there anything else I need to configure?
I see that there are users who use it without problems, so I rule out a bug and I must be doing something wrong.
Thanks, Bernardo.
-
@Shelknam so what’s the status you get on the connection screen
-
@Shelknam said in Problem with Tacview RealTime Telemetry and OpenRadar:
For RT you only need to setset g_bTacviewRealTime 1Other defaults are just fine
-
Hi @oakdesign, all the time is Connecting refuse, retrying in 10 seconds 1/0. I didn’t mention it in the previous post, but I also tried changing the default port, 42674, to something else with the same result. I checked -although it shouldn’t affect the server and client if they’re on the same PC- the firewall settings… it was frustrating.
Any suggestions ?
Thanks, Bernardo.
@oakdesign said in Problem with Tacview RealTime Telemetry and OpenRadar:
@Shelknam so what’s the status you get on the connection screen
-
@Shelknam said in Problem with Tacview RealTime Telemetry and OpenRadar:
set g_bTacviewAcmi 0
should be set to
set g_bTacviewAcmi 1
-
Hi @Tumbler31, yes, I know, but in an effort to find the solution I also tried 0 just in case. Thanks for the confirmation.
@Tumbler31 said in Problem with Tacview RealTime Telemetry and OpenRadar:
@Shelknam said in Problem with Tacview RealTime Telemetry and OpenRadar:
For RT you only need to setset g_bTacviewRealTime 1Other defaults are just fine
-
Hi @oakdesign, no, the Technical Manual it is very clear:
Enables / disables native Tacview support. Available options: 0/1. Default = 1
Yes, I know, it is confusing that 0 means enable -in programming it is always false- but that’s how it works.
Thanks, Bernardo.
@oakdesign said in Problem with Tacview RealTime Telemetry and OpenRadar:
@Shelknam said in Problem with Tacview RealTime Telemetry and OpenRadar:
set g_bTacviewAcmi 0
should be set to
set g_bTacviewAcmi 1
-
- I am a dev and well aware what true / false respresentation is
- Setting set g_bTacviewAcmi 0 will disable Tacview support and fall back to the old flt and vhs files
g_b means it’s a global boolean therefor 0 sets false 1 sets true.
I’m a member of UOAF and Openradar is developed by our group
-
@Shelknam said in Problem with Tacview RealTime Telemetry and OpenRadar:
Enables / disables native Tacview support. Available options: 0/1. Default = 1
doesn’t read as Enable is 0 / Disable is 1
-
@Shelknam if you have tacview advance you can try to connect to the stream same as Openradar would do
use the Real-time Telemetry not Falcon 4.0 Lagacy as that would require to have g_BTacviewAcmi 0 and read from the temporary flt file stream and will not be the furture of how tacview nor openradar interfaces with BMS.
-
Hi again @oakdesign, perfect, just to clarify:
-
The Tacview RealTime Telemetry protocol works with g_bTacviewAcmi set to 1 ONLY if I have activated ACMI in the launcher.
-
Now, with g_bTacviewAcmi set to 1, when I try to access the ACMI section, the error ACMI is disabled appears, and the F key does not move the switch on the AVTR console and no file in the ACMI user folder.
-
I was guided by several posts that say that, for ACMI to work in the cockpit, you must set the g_bTacviewAcmi to 0, in fact it is reported by our well-known @Revientor in this video:
P.S.: It’s a bit confusing, I’m not sure if I want to record all my flights.
To summarize, with g_bTacviewAcmi set to 1 the Tacview RealTime Telemetry protocol works only if ACMI is selected in the launcher, BUT, if ACMI is not selected in the launcher the Tacview RealTime Telemetry protocol does not work, since in Falcon ACMI appears as disable and therefore the F key does not trigger the recording… at least in my case… how do you have it configured? Maybe there’s another parameter I should put in the configuration.
Thank you very much for your help, the OpenRadar program is really very good and useful, congratulations !!!
Have a nice weekend, Bernardo.
@oakdesign said in Problem with Tacview RealTime Telemetry and OpenRadar:
- I am a dev and well aware what true / false respresentation is
- Setting set g_bTacviewAcmi 0 will disable Tacview support and fall back to the old flt and vhs files
g_b means it’s a global boolean therefor 0 sets false 1 sets true.
I’m a member of UOAF and Openradar is developed by our group
-
-
S Shelknam has marked this topic as solved
-
@Shelknam said in Problem with Tacview RealTime Telemetry and OpenRadar:
I was guided by several posts that say that, for ACMI to work in the cockpit, you must set the g_bTacviewAcmi to 0, in fact it is reported by our well-known @Revientor in this video:
your completely missunderstanding what is shown in that video.
BTW even so he put g_bTacviewAcmi 0 into his User.cfg which would have enabled to ingame viewer and disabled the recording in the .acmi file format, he never saved that change and therefore anything shown after the 2:59 minute mark is still using g_bTacviewAcmi 1 from the default setting and so is more confusing than showing what that setting does
this is the old BMS integrated vhs replay which indeed needs g_bTacviewAcmi 0 in order to be used.
Tacview and ingame Acmi/Vhs viewer are 2 seperate things. Tacview is a seperate software (not needed to run Openradar, but Open radar uses it stream protocol)
Evens so Tacview would be able to open a .vhs recording it’s a recommedned to use .acmi recording for Tacview usage itself and required to use any of the Realtime either with Tacview or with Openradar
Yes in order for openradar to work there must be an active recording which you either enable by activating the ACMI button on the launcher, or by pressing “F” default keyboard bind. If you say the AVTR switch is not moving if you press “F” tha you need to check if your binding is valid.
I’d recommend to use the Laucher version and if you are concerned of disk space just delete recording inthe User/ACMI folder time by time. Nevertheless Openradar will be able to connect if you use 3d pit switch “F” but then you have to manually use the connect button in openradar if the retry counts are already exceeded.
So again for testing and get it working auto activate recording by using the Launcher option
-
Hi @oakdesign, thanks for the explanation, everything is now working as it should, including recording in the cockpit.
Bernardo.
