Jump to content

Recommended Posts

Posted

I made today a flight with the Mi-8 and the MiG-21 on the Nevada VA-Server in 2.1 .

 

And for the first time since a very very very long time ...

The replay of this very .trk worked perfectly!

I could watch it in F2 view. I could speed things up and go back to normal. And both aircrafts followed the exact flight.

(And didnt end up completly elsewhere ... )

 

Even my cat says : Purrrrrfect!

Thanks ED! :-D

 

P.S. And i realy dont mind that deferred shading plus PBR needs tweaks ... at some places, if the sun is right, i ended up like this :

59574-wing-commander-sega-cd-screenshot-horrible-burning-death.png

 

;-)

Posted

I hate to say it, but that must just be luck. I can't imagine that if ED had made major changes to the track replay function, that they would not have mentioned it in the change log.

 

But, I would love to be wrong. :)

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:

Posted (edited)

Maybe ... but in the last (i dont know ... years) every track, realy every single one go wrong if i tried to play it back. (While my very own tracks would replay perfectly on a colleagues PC).

 

And those track failed to replay correctly in the very first seconds. One example, my spits doesnt even taxi correct in replay.

 

To replay succesfully a track for a flight period of somewhat more than an hour ... completly correct ... with slot changements and everything ...

THAT would be really "massive luck"! ;-) ... you get the gist ... ^^

 

Okey ... one minor "misstake" was there in the track-replay. The Mi-8 "forgot" the "LSHIFT-W" (wheel hand brake). But thats it.

 

Im on your side, such things should be "tested" thoroughly. Nevertheless, i was so excited after that successful replay..... ;-)

 

EDIT : Forgot to mention ... i freshly installed DCS2 at wednesday. Such 3rd-Party things which hook into dcs like Tacview are not installed at the moment.

Edited by Wunderwolf
Posted

I haven't finished downloading 2.1 yet. But, the tracks for 1.5.6 still won't work. It's really frustrating since I use the tracks to help me figure out where I go wrong on a mission or why my landing gear for the Mig-21 breaks on landing.

Modules:

Owned:

P-51D, F/A-18C, AJS-37, NTTR, F-5E, M-2000C, Bf 109, Fw 190 D-9, F-86F, Mig-15Bis, A-10C, Combined Arms, Mi-8Mtv2, UH-1H, Black Shark 2, Mig-21Bis, FC3, F-14A/B, Mig-19, Spitfire, JF-17, Persian Gulf

 

Would Like to See:

Mig-29K, Su-24, Mig-25, J-8II, J-10 , Tornado

 

__________________

Specifications:

Windows 10 64Bit, i7-7700K 4.2Ghz, GTX 1080, 16Gb RAM, T.flight Stick X

Posted

I learned a little about trk's screwing up.

 

I had saved a trk of a friend and I flying aerobatics and it worked perfectly. I later re-calibrated my joystick and edited axis in DCS and the plane won't make it to the runway, it instead makes a wide turn and gets stuck in the grass (when I replay the trk).

 

The trk could not work the rudders properly due to the different calibration and L-39 brakes did not work correctly.

Posted

Tracks are not working correctly. I watched a Track of my first flight over Normandy, and unfortunately I see the same issues as prior to the latest patch.

Posted
Tracks are not working correctly. I watched a Track of my first flight over Normandy, and unfortunately I see the same issues as prior to the latest patch.

 

Can you elaborate a little bit more ... was it a fresh install of DCS 2?

Have you something tied in something in the export.lua? (Simpit ... tacview ... DCS-SimpleRadio) ...

Posted

Saw the thread and watched a track as soon as the flight was over. Got hit by an Igla and flew home wounded. That did not happen in the track. It missed and everything was good. The track was close but not a replica. Can't exactly use it as a replay. It helped me see what happened sorta.

Posted
... The track was close but not a replica. Can't exactly use it as a replay. It helped me see what happened sorta.

 

Okey so ... its not fixed at all ... but it seems that it got "somewhat" better!? :-)

 

I've to admit ... since i was on the VA server, i did not have any sort of "engagement".

Just flying. But again, even simple flight input was always messed up on my replays.

 

Lets hope it will be fixed some day completly ,once and for all. :-)

Posted
Can you elaborate a little bit more ... was it a fresh install of DCS 2?

Have you something tied in something in the export.lua? (Simpit ... tacview ... DCS-SimpleRadio) ...

 

The Track replay shows my airplane lining up on the grass rather than on the runway for takeoff. During the takeoff roll in the Track my plane ran into a hangar, and of course, crashed and burned. When I was flying the actual mission, I made a successful takeoff., believe it or not (Spitfire).

Posted

I noticed that the track replay works great for some aircraft, but not for others. The Viggen and Mig21 are the worst for me. Viggen rarely makes it to the runway after cold start replay, but instead runs into hangars, gets stuck in the crops or god knows where. It's not even close to the correct path.

 

Mirage, Huey, Mi-8, Ka-50 no issues whatsoever.

This is true for 1.5.6, 2.0.5 and now 2.1.0 equally. YMMV

 

Given that track replay issues have been ongoing for many years, is there any realistic hope that it will eventually be fixed? I find tracks really useful to review own mistakes and learn from them.

My humble rig: Windows 10 pro 64bit; i7-6700k on Gigabyte Z170X G7; 32GB; MSI 980ti Twin Frozr; 512GB Samsung 950 Pro (NVMe/PCIe x4); 1TB Samsung 850 Pro; Komplete Audio 6; TrackIR 5 Pro;

DCS 2.5 with almost all modules; favourites: Shark, Mi-8, Harrier, Viggen, Mirage, Hornet

Posted

Still hoping we get the option to disable track replay recording for troubleshooting purposes, at or before 2.5 optimally.

 

I seriously need this option to eliminate one of the factors/variables, even if it's not the culprit.

Modules: A-10C I/II, F/A-18C, Mig-21Bis, M-2000C, AJS-37, Spitfire LF Mk. IX, P-47, FC3, SC, CA, WW2AP, CE2. Terrains: NTTR, Normandy, Persian Gulf, Syria

 

  • 3 months later...
Posted

Sry for bumping my old thread ... but ... after there were a statement about "fixing track recording/replay" in the changelogs recently ... i gave track replay another shot.

 

Just replayed some BF (nevada coldwar 2.1) sorties. It replays perfectly fine and according to memory/tacview.

 

So ... Yay?! :D

 

Does someone else did some more tests? Maybe someone who got more bad then good replay results in the past?

Posted

Nah, still depends on plane & mission combo. Some tracks are reliable, as they were, some aren't, as they weren't :).

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Posted

I tried both saved track and instant track with the Bf-109 yesterday, and it was a complete disaster. In the latest version of 1.5: 1.5.7.9459

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted

We made one Epsom mission together (friend of mine and myself) at wednesday. (So its 2.1)

In both Tracks the local machine goes nuts. Were the one recived from MP was perfectly fine.

 

So in my collegues replay my machine was ok and his was wrong. And in my replay it was vice versa.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...