Tacview 1.2 is out!
-
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.