linuxgurugamer

New release, 0.5.31.2 Found another instance field initializer which was calling gameObject when not in Awake or Start

A few questions: Can you please explain the differences between the following. I've listed them with what I think you are doing: LCL_DIR the main debug directory STEAM_DIR The source directory for the game itself GIT_DIR unknown. KSP_DIR The directory where the game is copied to and changes made Without an examples of what you are doing, the GIT_DIR and KSP_DIr are somewhat of a mystery. What I don't' understand is what the KSPRefs directory is used for, it's not part of KSP, and other than copying files there, I don't see the script doing anything with it. In fact, I can run the script and leave out the "copyAssemblies" step, and it will works.

New release, 1.0.7.1 Fixed Unity exceptions caused by invalid access ot uninitialized var KSPUtil.ApplicationRootPath

Its an old screenshot

Unity is not thread safe. Try using CoRoutines

@DMagic There is a problem with the SCANtoolbar in KSP 1.8.1. It's not visible unless you are running a debug build, which I was doing. This is the error: 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 'SCANtoolbar' on game object 'SCANtoolbar'. See "Script Serialization" page in the Unity Manual for further details. at (wrapper managed-to-native) UnityEngine.Application.get_dataPath() at KSPUtil.get_ApplicationRootPath () [0x0001d] in <9d71e4043e394d78a6cf9193ad011698>:0 at SCANsat.SCAN_Toolbar.SCANtoolbar..ctor () [0x00377] in <532e0c7735694646a2dba646ef08b593>:0 I looked at the code, and the problem is in the Instantiator: public SCANtoolbar() { if (!ToolbarManager.ToolbarAvailable) { Destroy(gameObject); // bail if we don't have a toolbar return; } if (HighLogic.LoadedSceneIsFlight) { * * * //Fall back to some default toolbar icons if someone deletes the SCANsat icons or puts them in the wrong folder if (File.Exists(Path.Combine(new DirectoryInfo(KSPUtil.ApplicationRootPath).FullName, "GameData/SCANsat/Icons/SCANsat_Icon.png").Replace("\\", "/"))) SCANButton.TexturePath = "SCANsat/Icons/SCANsat_Icon"; // S.C.A.N else I changed the instantiator to an Awake and that seems to fix it. Submitting a PR to fix. It's rather important, these bugs (in many mods) are causing random crashes

Ever think that he might have made a mistake? I looked at his github, and there are commits there specifically for KSP 1.8.1. I just (this moment) downloaded both 6.8.3 and 6.8.4. While the dates on the dll files are the same, the files are NOT identical. Besides having run it through a file comparer, here are the md5sums for both: 6.8.3: 6.8.4: This might be a language thing. Did you mean to say that the icon shows up on the main menu after having been in the flight scene in a game? Even so, that is such a minor thing which affects absolutely NOTHING in the game, [snip]

It is possible to hide the Toolbar Controller button. Just put it on the Blizzy toolbar. It has to be available, so it will be on one or the other. But, Blizzy can be configured to not show it. I am interested in hearing about possible improvements. No one has really ever said anything, other than their inherent objection to another dependency An interesting idea. Two things have to be addressed. First, how to display the group of buttons. Not as simple as it seems. And second, would be the UI to configure it. I wrote the mod to keep it small and lean. Adding this would probably require adding code to create a new toolbar which expands out from the head button (head for lack of a better name for now). The Toolbar Controller can be used even without Blizzy. It can hide buttons which aren't needed or wanted, even though the mod is installed Oh, and I forgot to say that I really like this mod, the critical temperature gauge. My only issue is that sometimes it seems to show a hot part when the game isn't showing any bar

Did you know that all releases on Spacedock are still there, click the Changelog link. and what bug are you talking about? I have been using this for years, and don’t know what you are talking about. There arent any open issues on github. If this is a real, repeatable bug, open an issue with all the details

It's been fixed, refresh your CKAN and the problem should be fixed

It shouldnt be, Ive opened an issue about it.

Welcome, I too would like to know

Very nice explanation. I didn't quote it all because of the size

Hi everyone, I just heard from @Galileo. The JNSQ repo has been made private while some issues are addressed. It should be back in the near future.

@Katten will hopefully respond, he's the author

I see. Well maybe they are working on a new release?

Welcome to the forums @WhoAmIYt It would help if you provide some information. See my sig below this post for a link to a page that tells you how to find the correct log file. What OS are you running? Computer specs, video card, etc What version of KSP? Any mods, if so, what are they? and why are you trying to use OpenGL?

Wait a few minutes and try again. According to the Github Status Page, things are normal. https://www.githubstatus.com/

Shades of necro’s. This is the longest I’ve seen, a reply to a post 6 1/2 years ago. Anybody know what the record is?

Because it takes me time to provide support, and getting the wrong information takes more time. Eventually I run out of time

I've combined all the new wheel sounds into a single file, see below I'm looking to see if I can have this work with KSPWheel as well. If I can, I'll be considering adopting this mod. Silly me, I forgot that KSPWheel has it's own sounds I'm still considering adopting it, if I do, it will get a new name to avoid conflicting with either @DoctorDavinci's version or @pizzaoverhead's version

Are you adopting it, or is this just a one-time rebuild?

It depends on your skill level. one thing you can do is look at the DMagic experiments, they do what you want

You are asking for trouble. WhT happens if you have upgrades, and all of a sudden you need to know which version is actually installed. I cant count the number of times I’ve asked for info, only to have the user give me bad info because they didnt have the version file available

Hmm. You should really upgrade to 1.7.3, at least. See below for info on log files