Tacview 1.0 is now available!

Does it work with FC2.0 ?

Yes

Indeed, since DCS A10 there is an offset between the velocity vector and the aircraft track depending on where you are into the map. This bug is specific to A10 which is using a new spherical projection system which is a bit buggy.

I've reduced this issue in Tacview 1.0 export script. I will try to reduce it further in next releases.

NP!

One more question, I've asked it elsewhere, maybe you can comment it there:

http://forums.eagle.ru/showpost.php?p=1141864&postcount=9

 

Why, in the TACVIEW, when replaying the track, the velocity vector is "off" to the left a few degrees ?

Some wishlist items:

- Allow manual setting of Y axis in the graph. Because of lag spikes you can have for example, someone shoot to M25 which sets the top of the graph to '25' and it then become difficult to read differences in sub-mach speed.

- Export of graph data. A simple .csv file would be quite adequate; then we can put this in excel or gnuplot or whatever our favorite graphing tool is to print it if so desired.

I'm definitely looking at getting the pro version.

Here some answers to your questions:

 

• In coming releases you will be able to select and analyze up to 4 objects at the same time
  
• The free version is really free (for home users). You don't have to register to use it. Obviously, at the end of 21-day trial advanced features will be disabled, the rest of Tacview will work as usual without popup or ads.
  
• Latest DCS: A-10C Warthog export scripts are available here: http://lomac.strasoftware.com/tacview-dcs.php
  
• I will probably work on the online-debriefing tool for Tacview 1.2 (the 1.1 release will be "dedicated" to Falcon 4 users ;))
  
• The main differences between each edition are listed here: http://www.strasoftware.com/buy/tacview
  

Some wishlist items:

 

- Allow manual setting of Y axis in the graph. Because of lag spikes you can have for example, someone shoot to M25 which sets the top of the graph to '25' and it then become difficult to read differences in sub-mach speed.

 

- Export of graph data. A simple .csv file would be quite adequate; then we can put this in excel or gnuplot or whatever our favorite graphing tool is to print it if so desired.

 

I agree with these points. I wrote a real time flight data analyzer that would output .csv so I could display it on another monitor running livegraph. It was a cool tool, but didn't include nearly the functionality that could be realized with Tacview.

Vyrtuoz, am I right to assume TR is turn rate? Did you calculate this using differential heading with respect to time like you have to do with other objects' speed? I used an equation involving g's, but of course at straight and level 1.0 G it will read over 2.x deg/s.

You are right about lag spikes; I will fix that in coming versions. The export option is already planned and should be available in Tacview 1.1 or 1.2.

Some wishlist items:

 

- Allow manual setting of Y axis in the graph. Because of lag spikes you can have for example, someone shoot to M25 which sets the top of the graph to '25' and it then become difficult to read differences in sub-mach speed.

 

- Export of graph data. A simple .csv file would be quite adequate; then we can put this in excel or gnuplot or whatever our favorite graphing tool is to print it if so desired.

 

I'm definitely looking at getting the pro version.

Since this thread is getting more attention, i'll post it here: Tacview detects only those units marked by a label. I was running weapons training mission and destroyed some unlabeled units and the tacview didn't detect a hit. Is this DCS issue or tacview?

I'd say it's a DCS issue. We've noticed the same thing flying multiplayer, where the server host can see all targets, but the clients can't. When the host kills a target nobody else sees, on the server side he gets credit for it... on the client side nothing changes.

future wish:

Able to see, which target every object is tracking with radar/ TGP or other tracking systems.

kind regards,

Fire

I'd say it's a DCS issue. We've noticed the same thing flying multiplayer, where the server host can see all targets, but the clients can't. When the host kills a target nobody else sees, on the server side he gets credit for it... on the client side nothing changes.

Most of such desync issues are caused by people fiddling with mods, tweaks and customizing .lua files. If client and server are not running 1:1 copy of the databases - you may expect such issues.

• TR is indeed the Turn Rate. I calculate it using differential heading (current_heading-previous_heading/dt), it is not linked to G calculation which is far more complex.
  
• Tacview handles properly anonymous objects (since Black Shark there are some objects without names, typically infantry). So, in your case, this looks like a DCS network issue.
  
• Radar/IR tracking and locks will be supported, but later (may be in Tacview 1.3), this is part of what I call "advanced telemetry". Beware that those data are usually available only for the local player aircraft.
  

Did the patch break the acmi exporting in DCS:A-10?

I have ran a couple of missions and it doesn't seem to have worked with the exporting.

Worked fine on my end.

I found an issue with the GBU-38.

The flight direction indication of the GBU-38 is false. I have an similar tac-file and there, the flight direction indication is also 90° left off the real flight path.

GBU-12s are fine.

kind regards,

Fire

User error.

#1) forgot which folder I had it set to save the files and

#2) tried to do a search for .acmi and came up with nothing.....but they were there. Havent totally figured out windows 7 yet :P

This is a bug in DCS: jettisoned objects are not properly oriented.

I found an issue with the GBU-38.

 

The flight direction indication of the GBU-38 is false. I have an similar tac-file and there, the flight direction indication is also 90° left off the real flight path.

GBU-12s are fine.

 

 

kind regards,

Fire

This bomb wasn't jettisoned, just a normal bomb release.

kind regards,

Fire

Love the new release by the way, I was waiting for it to support Warthog, no more screwed up tracks hopefully(fingers crossed).

I'm running on Win 7 x64.

I'm experiencing a strange problem - when I load an ACMI recording, tacview uses as much CPU as it can and is really, really slow. Has anyone seen this before?

Can you share me your ACMI recording, so I can check its content? (the original .txt one)

I'm running on Win 7 x64.

 

I'm experiencing a strange problem - when I load an ACMI recording, tacview uses as much CPU as it can and is really, really slow. Has anyone seen this before?

I can - it is happening with all of them though. I'll get you one ASAP.

Was trying to load up an .acmi file tonight and it was hanging the program. I have narrowed down what was causing it. Looks like a SU-24 dropped some bombs, but the tacview recording has the bombs being dropped + a Kh-29T that shouldnt have been dropped.

I opened up the tacview file and kept deleting entries until it opened correctly :)

Here is a .zip file that contains both the whole .acmi file plus the debrief.log from the DCS Temp files.

The first time it pops up is at the reference time in tacview of #1002.40

If I delete line 301152 (and everything afterwards), it loads fine. If I include that line tacview hangs when I try to load the file .

In the .log file the corresponding time is T=43602.390

Here are the offending entries:

#1002.40
+1f700,?,40,1,?,Kh-29T (AS-14 Kedge),,?,?
1f700,6.096472,4.957169,3024.51,0.0,0.0,5.9
+1f900,?,4c,0,ru,RBK-250,,?,?
1f900,6.096454,4.957164,3025.75,-61.5,-35.7,123.3
+1f800,?,4c,0,ru,RBK-500AO,,?,?
1f800,6.096461,4.957155,3025.93,-61.5,-35.7,123.3

Been playing around way too much with this :). Apparently the Su-24 jettisoned weapons after being fired upon by a Blue CAP flight. For some reason it appears that the program does not like having two objects being so close together at the same place and time!

I was able to get the .acmi to load if I did the following with the jettison event quoted above....I placed a slight time delay in the file to get the following:

#1002.40
+1f700,?,40,1,?,Kh-29T (AS-14 Kedge),,?,?
1f700,6.096472,4.957169,3024.51,0.0,0.0,5.9
+1f900,?,4c,0,ru,RBK-250,,?,?
1f900,6.096454,4.957164,3025.75,-61.5,-35.7,123.3
#1002.41
+1f800,?,4c,0,ru,RBK-500AO,,?,?
1f800,6.096461,4.957155,3025.93,-61.5,-35.7,123.3

The other Su-24 also jettisoned ordinance at time point #1270.94. I also had to split up that group to get the entire .acmi to load. This is what I changed it to:

#1270.94
+33600,?,40,1,?,Kh-29T (AS-14 Kedge),,?,?
33600,6.009663,5.125368,3484.89,0.0,0.0,6.0
+33800,?,4c,0,ru,RBK-250,,?,?
33800,6.009657,5.125381,3486.89,-96.2,-29.4,90.1
#1270.95
+33a00,?,4c,0,ru,RBK-500AO,,?,?
33a00,6.009657,5.125373,3487.78,-96.2,-29.4,90.1
+33b00,?,40,1,?,Kh-29T (AS-14 Kedge),,?,?
33b00,6.009668,5.125393,3488.64,0.0,0.0,6.0
+33700,?,4c,0,ru,RBK-500AO,,?,?
33700,6.009656,5.125368,3486.94,-96.2,-29.4,90.1
#1270.96
+33900,?,4c,0,ru,RBK-250,,?,?
33900,6.009658,5.125410,3485.54,-96.2,-29.4,90.1

When I made the two edits above, the .acmi loaded properly.

One other thing to note: Not sure if it is a tacview problem or it has to do with the sim, but the Kh-29T is being recorded as BLUE object instead of a RED object.

I really appreciate your feedback Zamboni. Thanks to your report I was able to reproduce the issue.

It happens because the sub munitions [RBK-500AO] are released at the very same time as the bomb [RBK-250]. Tacview does not know which one is the parent object, so it get lost during data analysis...

This case is ultra rare. You are the first to report it to me in 4 years :)

I'm going to fix this in Tacview 1.1.

Was trying to load up an .acmi file tonight and it was hanging the program. I have narrowed down what was causing it. Looks like a SU-24 dropped some bombs, but the tacview recording has the bombs being dropped + a Kh-29T that shouldnt have been dropped.

 

I opened up the tacview file and kept deleting entries until it opened correctly :)

 

Here is a .zip file that contains both the whole .acmi file plus the debrief.log from the DCS Temp files.

 

The first time it pops up is at the reference time in tacview of #1002.40

If I delete line 301152 (and everything afterwards), it loads fine. If I include that line tacview hangs when I try to load the file .

 

In the .log file the corresponding time is T=43602.390

 

Here are the offending entries:

#1002.40
+1f700,?,40,1,?,Kh-29T (AS-14 Kedge),,?,?
1f700,6.096472,4.957169,3024.51,0.0,0.0,5.9
+1f900,?,4c,0,ru,RBK-250,,?,?
1f900,6.096454,4.957164,3025.75,-61.5,-35.7,123.3
+1f800,?,4c,0,ru,RBK-500AO,,?,?
1f800,6.096461,4.957155,3025.93,-61.5,-35.7,123.3

Glad that it is ultra rare :)

When it didn't load I peeked into the file and decided to see what was different why one .acmi file loaded, but another didn't. Was interested in seeing the .acmi also because for some reason in my debrief, I didn't see what caused my right wing to be blown off and forced me to eject. Thought I may have fragged myself with a cluster bomb, but the .acmi showed it was tank fire that did the deed.

This mission came after I had been merged with 2 MiG-29s and took a missle hit. I didn't even look through the debrief because I knew I had Tacview to get the same info :). Turns out it wasn't the MiGs that did the damage, it was friendly fire from some F-16s that sent a slammer into my side!

very interesting tool... Is there a way to make a sams' site range standout when selected ? All that red upon red (or blue upon blue) is confusing if you are trying to single out the range of a particular site. I only see I can either have then all off or all on... not just select a few to be on / off... Or am I missing something... Or even change the selected object to another colour would be nice so it and it's range standout.

Thanks...