Freshmeat

I seem to experience massive slowdowns and glitching to the point of being unable to play when EVA'ing on the KSC, especially if I open a KIS window. It might just be my GPU crapping out, it has it coming, but has anyone else seen something like that. Will provided log and scenario once I reinstall (Removing KS3P solved the slowdown, making it a prime suspect).

In terms of impact on the game, I think @Scarecrow is spot on: The Mun where the real game starts, the first great victory in KSP. Heck, we still give thumbs up to those who post their first arrival in General Discussion, for a reason. Personally, I have fond memories of Vall, being the only moon in the Joolian system I have explored at any length. To date, it has been the greatest logistic challenge I have met.

Following @stibbons lead, I tore out an old PSU from an abandoned PC. Has 12V, 5V and 3.3 V with a lot more amperage than I need, drawn from the motherboard molex connector. I thought about buying a wall wart as the efficiency rating of the PSU at low load is supposedly atrocious, but it was free and had the correct voltages. The 5V is connected to Vin on my Mega board, and both 5V and 3.3V are connected directly to the perfboard that hold all my circuitry. Ground is of course shared between the units. Downsides are the power consumption, as noted, and the physical size that made for some interesting layout callenges while building the actual controller. Link to construction

An i5-4670K, but my wife needed an upgrade from an i5-650 so she got that one. I am one grateful husband for the way it worked out. I think I could have overclocked the Haswell if I had sufficient cooling, but the limiting factor of the rig was 8 GB ram, causing HD swap for massive slowdowns and stutter. A high speed i3 could in theory perform some 90% of my rig on single ships, but it would hamper docking approaches with heavy ships, where you need the fps most.

I doubt that you will get 1000 parts at 30 fps on any rig. I recall @Whackjob literally melted his pc, and most of the monstrosity builders talk of seconds per frame. When I had to buy a new rig this year, I went for a i7-8700K and 16 GB RAM, but reuse my daughters second hand GPU because it really does not matter. Cheap is not an option for great KSP performance, and you need every Hz you can get. Water cooling OC might eventually be on the table, but not this year. An SSD will decrease loading time, but has no effect on the actual game, and I use 6 GB with a ton of mods, so 16 GB will do unless I go off the bat. I have not launched above 380 parts, and that one went a bit yellow on Eve reentry (red on phys warp, though). Some mods are really performance intensive, and be careful of those adding additional mechanisms to the game.

I wonder a bit about the mass readout. My craft reads a mass of 233,249 / 574,346 kg. Total of fuel and oxidizer is 416889 kg, so either is 233t not dry mass or 574t not total mass, which I previously had assumed. Anyone knows?

That the game is as much played in Excel as in game.

If you want one that looks like the one you posted, you need the entire rocketry branch apart from nukes. And it will take you to Jool and back. I do a lot of separate lander missions on the Mun in early game due to mods. The booster I use is based on either a Mainsail + Jumbo or Twin Boar, supplemented with Kickbacks.

In a confirmation of what we already know, I designed a shuttle to take a jumbo to LKO. This endeavor has filled my playing time for the last few days, and the shuttle is pretty nerve wracking to get to orbit and back. The non-reusable parts amounted to ~60 000. Incidentally, my rock solid Raven Vb launcher takes a similar payload to LKO at ~70 000, taking half the time and absolutely no brains to fly. So back to the basics we go. In hindsight, it might be due to the fact that the Ravens are the result of a long research into boosters, while the shuttles are more or less thrown together to look shuttle like and then improved upon until orbit is possible. But the time to land them taxes my patience and my skill to much for routine and resupply missions.

Somthing like this: https://www.ebay.com/p/Pl2303hx-USB-to-Rs232-TTL-Auto-Converter-Adapter-Module-for-Arduino-W-Cables-X2t/1269181688?iid=181834391784&_trkparms=aid%3D555018%26algo%3DPL.SIM%26ao%3D2%26asc%3D47300%26meid%3D77e61ca4364248ffa5616e6e2d85f516%26pid%3D100005%26rk%3D4%26rkt%3D6%26mehot%3Dag%26sd%3D180953299346%26itm%3D181834391784&_trksid=p2047675.c100005.m1851 I bought one before I upgraded to win 10, but did not need it. You can get one at amazon for 5 times the price, but then you do not have three weeks for it.

While the extenders are fast, the libraries are AFAIK not. I run a couple of LCD displays on I2C, and takes some pain to keep the communication to a minimum.

@Alshain Sorry to bother you, but the updated MM throws errors on the .cfg you wrote, and the revamped parts show up as separate parts. It is not the only script around that has that problem, but I am unfortunately throughoutly illiterate with KSP scripting so I cannot do anything about it myself. Can I get you to look into it? The relevant lines fromKSP.log are pasted below: [ERR 17:40:31.947] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/-PART[mk1pod]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.950] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/-PART[liquidEngine3]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.953] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/-PART[liquidEngine]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.955] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/-PART[fuelTankSmallFlat]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.958] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/-PART[fuelTankSmall]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.960] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/-PART[fuelTank]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.962] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/-PART[fuelTank_long]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.965] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/@PART[fuelTank100]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.967] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/@PART[fuelTank200]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.969] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/@PART[fuelTank400]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.972] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/@PART[fuelTank800]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.974] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/@PART[mk1podNew]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.976] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/@PART[liquidEngineT45]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.978] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/@PART[liquidEngineT30]:AFTER[Squad]:FOR[PartOverhauls] [ERR 17:40:31.980] [ModuleManager] Error - more than one pass specifier on a node: /porkjet_replace/@PART[liquidEngine909]:AFTER[Squad]:FOR[PartOverhauls]

From my own adventures, I think you will run out of RAM handling all that stuff, and I think that the processor speed will be a problem as well. Try getting a Teensy or Due, compared to the rest of the budget the investment will be minor. Those around here who actually knows stuff seems to be of the opinion that I/O extenders are quite slow, and you seem to be wanting a lot.

I just wanted to add that your base looks BadSS

They still have plenty of opportunity to scrub the launch, though. I am really happy about the price tag. Means I do not have to seriously consider whether to get the new toys or not.

@RizzoTheRat Of my DX2-50, nothing remains. My Honeywell keyboard held out the longest time, but while DIN->PS2 was possible, DIN->PS2->USB was a bit to cumbersome. The reason for my upgrade was actually that my wife needed to replace her i5-650, and since I play the most CPU-heavy games, she took my i5-4670k and I got an i7-8700K . My daughter got an Gtx970 from my brother-in-law when he bought an Gtx1080 in the autumn. and I got her RX280 because my HD6990 was crapping out with lockups of a couple of seconds on certain instructions. However the RX280 has occasional loss of signal, blinking the entire screen at random intervals. So I follow the bitcoin value, and hope that miners decide that it new investments cannot repay themselves and Nvidia lowers prices again. Gtx-1060 6GB is at just above €350 now, and I can pay that in a month or two and live with hiccups for now. Had the RX280 worked flawlessly, it would have served it purpose for another couple of years, but alas.

I had forgotten all about this awesome project. Impressive that you keep going, hope that this time around is success.

Oops Thanks, solved it. This is why I am a bit reluctant to initiate my Eve mission, I know I am gonna miss something absolutely obvious.

I am getting back into installing KSP, and MM spits out an error on load: [ERR 11:40:26.064] [ModuleManager] Error - more than one pass specifier on a node: PlanetaryBaseInc/ModSupport/Configs/LifeSupport/KPBS_MM_TAC_LS/@PART[KKAOSS_Habitat_MK2_g]:FOR[PlanetarySurfaceStructures]:AFTER[TacLifeSupport] [ERR 11:40:26.068] [ModuleManager] Error - more than one pass specifier on a node: PlanetaryBaseInc/ModSupport/Configs/LifeSupport/KPBS_MM_TAC_LS/@PART[KKAOSS_Habitat_MK1_g]:FOR[PlanetarySurfaceStructures]:AFTER[TacLifeSupport] [ERR 11:40:26.070] [ModuleManager] Error - more than one pass specifier on a node: PlanetaryBaseInc/ModSupport/Configs/LifeSupport/KPBS_MM_TAC_LS/@PART[KKAOSS_Central_Hub]:FOR[PlanetarySurfaceStructures]:AFTER[TacLifeSupport] It happens on line 14323 in the log. Mods by directory (sub directories of GameData): 000_TexturesUnlimited 000_USITools ASET CommunityCategoryKit CommunityResourcePack CxAerospace EnvironmentalVisualEnhancements JSI KerbetrotterLtd ModRocketSysLite MunarIndustries NearFutureConstruction NearFutureProps NearFutureSpacecraft Nereid PlanetaryBaseInc REPOSoftTech ScifiVisualEnchancements Squad StationPartsExpansionRedux ThunderAerospace TriggerTech UmbraSpaceIndustries UniversalStorage Windows 10 Enterprise, KSP 1.3.1.1891 (WindowsPlayer x64) en-us. Is it something I should worry about and is there any further information you need right now?

@JoshTheCoward The map mode is not implemented. My controller has a USB keyboard IC included to get keystrokes for map, IVA, next/prev ship, time warp and cycle view. As for MAX7219, I followed the tutorial on Arduinos website. Feel free to ask specific questions, and share your code and what you are trying to do. The LEDs draw a lot of power, though, so be prepared to supply some extra juice to your controller. If you can get a 5V 2A wall wart for a tablet, it goes a long way. Otherwise an old PSU is assured overkill for everything you ever are going to hook up.

@JoshTheCoward: That looks pretty cool. How did you make the print on the controller, and the markings inside the annunciators?

@hugopeeters: I am just gonna leave this here. It links from the front page right now: https://blog.arduino.cc/2018/01/24/create-a-custom-kerbal-space-program-cockpit-with-arduino/ I think that is a sign of "making it"

Until it does not work out like that any more. I am quite convinced that bitcoins are gonna tank heavily this year, and prices on GPUs are going to reflect it.

Bitcoin miners are using every GPU they can get their dirty hands on. My favorite online parts dealer just turned down an order of 1000 cards, and every AMD GPU is out of stock. I am hanging on to an RX 280 with a flaky connection while I wait for the cryptocurrency market to crash and burn, leaving the retailers with a stockpile.

The beauty of FrankenPC's is that you can spread out the upgrade cost. Invested in new MB+CPU+RAM last week, going to get a new GPU in a couple of months, and eventually a couple of additional RAM blocks (and a new SSD before that. My HD caught a short circuit and took my SSD with it )