blu3wolf

BoulderCo is apparently part of the normal EVE install. Removing that fixed it, cheers!

no clouds in game menu or tracking station. http://images.akamai.steamusercontent.com/ugc/263835861948444384/05AAEB0ED4C3CFB05A0084519FC9E17CF61E651C/?interpolation=lanczos-none&output-format=jpeg&output-quality=95&fit=inside|1024:576&composite-to=*,*|1024:576&background-color=black From your picture... the clouds look great, but the planet looks like it uses the stock texture still?

I installed this: https://github.com/Nhawks1717/StockVisualEnhancements/releases/download/0.6.4/StockVisualEnhancements_0.6.4-HR.zip Before that, I had it installed through CKAN, and uninstalled with CKAN, then checked gamedata for the EVE and SVE folders (they were not there). You can find my KSP.log at http://www.blu3wolf.com/KSP/KSP.log I dont have an output_log.txt in my KSP folder, where should it be?

Well I get the same result whether I use CKAN or not. Still no clouds, stock textures... Seems like its a little premature to claim CKAN is the root of this issue.

CKAN updates are in the hands of users, actually. The issue with it presently is that 1.7.1 is marked as being compatible with KSP version 1.1.0 only. Unless someone opens an issue about it, or submits a pull request fixing it, its not likely to get noticed by the CKAN maintainers.

this looks like it would be awesome... would be great if I could use it with EVE as released elsewhere. Is there significant changes between your included version of EVE, and the present standard EVE?

Alternately, you could advise them of this, by opening a new Issue on their Github page @duha54rus - that would ensure it is at least noticed sooner rather than later.

Any chance of this getting a release? If not, anyone know of another tool that can list all parts from the GameData folder in a text list? Would like to have a checklist of all parts in my install, but doing it by hand is difficult and easy to make mistakes and omissions. Cheers!

KKS plus KIS are the only two mods needed to install to reproduce, so its not rocket science.

I note that with the stock config, the FL-100 fuel tanks always have a MTBF of 111.11 minutes, regardless of the data gathered on them. Is this just a shortcoming of the config file? Is there notes somewhere on how to write my own? EDIT: found the wiki. More info there than I had, but less than I was hoping for. Is there a description somewhere on the reliability curve? what shape it is, what the keys mean? EDIT: so I found that info also. Is there a minimum value for reliability/Failure Rate? I see why the tanks have that MTBF now, the config file basically defines their MTBF against data gathered as essentially a flat line.

Well, I started a new game. Messed with a lot of my mods, reinstalled all of them, changed which ones are installed... and on the new game, the issue is fixed. Cheers! Is it possible to alter the priority of a ribbon? Say if I wanted the KSA/NASA style ribbon to display before all the flag style ribbons? Also, I note that its possible to gain the new 'landed with less than 1%/5% liquid fuel remaining' ribbons just by landing a rocket with 0% liquid fuel remaining via parachute. Such as one tends to do quite often in the early days of Career mode.

Have just determined that its an incompatibility between KIS and Kerbal Krash System. If those two are installed, that causes this bug. Guess KKS has to go for now! EDIT: using KAS 0.5.7, KIS 1.2.9 presently. Installed all these through CKAN.

Discovered that the bug in question depends on having KIS and KAS installed.

Ive discovered a weird EVA bug on my modded install (quite a lot of mods). Specifically, when I board a vessel from EVA, the kerbal in question stays on the ladder, and cannot be switched back to. Anyone seen that before? { "kind": "metapackage", "abstract": "A list of modules installed on the default KSP instance", "name": "installed-default", "license": "unknown", "version": "2016.05.07.02.25.52", "identifier": "installed-default", "spec_version": "v1.6", "recommends": [ { "name": "ModuleManager" }, { "name": "AnimatedDecouplers-x86" }, { "name": "CoherentContracts" }, { "name": "TestFlightConfigStock" }, { "name": "ContractConfigurator-FieldResearch" }, { "name": "ContractConfigurator-Tourism" }, { "name": "CrowdSourcedScience" }, { "name": "DeepFreeze" }, { "name": "KerbalNRAP" }, { "name": "FirespitterCore" }, { "name": "TestFlight" }, { "name": "KerbalAlarmClock" }, { "name": "KerbalJointReinforcement" }, { "name": "FinalFrontier" }, { "name": "ContractConfigurator" }, { "name": "LaunchNumbering" }, { "name": "KIS" }, { "name": "RasterPropMonitor" }, { "name": "RCSSounds" }, { "name": "ScienceRolesFinalFrontierRibbonPack" }, { "name": "STMsFFRibbonPackEngineeringRoles" }, { "name": "STMsFFRibbonPackExpeditionRibbons" }, { "name": "KerbalFlightIndicators" }, { "name": "KerbalEngineerRedux" }, { "name": "STMsFFRibbonPackOperationsRoles" }, { "name": "KAS" }, { "name": "OrbitalDecay" }, { "name": "WaypointManager" }, { "name": "REPOSoftTech-Agencies" }, { "name": "RasterPropMonitor-Core" }, { "name": "KerbalKrashSystem" }, { "name": "AlcubierreStandalone" }, { "name": "CommunityResourcePack" }, { "name": "Karbonite" }, { "name": "KarbonitePlus" }, { "name": "KaribouExpeditionRover" }, { "name": "UKS" }, { "name": "USI-EXP" }, { "name": "USI-FTT" }, { "name": "USI-LS" }, { "name": "USI-NuclearRockets" }, { "name": "USI-SRV" }, { "name": "USI-SubPack" }, { "name": "USITools" }, { "name": "USI-Core" }, { "name": "USI-UKS-Shared" }, { "name": "AGExt" }, { "name": "CactEyeCommunity" }, { "name": "ContractConfigurator-ContractPack-SCANsat" }, { "name": "ContractConfigurator-InterplanetaryMountaineer" }, { "name": "ContractConfigurator-KerbinSpaceStation" }, { "name": "CustomAsteroids" }, { "name": "OuterPlanetsMod" }, { "name": "Toolbar" }, { "name": "KSP-AVC" }, { "name": "SCANsat" }, { "name": "Kopernicus" }, { "name": "PreciseNode" }, { "name": "RealChute" }, { "name": "RealPlume" }, { "name": "RealPlume-StockConfigs" }, { "name": "SafeChute" }, { "name": "SigmaBinary-DunaIke" }, { "name": "StageRecovery" }, { "name": "Trajectories" }, { "name": "UniversalStorage" }, { "name": "DMagicOrbitalScience" }, { "name": "SolverEngines" }, { "name": "SmokeScreen" }, { "name": "SigmaBinary-core" }, { "name": "B9-PWings-Fork" }, { "name": "ChampagneBottleRedux" }, { "name": "CustomBarnKit" }, { "name": "DeadlyReentry" }, { "name": "EveBiomesPlus" }, { "name": "ExtraPlanetaryLaunchpads" }, { "name": "JoolBiomes" }, { "name": "InfernalRobotics" }, { "name": "KerbalStats" }, { "name": "USI-ART" }, { "name": "AdvancedJetEngine" }, { "name": "BZ1RadialAttachmentPoint" }, { "name": "Ceteras-Suit-Pack" }, { "name": "ContractConfigurator-RemoteTech" }, { "name": "FieldExperience" }, { "name": "InFlightFlagSwitcher" }, { "name": "Mk1RPMInternal" }, { "name": "ModularRocketSystem" }, { "name": "SpaceY-Expanded" }, { "name": "SpaceY-Lifters" }, { "name": "StationScience" }, { "name": "IndicatorLights" }, { "name": "TextureReplacer" }, { "name": "notes" }, { "name": "RealHeat" } ] } Additionally, Distant Object Enhancement, FAR, MFI, Persistent Rotation, PlanetShine, Procedural Fairings, RCS Build Aid, and RemoteTech are installed, although they do not appear in the list above.

Plock indeed belongs to OPM, although I am using quite a few mods... OPM, and also SigmaBinary is installed. Still havent gotten to orbit yet, so unsure if Im going to get a ribbon unexpectedly. Is there a file somewhere that matches ribbon codes to ribbons? That would be handy if I need to add/remove some ribbons. I guess I can remove them easily enough through the config.

The text of my Closer Solar Orbit ribbon reads: Awarded for orbiting sun half between Plock and sun. Im not one to nitpick, but Plock is the furthest body out in my game. Moho being the closest. Havent gotten to orbit yet, but is this likely to trigger as soon as I do?

Doesnt seem to be. Whether thats due to it not being updated yet for CKAN, or whether there is some screwiness with the automatic install, Im not sure.

Hmm... not sure which tool would be best for that. So the problem is limited deltav, a specific starting orbit around eve (which is highly elliptical, highly inclined), and a transfer solution back home. Thinking about it, you need to find transfers into a specific hyperbolic trajectory around eve which lead into a transit orbit back to kerbin. So you need the specific hyperbolic orbit around eve to have a similar RAAN, a similar inclination, as well. The basic two body porkchop plot for TOT could do this couldnt it? Then once it has a candidate trajectory, put it into the mission architect... yeah that sounds totally doable!

well, you can get the info quite easily from the .sfs file. Interpreting it in a report is another matter. I dont think there is a tool designed for the purpose, but it shouldnt really be difficult to do so. The data is saved pretty clearly in the .sfs file, so your options are either to write a tool which can pull the data automatically, to copy the data from KSP while FF is open, or to manually note down the info in the .sfs file and interpret it yourself... Id go for option 2 myself, but option 1 would help a lot of other folks, I imagine. well, its not a rare bug for me. I have to say though, I didnt realise it was a bug! I just noted that, if the kerbals didnt get any ribbons on the last mission (such as when they never launched before being recovered) they would display the ribbons from the last mission they went on.

Ive done it with hyperbolic orbits around minmus, so sure. That said, the specific tool I was using that I am thinking of, the Rendezvous Maneuver Sequencer, assumes you will only make 2 burns, so for a hyperbolic trajectory it is quite inefficient; I found I could save lots of delta V by circularising first, then solving the problem. Next question is what sort of problem do you have? There is a lot of tools included in this software, but all of the ones I have tried, you could input the starting orbit, to include inclination and eccentricity. In fact, if KSP is running in the background, you can have it pull the orbital parameters directly from it (or even if it is not running, but its a little faster if it is running). The toolset that TOT provides is I can safely say the most powerful that I have ever used for KSP, in any event. I think you will like it.

I have used this tool to solve a variety of orbital problems from a wide variety of starting orbital configurations, including very high eccentricity and highly inclined orbits.

I feel like Navigation deserves its own specialty. Knowing where we are with pinpoint precision is taken for granted in kSP, though.

Ops roles title is still engineering roles set 2 in the OP. Im not sure i see all of those as being roles a pilot could be expected to specialise in - although i guess kerbonauts like astronauts could have to pull double duty so that therr is enough skillsets to go around. For suggestions, I would suggest life support moving to engineering or science (the latter obviously being hard to do til FFs 1.1 update), and Trajectory Optimisation specialist added to enginnering or operations.

If its not done it automatically after checking the box, that is unusual. If you have a more complex install process than 'copy this GameData folder into your Gamedata folder', then I believe you do need to create a netkan file. I think I am going to need this mod :/ yet another thing to fit into limited memory

Hmm. I get a 401 error trying to get the expedition pack from KerbalStuff. Thats unusual. EDIT: got it now, not sure whether logging in fixed it or something else.