Galacticat

Could I get a name change to Galacticat please?

Thanks for the response!

Thought I'd get back into KSP after a long time, glad to see how so many brilliant mods like Kerbalism have grown so much, however, it's not all without problems. There's this rather obnoxious game freeze when I transmit science. Every time a bit of science is uploaded, the game freezes for a second. Wondering if this is a known problem or incompatibility between mods. The only mods I have that touch science and uploading is Kerbalism and [x] Science!.

Would it be possible to make this work with CRP and its hydrogen fuels rather than 'liquid fuel'?

My thinking is that it may be due to the x64 bit limit. TBG would never be possible in x32, but if you have SO many stars with so many planets around them and so many moons around those, you may be hitting the x64 bit limit, causing inaccuracies in the lower end of float variables which will cause truncated decimals. Those truncated decimals will be misplaced meshes/collisions, not dissimilar to what RSS had back when KSP was x32.

Tried doing the Kick Off Space Tourism contract, and it refuses to realize that my periapsis above 75,000m, or even that I'm in orbit... Don't know what to do. EDIT: Well nevermind then... seems doing a quick save and reload fixed it...

Wormholes may be a bit ambitious for someone who has yet to even get their feet wet in KSP modding, but it'll eventually be feasible. And as for billboards and distance fog - I am curious how Unity handles volumetric fog. If it can handle it, it might be possible to put in a non-physical nebula that people can fly through. Though I'm going to be honest here and think that neither are within my reach right now. For now, I'm just going to work my way up and familiarize myself with the program you've made.

Yea, I know C++, and self-taught quite a few others from that knowledge, and I know scraps of C#, though it's pretty easy to learn the syntax. What did you have in mind?

Staying up way too late here, but looking through all the posts and seeing everything going on, it kinda makes me want to dust off my programming skills and contribute.

I'm so excited for this mod, it can't come soon enough! Though that doesn't mean I want you to rush. Anywho, been watching this thread closely ever since Kottabos made that video and am waiting patiently for more complexity!

I can confirm this. Although the new versions of 4.1 and 3.1 are up on CKAN, there is a CryoTanks 3.0 version as well which KA and CE both require. And it's that 3.0 CryoTanks that is causing the bug to continue on CKAN installs.

Went through all my mods, and if you have Cryogenic Tanks, that's what's doing it for me. Problem disappeared when I uninstalled it as well as when I had a clean install except for Cryogenic tanks and the problem popped back up. EDIT: though despite google not showing any results about it, it seems Nertea already knows about this problem.

Same thing here. It happened before I installed Contract Configurator (was hoping that would fix it, but it doesn't). Rather than posting a log and load order, I'm going to just push through each mod I have and find out which one is doing it then report to that mod's thread. I'll report back here with the suspected mod.

Nice job! Always loved TAC-LS!

IIRC from the 1.1 KSP release, Nertea said that it is technically compatible with future updates, but it won't have all the features he wants in it until the mod is officially updated. So you can install it, but it won't do much on its own without other mods populating the tech nodes.

I know it's been a while since anyone's been on this thread, but I was just wondering when you return to this, maybe you could add functionality with Kerbalism's radiation mechanics.

All the packs that are compatible (on the OP) can all go in the game at once and not break anything - though it is recommended to use the 64 bit version since it doesn't have an upper limit to ram usage. And as for existing saves, I don't know if all your probes and ships will translate to the new location Kerbin is in, but if you start a new game, Remote Tech should work just fine. If you're looking for new solar systems to play with in your existing save, you could install both Other_Worlds and Extrasolar without Galactic Neighborhood, and they'll just be orbiting Kerbol on the closer side of a lightyear away. How Galactic Neighborhood works is by turning Kerbol into a black hole as the Galactic Core, and assigns Kerbin to a new Kerbol that orbits the core alongside several other stars. Then each new planet pack is assigned a new star at some random orbit. Since Kerbol is at the universe's center in stock KSP, Kerbin is at a new location lightyears away with the new Kerbol, hence why existing ships probably won't translate to the new location.

Right now you gotta work with the workaround that Sigma implemented. I've been doing quite a bit of testing on the subject and his implementation, though crude, works. @Sigma88 For the overheating bug, I've tried a host of different approaches short of making the galactic core a barycenter which I might do next time I'm looking at this mod, but that's not why I write. ShotgunNinja, the creator of Kerbalism, has a bit more of an elegant solution for solar panels than making them a flat RTG.

I was laying awake at night, thinking about this mod and the problem with overheating, so I decided to dig through the Kopernicus code and this plugin's code: This is a clip from LightShifter.cs - this part in particular deals with the default properties of stars. Look near the bottom at prefab.solarLuminosity - my guess at what that means is PhysicsGlobals is a set of functions that deals with the actual physics of the universe and SolarLuminosityAtHome, being a function in the library PhysicsGlobals, is a function that takes the luminosity level that Kerbin is supposed to be at and then says what the star's luminosity level needs to be in order for Kerbin to be normal (most likely to make RSS easier). So, if you move Kerbol several lightyears away and rename it Black Hole, its default luminosity will be recalculated so it can still shine on Kerbin - incidentally, this means all the function's flaws are exacerbated and ends up burning up all ships. To confirm this, I see what you did to the original Kerbol, in the file GalacticCore.cfg and you turn off its visual lights, but you don't touch it's luminosity, so it's still calculating its luminosity based on its distance to Kerbin, and heating the galaxy appropriately so Kerbal kind can enjoy their lunches in the warmth. I bet you if you remove your hackish fixes, that is instead of turning off all luminosity, and redo the Core's luminosity - hell why not all the important sun properties of the Core for safe keeping - I bet you the problem will disappear. Then again, I'm severely sleep deprived and be making a complete fool of myself. Either way, good night and good luck. EDIT: Looking at all the other stars in your mod, I really don't know if the 'StarLuminosity' is a ratio based off of that contrived luminosity number that Kopernicus gives or the default KSP luminosity number. Hopefully the latter or else you'll have to do some math to reverse the large number Kopernicus will give.

Wanted to try this out with Kerbalism, but I don't know how compatible it is with 1.1.2. Eagerly awaiting any news on this mod Anyway, congratz on the girlfriend.

Does this mod work with Research Bodies?

Hello, Earlier today, Steam updated my KSP install to 1.1.1. I did a few missions, all of which were probes as I have unmanned before manned installed, and I was just about to get into manned flights and I had zero issues. That was until I accepted a tour contract. In this contract, I have to ferry 3 Kerbals from point A to point B which they all waited on KSC grounds for me to pick them up. It was after I made my vehicle in the SPH and hit launch, that KSP shot from 30% cpu usage to 85% cpu usage on a 20-part plane. I'm fine going to my satellites, and I've tried going back to the launch pad, all 85% cpu usage with heavy stuttering and VERY low FPS. I believe it is most likely these loose kerbals that are causing the heavy CPU usage. Why would they? I don't know, but everything was working perfectly until those three kerbals showed up on my doorstep. Anyway, I tried to slog through the lag to get far enough away with my plane, but KSP crashed my computer with a BSOD before I could get off the runway. Gunna try to see if a clean install will help at all. KSP.log

Would love to see this updated to 1.1. If @xEvilReeperx isn't able to from RL or lingering burnout, I bet there's several people in the community (myself included) who would love to update it for him if he could upload the source somewhere now that KerbalStuff is down.

Wait, no Devnotes this week?

Anyone catch that single frame on 2:17? No idea what that's all about.