Inaccuracy in V1 Mission Track Recording

[WytchCrypt]

Hi all,

I've recently run a V1 intercept mission on IL-2 1946 4.13.4. In the mission I shot a V1 out of the sky with guns, but on the track I miss the V1 and are shown shooting at nothing while the V1 continues to fly unharmed. Can anyone tell me why this is happening? My favorite thing to do with IL-2 is to record tracks and play them back, but this inaccuracy is definitely frustrating.

Thanks!

[Jumoschwanz]

Tracks saved of the Quick Mission builder are never accurate these days, the computer seems to just make up whatever it is in the mood for. I am not sure about missions run with the Full Mission Builder, but online tracks are still good. So if you want to run a scenario and record it then build in in the Full Mission Builder and then start a server and pick what you have built as the online mission. This way your track of what happens will be accurate.

[Storebror]

Not really a QMB/FMB issue but rather a TRK/NTRK one.
Explained in detail here: https://www.sas1946.com/main/index.p...c,57038.0.html

Best regards - Mike

[dimlee]

Perfectly explained by Storebror in the link he referred to.

Just to add from my own observations. Other "strange" things one can see while playing NTRK:
- bomb doors remain open despite they were closed automatically or manually
- mid air collisions seem as caused without actual contact between two a/c
or
- NTRK shows a "collision" while no damage happens actually
- torpedo trail missing
- bomb with delayed fuse explodes immediately at impact - but message "target destroyed" appears later
- clouds positions might be off set a bit (for example, NTRK shows that you fires and hit your target in zero visibility conditions).

[WytchCrypt]

Originally Posted by dimlee

Perfectly explained by Storebror in the link he referred to.

Agreed. That's the same thread I started on SAS