MisterFister

And what of adding a .version file to the download package?

Hi there. I cannot seem to figure out the proper formatting of the bb-code to put inline photos in these posts. The closest I can seem to accomplish is a fancy link to an imgur or dropbox link. I am equally confused as to how to do this for one or multiple images, and I seem to also cannot figure out how to properly nest an image within a spoiler tag (though spoiler tags themselves I can get to cooperate.) Any help?

Or, in the alternative, since someone else in this thread recently reported that this mod is running well in KSP v1.2.2, if someone maintaining the mod could verify this would it be possible to update the .version in the download? This way the AVC and CKAN would be able to correctly report on compatibility.

The derpitude was strong with this one! Wow, I think I might need to get some rest. Thanks for the patient replies, though.

No, I have no idea what would be involved. I'm very public in admitting that my computer skills are in troubleshooting wiring and drivers, not in software design. Hence why I was perhaps more disbelieving than my text was capable of conveying when I asked. ("What does this mod actually do" seemed a little counterproductive of a phrasing for my question, however.)

I admit to having been rather "aggressively hopeful." Is there anything that would allow for what I described?

Does this mod allow for in-flight fuel-switching? Can I launch a tank from KSC with LFO, empty it during flight, and land at a drilling rig on Minmus and fill the same tank with ore for liftoff to Minmus orbit?

Greetings all. I have an issue that I suspect might not be caused by TR itself. My planet textures are displaying in the TrackingCenter as purple or magenta spheres, though the terrain models are still accurate. Heavily modded, mostly-CKAN with a handful of manually-managed mods. KSP v1.2.2. Log file and other informative image-files are available here. Note that I cannot reproduce the symptom System specs: Dropbox contents: Any advice on likely culprit-mods to segregate first in troubleshooting efforts would be appreciated. Edit: I discovered that Kethane v0.9.8 was the culprit. The zipfile ships with three separate texture files for the geodesic grid: one for Linux; one for Mac; and a third for Windows. The user is on his or her own to delete the two that are inapplicable to that person's system, which I had failed to realize was necessary.

And you can corroborate this with logs to establish that there aren't silent errors being thrown? Or are you instead (helpfully, of course) simply reporting that you use it either alone or with some list of other mods with no user-visible ill effects?

Not sure if I should post this here or on the release thread, but does this devbuild for KSP v1.2 also work reliably on KSP v1.2.2?

If NFC = NearFuture Construction, then yes I run that mod, as well as NF Electrical. Can anyone else (@CaptRobau perhaps?) specifically address my curiosity as to this mod running on KSP v1.2.2, despite the specific-ness of this thread title and other metadata (such as AVC or CKAN) stating v1.2.1?

@Nertea do I understand correctly that though the OP in this thread (and a metadata visible to SpaceDock or CKAN) indicate that this mod v2.3.3 is keyed to KSP v1.2.1, it'd still work well on KSP v1.2.2?

This mod doesn't need to be updated, because it runs with 1.2. Just use the latest version of Kerbal Konstructs and you'll be fine. I suspect that this person asked the updating question because the metadata for CKAN and SpaceDock each indicate that "this" mod is keyed for KSP v1.1.x, and not v1.2.x. I admit that this confusion was one of the two primary reasons I've visited this thread just now, in fact. Knowing that I can manually install it as long as KK is updated satisfies my concerns. And @AlphaAsh, thank you for a wonderful mod.

Do you have any reason for us to believe that your mod won't work correctly on KSP v1.2.2? If not, would you care to modify the versioning info embedded into the zipfile metadata so that AVC and CKAN can update their listings at the next automated pass?

Just to make sure I understand, the most recent version of MM I can see in any of my currently-running KSP modtesting installs is v2.7.5 (itself redistributed from one of any number of mods I'm currently runtesting with CKAN). Is this reference to 1.7.5 a typo?

Thanks for the speedy reply, though.

Thank you @Jebs_SY for alerting me to my own derpitude, I just didn't search thoroughly enough for the info I sought. @NavyFish I too love your mod and consider it a must-install in a very heavily modded install. Thank you for your work.

Following your very kindly offered link, it seems that the string you describe is listed right after its SpaceDock reference. Given that the zipfile I downloaded for v6.5.1 has no .version file bundled with it, it would seem that it's looking for info that is not there.

I am ignorant as to what kind of differences exist between KSP v1.2 and v1.2.2 (I run the latter.) Would it be possible to add a .version file to the zipfile to better illuminate this? I'm led to understand that this would also assist with AVC and CKAN versioning efforts, as well.

Is v6.5.1 of this mod specifically known to be compatible with KSP v1.2.2? The only metadata I can find is the changelog that references KSP v1.2. Also, am I correct to understand that CKAN and AVC both get some of their metadata from a .version bundled into the zipfile? Could it be possible to create one for the next version push?

It's up!! I love this mod!!! Thank you @icedown!!!

I too am confused. Does this mean that you are the primary-active caretaker / maintainer / developer of this mod? @DasPenguin85's profile indicates that he hasn't been on since 2015 (I hope he's ok) so maybe someone might consider starting a new forum thread with a new OP that can be updated?

Do you mean v1.2.2? Also, if it's already compliant with KSP v1.2.2, could someone repackage the zipfile with a .version for AVC / CKAN purposes?

The OP in this mod indicates that this is keyed to KSP v1.2, with no reference to sub-versions (such as v1.2.2, which I run.) There is also no .version file in the download, which I think might be a source of CKAN metadata, as well as AVC. Can you confirm that this mod is ok for v1.2.2, and in any event, would you please consider updating the zipfile packaging to include a .version?

My understanding is that CKAN derives versioning from the .version file as well. Pushing an update that packages that fix might be helpful on the CKAN side of things.