General Support Issue

[Lisias]

General Support Issue.

For things that do not deserve (at least, yet) an Issue.

[Lisias]

Fellow Kerbonaut Krazy1 reported a weird issue related to Cargo and Inventory parts, apparently affecting Illuminator Mk1.

Well, I did this a try but no dice. I could not reproduce it on a naked KSP (only with KSP-Recall and TweakScale).

KSP.log

As a matter of fact, however, I found this exception on KSP.log while exiting the game:

[LOG 06:31:49.406] [PlanetariumCamera]: Focus: Kerbin
[ERR 06:31:49.411] Exception handling event onPlanetariumTargetChange in class KnowledgeBase:System.NullReferenceException
  at (wrapper managed-to-native) UnityEngine.Component.get_gameObject(UnityEngine.Component)
  at KSP.UI.Screens.KnowledgeBase.ActivateApps (KSP.UI.Screens.KnowledgeBase+KbTargetType targetType, MapObject target) [0x0010f] in <cf1abf6b50ac49c3b967fb61a43f1e5f>:0
  at KSP.UI.Screens.KnowledgeBase.OnMapFocusChange (MapObject target) [0x000f4] in <cf1abf6b50ac49c3b967fb61a43f1e5f>:0
  at EventData`1[T].Fire (T data) [0x000b0] in <cf1abf6b50ac49c3b967fb61a43f1e5f>:0

[EXC 06:31:49.536] NullReferenceException
    KSP.UI.Screens.KnowledgeBase.ActivateApps (KSP.UI.Screens.KnowledgeBase+KbTargetType targetType, MapObject target) (at <cf1abf6b50ac49c3b967fb61a43f1e5f>:0)
    KSP.UI.Screens.KnowledgeBase.OnMapFocusChange (MapObject target) (at <cf1abf6b50ac49c3b967fb61a43f1e5f>:0)
    EventData`1[T].Fire (T data) (at <cf1abf6b50ac49c3b967fb61a43f1e5f>:0)
    UnityEngine.DebugLogHandler:LogException(Exception, Object)
    KSPe.Util.Log.UnityLogDecorator:UnityEngine.ILogHandler.LogException(Exception, Object)
    ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
    UnityEngine.Debug:LogException(Exception)
    EventData`1:Fire(MapObject)
    PlanetariumCamera:SetTarget(MapObject)
    PlanetariumCamera:OnVesselDestroy(Vessel)
    EventData`1:Fire(Vessel)
    Vessel:OnDestroy()

I failed to correlate this to Recall or TweakScale.

[Lisias]

Fellow Kerbonaut Warro have some problems with his/her installment.

Log: KSP.log.zip
Sample craft: Auto-Saved Ship.craft.zip

On a clean Test Bed (KSP 1.11.2, KSPR & TweakScale), things are working fine with KIS. KIS is not a problem. (KSP-Recall neither) at this moment:

Based on the sample craft file, the list of probable triggers for the problem appears to be:

• TAC Life Support
• SCANSat
• USITools (and, so, everything USI related)
• Wild Blue's PathFinder and Buffalo.

At this moment, there's no other solution but to carry on an Uninstall Fest, hunting for the trigger of the problem.

-- EDIT --

A new test. This time I dropped the Electric ScrewDriver on the ground before recovering.

The cost if the ScrewDriver was not recovered, what's the expected behaviour.

[Lisias]

Fellow Kerbonaut Krzesny found something weird on Baha EPL Redrilled that I found yet more weird, and so I decided to give this a look.

The described behaviour was not reproduced on KSP 1.5.1, so I ruled out a problem on the config files.

My current guess is the need to use the latest Interstellar Fuel Switch, as the one provided with the original download is too old to be used on KSP 1.11.2.

ERRATA

I used the wrong container! The Ore one works fine, it's the Expanding Rocket Parts Container the problem!

So, the guy was right. There's a problem on the Config file, his assessment of the situation was correct!

Since we are here, I gone back to the latest version released by BahamutoD and it also has the problem. I double checked the Community Resource Pack for the RocketPart resource used by this Part back to the released dated to the time used on the files of the RAR archive, and the Cost of the resource were defined since the beginning!

Well.. Apparently Krzesny detected a pretty old bug on the thing! :)

[Lisias]

Fellow Kerbonaut Krazy complained about the Refunding stunt being shown in-game:

One small annoyance - the resource display show Refunding in-game. I would be nice to hide that. If you can't in stock then maybe in Alternate Resource Panel?

Probably on KSP 1.12.2? Let's check...

Well, it's working as intended. On flight, there's no trace of the Refunding stunt, and on recovering the Refunding is displayed to the user has the chance to audit the recovered Funds.

On a hunch, perhaps on Editor Scene?

Well, nope neither. I think this is related to some 3rd party addon. Perhaps Construction?

[Lisias]

Following up the report from Krazy1, this is the list of installed Add'Ons:

• 000_ClickThroughBlocker
• 001_ToolbarControl
• 999_KSP-Recall
• BetterLoadSaveGame
• CommunityTraitIcons
• CraftManager
• DistantObject
• DMagicUtilities
• EasyBoard
• EasyVesselSwitch
• EditorExtensionsRedux
• FillItUp
• FShangarExtender
• ImprovedChaseCamera
• KerbalEngineer
• ksp-advanced-flybywire
• KXAPI
• PlanningNode
• PortraitStats
• QuickMods
• SimpleFuelSwitch
• SmartDockingAid
• SN1006-Unedited-Skybox
• SpaceTuxLibrary
• Stock folder: Squad
• Stock folder: SquadExpansion
• TacFuelBalancer
• TextureReplacer
• Trajectories
• TriggerTech
• TweakScale
• WaypointManager
• ZeroMiniAVC
• [x]_Science!

KSP.log: KSP_log.zip

[Lisias]

First results on the testings: Kerbal Engineer Redux is working fine on my rig. This is relevant because if KER is working fine on my test bed and not on the Krazy1's rig, it means that something had changed the Refunding Resource itself to make it visible - otherwise KER would not be showing it on his machine (not to mention the Stock Resources widget).

If this is happening at runtime or in a patch is now my line of research.

[Lisias]

Have ruled out some add'ons by now. No fancy testings, just load KSP, then a craft then check Resources from KER.

[Lisias]

Krazy1 outsmarted me. :) He nailed the problem.

craft.zip

The two first (beta) releases of Refunding was using the default isVisible attribute, that ends up being true. Only the third release (0.0.7.6) had it right: 71c9ea3#diff-1b10535b2f60b2efead284092829b012fa4dd93ea17b242f5025abd38e0ea9df

Oukey, manually editing the resouce's isVisible to false will solve the problem. Perhaps I should write a workaround on Refunding itself? I think this would be a little hostile, as someone could have a good reason to make this visible in the future...