Disable save track feature

[daemon1808]

Saving the flight in "real time" feature is very bugged. Most of the time, when you replay the track, things happen that don't happen during the game (been killed when and where you weren't, crash onto the ground, etc)

 

So, for me this feature is useless 90% of the times. Why having processes consuming CPU every time you fly, when most of the times you will not save the track in the end?

And, as bugged as it is, this is more true. When you need to record some achivement or for trying to understand what happens during the flight, it is useless too. So, what is the point of having this process running yes or yes?

 

Will it be possible in future releases to have a "checkbox" in the settings to remove/allow this option?. I mean, to remove/activate the process that is saving the flight in real time into memory.

I don't know if the performance of the game will be affected by far, but surely to eliminate these processes will be not harmful. Every MHz or FPS gained will be welcome.

[Tholozor]

Put

disable_write_track = true

in your autoexec.cfg.

[Gryzor]

Put

disable_write_track = true

in your autoexec.cfg.

 

This not disable track data saving during mission, so CPU cycles are the same (with or without). Only prevents save the file at the end of the mission.

[Hawkeye_UK]

I first reported this about 3/4 weeks ago and for me in VR it has helped the smoothness in MP. I also go from (if on large MP sessions with alot of CA) 200mb track files to 1mb, thus reducing the requirement to constantly delete.

 

I would only take this out of my autoexec file if wanted to record for testing failures,

[Bozon]

Put

disable_write_track = true

in your autoexec.cfg.

 

I first reported this about 3/4 weeks ago and for me in VR it has helped the smoothness in MP. I also go from (if on large MP sessions with alot of CA) 200mb track files to 1mb, thus reducing the requirement to constantly delete.

 

I would only take this out of my autoexec file if wanted to record for testing failures,

So this does not reduce CPU load, but does reduce HD workload? May help my system a bit. Thanks.

[daemon1808]

Put

disable_write_track = true

in your autoexec.cfg.

 

 

But the point should be disable the "live" process, not the action of saving at the end of the flight. The idea is to reduce the load on the CPU during the game (as well as the time spent saving is a waste of time, even in the RAM, if at the end of the day you don't want to save a track)

 

Thanks for the tip, anyway!

[Gryzor]

Yes. I hope some option just, not tracking but in live process (maybe it could gain a small percentage of fps). I remember many years - 2004 - ago that in LockOn we had that option: we have a key to start saving the track, into mission (a small fps hit happened, just when tracking started).

[discwalker]

Save track feature is harmful to your SSD, because continually updating more .bin files in DCS temp folder during your missions. (Not recorded to RAM.)

Only after the mission ending compile the hundred megabytes big .bin files to your LastMissionTrack.trk for single player (.zip-ed) that can you save as other name.

In my installation NTFS folder junction point DCS temp folder to HDD.

[daemon1808]

Save track feature is harmful to your SSD, because continually updating more .bin files in DCS temp folder during your missions. (Not recorded to RAM.)

Only after the mission ending compile the hundred megabytes big .bin files to your LastMissionTrack.trk for single player (.zip-ed) that can you save as other name.

In my installation NTFS folder junction point DCS temp folder to HDD.

 

 

That's even worse! if it's continuously saving in the hard disk, the process should be slower and more time consuming.

 

Where is the DCS temp folder?

[discwalker]

C:\Users\uname\AppData\Local\Temp\DCS

C:\Users\uname\AppData\Local\Temp\DCS.openbeta\

 

don't afraid from zero bytes long .bin files, if DCS runs those are growing;

to examine real state kill DCS process in mid a long mission

 

I use track recording for only when I directly report a bug.

Edited April 29, 2020 by discwalker

[daemon1808]

thanks

[Rookie1983]

Check the "DCSWorld/Config/ModelTimer/ModelTimer.lua"

[Gryzor]

Check the "DCSWorld/Config/ModelTimer/ModelTimer.lua"

 

Why? Is it possible to disable traking by editing that file?

[Rookie1983]

Use Notepad++ to open ModelTimer.lua

 

Find the following lines :

 

"TraceCommandsDiscreteOn = true"

"TraceCommandsAnalogOn = true"

I never tried it myself, but I believe that if you disable this commands ( "false" instead "true"), DCS World would no longer track and record your inputs commands during the flight. Which would definitely increase your FPS.

If it's works, please let me know. I'm kinda curious myself...

[daemon1808]

Nope, it doesn't work at all. Even with those to variables set to false, after the flight you can replay the gameplay. So its obvious that the process is still saving the inputs.