Stone Blue

@Ser Thank you very much for the 1.1.3 and 1.2.2 support... However, i was just wondering if the DLL you linked back for the 1.1.3 fix, and the one above, for 1.2.2, are both for the same dll, or if they are indeed seperate compiles?

I've been occasionaly getting this too the last few days... usually a page refresh or two takes care of it for me... ??

So I DID remember correctly...

Wow.... I guess this.... went.... D-E-D... ??? I guess there really IS a curse on any SLS mods... lol Links still work... At one point, MediaFire links got blocked across the forum, but IIRC, they arent any longer.... ?? Anyway, you just have to add "mediafire.com" in front of the "/download/" when you copy/paste the url...

Plz read at LEAST the last few posts in a thread, BEFORE posting requests for updates... Thanx

Pretty sure this is the one... @Kiro https://drive.google.com/open?id=0B0D_PFGuuyqoQWxiaDNyNHA0Zkk

I have it, if @MeCripp does not...

Thanx a BUNCH! Hey, since its pretty obvious Smelly most likely wont be back, and the fact that it looks like youre the 3rd or 4th person to take up this mod, any chance youl'd want to start a fresh thread of your own? I dont think anyone would argue, as you're all but officially the new "continuer"... With everything new, except your own thread...

Then you wouldnt have had a reason to up your post count by asking this snarky question...

I've asked this before... Unfortunately, the zoom levels seem to be limited by the maps themselves... So unfortunately, dont look for additional zoom levels any time soon... And ditto on the "Cheers", @AntiSol

Best thing to do while posting a (legitimate) request for update or mod status, is to ping the mod author in your post, as so: @xytovl And be patient.... KSP 1.3 hasn't even been out a month yet...

I'll give you all your statements, except, that last part, which all your statements are premised on... From what I gather, the WHOLE issue with Squad, and the letter, which I guess was a C&D or request, was to change/stop using the "kerbal"stuff site/domain name... So why WOULD he hand over the domain name as-is, which was contentious, and possibly in the midst of pending legal action? I suppose he could have, but certainly shouldnt be demonized for not doing so... And as to modders hosting on KS, having to scramble, from what I understood, the domain/server was WHOLLY paid for by SirCmpwn out of pocket... @ $100US/mo IIRC.... There certainly didnt seem to be a whole lot of donations coming in from the community... And whats to say Curse, or SD or any other future mod hosting site wont just shutter the doors with no notice, leaving modders to scramble again? I mean, didnt Squad pull that exact move themselves, when they shut down kerbalspaceport?.... Wheres the outcry for THEM leaving modders out in the cold to scramble for new hosts?

I dont find your slanderous statement credible... The way I remember it, SirCmpwn DID indeed decide to closedown KS, after much drama on all sides... HOWEVER, after the closing, he hosted a full 60+GB torrent of EVERY mod that was on KS, as WELL as the source code for the site itself, with an open license... From what I remember, Vitas took the code and basically used it to build SpaceDock.info... AND, IIRC, SirCmpwm was helpful and active in getting SpaceDock up and running... If thats what happened, that sure doesnt sound like someone who maliciously shutdown a huge mod hosting site "in a way intended to maximize the harm to the community".... Also, where do you think LinuxGuruGamer has gotten many of the files and sources for many of the mods he has "revived"?... From that KS torrent... PS- pinging @VITAS if he wants to verify/negate my SD statements...

And here we are years later, with KSP 1.3.0 recently dropping, and absolutely NOTHING like this has been in stock yet... And I'm guessing it must be REALLY difficult to make a mod for this, since no one has done it yet... Anyone interested in taking up the challenge, and re-examining the API/code for the tracking station/map views, to see if anything has changed, to make a mod a possibilty?

THAT, I dont know... My advice was for a NON-Steam install... Steam is whole other ball-game, that I dont really know much about, as I get my KSP updates right from the KSP Store... What I HAVE read from those who have Steam, IIRC, is that when modding KSP, or if you dont like the auto-updates, or if you want to keep the old KSP version when Steam DOES update the game, its best to copy your Steam fresh install, and copy the whole folder to a different folder outside your Steam folder, then play THAT install... But best to get verification from people who actually do use Steam...

Hmmm... seems that might be a good feature to add, if not already included... Have user-selectable choice, for it to check for updates for ONLY the installed version of KSP, and a choice to ALSO check for updates for newer versions of KSP... That way, it might help with people who dont update to newer versions of KSP, until most of their fav mods are updated to that version... Once their list of installed/fav mods show updated to the new version of KSP, then user's could decide/know its OK to update to the newer version of KSP...?? Make sense?

@cybutek Any thought on my idea of maybe re-organizing the folder structure for MiniAVC, as I suggested above? It might be a dramatic change, and wouldnt cover old release packages of mods with it, but might make things better going forward...And now, at the beginning of a major KSP update, while the majority of mods are updating, might be a good time to do it... (if possible) Again, any way to have the MiniAVC files in their own /GameData/MiniAVC folder, to be packaged with mods, so yould have: /GameData/MiniAVC along with /GameData/<mods' folder>, packaged up by mod devs? Rather than having the MiniAVC files packaged directly into the mods' "plugin" folder? Then, if MiniAVC was able to create a settings.cfg or something, on the first instance of running in someone's install, that would include an "opt-out", so any subsequent "reinstalls" of MiniAVC from another mod that packaged it, the settings file could be read, and the optout seen, and thus keep MiniAVC from running AT ALL, until changed by user input? That seems it would keep people who do NOT use AVC, and do NOT want the benefits of MiniAVC, from hating on MiniAVC.... I'm sure those people probably give that feedback to the devs who package MiniAVC, and it might convince devs from dropping/not including MiniAVC support, at all...?? i mean, if Malah's ZeroMiniAVC can work, couldnt its basic premise be built-into MiniAVC itself?

Excellent point... I've always thought of CKAN as doing its "auto-updating" stuff in the background for those who dont know how, or want to take the time to control their installs (NOT a knock against CKAN, so lets not go "there"... lol)... And AVC as an alternative for those who DO their own manual installs for whatever reason... So yeah, i would think AVC SHOULD have the ability to "manually" control whether/when it "works"...

Well, I think as far as AVC itself goes, opting out would be NOT installing it in the 1st place? ... lol But yes, I can see where you might want to turn it on/off at different times, within the same game install... Maybe that should be added if not already in the Settings... As to MiniAVC, thats a bit different... I think for this discussion, AVC itself, and MiniAVC should be considered two different things, though they may use the same "mod engine" and means of version checking... And, yeah, MiniAVC could definately use some refactoring, or opt-out ability, rather than insidiously rearing its head for EVERY time you install a mod that has it... plus, even though we now have 64bit KSP with no RAM ceiling, do we really need a hundred identical copies of MiniAVC and its files, scattered through-out the GameData folder....?? Maybe if MiniAVC was packaged with each mod, in its OWN "MiniAVC" folder along SIDE whatever mods' folder, that would eliminate much of the "weed pulling", and also it would just overwrite with each different mod install, and again, if there was a settings config or something created the first time it ran, then successive "installs" of it would be in ONE folder, and able to "read" the file, knowing that an opt-out was selected, and you would never hear from it again... ???

latest update of what: Win10 or KSP (v1.3)? I know lots of plugin mods are recompiling for 1.3, and Telemachus doesnt seem to have updated for 1.3 yet... Maybe someone who knows how can try a simple recompile... Otherwise, I wouldnt be too awful surprised it doesnt work with 1.3 yet

While I use KSP-AVC itself in my "play" installs, and I do understand the usefulness of MiniAVC, (and would probably include it in anything I released), I do a search in Windows Explorer for my GameData after whatever mods I want at the time are installed, and one of the things I search for to delete all instanes of is all the MiniAVC files... (as well as all the readme's, license, and changelog files... (after I READ them, of course )).... Rather than all or nothing with MiniAVC, I'd like to see the functionality of ZeroMiniAVC incorporated into it, somehow, so you could opt out ONCE and be done... Like maybe have MiniAVC start once, with an opt-out/nuclear option, and it saves a settings or config file somewhere in your GameData, that any future installs/instances of MiniAVC will check before running, and if opted-out, they wont run at all.... Do-able???....

No problem... Sorry, it sounds like I certainly didnt comprehend what you were asking... Maybe I shouldnt have said "sole" purpose... more like its "main" purpose seems to me to be version checking... vOv Hopefully someone more knowledgeable can address your question

What do you mean?... That you get AVC notifications on mods you have installed, that include MiniAvc?... I'm assuming you dont actually have KSP-AVC itself installed, as its sole purpose is exaclty what you've asked for it to ignore? If its the first, there's a little plugin by Malah, (ZeroMiniAVC), that deletes, prunes, and/or disables the MiniAVC files included with mods that package it... Should give you the results you want... to never hear from AVC again... ??

Sweet! Thanx

Yes, please do! You did an awesome job in it with the FSRedux, and I like it a lot, but I'd also like to see a more modern layout, too...I know one of the things you wanted was better interior lighting, which I think I got... Akron had helped me with the exterior texture. I need to do external lights, and redo the heatshield. I may try to reshape the the lower deck portholes, and maybe evn add some lower deck detail. It will be nice to use the other pods as examples, to see if I can figure out the MAS props, too