allista / at_utils Goto Github PK

 Editor. When I try to add ships, nothing happens when I click on Load after I select a ship.

The good news is there is a workaround. Subassemblies load fine. Probably because you provided your own window to load them up instead of using the stock window like in loading ships.

Here are the logs...  https://www.dropbox.com/s/sgpkqeowglkmjck/log20200707.zip?dl=0

NullReferenceException: Object reference not set to an instance of an object at KSP.UI.Screens.CraftBrowserDialog.onPipelineFinished (ConfigNode n, KSP.UI.Screens.CraftEntry sItem, KSP.UI.Screens.CraftBrowserDialog+LoadType loadType) [0x0005b] in :0 at KSP.UI.Screens.CraftBrowserDialog+<>c__DisplayClass126_0.b__0 (ConfigNode n) [0x00000] in :0 at KSPUpgradePipeline.Process (ConfigNode n, System.String saveName, SaveUpgradePipeline.LoadContext loadContext, Callback1[T] onSucceed, Callback2[T,U] onFail) [0x00142] in :0 at KSP.UI.Screens.CraftBrowserDialog.pipeSelectedItem (KSP.UI.Screens.CraftEntry sItem, KSP.UI.Screens.CraftBrowserDialog+LoadType loadType) [0x00033] in :0 at KSP.UI.Screens.CraftBrowserDialog.ConfirmLoadCraft () [0x00068] in :0 at KSP.UI.Screens.CraftBrowserDialog.onButtonLoad () [0x00055] in :0

With the Hangar 3.2.1.2 hotfix, the DLL loading chokes when it gets to Hangar.dll:

ADDON BINDER: Ingoring binding redirect due to incompatible versions: 002_MultiAnimators, Version=1.1.6213.41683, Culture=neutral, PublicKeyToken=null => 002_MultiAnimators, Version=1.1.6213.35278, Culture=neutral, PublicKeyToken=null
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

ADDON BINDER: Ingoring binding redirect due to incompatible versions: 001_AnisotropicPartResizer, Version=1.2.6213.41683, Culture=neutral, PublicKeyToken=null => 001_AnisotropicPartResizer, Version=1.2.6213.35278, Culture=neutral, PublicKeyToken=null
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

AssemblyLoader: Exception loading 'Hangar': System.Reflection.ReflectionTypeLoadException: The classes in the module cannot be loaded.
  at (wrapper managed-to-native) System.Reflection.Assembly:GetTypes (bool)
  at System.Reflection.Assembly.GetTypes () [0x00000] in <filename unknown>:0 
  at AssemblyLoader.LoadAssemblies () [0x00000] in <filename unknown>:0 

The loader then chokes on all of Hangar's classes and such. The DLLs shipped with AT_Utils 1.3.1.1 are build 35278, but it looks like Hangar wants build 41683 (though I've never seen any other KSP mod so insistent about its dependencies' versions).

To allow for fully automated testing with test suites and result reports.

Just wondering when this is going to be updated. No rush, just would like to know if/when I should start building for 1.5 as my mod requires this as a dependency. Thanks!

Exception: MissingMethodException: Method not found: 'AT_utils.Utils.GLDrawPoint'.

This persists despite manual removal and reinstall via CKAN. Please advise if there is a known fix. Repeats every second if not faster.

Hello, I recently encountered a bug with KerbalJointReinforcement and Lisias came across some problems in my ksp.log (see below). I'm not quite sure which of my mods depend on AT_Utils so I can't really locate problems. Here is my mod list:

And here is my KSP.log: KSP.log
I hope this is of some value, tell me if you need anything else from me.

To reproduce with TCA

• move any of the HUD panels in flight
• close-open TCA UI by clicking on the app launcher button to trigger serialization
• quicksave to trigger serialization
• observe the changes of the saved positions in .xml file
• quickload

A switch is ON, the background is correct (depressed), but the color is for OFF

The name "BadParts" causes confusion among players who look into logs for one reason or another.

So when a part in a symmetry group is resized, its physical size is changed, and the Size gets propagated to counterparts, but their models are not updated.

This is needed mainly to make UIs for Globals to change user-related settings.

Hi Atilla!

I recently updated AT_Utils and some other mods through CKAN, and my game did not load afterwards. After some trial and error, I traced back the error to AT_Utils. For some reason it crashes KSP on startup. I can't say I'm very technical myself, but I thought you should know.

My mod list:

KSP: 1.2.2 (Win64) - Unity: 5.4.0p4 - OS: Windows 10 (10.0.0) 64bit
000_AT_Utils - 1.4.2 (<--- manually reverted back after crash)
Advanced Jet Engine - 2.8
B9 Part Switch - 1.7.1
B9 Aerospace Procedural Parts - 0.40.11
BD Animation Modules - 0.6.4.4
Camera Focus Changer - 1.0.1
Chatterer - 0.9.93.1804
Community Category Kit - 1.2.2
Community Resource Pack - 0.6.6
CommunityTechTree - 3.0.3
ConfigurableContainers - 2.4.0.5
Connected Living Space - 1.2.4.2
Contract Configurator - 1.22.2
Contract Pack: Historical Progression - 1.6
Contract Pack: Kerbal Academy - 1.1.7
Contract Pack: Bases and Stations - 3.6.1
Contract Pack: Grand Tour Contracts - 0.1.10.3
Contract Pack: Tourism Plus - 1.5.2
DangIt - 0.7.12
Deadly Reentry - 7.6.0.1
DistantObjectEnhancement - 1.8.1
Ferram Aerospace Research - 0.15.8.1
Firespitter - 7.5.1
Hangar - 3.3.1.1
HullcamVDSContinued - 0.1.6
Interstellar Fuel Switch - 2.5.1
JanitorsCloset - 0.2.20
Kerbal Attachment System - 0.6.2
Kerbal Engineer Redux - 1.1.2.8
KerbalHealth - 0.5.1
Kerbal Joint Reinforcement - 3.3.2
Kerbal Inventory System - 1.4.4
KSP-AVC Plugin - 1.1.6.2
KWRocketryRedux - 3.1.4
MagiCore - 1.2.5
ModularFlightIntegrator - 1.2.4
Docking Port Alignment Indicator - 6.5.2
NearFutureConstruction - 0.7.6
NearFutureElectrical - 0.8.7
NearFuturePropulsion - 0.8.7
NearFutureSolar - 0.7.2
NearFutureSpacecraft - 0.6.3
NRAP - 1.5.5.1
Procedural Parts - 1.2.10
RCS Build Aid - 0.9.1
RealBattery - 0.1.1.5
RealChute - 1.4.3
RealismOverhaul - 11.5
Real Scale Boosters - 0.15
RealSolarSystem - 12.0
Recovery Controller - 0.0.1
RemoteTech - 1.8.6
DeepFreeze Continued... - 0.23.4
RSSDateTime - 1.1
Saturatable RW - 1.12
SCANsat - 1.1.6.11
SETI-Greenhouse - 1.2.2
SolverEngines - 3.1
StationPartsExpansion - 0.4.3
StationScienceContinued - 2.2.1
Surface Mounted Stock-Alike Lights for Self-Illumination - 1.3.1
TAC Life Support - 0.13
Kerbal Alarm Clock - 3.8.4
TweakScale - 2.3.4
Universal Storage - 1.3.0.1
VenStockRevamp - 1.9.5
KSP Interstellar Extended - 1.13.10

Also see attached error log.

Let me know if you need any other info!

Cheers,

output_log.txt
error.txt

During my stream last night, we found that the actual broken bit was the AT_Utils, not GC, GC Core or CC.

I was told that you said to revert the mods, but in CKAN, you have to revert AT_Utils as well since it is installed seperately.

"The currently installed version of 000_AT_Utils was built to run KSP 1.6.1 - 1.7.2 with Steam version 1.7.3.2594."
Can you update the mod for the "new" version ?
I think there is no real compatibility issue here, right ?
thanks

Though one can change the color of buttons through 000_AT_Utils.user file (copy its content from the .glob file, then change as you please), it's not a user-friendly approach, and it doesn't change many other colored things, like status strings, etc.
What we need is something like a localization system that will automatically apply a color scheme via some placeholders. But that's a damn lot of work, and I don't even know where to start. It has to be a core framework, and it has to have a UI on its own...

Colorblind TCA user here.
It seems that no matter what colors I set in 000_AT_Utils.glob or .user, the changes are always the default ones.
Reverting to 1.6.3/3.5.3.2 in the meantime.

The damper works just fine with physics, but does nothing when in HIGH mode time warp. This makes it a lot less usable that it could be.

As a result of the upgrade to the current version of Unity, some previously acceptable coding practices are now causing hidden errors, which eventually cause the game to crash.
This is only visible on a debug install.

AT_Utils has at least one issue, the error is here:
Uploading Crash Report
UnityException: set_mode is not allowed to be called from a MonoBehaviour constructor (or instance field initializer), call it in Awake or Start instead. Called from MonoBehaviour 'TooltipManager' on game object 'TooltipManager'.
See "Script Serialization" page in the Unity Manual for further details.
at (wrapper managed-to-native) UnityEngine.Gradient.set_mode(UnityEngine.Gradient,UnityEngine.GradientMode)
at AT_Utils.UI.SimpleGradient.update (UnityEngine.Color _) [0x00012] in <8bfbc58247c04f19a32608d8d8e980d4>:0
at AT_Utils.UI.SimpleGradient..ctor (System.Collections.Generic.IEnumerable1[T] content) [0x0002e] in <8bfbc58247c04f19a32608d8d8e980d4>:0 at AT_Utils.UI.Colors..cctor () [0x000f1] in <8bfbc58247c04f19a32608d8d8e980d4>:0 Rethrow as TypeInitializationException: The type initializer for 'AT_Utils.UI.Colors' threw an exception. at AT_Utils.AT_UtilsGlobals.Save (ConfigNode node) [0x00013] in <06fc2bb492054b45919a0c96aa2441ac>:0 at AT_Utils.PluginConfig.Load (System.String[] files) [0x0003b] in <06fc2bb492054b45919a0c96aa2441ac>:0 at AT_Utils.PluginGlobals1[T].Load () [0x00023] in <06fc2bb492054b45919a0c96aa2441ac>:0
at AT_Utils.PluginGlobals`1[T].get_Instance () [0x0000c] in <06fc2bb492054b45919a0c96aa2441ac>:0
at AT_Utils.TooltipWindow..ctor () [0x00000] in <06fc2bb492054b45919a0c96aa2441ac>:0
at AT_Utils.TooltipManager..cctor () [0x00000] in <06fc2bb492054b45919a0c96aa2441ac>:0
Rethrow as TypeInitializationException: The type initializer for 'AT_Utils.TooltipManager' threw an exception.

For me it looks like AnisotropicPartResizer issue. Parts get offset more and more on some vessel reloads.
When first appeared, I notice that offset was proportional to default part size. Experienced it with space crane and hangar 6 way hab also. I'm fixing it it by editing save file.
It may be related to vessel reroot to some part perpendicular to old root when docking/grabbing.

Getting the common hang on Verifying Expansion: Breaking ground SquadExpansion/Serenity.

I checked the logs and it listed AT_Utilis as the fault. Unfortunately, i don't have the log after removing it and since it takes about a while to load until breaking ground, i have not gotten around to doing it. But wanted to let you know asap of this problem and i will post new logs later today.

I have also not tried removing mechjeb with at active. Mechjeb seems to be a catalyst for many other mods not working including fire spitter

Apparently starting from the latest release. Thanks @pmborg.