Ah ok, I see. Thank you. The other feature would also be nice, but as you say, would take dev time.
Can you elaborate on how the integration between Tacview and CMO will work? For example, if I click on a unit in CMO, will it be shown in Tacview?
I suppose the "FOW" (I'm still not sure what that means, if you could spell it out for me I would appreciate it) importance would just depend on how easy it is to see opposing units in tacview? If it's really obvious, then it kinda spoils things (for example, if I'm hunting a sub)
Any elaboration you could make would be very much appreciated. Thank you!
I'd also like to point out that we are all here because of the fantastic game you've made (and improved) over the years, so again, thanks for making this amazing thing :)
You are welcome, and thank you for the kind words.
We presented the basics of Tacview integration in this article last month: http://www.warfaresims.com/?p=4975
The way the interaction works is that you click on a unit or contact on the top-down map, and the camera centers on this object in Tacview, as in this example: https://steamcdn-a.akamaihd.net/steam/apps/1076160/ss_0093c7653341c089fc6dc7742709e303c103873c.jpg
You can zoom/pan the Tacview camera around the selected object, so you can go from close focus on unit all the way out to seeing the entire theater. The Tacview window is not a "fixed" part of the overall main window but is instead it own separate window. This makes it easy to resize it, move it around the screen to your preference or park it on a second monitor, if you have one.
As Sharana said, FOW refers to Fog Of War; because Tacview was originally developed as an AAR tool, it is designed to show the ground-truth and all objects, instead of a specific side's view. IMO this is the biggest limitation of this implementation so far, and we would very much like to implement more realistic FOW, but as I said before we first need to determine if it's reasonably feasible and if players actually want it (more than other items, that is).
The association between the database and Tacview’s 3D models (which model to display for unit-XYZ?) is handled by two Excel spreadsheets (one for DB3000 and another for CWDB) which list all database entries and the most suitable model for each (because there are not enough models for all platforms in the databases, often generic models or “close enough” substitutes are used instead of precise matches). The 3D models are stored as individual .obj files (Alias-Wavefront format). This is important, because it means that end users can tweak the associations and add their own custom models as desired. Some of our beta testers have come forward with many new models (example: https://twitter.com/warfaresims/status/1184695601935634434) which greatly enhance the visual experience.
Rory, (or Dimitris) sorry, one more - how can we avoid "cheating" while using Tacview? I imagine it brings a lot of immersion to the table, but I'm wondering how you use it, and avoid spoiling things?
< Message edited by JOhnnyr -- 11/4/2019 6:07:39 PM >