SlooFooD

Now I've got it wokring with changing options.lua entries to: ["plugins"] = { ["Tacview"] = { ["tacviewExportPath"] = "C:\\BV_SFTP_DCS_TGH_01\\DCS.openbeta_01\\Missions\\TacView-Files", ["tacviewDebugMode"] = 0, ["tacviewRemoteControlPort"] = "42675", ["tacviewFlightDataRecordingEnabled"] = true, ["tacviewRealTimeTelemetryPassword"] = "", ["tacviewSinglePlayerFlights"] = 2, ["tacviewTerrainExport"] = 0, ["tacviewAutoDiscardFlights"] = 10, ["tacviewRemoteControlPassword"] = "", ["tacviewRealTimeTelemetryPort"] = "42674", ["tacviewMultiplayerFlightsAsHost"] = 2, ["tacviewRemoteControlEnabled"] = true, ["tacviewRealTimeTelemetryEnabled"] = true, ["tacviewBookmarkShortcut"] = 0, ["tacviewMultiplayerFlightsAsClient"] = 1, ["tacviewModuleEnabled"] = true, }, -- end of ["Tacview"] }, -- end of ["plugins"]

Here is the RealTimeTelemetry-Window : And attached to this Post you'll find the DCS-Log from dedicated Server Options.lua has following entries: But in DCS.log you'll find this: 2022-01-25 16:56:28.571 INFO TACVIEW.DLL: Config={tacviewModuleEnabled=1, tacviewFlightDataRecordingEnabled=1, tacviewSinglePlayerFlights=2, tacviewMultiplayerFlightsAsClient=1, tacviewMultiplayerFlightsAsHost=2, tacviewBookmarkShortcut=0, tacviewAutoDiscardFlights=10, tacviewDebugMode=0, tacviewTerrainExport=0, tacviewRealTimeTelemetryEnabled=1, tacviewRealTimeTelemetryPort=0, tacviewRealTimeTelemetryPassword="", tacviewRemoteControlEnabled=1, tacviewRemoteControlPort=0, tacviewRemoteControlPassword="", tacviewExportPath="C:\BV_SFTP_DCS_TGH_01\DCS.openbeta_01\Missions\TacView-Files"} dcs.log

It seems that the service that is meant to be used for streaming (host) is not startet from dcs.server.xxx. When i start a DCS gaming instance on the same machine with a connection to the dedicated server that is running on the same machine but without activated TacView module then the streaming service is being started and a connection from other clients will be possible - thats really weird because with only 16 GB of RAM i can only host one dedicated DCS session and not another gaming-session that needs a lot of addiotional RAM and effects performance. Anobody else here, that can help?

I have had some testing the last few hours: I can get live telemetry working only on my "Gaming Rig" - the machine where i activated my license first. On All machines i used the same settings - firewall sittings included. But i wwould like to enable My/Our Game Server to stream the recording - but this does not happen - is it possible to be related to license type? Would be happy to have some help.

I am using the latest Version if Tacview (advanced) running on my dedicated server and on my client. I am trying to get the real the real time telemetry working but it won't work. DCS running in dedicated mode you cannot set your properties in GUI (DCS Special Menues) - so you have to edit options.lua - i have done this like: ["plugins"] = { ["Tacview"] = { ["tacviewExportPath"] = "C:\\BV_SFTP_DCS_TGH_01\\DCS.openbeta_01\\Missions\\TacView-Files", ["tacviewDebugMode"] = 0, ["tacviewRemoteControlPort"] = 42675, ["tacviewFlightDataRecordingEnabled"] = 1, ["tacviewRealTimeTelemetryPassword"] = "", ["tacviewSinglePlayerFlights"] = 2, ["tacviewTerrainExport"] = 0, ["tacviewAutoDiscardFlights"] = 10, ["tacviewRemoteControlPassword"] = "", ["tacviewRealTimeTelemetryPort"] = 42674, ["tacviewMultiplayerFlightsAsHost"] = 2, ["tacviewBookmarkShortcut"] = 0, ["tacviewRealTimeTelemetryEnabled"] = 1, ["tacviewRemoteControlEnabled"] = 1, ["tacviewMultiplayerFlightsAsClient"] = 1, ["tacviewModuleEnabled"] = 1, }, -- end of ["Tacview"] }, -- end of ["plugins"] The Files are recorded properly bute i cannot make realtime telemetry running. Connection fails everytime i try to connect. I've tried a lot and i am sure to have to specified ports being opened: Also it seems that all parameters were loaded as expected (dcs.log): 2022-01-22 16:25:47.689 INFO TACVIEW.DLL: Tacview Flight Data Recorder 1.8.7.200 Loaded. 2022-01-22 16:25:47.689 INFO TACVIEW.DLL: Config={tacviewModuleEnabled=1, tacviewFlightDataRecordingEnabled=1, tacviewSinglePlayerFlights=2, tacviewMultiplayerFlightsAsClient=1, tacviewMultiplayerFlightsAsHost=2, tacviewBookmarkShortcut=0, tacviewAutoDiscardFlights=10, tacviewDebugMode=0, tacviewTerrainExport=0, tacviewRealTimeTelemetryEnabled=1, tacviewRealTimeTelemetryPort=0, tacviewRealTimeTelemetryPassword="", tacviewRemoteControlEnabled=1, tacviewRemoteControlPort=0, tacviewRemoteControlPassword="", tacviewExportPath="C:\BV_SFTP_DCS_TGH_01\DCS.openbeta_01\Missions\TacView-Files"} 2022-01-22 16:25:47.689 INFO TACVIEW.DLL: Running as the host of a multiplayer session. 2022-01-22 16:25:47.690 INFO TACVIEW.DLL: Tacview is set to [Record All Available Data] 2022-01-22 16:25:47.690 INFO TACVIEW.DLL: Export path: [C:\BV_SFTP_DCS_TGH_01\DCS.openbeta_01\Missions\TacView-Files\] Using a dedicated server on the same system with its own properties have been working regarding real time telemetry - but my (/our) server is running in a professional data center. Server and Clients are using IPv4 - so i need help to get this working. Any Ideas? Thanks a lot for helping me.

Now I've got TacView to record flightdata on dedicated server. I've inserted the following lines to "options.lua" ["plugins"] = { ["Tacview"] = { ["tacviewModuleEnabled"] = 1, ["tacviewFlightDataRecordingEnabled"] = 1, ["tacviewSinglePlayerFlights"] = 2, ["tacviewMultiplayerFlightsAsClient"] = 1, ["tacviewMultiplayerFlightsAsHost"] = 2, ["tacviewBookmarkShortcut"] = 0, ["tacviewAutoDiscardFlights"] = 10, ["tacviewDebugMode"] = 0, ["tacviewTerrainExport"] = 0, ["tacviewRealTimeTelemetryEnabled"] = 1, ["tacviewRealTimeTelemetryPort"] = 51437, ["tacviewRealTimeTelemetryPassword"] = "*****", ["tacviewRemoteControlEnabled"] = 1, ["tacviewRemoteControlPort"] = 51438, ["tacviewRemoteControlPassword"] = "******", ["tacviewExportPath"] = "C:\\Users\\******\\Saved Games\\DCS.openbeta_server\\Missions\\TacView-Files" } }, My Problem is now that i get no connection to RealtimeTelemetry. Neither on Server itself using "localhost" nor on client using server-ip (or DNS-Name). And i am sure that i have opened the defined ports (TCP and UDP). Any Ideas?

unfortunatly everytime i am trying to start the server after inserting ["plugins"] = { ["Tacview"] = { ["tacviewBookmarkShortcut"] = 0, ["tacviewClientTelemetryPassword"] = "", ["tacviewCompressionLevel"] = 0, ["tacviewDataRecordingEnabled"] = true, ["tacviewDebugModeEnabled"] = true, ["tacviewHostTelemetryPassword"] = "", [b]["tacviewPlaybackDelay"] = 0,[/b] ["tacviewProfilingPeriod"] = 600, ["tacviewRealTimeTelemetryPort"] = "42674", ["tacviewRecordClientsSessionsEnabled"] = false, ["tacviewRemoteControlPassword"] = "", ["tacviewRemoteControlPort"] = "42675", ["tacviewTerrainExport"] = 0, }, }, to [%USERPROFILE%\Saved Games\YOUR_SERVER_NAME\Config\options.lua] the server won't start. I am using the latest version of TacView with the latest Version of DCS.Server.openbeta. There is an error telling something like "failed to load Tacview .... Not authorized" TacView recording is being started without the TacView entries under plugins as described above. It seems that standard configuration is being loaded from tacview.dll. Is there a way to edit this file? Withoutn changing tacviewPlaybackDelay to 0 I wqon't be able to use realtime telemetry Thanks for help

Is there a working solution for this problem? Here is my Log: 2022-01-14 12:26:48.357 INFO Scripting: plugin: SKIPPED 'Tacview by Raia Software': not authorized and with this a cannot get my server working

in the meantime I have tested a lot and the results were partly weard. With a mission that was created as simple as possible - i've got correct CallSigns in GamePLay independent of "late activation" or "immediate activation". But things are getting weard as you are using common frameworks to expand possibilities for mission editing like the MOOSE-Framework. If You are changing common CallSign-Tables that would likely change behavior of these frameworks.Would be nice, if people that are contributing these mature framworks would be involveld into mature changes, so that nessesary changes could be done just before a release of a new update. here is a video of my last Test-Flight in my latest mission: independent of "late activation" or "immediate activation: I have only 2 "Late activated" tankers(Arco-1-1, Arco-2-1) in my mission and additional every player is able to spawn an additional one depending on his Coordinates and other parameters like height. That works well - worked well before update. Now the assignment of the callsigns seems to be broken - you have added a lot of stuff for the hornet and the viper - maybe due to this we have issues withe moose at this point. At the moment you can see in the video above, that both tankers get the same CallSIgn (radio menu sequence) - the later spawned tanker get's correctly Shell-1-1. I will redo this video on dedicated server - the results there are different > Shell-1-1 get's the CallSign "Texaco-1-1" And i am wondering why the Tanker spawn and refuleing was not being recorded in TrackFile. If You are interested you could get the MIZ.File 6_06-00_op pat_0615_LightScattered1.miz20211229_BrokenCallsSigns_op01.trk

i had this problem also without late activation, all arco tankers (1.1, 2.1, 3.1) in Radio-menu same entry. arco-1.1

If you have multiple tankers and you would assign for example callsign "Arco-1-1" and "Arco-2-1" for different planes in ME, then both appear in radio menu as exactly same "Arco-1-1" - hope you can get this fixed soon. Btw: assignment of Callsigns using moose seems to work well in singleplay but in MP all tanker planes get "texaco".

now i've installed marianas map on server with the shortcut method and it seems to work properly

btw: there seems to be no possibility to start a marianas mission on dedicated server right at the moment. I've tried to and i can add a ME-Mission in mission list of the server but the server crashes instantly when starting this mission. I didn't try to install the marianas map with some short cut work around like you have told above. Seems that this could be the reason - we will have to wait until ED has updated the server files.

Many thanks for the quick answer, even if it is not really satisfying. Good to know that ED is going to made this feature happen. We all know how often and many new features are announced - but bringing them to an end seems to be an issue at ED. Reinhold Niebuhr would say: "God, grant me the serenity to accept the things I cannot change, Courage to change the things I can, And wisdom to know the difference."

Pre-Planned Targets for F/A-18C in ME via Cartridge - Update needed I spent hours looking for a way to pre-plan targets for the F/A-18C. I knew that multiple targets for the JDAM/JSOW could be entered directly through the UFC. This option is certainly nice and important as a supplement. But it's called Pre-Planned, so I want to plan the targets in advance. For the JF-17 this possibility exists via cartridge system. In ME there is a special menu for the plane to set the targets (PP1, PP2, PP3, PP4) and you can also set targets via F10-map "on the fly". Is there an update when this function will be added for ED-Modules (F/a-18C)? Wags announced early last year that they are working on this topic. Does anybody know?