Jump to content

Recommended Posts

Posted

So I decided to load up an Instant Action mission and give it a go solo. First of the 5 options. I start, I tell me Wingman to RTB at the beginning over the UHF. Then I spend the next 20-something minutes completing the mission myself, and I did quite good actually. All my bombs landed on target, didn't get a scratch on my hog.

 

So I decided I would load up FRAPS and take a video. Go to replays, watch the track, record from the start.

 

So the video does exactly as I did most of the way. Gunned the transports, missiled the infantry, blah blah, here comes the Bridge. Maverick away, hits the ZSU-23-4. Here comes the bridge, JDAM is ready, release authorized...

 

...

 

...the bomb doesn't release. I DID release it at that point, when I actually had played the mission, but not here, I sail over it. And then the next 10 minutes is my aircraft wandering around the skies, still under control, but doing nothing that I remember, almost as if controlled by a ghost. Then it crashes into the ground.

 

So, what the **** just happened? Does it have to do with me using the time acceleration controls (+LShift/Alt/Ctrl + Z)

Posted (edited)

The Replay has its bugs and limitations before it bugs out. Doing anything switching views from the original screws it up.

 

Best thing to do is small missions it bugs alot on long flights.

 

Its been this way ever since lockon sometimes the AI do not replicate your flight.

Edited by aceflier
Posted

So, what the **** just happened? Does it have to do with me using the time acceleration controls (+LShift/Alt/Ctrl + Z)

 

This is a known issue although the exact cause is not, AFAIK. Messing with time seems to be one of the possible issues. Also view changes seem to sometimes be the cause.:huh:

 

There are a few threads about the problem but I don't think the exact cause, or a solution, has been found.

 

I have not messed with the replays since 0.9 but what happened to you is exactly what others have seen prior to the patch.

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

or maybe you're losing your grip on reality and you're actually a really terrible pilot.

i7 8700K @ 4.4Ghz, 16G 3200 RAM, Nvidia 1080Ti, T16000 HOTAS, TIR5, 75" DLP Monitor

Posted

Watched the track again.

 

The ghost-JDAM from before actually dropped and hit its mark. 2 Mavericks and a GBU-12 hit its mark before it all went down the shitter again. Aircraft has a brain fart, then it dives at the ground firing cannons and crashes.

 

Watched it again. It followed my inputs an extra 5 minutes. Is there a possible explanation?

Posted

The explaination is that ED are using an utterly ineffective method of creating recordings of missions. It needs to be thrown out and rebuilt in a manner which works. There are a dozen hazily-proven methods for ensuring track integrity, from ensuring the DCS window doesn't lose focus when recording the track, to not switching views whilst replaying one. The only constant seems to be that the longer a track runs for, the lower the chance of it being accurate.

Posted
The explaination is that ED are using an utterly ineffective method of creating recordings of missions. It needs to be thrown out and rebuilt in a manner which works. There are a dozen hazily-proven methods for ensuring track integrity, from ensuring the DCS window doesn't lose focus when recording the track, to not switching views whilst replaying one. The only constant seems to be that the longer a track runs for, the lower the chance of it being accurate.

 

That's a bit strong.

There is an ingame avi recording tool. Search forums should find posts about it. :)

i5 8600k@5.2Ghz, Asus Prime A Z370, 32Gb DDR4 3000, GTX1080 SC, Oculus Rift CV1, Modded TM Warthog Modded X52 Collective, Jetseat, W10 Pro 64

[sIGPIC][/sIGPIC]

Posted (edited)
So far in 0.9 my tracks have always played correctly. Now, when I use helios they are all out of wack but as long as I don't use helios they have been good.

 

I've personally noticed that as soon as my game is windowed or alt-tabbed in any way, the subsequent track WILL be dodgy.

 

I suspect HELIOS is windowing your game or doing something akin to alt-tabbing, so unfortunately your tracks will not work properly while it's running. I don't use HELIOS or any interface solution at the moment, but when I do try one I expect my tracks to become worthless.

Edited by Crescendo
Posted

I've been dealing with this a lot since I have been recording many long campaign missions using fraps (after mission completion.) I can tell you from experience with both sims that A-10C has improved over KA-50 at recording accurate tracks.

 

In KA-50 tracks, it was 50/50 shot at getting a good recording. With A-10C tracks, it's more like 75-80% success at recording. So while not perfect, it's getting better, from my experience at least.

 

One day, if multi-threading becomes reality, we might see this kind of task handed over to another thread? That would be cool.

i7-12700k, 32GB Ram, RTX 3060 12GB, TrackIR 5, Lots of SSD Space, etc etc

DCS World - All the cool modules

  • Recently Browsing   0 members

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