Sinister Posted April 3, 2010 Posted April 3, 2010 1 .. I have been finding that for some reason, when reviewing a track, if you advance (fast forward) that track more than 8 or 10x, the track will start to lag and lock up the game and will have to resort to having to do a FORCE QUIT of the program. 2. The Tracks dont play back the same way the mission was flown. I am not sure if the fast forwarding has anything to do with degradation of the track data. I will test later on. But I am not the only one who has this problem. And it does not occur at the same time in the track.. You could play it once and it will screw up after 10 mins.... or play it again and it screw sup at 7 mins.. So it wouldnt have anything to do with packet loss or lag from client to host. It shouldnt matter. any suggestions or fixes.? [sIGPIC]http://www.virtualpatriots.com/images/Sigs2/Virtual/sinister.jpg[/sIGPIC]
LawnDart Posted April 3, 2010 Posted April 3, 2010 Tracks aren't actual recordings, more like recreations based on data (such as control inputs and events). While I haven't seen this yet in FC2, it's happened several times in FC1. It's like Wags put it regarding their decision to use training videos rather than training tracks: "Tracks could break if you as much as blow on them". Just for reference, not a solution (I know), I FFWD'ed one of my tracks up to 90x just the other night and it still recreated the events and flying "as it happened" the full 20-25 minutes the mission lasted. Just guessing here, but in my experience when a track replay has gone awry it's often been caused by some form of control input device and/or a setting (such as unlimited fuel vs. limited fuel) being changed between flying the mission and playing the track. Btw, shouldn't this be moved to the Lock On forums. ;) [sigpic]http://www.virtualthunderbirds.com/Signatures/sig_LD.jpg[/sigpic] Virtual Thunderbirds, LLC | Sponsored by Thrustmaster Corsair 750D Case | Corsair RM850i PSU | ASUS ROG MAXIMUS X CODE | 32GB Corsair DDR4 3200 | Intel i7-8086K | Corsair Hydro H100i v2 Cooler | EVGA GTX 1080 Ti FTW | Oculus Rift | X-Fi Titanium Fatal1ty | Samsung SSD 970 EVO 1TB NVMe | Samsung SSD 850 EVO 1TB | WD Caviar Black 2 x 1TB | TM HOTAS Warthog | TM Pendular Rudder | TM MFD Cougar Pack | 40" LG 1080p LED | Win10 |
Kilgore Posted April 3, 2010 Posted April 3, 2010 Has anyone else had a bluescreen of reboot yet while trying to save a track? I just finished a mission and thought I'd watch my flying but when trying to save after quitting, my computer hit a bluescreen and rebooted.
Distiler Posted April 3, 2010 Posted April 3, 2010 1 .. I have been finding that for some reason, when reviewing a track, if you advance (fast forward) that track more than 8 or 10x, the track will start to lag and lock up the game and will have to resort to having to do a FORCE QUIT of the program. Because it's not a video, it's a recreation of what you did, so all the IA and flight physics are calculated in real time like when you flew, so if you accelerate time, you need to calculate all this faster. This is why your fps go down. AMD Ryzen 1400 // 16 GB DDR4 2933Mhz // Nvidia 1060 6GB // W10 64bit // Microsoft Sidewinder Precision 2
Distiler Posted April 3, 2010 Posted April 3, 2010 2. The Tracks dont play back the same way the mission was flown. I am not sure if the fast forwarding has anything to do with degradation of the track data. I will test later on. But I am not the only one who has this problem. And it does not occur at the same time in the track.. You could play it once and it will screw up after 10 mins.... or play it again and it screw sup at 7 mins.. So it wouldnt have anything to do with packet loss or lag from client to host. It shouldnt matter. any suggestions or fixes.? Havent noticed any of this. Tracks seem to play correctly in my computer. AMD Ryzen 1400 // 16 GB DDR4 2933Mhz // Nvidia 1060 6GB // W10 64bit // Microsoft Sidewinder Precision 2
Panzertard Posted April 3, 2010 Posted April 3, 2010 1. it can happen that the replay gets out of sync on very fast forward. With very high forward actions may stack up - and processing gets harder. Workaround: Avoid very high fast forward. Fix for code: Not sure if it's a high priority. But maybe it's possible to tune the queue / actions somewhat. I'll put up a request. 2. Yes, same as with 1, in some situations teh recording may get out of sync - you move your aircraft harder than your computer can record. This is due to how the track recording works atm. Workaround: If it's important to record correctly - try to avoid the "hard / breaking manouvers". Fix in code: Depends on how badly it is broken - ED needs to have a look at it. But you can get out of sync if you really try. The mind is like a parachute. It only works when it's open | The important thing is not to stop questioning
Recommended Posts