Korb Biakustra

I'd kill for a Minmus with the same default colorset (as it is something very special with this moon, and Jeb will have to deal with it anyway when he will crash on it and stay there waiting for rescue), but with higher resolution. I don't know if this is related to its small size requiring zooming in, but Minmus really looks low quality and blurry when you look at it in the map.

Will you update your 9K+Clouds texture to 8K?

Am I the only one having trouble making KAS attach ships outside the launchpad in 0.21? I uninstalled Attachment Pack 06, but still have the same issue. Sometimes I also have no indicator at all (no green/yellow/red part), only the message stating to press b/n to rotate.

Well, perhaps I should remove the link then. Could you edit your quote?

Oh sorry, I misunderstood a previous post here and thought it was challenging. Don't know what he has done exactly, here is the post. You probably already know how to do it anyway, sorry for the misunderstanding.

I've done the texture changes several hours ago but I'm still playing KSP right now. Just have to say I keep being amazed by the graphics now. It's outstanding from space, building my Kerbin Space Station, I feel like I'm watching a NASA or ESA channel. I can't imagine how it would be if I was skilled enough to run a mission like the Constellation mission I've seen on this forum. A asynchronous cloud feature would be awsome, I'd prefer that over suit customisation at first. However, on a French forum, there's already a guy who've succeeded tweaking the Kerbal faces. :]

Good catch, thanks! I've just fixed all my FusTek .cfg files thanks to you.

eRe4s3r, we have to rename sun_flare.tex_.dds in sun_flare.tex.dds (and backup the original file before) before "Import from DDS", right?

Thanks a lot. Now I'm eagerly waiting for a release from Mushroomman, and I'll have a KSP game graphically more impressive than Space Engine. [Edit] Wonderful! Thanks Mushroomman!

Could you post a before/after comparison? It's difficult for me to see what exactly in the screenshot results from the modification, and what was already there.

Well, I really hope it is. The results are awsome.

Great work! Some lower resolution files would be much appreciated, just in case these ones alter performances. Do I just have to resize the .png in Phosohop, and save? Which settings shall I set when saving the .png?

Well, it is the first pack linked (and recommended) in the OP, that's why I did not link it. Check it out here: https://www.dropbox.com/sh/1en92k9curnlm9g/3QJtpl4bK4!

Thanks for your reply. I don't think I've turned CSV writing on if it is off by default, as I don't know how to do it, plus I have no CSV files in \Kerbal Space Program\GameData\Innsewerants Space Agency\Plugins\PluginData\ISA_MapSat. However the issue I have is very similar to what you've reported. :/ Don't really know what to do.

The pack I used for the pics in previous page was mentioned in my post. :[

I did, and I have issues. Don't know if this is related. I bet there are hundreds of people running it correctly with 0.21 though, this is a popular mod.

Awsome. Thanks a lot for this great plugin and for the Rareden's texture pack; I have not tried other packs yet. For reference for people hesitating, well, don't hesitate: It's the non-HD version of Rareden's pack.

I get very regular freezes when scanning (not when not scanning). I don't know if it is the issue, but it looks like if it was writing data to the disk, but the disk wouldn't be rapid enough, resulting in freezes every XXX frames, and then smooth again, until next freeze. It gets worse when I warp (freezes occur more often, i.e., less than one second of smooth game at 10X, and last a little bit longer, i.e., one second), suggesting that it might be indeed related to the amount of data being saved. I'd be surprised my disk is limiting though, as it is a healthy SSD, and I've also tried on another computer with a SSD and experienced the same issue. I have it for every planet or moon I scan. I have recently updated to 0.21 and updated ISA Mapsat with the Dev version, but I had not experienced that with pre-0.20 (I was not using Dev version of ISA Mapsat if I recall correctly). Is it a known issue? Did I do something wrong with the settings? I already tried reducing the scan resolution, no success. Orbits I've tested are 100 Km (Kerbin, Mun) and 80 Km (Minmus).

Astronauts normally sleep upright in harnesses, but all in all, you could adjust it just by rotating the whole module if you want to adapt it to a ground station, with horizontal beds. Anyhow, Kerbals are cubic, their height barely exceeds their width, hence their beds should be squared. Solution. :]

Yep, I'm actually touching the surface I want to attach the connectors/struts to. Actually, based on the situations where it worked, I'm way closer than that. Even tried while grabbing a ladder to ensure my own velocity difference with the ship was not the issue. :[ (Just edited the previous post with another experiment.) And that's a no. Too bad. :[

Ok so in case it's useful, here is what I've just done and I could successfully attach the connectors (and struts from the other mod): - copied the exact same Mun station from the quicksave.sfs (i.e., assembled modules with docking ports); - placed it onto the launchpad, high altitude, by tweaking a new ship in the quicksave.sfs; - triggered debug menu and enabled: pause on vessel unpack, unbreakable joints, no crash damage, and hack gravity; - for some reason, the station fall on the ground despite the gravity hack, but without exploding thanks to the aforementioned cheats; - got Bill EVA, tried to attach connectors and struts. It worked. There must be something wrong with orbit, right? Or Mun? Or velocity? Of course this is not a workaround - unfortunately! I'd really hope to have one. This is just some tests I've been done to try to figure out what's wrong. I still don't know, but here's exactly what I've done to try to pinpoint the source of the issue. Just wanted to make sure that this was not a problem with the station itself, hence I wanted to try on the existing station, not a new ship. Noteworthy, on a brand new ship, it will always work on the launchpad, without tweaking the savefile, as mentioned in an earlier post. Is someone inspired? [Edit] Putting the station 100 M Km away, outside of spheres of influence, doesn't help: attachments do not work. They appear to work only on/near (how much?) the Kerbin launchpad. [Edit 2] I tried the same situation but with Gravity hack, I apparently was able to attach connectors (well sort of: they did not stick, but I could drop them thanks to the green indicator). After removing the gravity hack... Still working. Weird. Let's try with my orbit around the Mun in the genuine save file.

I've gone through the whole thread searching for the keyword "yellow", and found that several people are experiencing the "yellow ghost syndrome", where you have a connector in EVA, you're touching the surface you want to plug it in, and it is still yellow and beeps when you try to connect it. Any solutions? There seem to be a lot of people concerned, but I've not seen any workaround in the thread. It worked correctly on the Kerbin launchpad, but it doesn't in my Munar station in 1000 Km orbit. In case it helps, I'm also using this mod which may conflict, but it didn't on the Kerbin launchpad: I successfully attached struts to my ship, on the same surfaces I'm trying to do so in orbit now, and it doesn't work either.

Thanks for your reply. I am sure it is not a CPU-temperature-related problem. It really looks like a CPU-temperature-related problem, that's why I've checked underclock settings dozens of times in Advanced power settings, as stated above, and additionally, the temperatures remain way below the values they can reach when Windows indexer is running, for instance. Maybe there is a thermal limit for the GPU though, and if yes, then I don't know how high is this limit and if KSP makes the GPU reach it. However, as the 0.75 GHz limit can occur without running KSP, I doubt it results from the GPU usage in KSP. As mentioned above, I'm unfortunately already using the High Performance setting, and I've already made sure System cooling policy is set to active and Max processor state is set to 100%. I'm running out of ideas, that's why I believe it might be a bug with the BIOS, as the BIOS for a convertible laptop/tablet might be somehow experimental, and others are experiencing the same issue (namely in the thread you have linked, I had already posted in it: I'm Kabouik, end of page 6). Thanks a lot again for your help. Unfortunately these ideas have already been tried, and I have no additional ideas right now, but anyone does, please don't hesitate to share because I'm getting desperate! I want my Kerbals to conquer the cosmos!

Thanks for the input. Here is the screenshot: Yesterday I've been playing KSP and, as described earlier, the CPU was sometimes at 2.5 GHz and sometimes at 0.75, with no apparent reasons to change (not high temperature nor KSP requiring less performance). The last minutes (or hours), it was stuck to 0.75. I've let the laptop in sleep mode during the night, and today it still seems to be locked to 0.75 GHz, even under stress test as in the screenshot above. I have HWMonitor to control temperatures, as well as TPFC (Thinkpad Fan Control, but it is not set to a conservative mode that might throttle the CPU down, it only acts on the fans and it lets the CPU reach higher temperatures than those experienced here, I've seen it plenty of times). The computer is not in a power saver mode but in "High performance" power management scheme, and it happens both with AC power and battery. The BIOS is up to date, but I believe it could still be a BIOS problem related to the convertible nature of my laptop. When undocked in tablet mode, it is supposed to throttle down the CPU a little bit, but it should revert it back to its normal state when docked back. That is where the issue may be in my case (not only though, see below). On the Lenovo forums, people have reported this behavior to work correctly, but there are others that have the same issue I described here. No solution as been found so far, unfortunately, and the Lenovo technicians have not been able to reproduce the issue yet. :/ Noteworthy, since the yesterday's reboot that allowed full power of my CPU in KSP, before the CPU returned to a locked-0.75 GHz state, I have not undocked the tablet, so the issue does not specifically result from undocking/redocking. Perhaps there is still an issue with the BIOS that is certainly a modified version for such hardware, and that may cause problems even when I don't switch between tablet and laptop modes. It's really unfortunate that there are no solution yet, and even not identification of the source of the issue. We are a few experiencing this, but not a majority, so it might take long before we solve this. Thanks all for your help. I hope I'll figure out how to solve this soon, because rebooting is not a decent workaround, and it doesn't totally solve the issue anyway because I'm stuck again now.

As posted above, that's one thing I've checked at the beginning and I re-checked it several times just to make sure, because it would have been very relevant, but no, I'm in High Performance with max CPU speed set to 100%. I've tried rocket science: rebooting. Running again the Intel Burn test resulted in CPU usage above 30%, and speed above 0.75 GHz (though still not 100% and 2.5 GHz, but better than before anyway). KSP was way smoother. Beside the fact that it is already weird that it required a reboot, the other weird thing is that it did not totally solve the problem either. Sometimes, it reverts to this 30%/0.75 GHz limit. I'm currently playing KSP and during one flight, it will change from 2.5 GHz to 1.8 GHz and eventually 0.75 GHz for a while, and thus framerate will drop to < 5 FPS. It's really surprising that this throttling is not related to the game's requirements or CPU temperature. I don't understand what governs this CPU management, but for sure, again, it's not temperature and it appears it is not KSP either since the framerate drops dramatically when the CPU is throttled down that much. KSP will of course increase CPU usage compared to a situation when it's not running, but something seems to overrule it.