Jump to content

Recommended Posts

Posted

Hi.

I have made several attempts to watch a track after failing a mission on the F15 campaign. They show a totally wrong movement of the plane. They show my plane trying to take off on the grass and exploding, where in fact I took off from the runway and was flying for a while.

 

Not sure if this happens with other planes or missions.

DCS Rosetta, my automatic DCS mission and campaign translator: https://forums.eagle.ru/showthread.php?t=233877

Posted

Wath Track - record problem

 

Also 1.5 the track record don´t work correctly. it play somethink too diferent and wrong at 1.5.

 

This night...

I take off from Tbilisi in my 109 and will fly 50 min heading 284 tryng to navegate with instruments only (over montains) to sochi and landing there. After 45 min of fly and near to empty of fuel over the mountains i check the map to view my position and see how wrong i was.

I was 5 degrees wrong of planned. i aborted to try to land at Sochi goes to the cost, spot back left Gadauta and land there.

 

Was a very nice execise. I try to wath the track to view my good takeof and land.....and what i see? A crash at takeoff...hehehheh

 

Can be more wrong? I think that will be fix for sure. But I am reporting to alert if no one has done before.

Posted

Seeing the same, pretty much every track recorded in 1.5 results in a very different outcome when you watch is back to what actually happened in the flight. Almost always you crash and die after a few minutes.

  • 1 year later...
Posted

Come on ED!! I spent lots of time training to make an 10 minutes Airshow demonstration with lots of close calls and low passes to feed my youtube's channel to only discover that tracks are broken?

Well i don't know what's happening out there, but you should consider stop releasing modules and start to fix bugs.

Every update a new surprise... :(

Who cares...

Posted
Every update a new surprise... :(

 

The track problem is many things but a 'new' surprise is certainly not one of them.

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
The track problem is many things but a 'new' surprise is certainly not one of them.

 

 

No no, i'm not meaning "Track problem" as a new surprise, this have been screwed a long time, but it used to work fine lately and then update and bang, then update and work, then update and bang again.... Affs.

Who cares...

Posted

That's odd, I haven't recorded any tracks in a long time but just did so last night when I took my M2000 up to attack some ground vehicles and then dogfight a Mig-21. Played the track back and it was exactly how things went. Now I've read in the past that if you accelerate time while recording or playing back can screw things up, in addition to having a very long track can also cause issues but I was surprised how accurate this track was.

Justificus

 

System Specs:

i7 4970K @ 4.8, GTX 1080 SC, 32GB G.Skill DDR 2133,Thermaltake Level 10 Full Tower Case, Noctua NH-D15 6 Cooler, Win 10 Pro, Warthog, CH Pro Pedals, CH Throttle Quadrant, Oculus, 1 32" & 2 19" Monitors

 

 

 

Modules Owned: A-10C I+II, Ka-50, FC3, F-86, Mig-15, Mig21, UH-1H, Mi-8, CA, P-51D, BF-109K-4, FW-190 D-9, Hawk, NTTR, M-2000C, SA342, F-5E, Spit Mk. IX, AJS-37, Normandy, WWII A.P., AV-8B, F/A-18C, L-39, Persian Gulf, Mig-19P, I-16, Super Carrier, F-16, Channel, Syria

  • Recently Browsing   0 members

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