bainsy

Client side. Tacview was not running server side.

A member of our group was encountering this issue. Upon examining his logs immediately after a GBU related crash, we noticed that the last events logged involved Tacview. On a hunch we entirely removed Tacview and all associated scripts and the problem was solved.

Done! Thanks for your help. I didn't even realize there was a new version.

Thanks for your reply. Current versions: SimShaker for Aviators - Version 1.3.13.0 Seat Handler 1.0.0.10

Is Jetseat/Simshaker currently supporting the new A-10C II? I am getting the following error (see screenshot) when starting the A-10C II and no activity from the Jetseat.

Did you ever figure this out? I just setup my stick and throttle and with an extension the stick tension is too loose.

Our group ( VFA-88 ) is currently using script as follows: MOOSE: Airboss (allow more advanced carrier ops), randomizing enemy groups, randomizing enemy bandits, repeating tankers/rescue helos/awacs, presence of civilian traffic commuting between airfields CTLD: JTAC Autolazing and giving Helos something to do (unit generation, troop deployment, etc) Skynet IADS: Increase realism of SAM networks and behavior Pikey's Persistence Scripts: Allow persistent unit status across restarts during our campaigns

Longtime VA / Vaicom user here who has had nothing but frustration and trouble with AIRIO. I have decided to cut my losses and remove it. Does anyone know the correct procedure? Disabling it and/or removing the DLL file results in it trying to reinstall/update every time VA starts. Also, how do I get my Keywords database back to default non AIRIO? EDIT: Solved by uninstalling and wiping Voice Attack entirely, repairing DCS, then reinstalling Voice Attack/Vaicom.

Thank you for the update Bignewy.

Hi BIGNEWY. This is a problem with DCS Tracks. Due to problems that have existed for many years now, the track files are often not an accurate representation of what occurred in the session. Having said that, this track file does actually show weapons employment but not until about 30mins into the session. In summary, the dev team needs to be made aware that there is a problem with unit dispersion in multiplayer. Once units under attack have dispersed, issues occur including the following: 1) Occasional instantaneous warping of units from one location to another location (unit disappears and instantly reappears nearby) 2) Occasional shifting of units (units sometimes appear to float sideways to a new location) 3) External scripts and Tacview receive incorrect location data for enemy units. Scripts and Tacview see the enemy unit 30-80m away from where it actually was in the session. In session, weapons often miss, while in Tacview, they were a direct hit. 4) JDAM TOO designation (tested on Hornet TGP) on units after dispersion is unreliable. Weapons often miss by 30m even though designated correctly. This is never a problem prior to unit dispersion. It is disappointing that a bug of this magnitude is still not marked as REPORTED. This type of issue will most certainly continue to cause cascading issues in DCS's MP stack, and the longer it goes unaddressed the more complex a fix will be.

I believe this bug has already been reported by RedKite.

Anyone else having trouble with CTLD Autolase in multiplayer missions? We are finding that the first designation works however after one enemy unit is hit and the remaining units disperse, CTLD is lasing the wrong location resulting resulting in misses (by approx. 50 meters).

Further to this, there is definitely something odd going on with unit dispersion. When a unit within a group is hit, there is some sort of desync occuring in MP which results in: 1) Some clients see units floating left/right or instantly warping to a new position 2) JDAM/JSOWs (designated by Hornet TGP) miss targets by 30m even though replaying the Tacview track shows a direct hit 3) JTAC scripts also see the unit in a different location than what is rendered to clients In the attached screenshot, Tacview shows a direct hit, while in game this bomb missed the vehicle by 30 meters. Another potential clue for the ED dev team is that self lasing a designated target that dispersed with the hornet TGP works (GBU-12), but trying to hit a designated target with a JDAM (TOO mode GBU-38 ) misses by approx 30 meters every time. My theory is that the elevation output after dispersion is corrupted.

My group has noted a strange issue since OB 2.5.6.49718 where unit position reported to Tacview and scripts (in our case CTLD) differ from actual unit position in the game. We first noticed that LGBs dropped on targets that were designated using the CTLD JTAC Autolase script were missing their mark by approx. 50 meters. The first bomb in the attack sequence would always hit, the remaining targets would disperse by 20-100 meters as they normally do after an attack, then all subsequent bombs would miss even though the script was reporting that it is lazing a new target. Upon analyzing the Tacview recording, the bombs that missed appeared to be direct hits in the Tacview file, therefore the data read by Tacview and CTLD is the same, but inconsistent with actual unit location in the sim (we were seeing the bombs hit 50 meters away in F6 view). These observations were made on a Dedicated Server hosted mission (Track File Attached). To be clear, I fully understand that Tacview and 3rd party script are not supported by ED. In this case, Tacview and CTLD script just help expose the symptoms of the problem (inconsistent unit location data output from the sim). Track File: https://www.dropbox.com/s/tsx3bpy8zh0x2o2/current-20200529-091301.trk?dl=0 Server Spec: Intel Core i7-9750H 16GB Ram Nvidia GTX 1070 512GB SSD

@Der Hirte, Bring up the VAICOM PRO config with LCtrl+Lalt+C, select Reset, tick the Lua code box, then MASTER ZERO. Quit DCS and VoiceAttack and relaunch both.