1.2.x how to watch the ingame config?

[Skalou]

Hi,

in older KSP version ( 1.1.3), there was a way to look at the part.cfg in-game with the Alt+F12 menu, but i don't know how to do it in 1.2, i can just display the part list:

KSP v1.1.2

KSP v1.2.0

Am i missing something?

I ask this because with module manager affecting the .cfg, i would like to be sure of what is done in-game,  maybe there is a way to display it with module manager itself?

thank's

 

[InsaneDruid]

I would like to know this, too.

[Eleusis La Arwall]

IDK anything for ingame but the ModuleManager.ConfigCache located in GameData lists all part-configs with applied MM-patches.

[tg626]

I think under debugging is a button to dump the database to a file.  I'm not a fan.

[Skalou]

7 hours ago, Eleusis La Arwall said:

IDK anything for ingame but the ModuleManager.ConfigCache located in GameData lists all part-configs with applied MM-patches.

thank you! didn't know we can read it with a text program , that does the job! even if i find it was easier in 1.1.3)

1 hour ago, tg626 said:

I think under debugging is a button to dump the database to a file.  I'm not a fan.

there is a "immediatly flush log file to disk" but i don't unserstand what it does.

Edited November 3, 2016 by Skalou

[Shadowmage]

19 hours ago, Skalou said:

thank you! didn't know we can read it with a text program , that does the job! even if i find it was easier in 1.1.3)

there is a "immediatly flush log file to disk" but i don't unserstand what it does.

The 'flush immediately to disk' will force the engine to do file-write operations for every line that is sent to the console, immediately as it is sent.  This is contrasted by the normal functioning of only flushing to disk every 20-40 lines or on scene changes.

It is useful in cases where a crash may occur during/immediately after something was written to console.  Without the option checked the log file may end abruptly and the error may not be logged.  If it is enabled the only time the error would not be written to the log is if it is 1.) from another thread (specifically the render thread will not log errors, only crash), or 2.) an error in the file-writing itself.

Edit:  For performance purposes it is best left off.  I would only turn it on while doing debugging and expecting crashes.

Edited November 4, 2016 by Shadowmage