linuxgurugamer

There may be, but I'm not going to do that. This mod does not do anything with the Axis groups, and if I did that replacement, then you would lose the ability to edit the axis groups in-flight

New release, Quickhide 3.3.0.7 Fixed nullref when only on Blizzy toolbar Fixed typos in english cfg Fixed entry of time to only allow valid numbers and not show exceptions if an error Made right-click work on the Blizzy toolbar same as stock

Probably a result of the .version file not being updated

I think you meant “slipped” you can try the grip pads in one of the DLCs, or there is another mod with a ground anchor

Post a list of your mods, if you have a .ckan file that would be better

I've been trying to replicate this issue, and can't. Can you either post a video or a series of pics showing what's happening? Also, see my post right above, if there is a symmetry issue that might be the cause

I've been working my way through all my mods, and was pretty happy with the way things were going. I had actually finished updating all the code-based mods and was proceeding on the Part-only mods, when a bug report made me aware of a significant issue with a few mods. So I went ahead and built a full debugging environment, loaded up my new career game and took a look at the log file. Initially I thought it was just a bug, but then I found the same problem in 4 mods which were not mine, and 3 of mine, so I knew there was something pervasive and started to look. Then I started realizing that there had been various reports of KSP just hanging, just before it got to the main menu. As I started looking into this, I found that my new career install was hanging about 3/4 of the time before the main menu, but when I removed the bad mods (at the time, a total of 7 in a 150 mod install), the hangs disappeared. I realized I was onto something rather big. These were errors which weren't showing up in the regular log file, I needed to be running a debug version to see the errors; the debug version is much more verbose in logging. What I found was that as a result of the Unity upgrade, a lot of what used to be acceptable coding was no longer acceptable. Actually, in one sense the coding never should have been considered acceptable, but it worked, so was never an issue until now. I broke the issues down into the following categories: UnityException: get_dataPath is not allowed to be called from a MonoBehaviour constructor (or instance field initializer), call it in Awake or Start instead. A somewhat misleading description, most often caused by trying to reference KSPUtil.ApplicationRootPath in either a constructor or as a property in a MonoBehaviour class UnityException: RandomRangeInt is not allowed to be called from a MonoBehaviour constructor (or instance field initializer), call it in Awake or Start instead. This happened a few times, RandomRangeInt was being called in either a constructor or as a property in a MonoBehaviour class UnityException: SupportsTextureFormatNative is not allowed to be called from a MonoBehaviour constructor (or instance field initializer), call it in Awake or Start instead. Very obscure, took a while to track down. A Texture2D or Texture3D was being initialized in either a constructor or as a property in a MonoBehaviour class Exception loading ScenarioModule *********** System.TypeInitializationException: The type initializer for *********.********* threw an exception. ---> UnityEngine.UnityException: get_dataPath is not allowed to be called from a MonoBehaviour constructor (or instance field initializer), call it in Awake or Start instead. Called from MonoBehaviour ********** on game object 'ScenarioLogic'. A very obscure message. Turned out that the original mod was written as a ScenarioModule and worked well, but in the updated game it seems that things which were being done inside the ScenarioModule which should have been in a MonoBehaviour were causing problems. The symptom of this was getting null refs when attempting to enter some or all of the buildings at the KSC Unity not being thread safe This was a problem with the KSP-AVC and MiniAVC mods. I had seen a couple of messages about MiniAVC not working, and was planning on getting to it when finished with all the updates. Tracking these issues down in over 160 mods, written by at a guess of over 100 authors, turned out to be a major timesink. As of now I'm pretty sure I've caught most if not all of these issues in my mods. In total about 30 of my mods, both adopted and ones that I write, were affected. I also did some work on other author's mods to fix the issues and have submitted PRs (fixes) to all of those authors. Please note that while I listed the majority of the issues above, I think there were a few which I fixed which were mostly one-offs. The main reason this happened now was as a result of the Unity upgrade. The new version of Unity fixed a lot of bugs as well as adding significant performance improvements. Many of the issues I found and corrected were actually poor coding practice, but was accepted because Unity allowed it. There were times in the previous version of Unity that KSP used that these issues arose, but that was in some very limited and specific instances. For myself, everytime I adopt a new mod moving forward, I'll be testing it in a debug install to catch any issues before it gets released.

Make sure all dependencies are installed If that doesn't work, then post a log file (Player.log if KSP 1.8.x, otherwise output_log.txt)

That Output_log.txt is from KSP 1.3.1: [KSP Version]: 1.3.1.1891 (WindowsPlayer x64) (x64) en-us ============================== I have an indication that you may have two copies of the ToolbarControl installed: [LOG 09:04:55.633] ADDON BINDER: Create binding redirect: ToolbarControl, Version=0.1.7.0, Culture=neutral, PublicKeyToken=null => ToolbarControl, Version=0.1.8.2, Culture=neutral, PublicKeyToken=null [LOG 09:04:55.698] ADDON BINDER: Create binding redirect: ToolbarControl, Version=0.1.6.17, Culture=neutral, PublicKeyToken=null => ToolbarControl, Version=0.1.8.2, Culture=neutral, PublicKeyToken=null Or something else, I'm not sure. I really need the correct output_log.txt Edit: From what I can tell, you have ToolbarController 0.1.8.2 installed, which is the last version for anything prior to 1.8 You have version 1.7.19 installed of the Blizzy toolbar, you need to install 1.7.22.2, you can get it here: https://spacedock.info/mod/2090/Toolbar/download/1.7.22.2 or here: https://github.com/linuxgurugamer/ksp_toolbar/releases/tag/1.7.22.2

Check your recycle bin

Log file, please. I'll have to check to see what's going on with CKAN, and then maybe get out an update for the toolbarcontroller for KSP 1.7.3 and earlier

Nice catch, that was the problem line. Fixing it now New release, 2.2.0.8 Quickstart Fixed initialization of path to config file

New release, 0.4.3.2 Rebuild to fix a bad packaging job

New release, 2.2.6 Added InstallChecker Updated for KSP 1.8

New release, 1.4.1.1 Shortened the timeout on HttpWebRequest

Please provide a log file showing the issue. Player.log is the one I need.

I’m waiting on @Dave93 to respond to a PM. If he decides to not go ahead, then I will, but I have to finish my bug hunt and then finish the mod updates before I do a full adoption

Are you running Launch Numbering by any chance? This was the exact bug I fixed last night in that mod.

Your problem was caused by Launch Numbering. I fixed that exact bug i. It last night

Hmm. It may have been mentioned in the toolbar thread

Looks like it, I’ll fix it this evening

It’s a known problem, no idea yet what is causing it

Sorry. I looked at the config and didn't see anything obvious. May be something in the model, will look at that later Try removing the following line from inline.cfg: stackSymmetry = 1

As I acknowledged here: Please try this: https://www.dropbox.com/s/r8w605xl0gz9mki/KSP-AVC-1.4.1.1.zip?dl=0 I shortened the timeout on HttpWebRequest from 100 to 10 seconds

According to Dr. Google, those are normal and ok. yes only appear in AVC 1.4.1, I believe that is something related with the link used by AVC to check the release, when that link don't exist any more, or don't exist yet , that probably might happen only for development releases? Kopernicus is not updated for 1.8.1. I will be looking into AVC, but I can't troubleshoot anything with an unreleased mod. The pics you posted look ok. I'll look into why the "checking ##/##" isn't going away Reverting to the previous version is useless, it wasn't functioning at all, so just remove it for now