![]() |
|
#1
|
|||
|
|||
![]()
Please forgive me if this has already been brought up, but it's the first time I've noticed it and I haven't seen it in other bug posts:
The .ntrk feature seems to be broken. I'm using a stock install with no mods at all, and when I record flights (by using the record button to record .ntrk instead of after flight .trk), the resulting records very quickly turn very bad. The aircraft fly at impossible angles, and often things happen in the video that did not happen in the actual flight. I can record this with a screen capture so you can see what I'm seeing, and I can upload an .ntrk if needed. Please let me know if you need either of those things. Thanks! |
#2
|
||||
|
||||
![]() Quote:
__________________
Q: Mr. Rall, what was the best tactic against the P-47? A: Against the P-47? Shoot him down! (Gunther Rall's lecture. June 2003, Finland) |
#3
|
||||
|
||||
![]()
Using The 4.13.1m stock Dedicated Server in dogfight mode.
When a player shot down a B-25J-1NA he only got 100 points. The B-25J-1NA is a twin-engine plane. Whyn't 200 points? Of course the killer RTB without any problem so he's full scored. Attached: 2 B-25J-1NA are above Argentan 45 min after the mission beginning. |
#4
|
|||
|
|||
![]() Quote:
It seems that actions started before starting recording are not recorded correctly. E.g. if you're engaged in a dogfight, and you start recording when you're already shooting at your opponent, it won't be replayed correctly. Workaround: start recording when you engage, start recording before you drop your bombs, etc.. Last edited by KG26_Alpha; 05-09-2016 at 09:47 PM. |
#5
|
|||
|
|||
![]()
Yup NTRK stands for Network TRK. It's a packet recorder, so it's like a mini network game. In your conf.ini, make sure your rate is set to the LAN setting (or use the game interface to do this). Especially helpful when you make NTRK in SP mode—the network rate still plays a role.
What is captured is any/all events that are flagged to BE captured. Some issues relate to what "STATE" an object is in the game. For example, around 4.09 or so, the Gunsight dimmer was always captured in the wrong initial state. This was fixed... In 4.13.1, sometimes the bomb bay doors are in the wrong initial state, etc. And most of all the bombsite clutch's initial state is NOT captured correctly. I hope to see this get fixed!! Objects away from the host don't get the same packet priority, so you'll see some weird warpy-things. Especially noticeable in Multiplayer NTRK recording.' Quote:
|
#6
|
||||
|
||||
![]()
Right, bomb bay doors wrong position is typical. I cursed myself for not closing them many times until I realised it was just recording glitch.
![]()
__________________
Q: Mr. Rall, what was the best tactic against the P-47? A: Against the P-47? Shoot him down! (Gunther Rall's lecture. June 2003, Finland) |
#7
|
|||
|
|||
![]()
Thanks Tolwyn for the explanation! Possibly my workaround is just wishful thinking...
|
#8
|
|||
|
|||
![]()
The R-5 pilot skins change from the selected skin to the default when switching view from cockpit to gunner to exterior.
|
#9
|
|||
|
|||
![]()
The course autopilot doesn't work on the JU-88 A17 and only works like a level stabilizer.
|
![]() |
Thread Tools | |
Display Modes | |
|
|