Charlie-1 Posted February 24, 2020 Author Share Posted February 24, 2020 If the DCS is on another SSD, track write shouldn't be the problem because it's writing to the OS SSD. I just came independently across one side of this thing thing, I'm doing vairous bug hunting and this is the next report I'll be posting today, but it probably is not limited to 2.5.6, it's a general thing with memory/disk/terrain loading. I think I mentioned in this thread I'm actually experiencing the stutter problem in 2.5.5 and back in 2.5.3 also installed to use the Hawk. Luckily I'm not too bothered about track record as that doesnt work reliably either! :( Intel Core i3 8350K 4GHz, MSI RTX 2080 Super, AS Rock Z370 Pro4 Motherboard, Samsung SSD, 32G DDR4 RAM, Windows 10 PRO 64 Bit Rift-S, Tripple Samsung 27" C27F Display, Hotas Warthog, Saitek Pro Flight rudder pedals, EDtracker, Track IR. Link to comment Share on other sites More sharing options...
TOViper Posted February 25, 2020 Share Posted February 25, 2020 (edited) Update - After many hours studying the Resource monitor it seems the culprit is DSC's own track recording. I have now set Tackview to false in the Options file and added an autoexec.cfg with "disable_write_track = true" and so far so good!:doh: Hi Nake! unfortunately this strategy has several nasty side effects on my machine when using an autoexec.cfg. This includes difficulties with GUI menus not showing up, and problems when creating multiplayer games. It seems the autoexec.cfg is killing a few things here. Where is this option disable_write_track = true normally placed? Is it normally located somewhere within the options.lua? Thanks Edit: also when choosing "Fly again" after playing a single mission the cockpit (in this case the Viggen) is totally weird. Edited February 25, 2020 by TOViper Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1 Link to comment Share on other sites More sharing options...
Charlie-1 Posted February 26, 2020 Author Share Posted February 26, 2020 Hi Nake! unfortunately this strategy has several nasty side effects on my machine when using an autoexec.cfg. This includes difficulties with GUI menus not showing up, and problems when creating multiplayer games. It seems the autoexec.cfg is killing a few things here. Where is this option disable_write_track = true normally placed? Is it normally located somewhere within the options.lua? Thanks Edit: also when choosing "Fly again" after playing a single mission the cockpit (in this case the Viggen) is totally weird. I created a simple text file called autoexec.cfg and placed it in the same saved games Config folder where the Options.lua is. I have not noticed any adverse effects yet.:thumbup: Intel Core i3 8350K 4GHz, MSI RTX 2080 Super, AS Rock Z370 Pro4 Motherboard, Samsung SSD, 32G DDR4 RAM, Windows 10 PRO 64 Bit Rift-S, Tripple Samsung 27" C27F Display, Hotas Warthog, Saitek Pro Flight rudder pedals, EDtracker, Track IR. Link to comment Share on other sites More sharing options...
TOViper Posted February 26, 2020 Share Posted February 26, 2020 I created a simple text file called autoexec.cfg and placed it in the same saved games Config folder where the Options.lua is. I have not noticed any adverse effects yet.:thumbup: I got it sorted out, had a wrong encoding on my autoexec.cfg (was "UTF-8 BOM" instead of "UTF-8"). Now it works, but I didn't notice any difference, because in multiplayer it is still creating the TRK file. In SP it seems it is not creating a TRK file anymore, which is good. Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1 Link to comment Share on other sites More sharing options...
Worrazen Posted February 27, 2020 Share Posted February 27, 2020 According to my findings, it's not he track file, but I'm not saying I have found the only thing, there's many things going on. Modules: A-10C I/II, F/A-18C, Mig-21Bis, M-2000C, AJS-37, Spitfire LF Mk. IX, P-47, FC3, SC, CA, WW2AP, CE2. Terrains: NTTR, Normandy, Persian Gulf, Syria Link to comment Share on other sites More sharing options...
Recommended Posts