Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
For example, I can get the UV (=XZ) coordinates, and the altitude (=Y) for the aircraft, but if I bail out, these data do not exist for the parachuting pilot (thus, I can't figure out where he lands). The same thing applies for bombs/rockets/etc..
Here's a sample...
Any suggestions on how to get UV output for all objects? Thanks again.
I am not sure why U and V wouldn't be available for all objects. Can you please share your ACMI file with me?
Thanks. I have re-run the test very carefully with a minimum-working-example. This involves a simple mission, with a single aircraft where I drop a single bomb and then bail out.
Then, using Tacview Advanced, I generate a CSV file, where I export everything (I selected the "All" options, and 10 Hz rate, during the export).
The bomb is now showing U,V data, so I suspect that this was user error on my part from earlier. However, the ejected pilot is definitely not showing in the CSV.
I cannot post attachments on Steam, but if you wish to download the files, I have put them here.
DCS track file :
http://stormofwar.info/temp_docs/tvt/server-20210824-221719.trk
The Tacview ACMI file :
http://stormofwar.info/temp_docs/tvt/Tacview-20210824-221735-DCS-test-tacview-export-v01.zip.acmi
Exported CSV file from Tactview advanced :
http://stormofwar.info/temp_docs/tvt/Tacview-20210824-221735-DCS-test-tacview-export-v01.csv
Any suggestions? Thanks for the support.
Thanks for simplifying the file to make it so easy for me to see the problem!
In this example, the ejected pilot has been mistakenly typed Misc+Shrapnel by the exporter.
To save memory, U,V is not included for such simple objects as shrapnel. But if the exporter had properly typed the ejected pilot as a Parachutist, the U,V would be there.
It is complicated for the exporter to understand which objects are Parachutists. We have to manually add certain information for each aircraft.
Could you reproduce this with Debug set to Minimal in the Tacview Options in DCS? That will give me the information I need to update the exporter.
I have set "Debug Mode = Minimal" in the DCS->Options->Special->Tacview section.
I then ran the exact same mission as last time. Here are the same files, but for this new run...
http://stormofwar.info/temp_docs/tvt/Tacview-20210825-232049-DCS-test-tacview-export-v01.zip.acmi
http://stormofwar.info/temp_docs/tvt/Tacview-20210825-232049-DCS-test-tacview-export-v01.csv
http://stormofwar.info/temp_docs/tvt/server-20210825-232005.trk
Awesome! We added the information in the beta I just published so now pilots ejected from FW-190D9 should show as parachutists and have U,V included. Let me know how it goes! And don't hesitate to let me know about any other incorrectly typed objects, you'd be doing me a favour!
At the moment, I am still unable to get it to work, but I'm not convinced I have the correct version. If I open Tacview, and then go to the "About" menu option, it causes a little window to appear in the centre of the screen which says I have "Tacview 1.8.7 64-bit-advanced". But there is no mention of "beta 11". Is that correct?
I have the "beta - Beta builds for Standard and Advanced users" selected in Steam -> Tacview -> Properties -> Betas.
Is there something else I need to do to pick up the new version? Thanks!
Sounds like you definitely have some beta of Tacview 1.8.7 at least. In the top left corner of the Tacview window, in the menu bar, it should say something like "Tacview Advanced 1.8.7 beta 11".
You might have to close and re-launch Steam entirely to get the new beta.
You will have to do a whole new flight recorded by the new beta in order to see the improvements.
If none of that helps can you share just your DCS log and ACMI file from the new flight?
Yes, I can confirm I have the Beta 11. I have restarted Steam, restarted DCS, and flown the mission again.
I still have the same problem.
Here are the ACMI and CSV files.
http://stormofwar.info/temp_docs/tvt/Tacview-20210904-131929-DCS-test-tacview-export-v01.zip.acmi
http://stormofwar.info/temp_docs/tvt/Tacview-20210904-131929-DCS-test-tacview-export-v01.csv
At first, when I ran this test, I looked into the DCS log and have noticed that BOTH 1.8.7 and 1.8.6 get mentioned. Updating TacView and running it again, I still get:
I suspect I need to fix the
Try this:
I tried this, but it made no difference. It claimed all the files were okay and it verified without error.
HOWEVER . . .
What I then did, was to completely uninstall TacView. I also manually checked that the files were indeed removed, and I also re-installed the original Export.lua that I had saved from earlier (i.e. a default Export.lua for DCS).
I then re-installed TacView from scratch (full download, install dialogue, etc.).
Then, I checked TacView and it is now 1.8.7 beta 12.
I then ran the DCS test mission again from scratch, with the debug settings that you suggested earlier, then loaded the new ACMI file into TacView and exported all data. And...
. . . IT NOW WORKS !
So, in summary, a complete reinstall was needed to pick up the new version of the .dll. And, once that was done, the new version indeed tracks and outputs the telemetry for the pilot while he is parachuting down. I have since also re-installed SRS and, yes, Tacview is still working okay. So, this is where I wanted to be.
Problem solved.
Thank you very, very much for the support and help. This level of responsiveness from a developer is very refreshing and very welcome indeed. I am grateful for the time and effort you took to help get this resolved and I also appreciated the prompt action to the initial problem. Thanks again!!