DMagic

Can you try this version and let me know if it is working correctly? https://github.com/DMagic1/KSP-Portrait-Stats/releases/tag/11.0

@tjt Nevermind. This happens when clicking on the EVA button on the portrait? It seems to not be resetting the highlighter when that happens.

@tjt Do you have log files?

I don't think I've specifically tested the current versions in 1.1.2, but they should both work fine. Old versions are available at all three of the download locations if there is any problem. Adding or removing either from an existing save is fine.

I'm not sure off the top of my head what the MM syntax for adding on to an existing line is, but the fields for my contracts can be found in the DMContracts.cfg file under: DMContracts { DMMag { Magnetometer_Parts = dmmagBoom,dmUSMagBoom RPWS_Parts = rpwsAnt,USRPWS } } Just add additional part names separated by a comma.

@Sudragon I think the version of DMagic Orbital Science you are using is out of date. There were some problems caused by the latest KSP update that might have caused that error.

For stock contract part requests check the GameData/Squad/Contracts/Contracts.cfg file. A MM patch can be used to add additional parts that will fulfill those requirements. For Orbital Science contracts check GameData/DMagicOrbitalScience/Resources/DMContracts.cfg. The parts requested for the magnetic field and recon surveys can be changed or added to there with MM.

@kerboman25 You are using For Science? It doesn't work at all for non-stock (or stock-alike) science experiments. You'll have to find something else or run things manually if you want to use my experiments. I don't see anything wrong with Remote Tech, so it shouldn't be the problem. For Science is the only thing that I can see causing problems. I should probably go ahead and list For Science as a conflict for CKAN, since there is no simple way to notify CKAN users (who may not read deep into the forum threads) that they don't work well together.

While updating Portrait Stats on Space Dock and adding it to Curse Forge I noticed something today: Pretty impressive for just a few months. That could mean 746 mods plus the six on the front page, but regardless, it's a lot, and it's probably fair to say the Curse has a lot more outdated and/or dead mods.

Portrait Stats version 10.0 is out; get it on Space Dock (it's also available shortly on Curse Forge, which it wasn't before for some reason). It adds the part title that each Kerbal resides in to the trait icon (or title) tooltip, and adds a part highlighting function when hovering over the portrait (thanks for the suggestion @tjt). The highlight color will match the icon color; both the colors and the highlight function can be adjusted in the settings file (hoverHighlight; set to true by default). See pictures a few posts up for examples. The highlight function can interact in weird ways with other highlighting functions in some cases (crew transfer for instance), but resetting the other highlight function always seems to clear up any problems.

@Pratherdude It's hard to say with all of those mods. This kind of error is pretty much always a duplicate experiment definition hiding somewhere in the GameData folder. If it was working find until a certain point I would try to figure out what has changed since then. Orbital Science hasn't been changed for several weeks. Contract Configurator seems to be having lots of science related issues with CactEye, so maybe that would be a good place to start.

@Deimos Rast Nope. @kerboman25 Sounds like a Remote Tech problem. I would need to see log files to say anything more.

@Aethon I'm not sure about any stock scanner bugs, they shouldn't have anything to do with SCANsat. There are descriptions of the resource scanning settings in the KSPedia entry, the settings window help tips, and the SCANsat wiki. If you don't want to interact with the stock scanning system just make sure that it is disabled (which will automatically disable the instant scan option, too). The biome lock and narrow band scanner requirement settings will adjust how much beyond simple orbital scans is required for fully accurate resource data.

@Loren Pechtel What do you mean about rescue Kerbals not having portraits? They seem to be working fine for me. As soon as I get within loading distance of the spawned vessel I can switch over and see the portrait just fine, both on stock and with Protrait Stats.

Not necessarily, since VS adds that to the using list by default. But the quickest way to check if you are using Linq is to delete that using line if it's there. Then everything with Linq will have errors. And there are many more things other than the From, Select that use Linq; lots of methods that are used to modify or specify certain members of a list use it, like Any, OfType, Where, First, FirstOrDefault, etc...

@IvanSanchez That is sort-of a by product of the weird shading system used on the small map. It highlights areas of the map that have been scanned with your currently active scanners. So if only the BTDT is active you can end up with that kind of image. Something similar might be possible for the big map (and it would be east to export, since it directly alters the map's colors), I'll just have to see if there is a good way of adding that option. @barfing_skull The zoom map can be re-synced to the settings of the big map by clicking on the zoom level indicator in the top-center of the window. Doing that will allow for using the biome or slope view, or using polar projection, it will also reset the planet to the one displayed on the big map. The KSPedia entry could probably use some info on how the zoom map works.

How about this: Or this: Or both? I'll have to look into the rescue Kerbal problem.

Version 2.0 of Flexible Docking is out; get it on Space Dock. It fixes a problem with the Jr. docking port's deploy animation and uses the proper max rotation value from each part's config file.

@brusura Whoops, it looks like there is an error in the animation for the Jr. port. I'll see about fixing it.

@theJesuit Do you mean rotating the docking port head by 90o? No. That would severely distort the geometry of the flexible section; segments would be clipping through other segments. But I did just think of a change that might allow for significantly more rotation, up to maybe 30-45o. It should work for the model, but I'll have to check to make sure the math still works for actually positioning the port.

I don't think I mentioned it in the config files, but the Max Translation and Max Rotation values cannot be changed. The only thing that can really be adjusted are the active magnetic values (and the standard magnetic values, which are set to their default values of 2, and so use "hidden" config file fields: acquireForce and acquireTorque). Of course, all of the standard fields (tech tree nodes, cost, mass, etc...) can be adjusted.

@BadOaks That's very strange. It looks like the transition from one SOI to another is triggering a progress node event, which then triggers the contract system to refresh and it crashes on a recon contract, which goes all the way back up the chain to screw up the vessel's orbit... I'm not sure why the error occurs on the contract, it happens more than once during a regular contract refresh, so it doesn't seem to have anything to do with the SOI transition, that's just the failure point. I'll have to install RSS and see what's happening. It's possible to trap errors in the contract generation method, so that it at least doesn't effect everything else, but that's not the ideal way to go about it. It would be best to figure out where it's going wrong and fix the problem there.

The final release version of Flexible Docking is out; get it on Space Dock. Anyone upgrading from previous version needs to completely remove those installations, as the folder name has changed. A few texture and model fixes are included in this version, along with finalized part configs with tech tree positions, cost, mass, attachment node positions, agency, title, and descriptions. A MM config is included with CLS support and stock docking port contract requests. A .version file is also included for KSP-AVC support. CKAN support is forthcoming. Also, @vardicd, I used your video in the first post since it demonstrates how they work and what they do.

Not sure why I've never looked into this before, but there's a simple Chrome extension that shows the download count on the release page, next to the file name. https://chrome.google.com/webstore/detail/github-release-downloads/ncgomhdgmkicjeclohgokhciihpfdlhi?utm_source=chrome-ntp-icon

https://api.github.com/repos/S-C-A-N/SCANsat/releases Just replace the bit after repos/ with your github account and the specific repo name. Scroll down about 30 lines to "download_count": Why they couldn't just put that number in the releases page is beyond me. And to answer the question, whichever site CKAN points to will get the most downloads by far. SCANsat gets as many downloads in a day from Space Dock as it does from several weeks on GitHub or Curse.