Jump to content

Recommended Posts

Posted

When creating a thread for a bug, I get asked for the track file. That makes sense, except that 4 times out of 5, tracks are broken, and don't actually replay what happened. Taildraggers take off (if they even make it) in the wrong direction, then crash. Aircraft crash when they didn't. Getting hit by that cannon cut your wing clean off before, but in the replay, you keep flying. What is the point?

Hardware: T-50 Mongoose, VKB STECS, Saitek 3 Throttle Quadrant, Homemade 32-function Leo Bodnar Button Box, MFG Crosswind Pedals Oculus Rift S

System Specs: MSI MPG X570 GAMING PLUS, RTX 4090, Ryzen 7 7800X3D, 32GB DDR5-3600, Samsung 990 PRO

Modules: AH-64D, Ka-50, Mi-8MTV2, F-16C, F-15E, F/A-18C, F-14B, F-5E, P-51D, Spitfire Mk LF Mk. IXc, Bf-109K-4, Fw-190A-8

Maps: Normandy, Nevada, Persian Gulf, Syria, Germany

 

Posted

Great to know that the devs even can make use of a track that doesn't play correctly. I always thought they had to be alright.

 

Well, it basically is a record of all the inputs made, so they can track down every single button press etc we did.

 

But in general, if it's something we can reproduce, it's always a good idea to make short tracks of just that instead of hoofing in a 4 hour online session with roughly estimated time codes rdlaugh.png

dcsdashie-hb-ed.jpg

 

  • Recently Browsing   0 members

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