Shryq

xxHan replied about 40 days ago that benjee was working on the interiors? Even if this is true, I wouldn't mind dicking around with some things, especially the Viper. Maybe polish some things?

I haven't even checked the thread in nearly 8 months, much less the parts. Someone fill me in; is the RCS on the range still unusably imbalanced? I remember figuring out a fix for it, but IDK if that made it into the release before I went on hiatus. I'll send benjee a message and see what I can do.

Hey guys! The mod looks great! I was just planning on checking how it was going... but then: I wouldn't mind picking back up a small part of this mod I've been working on other projects in unity a lot, I've got a pretty solid understanding of the class/component relationships. Could probably even make a .dll if necessary. For anyone that doesn't know me: I built the range initialy(sans IVA).

Never ever. I'm busy with IRL stuff as well. I have the next couple days off so I'm going to try to get some work done then. No promises though.

I am very aware of that.

Nope. Lander is mostly one piece. Most of the mass and the drag come from one part, where as the ranger the mass and drag are spread out and it gets off kilter. plus i think the shape of the lander is just more stable by default, sort of like a parachute instead of a plank of wood.

For balance and historical accuracy the Endurance cargo will become an empty cardboard box. Progress.

Just up the max temp values in the cfg. IRL is killing me right now D: I'd love to be able to do more, but... yah know. Yes.

NVM. I think I figured it out. no .mu at the end of the file path and for whatever reason it didn't like my 0.2.0 in the file path either.

That's exactly what I said. Textures, models and cfgs all in the same directory.

I have about 7 different parts that use the same texture, and I was trying to minimize the memory footprint by using a single texture file for all the models. I tried organizing it in a similar manner as the B9 parts, where there is one or two textures in a folder, and then multiple .mu files and their corresponding .cfg. The parts don't load at all. I don't even see an error message in the debug menu. So my question then is is there a specific standard that needs to be followed in order for this to function, or a specific file type or cfg setup?

Maybe I didn't understand the issue. What was the problem you were having?

I really like that idea. I'm thinking about it. It has lift. Are you talking about with FAR? Cuz yeah that doesn't work yet.

I can throw that in, sure.

Got a chance to work on the ranger tonight. The external textures are passable, I have all of the parts exported and ready for unity, except for the VTOL (and docking port--still deciding whether or not to make a custom one right now), which will be done when I get the rest of the vehicle into KSP and figure out where the CoM is. Should be pretty quick from here. All the parts use the same texture, I'm aiming for a greatly reduced memory footprint. Plus control surface. I have a regretably small amount of time as of late, but I'm hoping for a Thursday release.