TiktaalikDreaming

Adding support for wheel sounds iff the module is installed is just a matter of a NEEDS in the module manager cfg. It's pretty easy to do, even I managed it. And it's easy to use either their sounds or your own. Or a mixhttps://github.com/TiktaalikDreaming/KerbinRover/blob/master/SoundTest.cfg

It would also help with the inevitable rollovers. Something I'd like to see added to rovers in general is a tweakable steering limiter and perhaps a speed governor/cruise control. It'd make keyboard steering easier. I have a feeling there is a cruise control in one of the mods like mechjeb, but I don't know for sure. And yes, it would certainly lesson the load on that middle finger tendon that runs up the back of my forearm. I'll check the CoM. I think I did that once before, and it may have ended up overwritten at some point.

The original motivator was to have a giant pod type thing to put on top of my second stage nexus. So yes. But the eventually is still a long way off

A replacement craft file for stock Duna landings, is available here; https://github.com/TiktaalikDreaming/NAR_MEM/blob/master/ExampleCraft/Duna Excursion Module.craft There's some slow but ongoing progress towards a functional mission module. Parts together; After spending some time inventing greeble for the habitation section, I noticed the diagrams called out the outside skin as radiator for the environment control systems. So I added radiators as well. The top end houses the Kerbin Entry Vehicle, and power systems, plus a bunch of (not yet done) science thingies. The lower section that has the MEM docking has a telescope, RCS, and antennas etc. Anyway, not done yet, but it's progressing nicely IMHO;

Yep. Like many of the "never built" things, there's no single Nova. Hell, there's no single saturn, and they built those. The nova program was a collection of ideas of where to go after saturn, and it's a wide and varied field. Although there were at least prototype M-1 engines.

Quick update on 1.4 compatibility. It's *mostly* compatible. From what I can tell, the FX on any use of the old RCS module results in the FX going the wrong way, and this is affecting some of the RCSish vents from wing pieces (there's no genuine RCS, but there are hints of directed venting of exhaust out A-10 wings, and I implemented that as RCS. Other parts seem to work fine, but I'd wait for KJR before embarking on any A-12 flights.

Testing suggests that this works fine in 1.4. So I've marked it as such, and CKAN etc should pick up on that. At some stage I'm going to need to revisit the FX for the mono engines though.

It will, I just haven't got to it yet. RCS is one of those things that maybe kills old mods.

That's true. Some of the part corrections have invalidated the old craft files.

That's not really an issue with this mod. But space opera should pretty much work in 1.4. It just hasn't been confirmed to be working. The main issue for purely parts mods is fx from the old style rcs module. And space opera uses the newer rcs fx version. The only module is this this mod.

https://github.com/TiktaalikDreaming/Nexus/releases/tag/1.3.1 I fixed the pricing up (I think). It's a bit of a mess as there is stock config that doesn't have the included tankage for UF4 and W. And then the resources are added with MM code IFF community resource pack is installed, and there was no cost change associated with that. There is now. That's the 3 regeneratively cooled GCRs and the Helium cooled one. (I really want to do a multimode engine and drop the variants, coming soon, geologically)

I suspect the old pod will stay until at least 1.5. The dev version (github version) has a quick fix that I'll roll out and mark as 1.4 compatible. I'm a bit slow at the moment due to lack of time. But in the long run, it makes sense to either provide my own pod in that size bracket, or adapt to the new stock.

I've started working on a 1.4 update for this. Clearly with all the fussing, the first thing I needed to do was update the side of the Mk2-3 pod to reflect Take 2 changes. Not super happy with how the warranty text adjustment to hardware worked, so may end up picking a different section of the EULA. (also, that's at twice the resolution I'd be dumping into the game, don't want to kill people's RAM use). This is basically just a silly post to let people know I'm not dead or anything. The existing mod seems to work fine in the updated game. (Oh, and updated the download links with the github locations for anyone wanting development versions)

The telescope animation is a direct artifact of the door drawn in on the plans not being large enough to pass the telescope drawn in on the plans. I suspect the designs were a bit guessworky. But I made it work dammit. Anyways, moar greeble

Just posting to let people know I'm not dead, and am still (slowly) working on things. I have most of the MissionModule section A, logical vehicle tunnel thing done, including the deployable telescope and so on. I have the main mission module done up as per the documentation, and have started on the upper interstage (which also houses about ten experiments, the power supply and probably a partridge in a pear tree). My quandary at the moment is the actual mission module section is kinda boring looking. Everything else has all this complexity. and the MM is basically a capsule shape with just a central cylinder showing when put together. So, I'm going to greeble the snot out of it, using other craft as inspiration. There's not really any good excuse for this. Those outer walls are shielding and probably would be fairly boring looking. But, meh. It looks too plain. Also, can't leave teasers about animations without leaving a pic (sorry about the flickering, it's a "feature" of how the gif converting stuff works);

So, I read this as suggesting we'd be best off using an old Unity 5 install with the old part tools to avoid confusing ourselves with settings that won't save anyway. Especially if everything gets converted to the old before converting to the new. How much of ksp is not spaghetti at this stage?

To be fair, that got a fair bit easier recently. Well Apollo could have been so much more than a few quick tips to the moon as well. But when people gut your budget, there's only so much you can do.

There's a few reasons to look at rewriting how the modules interact already, like that it not being a part module means it can't adjust mass. I need to write up some basic ways for things to interact then grab the existing code and make that into the new frame work. The code does compile. It just doesn't do anything. . I should look at why. When I have time.

That's the one. If I hadn't been on mobile I would have sent you there. But, I get lazy on mobile. And yeah, it is definitely one of those searches you need to tell Google "no I do not mean this other unrelated thing, stop showing me those dammit".

And not my idea. Google ROMBUS for more of the original plan

It should mostly work, but not so nicely with the mk1-3 pod as with the mk1-2. Grumble. I haven't had time for a proper testing of all the bits, so I haven't marked it as 1.4 yet

The method varies depending on the mod and how it's hosted, but generally it's a ckan/netkan function to update the ckan indexed version. The netkan files for both KSPWheel and Kerbal foundries point correctly at GitHub, but I'm not sure how the version indexing works from there. There's a ref to the AVC thing, so maybe it piggy backs off that for this mod. "$vref": "#/ckan/ksp-avc", But that's not a lot to go on. But, if ckan is waiting for something else to update after the main update, then I'd expect some delays. Or, one delay for avc and a second one for ckan.

Awesome mod. And do it!!!!

Ha, guess who tests these things mostly in sandpit. I'm mostly busy with real life crap. This mod is probably next in line for a revamp after I get the Mars stuff fixed up. But things that I used to be able to do in a week are taking me months because I just don't have the spare time at the moment. I blame (rolls dice, consults chart) the Commonwealth games.