No FCR returns in-game, but the track replay shows otherwise

[Floyd1212]

I was complaining in another thread about not getting any radar returns for groups that are clearly right in front of me (often shooting at me), so I recorded a video and saved the track to post as a bug report.  However, when I replayed the track, there were times when I was getting returns in the track when I wasn't getting returns at the time in-game.

Here is a screenshot of what I was seeing in game, as captured by my video.

But here is what I see when I playback the track file.

The first thing you might notice is that the MPDs are displaying completely different things.  This may be part of the problem, though really it shouldn't be.

I use external touchscreen monitors in front of me running Helios to interact with them, and for some reason the track recording system does not register button presses I make through Helios.  It does in real-time while I'm flying around, but what you see during the track replay is totally out of sync.

But even when the displays don't match, every time I press the single-burst scan button, I see the white sweep back and forth.  Why would returns not show up on my displays in game, but then show up in the track replay?  At one point in the video, I am running in on the enemy units that are shooting at me, and still not getting any returns.

Here is the track and video file.

FCR Test.trk

https://youtu.be/REv8tLs6h5Y

EDIT:  I should also point out that the original reason I was making the video/track was because I couldn't get any returns while perched on top of that hill.  They are clearly within range and unobstructed by trees, so is it the look-down angle from up there?  Is the radar not designed to scan low like that?

And before you ask, yes, I manually adjusted the radar elevation to the lowest setting to look down, but you don't see me doing that in the track, just the video.

Edited December 20, 2023 by Floyd1212

[Fakum]

I dont have an answer for you but i will tell you that I ran into the same issue yesterday, but figured out it was a MOD I was using to make the Apache HMD Yellow instead of the default green was causing the same result. I wound up disabling all of my MODS to find that out. Im only mentioning it because, if I read this correctly, your using Helios. If that is correct, I suspect there is a reasonable expectation that may be the issue.

[Dangerzone]

1 hour ago, Floyd1212 said:

I use external touchscreen monitors in front of me running Helios to interact with them, and for some reason the track recording system does not register button presses I make through Helios.  It does in real-time while I'm flying around, but what you see during the track replay is totally out of sync.

But even when the displays don't match, every time I press the single-burst scan button, I see the white sweep back and forth.  Why would returns not show up on my displays in game, but then show up in the track replay?  At one point in the video, I am running in on the enemy units that are shooting at me, and still not getting any returns.

In regards to things operating differently in track replay - I'd suggest you're suffering from the same issue that we suffer from with VAICOM. DCS does not record any external inputs (DCS BIOS, etc) into the track file. As such, when recording track files, you'll need to not use external peripherals, or any mods (by mods, I'm including DCS BIOS, Helios, and VAICOM that integrates with DCS via hooks) to command your aircraft (or coms, etc) - and use only 'vanilla' DCS options such as bound joystick controls, keyboard, or mouse.

Given what Fakum says above with mods being an issue at present with FCR returns, it might be worth redoing another new track file with Helios (and other mods) disabled and see if you get the same problems, or if this resolves the issue. If you get the same problems, at least you'd get a replayable track file that replicates what you have.

[ruiner_]

2 hours ago, Dangerzone said:

Given what Fakum says above with mods being an issue at present with FCR returns, it might be worth redoing another new track file with Helios (and other mods) disabled and see if you get the same problems, or if this resolves the issue. If you get the same problems, at least you'd get a replayable track file that replicates what you have.

I think saying it is caused by mods based off of one person's account of it working one time without a mod is a bit anecdotal.

[Dangerzone]

1 hour ago, ruiner_ said:

I think saying it is caused by mods based off of one person's account of it working one time without a mod is a bit anecdotal.

No - I'm saying that the track replay issue is most likely a mod, as I have experienced this myself, as have numerous others. Hence my suggestion to try again with the mods disabled. That way, the track file will record correctly and will remove one already known variable from the equation .

[ruiner_]

But that's not what you said. 

Quote

Given what Fakum says above with mods being an issue at present with FCR returns

 

[BIGNEWY]

please remove all unofficial mods if any run a repair or verify of DCS

try to repeat the issue, if you still can attach the track and the dcs log from the same session so we can look for clues. 

If you export to helios or a second screen please try without first

thank you