[1.12.x] Kerbal Alarm Clock v3.13.0.0 (April 10)

[THX1138]

I think I'm experiencing a bug related to Kerbal Alarm Clock 3.7.0.0

In the screenshot you can see disparity between the time until periapsis and the time until the maneuver node. You also see that the fast forward arrows from the maneuver node are some distance along the blue orbit line. I vaguely remember that this was a bug Kerbal Alarm Clock had a long time ago.

[TriggerAu]

16 hours ago, THX1138 said:

I think I'm experiencing a bug related to Kerbal Alarm Clock 3.7.0.0

In the screenshot you can see disparity between the time until periapsis and the time until the maneuver node. You also see that the fast forward arrows from the maneuver node are some distance along the blue orbit line. I vaguely remember that this was a bug Kerbal Alarm Clock had a long time ago.

Mind sharing a save file showing that if you can - will saveme time getting stuff into position

[THX1138]

45 minutes ago, TriggerAu said:

Mind sharing a save file showing that if you can - will saveme time getting stuff into position

https://www.dropbox.com/s/kyqy6w84v6hsrwj/Init moho transfer.sfs?dl=0

The save file can be downloaded using the link above. After loading the save, click the fastforward symbol to trigger the bug. The bug also materialises if you warp to a point on the blue orbit line that is close to the maneuverve node.

[TriggerAu]

K, thats totally weirding me out, if you change the warp level quick enough it seems to bork something with the maneuver node timing - the node graphically stays where it is, but the time value gets messed up. Just trying a totally un KAC version here to see if I can repro it there as well. is weird

[TriggerAu]

not sure where to go with this one - I cant repro that with anything but that save file, and if that save file is loaded in a pure stock version of KSP the problem still occurs. When the warp values increases too quickly the man node time value is borked - as if the orbit is shorter all of a sudden. Running without KAC, binning the man nodes and making new ones, all seems to do that, but only if I start in that save file.

Will have a bit more of a ponder and look at whats in the save

 

 

[THX1138]

44 minutes ago, TriggerAu said:

not sure where to go with this one - I cant repro that with anything but that save file, and if that save file is loaded in a pure stock version of KSP the problem still occurs. When the warp values increases too quickly the man node time value is borked - as if the orbit is shorter all of a sudden. Running without KAC, binning the man nodes and making new ones, all seems to do that, but only if I start in that save file.

Will have a bit more of a ponder and look at whats in the save

Okay, thanks for looking at it anyway! I can let you know if it happens again. I haven't had it happen since then.

Edited June 26, 2016 by THX1138

[TriggerAu]

20 minutes ago, THX1138 said:

Okay, thanks for looking at it anyway! I can let you know if it happens again. I haven't had it happen since then.

Ah K, yeah do let me know - I'm not sure if its KAC or not, but if its a more than once thing can dig deeper. Thanks again

[Violent Jeb]

Thank you for this mod!

[JWag]

One spurious NRE with KAC:

[WRN 14:26:22.460] [HighLogic]: =========================== Scene Change : From TRACKSTATION to FLIGHT (Async) =====================
[LOG 14:26:22.461] 6/27/2016 2:26:22 PM,KerbalAlarmClock,Scene Change from 'TRACKSTATION' to 'FLIGHT'
[LOG 14:26:22.462] 6/27/2016 2:26:22 PM,KerbalAlarmClock,Active Vessel unreadable - resetting inqueue flag
[EXC 14:26:22.474] NullReferenceException: Object reference not set to an instance of an object
	KerbalAlarmClock.KerbalAlarmClock.UpdateDetails ()
	KerbalAlarmClock.KerbalAlarmClock.RepeatingWorker ()
	KSPPluginFramework.MonoBehaviourExtended.RepeatingWorkerWrapper ()
[LOG 14:26:22.480] 6/27/2016 2:26:22 PM,KerbalAlarmClock,Removing DrawGUI from PostRender Queue

Win 7 Pro x64, KSP 1.1.3 64-bit (Steam)

Logs, persistent file and list of mods here. There are only a couple part mods; the rest are usability.

[Thanny]

In KAC 3.7.1.0 with KSP 1.1.3, the maneuver alarms don't seem to be working correctly.

In the options, under maneuver node specifics, the default margin time seems to be ignored.  Adding a manual maneuver node uses the default alarm margin.  It does, however, add the half burn time correctly. 

When adding a fast maneuver node, in contrast, the configured margin is correct, but the half burn time is not added.  This despite the fact that the time displayed on the flyout menu is correct.  For example, with the margin set to 10s, and a maneuver with a half burn time of 6s, the flyout menu shows 16s, but the alarm actually added is only 10s.

The they have inverse problems - one ignores the margin setting, but doesn't ignore the burn time setting, while the other respects the margin setting, but doesn't respect the burn time setting.

I hope I've made that clear enough.

 

[THX1138]

Is it possible to set KAC so that the alarm sound is on by default when creating a new alarm?

[DarthXavius]

On 6/21/2016 at 8:35 PM, Wcmille said:

Version:

I have this error in KSP 1.1.3. Running Windows 10, 32-bit.

Problem:

KAC Window appear corrupted.

Steps to Reproduce:

Create new game, or load existing saved game.

Mods:

I have these mods installed, but the problem will reproduce for me with only KAC installed.

• Kerbal Engineer
• Final Frontier
• PreciseNode
• RCSBuildAid
• KAC
• TransferWindowPlanner

My log looks similar to the above.

Getting this same issue, tried following this thread for a solution, but seems there are multiple conversations going on about different bugs and no information on what bug is being discussed. It looks like there hasn't been a fix posted yet for this though, but if I am wrong please point me in the right direction. Thanks for any help.

[Wcmille]

19 hours ago, DarthXavius said:

Getting this same issue, tried following this thread for a solution, but seems there are multiple conversations going on about different bugs and no information on what bug is being discussed. It looks like there hasn't been a fix posted yet for this though, but if I am wrong please point me in the right direction. Thanks for any help.

Latest release fixed my problem.

[Frameshift]

12 hours ago, Wcmille said:

Latest release fixed my problem.

I'm still getting the issue the above posters mentioned,  even after upgrading to the current KAC version. 

[iamthesnee]

I am still getting this error with the latest version. It occurs on 32bit and 64 bit, and even when KAC is the only mod installed.

 

[Bran31]

I'm also getting the bug mentioned above by @Wcmille. The latest version has not changed anything for it.

[-dbv-]

Same here, First, I thought this was caused by the mods I installed this day, but even on a clean this mod doesn't work anymore.

[EddieKerbal]

I copied all the files to the GameData dir as instructed but the Mod isn't loading. I'm using version 1.0.2.842 of the game and v. 3.7.1.0 of the mod on a Win 8.1 system. Any suggestions?

[Merkov]

33 minutes ago, EddieKerbal said:

I copied all the files to the GameData dir as instructed but the Mod isn't loading. I'm using version 1.0.2.842 of the game and v. 3.7.1.0 of the mod on a Win 8.1 system. Any suggestions?

Wait, you're using KSP 1.0.2? I don't think the most recent versions of KAC will work on that version of KSP. 1.0.2 was before the Unity version upgrade in 1.1. From the version history notes, it looks like KAC version 3.3.2.1 was the last version of KAC that was built for KSP 1.0.2. KAC 3.4.0 and 3.5.0 (built for KSP 1.0.4 and 1.0.5 respectively) MAY work, since those were at least before the 1.1 update. You should be able to find these versions on the Github page.

[EddieKerbal]

5 minutes ago, Merkov said:

Wait, you're using KSP 1.0.2? I don't think the most recent versions of KAC will work on that version of KSP. 1.0.2 was before the Unity version upgrade in 1.1. From the version history notes, it looks like KAC version 3.3.2.1 was the last version of KAC that was built for KSP 1.0.2. KAC 3.4.0 and 3.5.0 (built for KSP 1.0.4 and 1.0.5 respectively) MAY work, since those were at least before the 1.1 update. You should be able to find these versions on the Github page.

Yea, I figured that out and got it working  Thanks.

[Luovahulluus]

I have the same bug as Wcmille. KSP 1.1.2 with lots of mods, latest KAC from CKAN, Windows 10, 64-bit.

[davidpsummers]

On 6/30/2016 at 1:18 PM, DarthXavius said:

Getting this same issue, tried following this thread for a solution, but seems there are multiple conversations going on about different bugs and no information on what bug is being discussed. It looks like there hasn't been a fix posted yet for this though, but if I am wrong please point me in the right direction. Thanks for any help.

I had the same problem as in Wcmile's picture.  I started when I upgraded to KSP 1.1.3, and upgrading KAC to the latest version fixed it...

[Sma]

I'm also having the corrupted KAC window problem after upgrading to KSP 1.1.3. I'm using CKAN and it did show an update for KAC. It says installed version is 3.6.1.0 but latest version is 3.5.0.0. I haven't tried it today, but did last night after updating KAC via CKAN and it was still messed up.

[Gryphon]

3 hours ago, Sma said:

I'm also having the corrupted KAC window problem after upgrading to KSP 1.1.3. I'm using CKAN and it did show an update for KAC. It says installed version is 3.6.1.0 but latest version is 3.5.0.0. I haven't tried it today, but did last night after updating KAC via CKAN and it was still messed up.

Are you sure you meant 3.5.0.0? The latest version of KAC for KSP 1.1.3 is 3.7.1.0

 

 

[Sma]

4 minutes ago, Gryphon said:

Are you sure you meant 3.5.0.0? The latest version of KAC for KSP 1.1.3 is 3.7.1.0

 

 

Yep, latest version column in CKAN says 3.5.0.0. I did just download 3.7.1.0 from git and that one works.