vossiewulf

I saw someplace in an old thread a mention that procedural panels were going to be included in Procedural Wings, but if so I haven't found them. I ended up using wings for this which worked out, but some procedural panels with a few texture options would be really handy. I do have some very nice non-procedural panels someone made that I also use here, but I'd prefer not to as the edges look like plywood, not exactly in keeping with space vehicles. So am I missing them? If not, any chance of ones being made? I don't have time to set myself up for modding KSP but I could do some textures easily enough.

It may not be a plane but... The Munge Meister 12 Gillion bis A. DON'T MAKE HIM ANGRY Designed for EL delivery, it features 10 tiny augurs, K&K smelter, K&K recycler, two Pathfinder inflated Wagons for metal ore and scrap metal, an MSV-2000 large metal storage can, enough solar EC to run it all, 45k battery storage, BTDT scanner, full science suite, 15G relay antenna, 12,000+ liters of storage, and still has plenty of surface acreage to festoon it with whatever you want. Driving wise, it tops out on Kerbin at 28.5m/s and can do a max-G turn at that speed with a quite reasonable turning circle without lifting a wheel. It's been tested for turning at all speeds and does so forward and reverse extremely well, it drives more like a sports car than a tank. And it snacks on innocent Packrat rovers.

When I post something without a full log, I'm asking whether it's something you want to investigate and/or it's a known issue. Sounds like it's not worth it for now. If you decide you do want to look into it, let me know.

Still trying to figure this out and am confused. What I just did was run up the ore tanks (so the ore IS incrementing correctly) to almost full and then turned on the ISRU for monoprop, then turned that off and turned on the LF/Ox converter. What I didn't notice before because it's hard to see (black text on dark green??), is that no matter which one I turn on, a drain equal to the conversion rate shows in the resource meters. It was running at -1.23 for monoprop, a bit less for LF/Ox, but it's like someone is opening a valve and just pouring out whatever comes out of that ISRU. So, I'm guessing this is something very stupid I'm missing.

Can someone help me with what is happening here? Last couple of days I keep checking on this guy who is supposed to be mining and converting to monoprop. Every time I come back, he seems stuck and I'll restart everything and leave again only to come back and again no progress. I finally sat and watched what was happening and it appears to be mining and converting but neither the monoprop not ore values are being incremented correctly. Another oddity is the ISRU says its converter is "Operational" but gives no load factor that it usually shows. I looked in the log, I see lots of WBI warnings, they seem all related to not finding parts on objects but the reason appears to be that said object isn't supposed to have those parts in its current configuration. If that's the case, that should probably be suppressed as I'm not sure what it's telling anyone. The only errors I saw don't seem to have anything to do with what's happening with my Buffalo, although it does seem to be a problem: there are literally a couple thousand of these: [ERR 15:41:17.196] Module WBIFlexFuelPack threw during OnUpdate: System.NullReferenceException: Object reference not set to an instance of an object at WildBlueIndustries.WBIFlexFuelPack.OnUpdate () [0x00000] in <filename unknown>:0 at Part.ModulesOnUpdate () [0x00000] in <filename unknown>:0 [ERR 15:41:17.202] Module WBIFlexFuelPack threw during OnUpdate: System.NullReferenceException: Object reference not set to an instance of an object at WildBlueIndustries.WBIFlexFuelPack.OnUpdate () [0x00000] in <filename unknown>:0 at Part.ModulesOnUpdate () [0x00000] in <filename unknown>:0 [ERR 15:41:17.396] Module WBIFlexFuelPack threw during OnUpdate: System.NullReferenceException: Object reference not set to an instance of an object at WildBlueIndustries.WBIFlexFuelPack.OnUpdate () [0x00000] in <filename unknown>:0 at Part.ModulesOnUpdate () [0x00000] in <filename unknown>:0 [ERR 15:41:17.403] Module WBIFlexFuelPack threw during OnUpdate: System.NullReferenceException: Object reference not set to an instance of an object at WildBlueIndustries.WBIFlexFuelPack.OnUpdate () [0x00000] in <filename unknown>:0 at Part.ModulesOnUpdate () [0x00000] in <filename unknown>:0 [ERR 15:41:17.637] Module WBIFlexFuelPack threw during OnUpdate: System.NullReferenceException: Object reference not set to an instance of an object at WildBlueIndustries.WBIFlexFuelPack.OnUpdate () [0x00000] in <filename unknown>:0 at Part.ModulesOnUpdate () [0x00000] in <filename unknown>:0 [ERR 15:41:17.643] Module WBIFlexFuelPack threw during OnUpdate: System.NullReferenceException: Object reference not set to an instance of an object at WildBlueIndustries.WBIFlexFuelPack.OnUpdate () [0x00000] in <filename unknown>:0 at Part.ModulesOnUpdate () [0x00000] in <filename unknown>:0 Considering there are only two of them total in existence in my little universe, that's impressive. Here is what I'm seeing. Note the monoprop values progressing up to the point they should increment and then just rolling over to 0 again. EDIT: 1) Oops, thought I was recording at higher res there but I think you can still see what is happening. 2) This is 1.30 and Buffalo 2.2.

LGG, was looking in log for different reason, saw this: [ERR 14:49:33.250] AssemblyLoader: Exception loading 'RCSBuildAidToolbar': System.Reflection.ReflectionTypeLoadException: The classes in the module cannot be loaded. at (wrapper managed-to-native) System.Reflection.Assembly:GetTypes (bool) at System.Reflection.Assembly.GetTypes () [0x00000] in <filename unknown>:0 at AssemblyLoader.LoadAssemblies () [0x00000] in <filename unknown>:0 Additional information about this exception: System.TypeLoadException: Could not load type 'RCSBuildAid.Toolbar' from assembly 'RCSBuildAidToolbar, Version=0.9.1.39319, Culture=neutral, PublicKeyToken=null'.

Ok, Pathfinder has this distribution network not requiring physical connection that seems to work for all KAS/KIS parts and I thought that was integrated into EL and the pad would have the same access. Ok, I will run some pipes over to the launchpad. Thanks for the quick answer.

New EL user and relatively new to KSP. Very cool mod and appreciate the efforts to build something this complex that adds this much to gameplay. I've built a Pathfinder base and have mining going and rocketparts on hand and a reactor generating oodles of power. I landed the pad a short distance away from the base, but it does not seem to be able to access the resources stored in the Pathfinder base. Is it because it's too far away? If so, how much closer does it need to be? And does anyone know of a sane way to move a launchpad that's already landed?

It was 2.13 with 1.30. When I went back a couple saves, it was still intact and moving forward from there was able to once again bring down the cargo lander (the one with a black/red tank) and land him with the Buffalo unmaimed. I'll check the logs but had no visible errors loading the game. Also will download latest and see if that stabilizes things any. And if you found that surprising, you would have found what I just saw amazing- I had reloaded a save when the cargo lander had just landed near the base this morning, and the Buffalo was still intact, so I just hit escape to freeze it and left it there. I came home for lunch and say down and hit unpause on the game, and watched in fascination as the ENTIRE base, including both Buffalo and the first 30t lander and all of the Pathfinder buildings, started thrashing around and then the entire thing along with the vehicles went ballistic, tumbling, so fast and so far that I'm not sure if they wouldn't have gone into orbit had I not reloaded. Before: One brief screenshot of the base flying overhead, too bad it was night. Closest thing is one of the Buffalos 574m up, and you can see other parts of the base >1km and still going upward. And the aftermath- exactly like an F5 tornado had gone through. Note the ONLY things that could be called part of the base that didn't fly away are the Telegraph (knocked over) and the Packrat, which seems to have been completely unaffected. And that's odd because otherwise that rover loves to zoom off into space for no reason.

Well... this is new. Yep, restarted and reloaded and entire back back of my second mining Buffalo is just gone. They're not floating in the air, just gone, the game somehow decided to saw a 25t vehicle and half and take one half home with it. I like how it inexplicably left the flex fuel power pack that was on top - the ISRU below disappeared and it fell to the surface. I guess the lesson here is don't leave your mining vehicles KIS attached to the base? Now to dig through saves to see where it happened...

I figured that was the case, but didn't know if there was something about how or when you place things that make them more prone to teleporting straight up. One thing I like about the Buffalo is that it's heavy and stable. The Packrat on the other hand, if a Kerbal even touches or thinks about the wheels or fenders, the thing shoots off pure vertical at 10m a second or so, my Kerbals now approach said wheels as if they were nuclear attack snakes. It's really crazy that some of these basic issues continue, it's not like we're talking edge cases, anyone who tries to build a base on the Mun will run into these over and over. I manage developers and we'd be all kinds of fired if anything we did had bugs this serious happening this frequently and you don't even need the five years part, a month would do it. Ok that will be my one and only rant on the matter, anyone who's built a Mun base deserves one for free. Thanks again for the Buffalo and Pathfinder, they have in fact made all of the problems easier to deal with. And I really had fun flying the Buffalo in with four of the really heavy SpaceY Dibamus RCS/OMS thrusters- four of those in a close square pattern around the CG make an excellent Mun lander. Brake most of the way with a standard engine, detach the Buffalo at 10k or so, rotate it 90 degrees to put its wheels downward and turn on the Diabamii, they are staged like other engines. Worked beautifully and was quite easy to land safely even though he was 28t when he detached.

I finally got it to work, thanks. It's another issue as with most of KSP where it's easy if you know the exact sequence to follow and how to avoid that pitfall and that one and oh yeah definitely don't do that one. In this case, after you have linked your base to the tanks you must be in base focus or the right click/alt right click doesn't work. I had tried it in EVA and it doesn't work there, so I then tried using that pump function when you right click the connectors and that didn't work either. Biggest other problem I have isn't even KAS, it's KSP in general. Like anything put down on the Mun has a reasonable chance of exploding for no reason, especially if you find the right sequence, 100% of those OX-10 solar panels exploded if placed on the ground and then moved to a different ground location. What has killed me though and I've lost two patio slabs, at least four Gaslights, and five of 16 solar panels I just took off of those cargo drones - whenever I switch between Kerbals at the base, there is a chance something sitting on the ground, even attached to the ground (as the Gaslights and the patio slabs were) will just disappear. It didn't take me long to figure out where they are, they move z + 1600m and hover there silently. The next time I'm cycling through control options, it will then switch me to one of the hovering pieces of equipment. And once I'm there, it won't let me leave because they wake up and start falling, and hey, we can't let you leave something that is moving over the surface?? That's the worst part, that it won't let me leave and forces me to watch these pieces of equipment accelerate in and bomb my base. I haven't figured out why- one patio slab has stayed there since I put it down, the other two went spaceward very shortly after I put them down. Any idea what causes this? Cargo cleared out and drones all sorted out. Except I also lost one of the lander bases and its main engine to the Z +1600m bug.

If you don't know something on the first question off the top of your head (which is what I was checking for), I will do more investigating, you don't need to worry about it. Once I figure out what is/was going on I will let you know. Second question, tanks are standard rockomax or whatever they are 2.5m x 32s, These guys. I brought them to the Mun on a single launcher and detached them in turn to land. Both fell over on landing, the second one BECAUSE I FORGOT TO PUT THE GEAR DOWN *facepalm* but in both cases nothing was broken so I just drove them the 100m or so from where they landed to here on their sides. The one closest to the base already has had his probe core and batteries removed, rest of equipment on both will be removed. Top K&K units have the rocketparts. You can see I've connected one to my LFO Chuckwagon. When I right click on either connector, I get the unlink and Pump Here options. I have no idea what "Pump Here" means as in does it mean pump TO here, or place pump here to pump the other direction? Regardless, when I click on either of them, buttons depress but no LFO is transferred from the tanks to the Chuckwagon. This is probably more of a KAS question than a Pathfinder question, I'll go ask them if that's what I need to do.

Another question - this is the first time I'm mining, I built a Buffalo for that purpose and landed it on the Mun at my base via monoprop engines. It has the drill, the ISRU, Tundra 200 and 400, Wagon, plus some saddle tanks for more ore storage. Last night I left it mining with the ISRU converter set to LF/Ox and happily converting mined ore. This morning I checked on him, and the drill was still going as was the ISRU but the LF/Ox numbers were low and not changing. The Wagon was set for LF/Ox storage and had less than 100 LF and about 120 Ox and was stuck there. Does the wagon get confused about whether it's inflated or not? It was acting like it had been left mining and converting when it had no storage left, so it was just dumping LF/Ox over the side for most of the night. Also, while I'm at it, another question although this one is more Pathfindery . I landed two cargo deliveries consisting of 2.5m 32s + K&K units filled with rocketparts right next to the LFO Chuckwagon. I have connected one to the Chuckwagon via KAS connectors and it all seemed to go correctly and the buttons on the right click connector UIs seem to work, but no fuel is transferred. I know I can just set them to share but I'd like a little more control of what is where

Did you try them pointed at each other? I think it's important you try that, it would seem to have much greater universe-destruction potential.

I thought I was ENABLING them not disabling. Sigh. Thanks for the quick answer.

Anyone know why this mod seems to have lost track of fuel? See the wet and dry mass are the same, and no dry CoM displayed. It was working for a bit with this vehicle but now it's stopped, trying to see where the dry CoM is as this is a self-landing Buffalo MSEV headed for the Mun that will land very light. Clicky full size.

Thanks! Hopefully @Phineas Freak will stop by and explain his updates. It'd be cool if they were working, some interesting tanks and engines and structural elements.

Thanks for the quick answer Ok, so I can just use your Manage Operations UI- I hadn't noticed the consume function so I didn't realize you could transfer, not just share. I was guessing that was a bug/oversight on the Wagon, I'll resist abusing that

Questions, and thanks for a great mod family. The buckboard 6000 and the wagon deflated are about the same size in the SPH. However, the Buckboard carries 1915.something ResearchKits while the Wagon holds 12,600, even deflated. Is this intended? I attached the Wagon to my rover in the SPH, inflated it, set it to ResearchKits, and deflated it back down. It still says it contains 12,600. And once I send either a buckboard or a wagon full of supplies like ResearchKits to my base on the Mun, how do I transfer them to the base resources proper so the Doc Science can make use of them? And actually I guess that applies across the board because the main purpose of this rover will be mining, including a drill and an ISRU and storage initially for ore, LFO, and mono. So I mine, convert with ISRU and store within the rover, how do I transfer the end products to the base storage? Said Mun base, all incuding rover came on that one lander. At this point I still hadn't hooked up the antenna or attached the S.A.F.E.R. reactor.

I haven't yet tried RO but I was looking at the RO thread parts list to see what is there, I clicked on the Constellation Essentials link and it took me to https://github.com/PhineasFreak/ConstellationEssentials with a commit note of "Rebalance for stock KSP & other fixes" from one month ago. Some googling brought me here, since the parts look very interesting. Read through here but not entirely sure if it will work for stock 1.3 or not, can someone clarify?

We could add a button that makes it short and go dark while sparking and smoking, much more satisfying than just making it go away. And add some Kerbal cursing at least, although even better would be a little Kerbal running out of the tower, down the ladder, and toward the shore with his pants also smoking and sparking.

Thanks, but I work in the Bay Area managing developers, so i'm a ringer Careful or I'll suggest we go Agile and designate a scrum master.

Listen to LG, he has about eleventy quadrabazillion times more KSP modding knowledge than I do, which approaches zero- I've just done a bunch of game/modding work elsewhere. I just had the idea, when it comes to implementation I'll trust LG's judgment. However instead of it being just another parts mod, I would like to see it be improvements you can make to the launchpad so players have to work for it and there are two levels that give you basic/fancy lighting if you choose to pursue it. And there are DISCO BALLS

Nope, the thought I had was lights on towers to light the upper parts of the vehicle and to track the vehicle up to 3km or so, and either more lights lower down on the same towers to light the pad itself and the lower parts of the launch vehicle, or make those separate searchlight vehicles like I did (except much more purpose-built). And start with a simple generic tower for the first level, and then look at Russian and US launch towers from the '70s and '80s and more or less copy those to create the level two light towers. Note I was NOT thinking of reproducing whole Apollo launch towers, instead create much simpler dedicated light towers, but use the US and Russian launch towers as inspiration for the design. And then maybe one more modern light tower for level two, something more modern that looks like it would be at home at a SpaceX nighttime launch.