Kerbal Alarm Clock not saving alarms after exiting game

[lextacy]

Kinda useless mod if its going to do that, what could be the problem?

[Master Tao]

How are you exiting? KAC 3.0+ saves alarms in the save file, so you would have to exit normally.

Also, it's completely possible that moving your saves and mods from Windows to Linux, instead of starting from Linux, is causing your problems. You really should mention that in each new thread.

Please upload your Player.log after quitting KSP normally and a complete list of mods including versions.

[lextacy]

i havnt played the windows version for a while and I just tried out kerbal alarm for first time last night. Now last night I did exit game uncleanly through the KCS sceen. Lets see if I exit this next time and it saves alarms......

[lextacy]

okay cleanly exiting game did not work, there is something wrong with the mod

[Master Tao]

Please read the How to Get Support (READ FIRST) sticky and post the requested information either here or in the KAC thread.

[lextacy]

Please read the How to Get Support (READ FIRST) sticky and post the requested information either here or in the KAC thread.

there is NO LOG FILES or any other information I can send, ive told this several times that there is no player.log file. Sorry but thats leaves the issue on the authors hands to figure out in his code its conflicting with any of squads mechanics or 3rd party plugins. Im not here to hold developers hands in solving issues with their own mods. If its their problem then its stays thier problem.

[Joshwoo70]

Ok calm down!

player.logs are in the ksp_data folder.

[Malah]

How this can be possible to have no log files If we have no information, we can't help you.

By default on Linux ".config" is a hidden folder, you can parameter your desktop environment to enable the display of hidden files. And if you're not familiar with Linux "~/.config/unity3d/Squad/Kerbal Space Program/Player.log" is "/home/YOUR_USERNAME/.config/unity3d/Squad/Kerbal Space Program/Player.log"

As Joshwoo69 has said, keep calm, the mods developers are people, they make mods on their free time, they are not forced to give mods support ... It is not their problem, it is your problem

[steve_v]

Unless you have explicitly disabled logging with the -nolog switch, there is a log file.

there is something wrong with the mod

Directly accusing one of the most respected mod authors here of writing crappy code, while providing no evidence whatsoever (i.e. logs) to back up your claim?

That's not going to work.

Nobody is under any obligation to help you, so if you want people to _volunteer_ time to solve this I suggest you ask nicely and make some effort of your own to provide the requested information.

Now, upload a log file and someone may be inclined to take a look.

Posting said logs in the KAC thread may even expedite the process

On a side note, ~/.config is a really super dumb place to put a log... er, you listening Unity?

Edited November 21, 2014 by steve_v

[TriggerAu]

Worked with lextacy to solve this one. The issue was caused by Tarsier Space Tech - which hasnt been updated in recent times. It contains a bug in the load code that kills the ScenarioModule loader for all mods that load after it.

Removing Tarsier solved the issue, and there is a pull request against the Tarsier source code that will fix the bug