Hi @oakdesign, thanks for the explanation, everything is now working as it should, including recording in the cockpit.

Bernardo.

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:

@Shelknam

1. I am a dev and well aware what true / false respresentation is
2. 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

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

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 set

set g_bTacviewRealTime 1

Other 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

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.