Tacview 1.2 is out!
-
Many Thanks Vyrtuoz.
Tacview is very useful to us !! -
Hi, I will try and have a good look at features of both later….what I did notice first was that in Falcon ACMI, ( and not in TacView) you can have the turn rate, radius and speed displayed as labels which is very handy to see where you gain and lose advantage. I have not seen how to show the energy charts yet…will delve deeper…
Cheers, Mark
-
Hi guys, thanks for your support
Here some answers to your questions:
- Your product keys will automatically work with this new version (up to Tacview 1.999)
- This is not a mandatory, but you can uninstall any previous version since this new version is way more powerful
- The home edition will display radar locks and all other advanced telemetry
- Real time analysis has not been developed yet; it will be available mainly for new simulators like DCS which offers pretty good export capabilities. Falcon does not export data in real time (aside the shared memory which contains only the main aircraft cockpit data). The best way to have it with Falcon 4/BMS would be to improve falcon itself to directly export data in real time in a format supported by Tacview.
- The same turn rate & radius data as in Falcon are going to be available in the next release (not enough time to add them in this release)
- For other data like the SPI, I’m going to see what I can do, but if they are not exported in the VHS file I cannot invent them
-
As per rl, it would be extremely useful for the debriefing process to display the radar search cone / coverage area.
Thanks 4 your efforts m8.
-
……and ECM status…
And also missile status, HOJ, Maddog, etc radar locked, radar cone from missile.
-
……and ECM status…
And also missile status, HOJ, Maddog, etc radar locked, radar cone from missile.
…and a partridge in a pear tree… You guys are demanding!
New version is positively AWESOME THANKS!
-
Is anyone having performance issues with v1.2? Previous versions worked fine on my machine, but v1.2 uses more CPU power and stutters more than BMS does.
-
Is anyone having performance issues with v1.2? Previous versions worked fine on my machine, but v1.2 uses more CPU power and stutters more than BMS does.
I gave the x64 version a try on my i7 just to see the new features and it glitched a bit. I tried the x86 version and that seemed to run fine - just like the previous version. I haven’t used the x64 exe since so can’t say if the glitch was a one off or not. I am unable to use Tacview on my GMA 3150 (OpenGL 1.4) based netbook as it doesn’t support the required OpenGL version (ie it CTD) so can’t say how it fairs on a weak system.
-
Is v1.2 optimized for 64 bit operating systems? I’m running XP.
-
Is v1.2 optimized for 64 bit operating systems? I’m running XP.
I don’t think so, the x64 exe has probably just been optimised for a x64 OS as I don’t see any difference in function. In fact the x86 version seemed faster and more stable on my x64 OS but this is the first Tacview version I’ve seen that included an optional x64 exe so I guess that might be the direction it’s going ie more features = faster CPU + bigger Memory. On the other hand it may just be required to link into DCS:World which is x64. There are a varity of sim’s and OS’s that require support so IMHO there will continue to be x86 and x64 optimised versions of the exe.
-
One word about the 64-bit version:
Obviously they are compiled with different assembly instructions; however, both versions are virtually identical. For instance, I have been working with the 64-bits version for several years.
What is the difference between the 32-bits and 64-bits versions of Tacview? In short: almost none. The features are exactly the same. The 64-bits version is just a bit faster and can open huge flight recordings (not limited anymore to about 1.2 GB of data).
Why the 64-bits version is slower on my computer? In that case you should check for OS and drivers for updates. I’ve done some benchmarks and – as expected – the 64-bits versions always run slightly faster on 64-bits computers.
Since I’m going to write a new 3D profiler, I wrote a profiler and I’ve done more benchmarks. (Reference Falcon 4 recording on Core i7+GeForce 560Ti)
- 1.1.1 : x86 209 fps
- 1.2 : x86 205 fps / x64 205 fps (slower than 1.1.1 because of new features)
- 1.2.1 : x86 225 fps / x64 230 fps (same as 1.2 + a minor performance fix)
-
When I downloaded it I didn’t see any mention about OS or anything, but I’ll take another look.
-
I’m a pro user and I noticed the KF-16C-32 doesn’t have unique model (just a triangle). Is this a known issue or am I doing something wrong?
-
Toto, you might want to post in this thread instead? Much more recent activity.
-
This is a known limitation of this generation of Tacview. This engine can display 3D meshes only for known objects. This will be improved in Tacview 2.0. Meanwhile I have added this F-16 to the mesh database so you should see the proper shape in the next release.
-
Awesome job m8, big fan! Question: are radar lock lines available in the freeware version now?
-
Among many other things, radar locks are part of advanced telemetry data. This is why it is (and will be) available only to Home and Professional users.
-
A question if I may…in some recordings of mp the oher side’s ordnance employment is not recorded, mostly canon.
It was checked on several occasions with DF where each side recorded and had everything but the other side’s canon bullets (all missing).
Is it a BMS or Tacview related and is there a way to resolve it? -
I need more information to understand what is going on. It may be an issue on BMS side related to network optimizations. However, it could be - as well - a bug or a limitation of Tacview (incorrect objects types interpretation for example).
Could you share me the original VHS files where I can see this issue? (it would be great to have the VHS recorded by different players during the same session)
Also, can you tell me which theater, version of BMS and aircraft(s)/time I should focus on.
-
I believe its usually an issue in falcon rather than in tacview, at some occasions cannon shots arent being showed in mp, thats propably why you cant see them in tacview either.