Disable logging on development branch?

[SixbySix]

I am on cycle 198 on the development branch and the game has slowed to a crawl.  I have stabilized the base and want to explore the new space biome at the top of the map.  However, with all the logging going on my game has slowed to a crawl, and I have a pretty decent rig.  Anyway to disable it/tone it down a bit so the game remains playable like the stable branch?

 

-SixbySix

[Soulwind]

The logging code is most likely built in with conditional compiles, at least that's how I put in logfing code. If so then no you can't turn it off without a new compile. 

[blash365]

Having available logfiles is one of the purposes of the preview branch.

It is a nice thing for the playerbase, but first and foremost it has the objective to identify and track down bugs. Deactivating an essential tool would lead to bugs making it to the release branch, which would in turn harm us all.

 

[SharraShimada]

Its not about logging. The game is logging all the time. Its the new alpha itself. Its not optimised in any way. That happens all the time, when the introduce something new. First it has to work. Then you can optimize it. Hey, its test branch. Its not supposed to work 100% perfect.

[joeyg]

Ditto, cycle 300 and have barely explored the surface. It's fun but have to pause to issue any commands. But, a few more weeks and it'll be on the main branch. It's one of those worth sacrifices.

[Coolthulhu]

As of Cosmic, log files get a bunch of lines for every single played sound.

This was probably useful for tracking down the sound overload problem that plagued Ranching, but it kills machines with weaker HDs. The log file can easily grow a 1gb per hour of playing and literally 80% of it will be just sound-related entries.

[blash365]

10 hours ago, Coolthulhu said:

As of Cosmic, log files get a bunch of lines for every single played sound.

This was probably useful for tracking down the sound overload problem that plagued Ranching, but it kills machines with weaker HDs. The log file can easily grow a 1gb per hour of playing and literally 80% of it will be just sound-related entries.

Hm, i wasnt aware that it is so extensive. I barely notice any slowdowns and i am using a computer that is at least 5 years old and was not purchased as "cutting-edge" technology.

Maybe it is really some oddity related to slow harddrives or something, making it more noticable for some. (which is not implying that i am using a ssd)

 

[chemie]

I wish i could turn off save file compression on the regular branch.  I hate that 10 sec pause every cycle as it saves 4MB to the SSD.  I would guess the SSD could save a 40 MB in one second instead without any delay.

[jambell]

Hey folks,

Sorry about this! We updated FMOD this upgrade and this logging got unintentionally switched back on in the process. There's a fix coming in the next patch!

[BlueLance]

Thats great! I cant even make it to the surface at the moment haha

[avc15]

On 6/3/2018 at 1:00 PM, SharraShimada said:

Its not about logging. The game is logging all the time. Its the new alpha itself. Its not optimised in any way. That happens all the time, when the introduce something new. First it has to work. Then you can optimize it. Hey, its test branch. Its not supposed to work 100% perfect.

No, we've been told by the devs on several occasions that the biggest "optimization" from every preview branch to release is that they turn off debug code.

It's not a speculation. Someone can provide a link. preview branches are always slow because klei has some pretty aggressive debug code in them.

But yeah agreeing with OP here, this preview seems much worse. I was getting noticeably really bad frames before cycle 100, when my base hadn't even stabilized yet. So, staying with ranch mk2 until it releases!