jomar machado Posted September 26, 2014 Posted September 26, 2014 I would like to know why all my missions recorded some time ago, gone crazy after I've made the update version of DCS to DCS 1.2? :( They all end now in the water or in the grass...
Abburo Posted September 26, 2014 Posted September 26, 2014 This is a pretty unfortunate feature of DCS as far as I know and experienced myself too :( Romanian Community for DCS World HW Specs: AMD 7900X, 64GB RAM, RTX 4090, HOTAS Virpil, MFG, CLS-E, custom
cichlidfan Posted September 26, 2014 Posted September 26, 2014 Missions recorded on older versions can often be problematic. If they were from before 1.2, which was a very long time ago, then quite a lot has changed. Wasn't 1.2 the first DCS World version? ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:
Buzpilot Posted September 26, 2014 Posted September 26, 2014 Missions recorded on older versions can often be problematic. If they were from before 1.2, which was a very long time ago, then quite a lot has changed. Wasn't 1.2 the first DCS World version? They change faster than that, i think the last one from 1.2.9 to 1.2.10 broke Replay, or maybe it was 1.2.8 to 1.2.10. i5 4670 - Sabertooth Z87- GTX Titan - Dell U3011 30" - 2x8GB RAM 1800 - Samsung 840 EVO 512GB SSD - Warthog HOTAS - CH Pro pedals - TrackIR5 - Win7 64bit EVERYTHING IS SUBJECT TO CHANGE :thumbup:
Art-J Posted September 27, 2014 Posted September 27, 2014 ^ Even faster. My recordings from "early" 1.2.10 are already pretty much useless. If You want to save some mighty replay for your grandsons to watch, you better learn how to use built in trk-to-avi converter. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
jomar machado Posted September 27, 2014 Author Posted September 27, 2014 ...and my joystick seems a bit too responsive. Is there a way to make it be a little slow? Thanks in advance bros...
Bimbac Posted September 27, 2014 Posted September 27, 2014 I think the easiest way to fix track issues is to go the same way as, for instance, TacView - which means exporting or recording angular speeds and spacial coordinates without using any features of the DCS engine, namely AI and physics. That way the replays would show what really happened and no bogus.
cichlidfan Posted September 27, 2014 Posted September 27, 2014 If the track is longer than about five minutes or has more than one aircraft in it, I don't bother saving it. Generally, it is not worth the time to sit through the replay to find out that it is broken. ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:
CookPassBabtridge Posted September 27, 2014 Posted September 27, 2014 Indeed. I made a thread asking for anyone who wanted to share their best tracks to watch in VR and folks kindly replied, however we are finding the same thing - that tracks made before the update have a few fatal inaccuracies that add up over time to a large crash :( See my sig for the link, YMMV and at least one works perfectly. Really good if you have DK2 :) [sIGPIC][/sIGPIC] I LIKE TO PLAY PRODIGAL WOMBAT STIMULATOR
AtaliaA1 Posted September 28, 2014 Posted September 28, 2014 If the track is longer than about five minutes or has more than one aircraft in it, I don't bother saving it. Generally, it is not worth the time to sit through the replay to find out that it is broken. So saving+opening it with the new ver. of the Editor included in the update doesn't work anymore to prevent this anymore, I take it? This was a Boutique Builder iBuypower rig. Until I got the tinker bug again i7 920 @3.6Mhz 12Gig Corsair XMS3 ram 1600 Nvidia 760 SLi w/4Gig DDR5 Ram Intel 310 SSD HDD 160 Gb + Western Digital 4Terabyte HDD Creative SB X-Fi HD Audio Logitech X-530 5.1 Surround Speaker System Dual Acer 32"Monitors. PSU 1200 w Thermaltake Win10 64Bit.
CookPassBabtridge Posted September 28, 2014 Posted September 28, 2014 (edited) So saving+opening it with the new ver. of the Editor included in the update doesn't work anymore to prevent this anymore, I take it? I will give that a shot, thanks EDIT: OK I tried opening the trk in the mission editor, then saving it and trying again. Also tried playing the replay FROM the editor. Not sure if I misunderstood your suggestion but its still playing back wrong? Cheers for help in any case :) Edited September 28, 2014 by CookPassBabtridge [sIGPIC][/sIGPIC] I LIKE TO PLAY PRODIGAL WOMBAT STIMULATOR
Mallard of Death Posted October 2, 2014 Posted October 2, 2014 What's the point in having the option to make a mission recording if the replay track is going to get corrupted??? Anyways, I wish I could enjoy this game 100%, yet I can not! Why? Because of the broken recording. For me 50% of enjoyment is lying on the bed, watching the replay track of some mission on my big TV... Damn.
sobek Posted October 2, 2014 Posted October 2, 2014 What's the point in having the option to make a mission recording if the replay track is going to get corrupted??? It's complicated... Good, fast, cheap. Choose any two. Come let's eat grandpa! Use punctuation, save lives!
Mallard of Death Posted October 2, 2014 Posted October 2, 2014 It's complicated... Would you be so kind and explain what is? Thanks.
sobek Posted October 2, 2014 Posted October 2, 2014 Would you be so kind and explain what is? Thanks. Making a simulation of this complexity deterministic. Backward compatibility of the track replay system is pretty much a pipe dream. Good, fast, cheap. Choose any two. Come let's eat grandpa! Use punctuation, save lives!
Mallard of Death Posted October 2, 2014 Posted October 2, 2014 Making a simulation of this complexity deterministic. Backward compatibility of the track replay system is pretty much a pipe dream. Well, it worked as it should for a time. Yesterday it went berserk :huh: I have noticed that this massive problem is present since beta (Autumn 2010)... Jiminy Cricket! On a side note, I think I've found a workaround: During the runway start, just speed up (LCTRL + Y) for ten seconds, then set it back to normal, and it sorta works. Note: DCS A-10C Warthog, mission 'Shooting Gallery.'
AtaliaA1 Posted October 2, 2014 Posted October 2, 2014 Making a simulation of this complexity deterministic. Backward compatibility of the track replay system is pretty much a pipe dream. Because the changes in the updates create an environment that the prior software programming doesn't understand? Seems like separating the two applications is the way to decrease the errors but then taking control of the flight wouldn't be possible I assume? If it is part of the software now it shouldn't be to difficult to work out the bugs that cause this error. Find it and eradicate it. (sounds easy) This was a Boutique Builder iBuypower rig. Until I got the tinker bug again i7 920 @3.6Mhz 12Gig Corsair XMS3 ram 1600 Nvidia 760 SLi w/4Gig DDR5 Ram Intel 310 SSD HDD 160 Gb + Western Digital 4Terabyte HDD Creative SB X-Fi HD Audio Logitech X-530 5.1 Surround Speaker System Dual Acer 32"Monitors. PSU 1200 w Thermaltake Win10 64Bit.
sobek Posted October 2, 2014 Posted October 2, 2014 Because the changes in the updates create an environment that the prior software programming doesn't understand? No because given the track inputs, when you change one detail (let's take AI pathfinding to make it obvious) the end result is going to differ completely from when the track was recorded. And then you aren't even taking into account that the physics engine might go through sample rate changes that put it out of sync with the track, which may result in ever increasing errors. I gotta admit given all that can go wrong with this system it works surprisingly well. Good, fast, cheap. Choose any two. Come let's eat grandpa! Use punctuation, save lives!
Mallard of Death Posted October 4, 2014 Posted October 4, 2014 No because given the track inputs, when you change one detail (let's take AI pathfinding to make it obvious) the end result is going to differ completely from when the track was recorded. With all due respect, that is a pi** poor excuse for inability to fix, or just simple unconcern for this bug that plagues the simulation since beta (!) If I only knew that it has game-breaking bug, I would have never... P.S. Oh, I didn't change anything in the replay track. I didn't touch any button, nor did I move camera.
Recommended Posts