-
Posts
24,989 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Everything posted by linuxgurugamer
-
Did you try deleting the firespitter in the Quiztech pack instead of the one in LLL? Also, regarding Quiztech, are you running the latest (1.3.0.1)? If so, then that's something I maintain as well, and will be updating the Firespitter pack to 7.3.0 I suspect you are hitting a conflict between the two firespitters. Re. the log file, Dropbox or Google drive would be fine, just post a link to the file
-
Send me the log file anyway, it has information not necessarily related to the crash which would be useful. However, one thing I don't see in any of your messages is what version of KSP you are running. I need to know, because, some of what I see (specifically BDarmory) is not compatible with 1.1.3. Also, look for another version of Firespitter in some of the other directories
-
That's very interesting, since it is the current version of FireSpitter (I just double-checked). Please provide a copy of the output_log.txt, among other things, it lists all the mods that are installed (those with DLLs, at least). Are you running in Career, Science, or Sandbox mode? If career or science, please provide a copy of your peristent.sfs file as well
-
Does placement of Reaction Wheels matter?
linuxgurugamer replied to Tyko's topic in KSP1 Gameplay Questions and Tutorials
The Reaction Wheels On The Game are so overpowered, it doest matter. But in real life, it does -
Still need logs. so, when you take your car to a mechanic, do you say "fix it" and just leave, or do you tell him what is wrong, symptoms, etc? When you go to a doctor, do you tell him how you are feeling, or do you expect him to read your mind? Saying that it's crashing without logs is exactly the same thing, and will get exactly the same amount of attention from me: NONE Post logs so we can see what is going on. Maybe it's a conflict with another mod. Maybe there is something else. But without logs, you aren't going to hear back from me again on this subject. I write and maintain a LOT of mods, and in all cases, when there is a problem (unless it is obvious like the one above when I had a typo in the version file), I (and ALL other mod authors) need the logs. I can't spend time tracking down something which for everyone else seems to work.
-
[1.12.x] Automated Screenshots
linuxgurugamer replied to linuxgurugamer's topic in KSP1 Mod Releases
not really. It would actually be a fair amount of work to do that. Why not put in a Github issue about this, it's an interesting idea and I can look into it when I get back to this mod -
kerbalx.com
-
Think of Chaff as a cloud of tiny pieces of tinfoil. Anything which can block light is good for blocking lasers, so Chaff would work. Also smoke, clouds, etc.
-
Well, I find the following: The part "LLL Skid" (LLLSkid), uses ModuleLandingGear "Landing Leg - Underside" (LLLUnderLeg) uses ModuleLandingLeg "Landing Leg - Small Underside" (LLLUnderLeg2) uses ModuleAnimateGeneric So I assume that I should change all to use ModuleAnimateGeneric (The LLLUnderLeg2 already uses ModuleAnimateGeneric, so it isn't needed in this patch): @Part[LLLUnderLeg] { @MODULE[ModuleLandingLeg] { -name = ModuleLandingLeg +name = ModuleAnimateGeneric } } @Part[LLLSkid] { @MODULE[ModuleLandingGear] { -name = ModuleLandingGear +name = ModuleAnimateGeneric } } Edit: This patch isn't working (yet), I'll keep working on it