Bahger Posted January 12, 2011 Posted January 12, 2011 (edited) I know it's the system, ever since LOMAC, this engine does not "record" activity but presents replays in the form of, well, true replays, i.e. the mission is literally replayed by the AI. The problem is, there are so many anomalies. In particular, tracks won't reproduce weapon data input properly, or behavior commanded in the original playthrough by player-JTAC comms and the results are often hilariously off-kilter, with hit targets not being hit in the replay, even planes crashing that survived the original playthrough unscathed. I'm talking about tracks made in the same beta version as the mission was made and played. It's been a while since I've used this engine, so please let me know if this eccentric behavior is simply "par for the course", thank you. Edited January 12, 2011 by Bahger
Nate--IRL-- Posted January 12, 2011 Posted January 12, 2011 Yeah, the longer a track or the more stuff going on in a track, the more likely it is to play back erratically. Par for the course. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
scoochy Posted January 12, 2011 Posted January 12, 2011 I noticed this last night when 2 replays showed me in completely different situations that what actually happened during the mission. One replay I was shot down when in the actual mission I returned home with minimal damage. Another showed me landing in the middle of a field and crash when in reality I landed back at base safe and sound. I also noticed that the mission summary IE Total kills for the player, changed. One total was shown at the completion of the mission, a different total was shown at the end of viewing the replay. Neither total actually made it into my logbook.
power5 Posted January 12, 2011 Posted January 12, 2011 Yeah, playback is annoying erratic, but hopefully smooths out in the retail version. I had a good 15 minute mission and watched the replay die in the first 45 seconds. Did not save the replay first, so its gone I guess. I can not remember as many errors in my BS replays. [sIGPIC][/sIGPIC] Aaron i7 2600k@4.4ghz, GTX1060-6gb, 16gb DDR3, T16000m, Track IR5 BS2-A10C-UH1-FC3-M2000-F18C-A4E-F14B-BF109
Frederf Posted January 12, 2011 Posted January 12, 2011 The track files are iterative instructions for the engine to work out each time. This means any modification to the calculation environment or simply vagueness in the collected data can cause drastic disagreements. One narrowly passes over a mountain and goes on to bomb the target. In the track you slam into the mountain. TacView on the other hand is absolute, the accuracy of any frame doesn't depend on the frame before it and is a million times more robust.
Dejjvid Posted January 12, 2011 Posted January 12, 2011 Sometimes I grab a cold one and just sit and laugh to the replays :) they're like the best movie ever, you never know how they end :) i7 8700K | GTX 1080 Ti | 32GB RAM | 500GB M.2 SSD | TIR5 w/ Trackclip Pro | TM Hotas Warthog | Saitek Pro Flight Rudder [sigpic]http://www.132virtualwing.org[/sigpic]
Bubb Posted January 13, 2011 Posted January 13, 2011 I did some tests on this and found out that if I run the simulation with "Administrator" elevation the replays won't get corrupt. I did a test mission, twice for each setting and the results were the same. Ramp start, Take off, kill 3 trucks with Mavs, kill 2 tanks with LGB and gun down 1 IFV. Running as "administrator" resulted in prefect playback both times Running without resulted in the track being corrupt even before shooting the first maverick. Don't know if its related but thats what happens to me. Running on Win7 x64. 1
Dejjvid Posted January 13, 2011 Posted January 13, 2011 I'm one of those stupid persons that always run everything as admin, and i get funny replays quite often :) x64 Win7 i7 8700K | GTX 1080 Ti | 32GB RAM | 500GB M.2 SSD | TIR5 w/ Trackclip Pro | TM Hotas Warthog | Saitek Pro Flight Rudder [sigpic]http://www.132virtualwing.org[/sigpic]
Recommended Posts