tg626

https://1drv.ms/u/s!ApRsS13p52FhmTgtupG64AA7Cw6I?e=tpIZwp The above is the savegame, craft file, list of mods, and ksp.log for a bug I hit. The enclosed probe has 4 cameras around it. I was "looking" thru one, watching the sunrise from orbit, when suddenly I was "popped" back to the external view (First error in the log) then when I used + and - in an attempt to go back to the camera, it no longer worked. I could right-click and "activate camera" but using + had no effect, and using - dumped me back to external view. I hope I was thorough enough with my zip file above. Thanks for your time @linuxgurugamer

Just commenting to get "subbed" - I just discovered this, and want to know what's going on with it.

Have to switch off Colors and FXAA to get anything to appear, otherwise it's just pink where the vessel should appear. I also can't rotate or change views (aside from Orthographic on/off) Is there an updated version I missed? Or are we waiting on an update? I've been away from KSP for awhile... NM, somehow I was using a SUPER old version.

Many of my launches follow a sort of Soviet naming convention. Whereas they just used KOSMOS-## and then renamed them if they worked, I use USC-##. Which is short for Untitled Space Craft. Named missions are not very imaginative Janus ## = Gemini Type Prospector ## = Sats with resource scanners K-Lab or StarLab = Station that starts like a Skylab/Salyut and ends up like a Mir if it was designed by Rube Goldberg etc.

Working in v1.12

KSP: Columbo Edition

I have one connected, but I don't touch it in KSP. I don't think it even does anything as I haven't mapped it.

I've done a lot since then, so no I can't unfortunately. Next time I'll include that too. What did you mean by "controller" - like Xbox controller or that stock robotics controller that I never use so I don't remember the name?

This is the correct answer, one I set them to pure white I got the lighting I was expecting.

Ok, functions, but not error free... LOG: https://1drv.ms/u/s!ApRsS13p52FhmTI7Sk5IpXXy7CH5?e=L7vozs My payload, but the rocket was the stock GPLV3 Craft: https://1drv.ms/u/s!ApRsS13p52FhmTOpyCN6qoGcjqbo?e=5yc46P

Found it. The problem occured because the root part was "Rockomax HubMax Multi-Point" and NOT a probe core or capsule. Once I re-rooted the craft so the RC-L01 Remote Guidance Unit was the root part, it worked correctly.

Perhaps a clue - variations of this thousands of times in my log

Anyone else experience this? Stage 1 (well, 6 because KSP counts from the top down...) 5 Liquid Fueled Engines Stage 2 4 SRB and Launch Clamps Hit "LAUNCH": Liquid engines fire up at full throttle. Hit Space to light SRBs and release clamps: Throttle goes to ZERO (should never drop below 33% per settings) Rocket flys with no guidance at all (no deflection of the Pitch Roll Yaw needles) fall over and eventually into the ground. Tried putting all engines and clamps in 1st stage, no good. Tried manual throttle and SAS and I can throttle up and SAS turns on (shouldn't both ignore me?)

I'll give it a try... I take it its not a "known thing" around the community then.

I've been away, probably over a year since I touched KSP. Yesterday I updated the game, and my mods (fairly short list, none of them lights). I started a new save, again. Launched a station, again. Put some lights on it, again. Once in orbit I hit the lights, and while the science lab windows are nice and normal brightness, the illuminator look like candles. I remember them casting a crazy amount of light and looking just ad "lit" as the windows. Did they get nerfed when the new nav and dome and spot lights got added? Is there a way to revert them if so, because right now they are pretty useless. Like inhave to switch them off to know for sure they are on!

Yes, no and yes. :). I'll try that version on the same mission and see how if differs. Thanks!

I have a different problem with Landing Guidance. It simply refuses to work. I'll see warping to braking maneuver but it doesn't warp, I'll start from a stable orbit and select land at target and nothing happens, I try to "help" it along and sometimes that gets things moving but I'm the end it doesn't brake and I crash. I saw a post about a month old saying it was being worked on but before I go the trial and error route, is there a version of MJ that has a work landing guidance in KSP 10.1? It's really the only thing I want it for, targeted landings. I'm assembling a mun base.

I seem to have found weirdness with resource transfers. Docked a craft to a space station. Moved monoprop from one ship tank to a station tank, worked as usual. Tried to move monoprop again after that, from the ship tank to a different tank on the station and nothing... try again from any tank to any tank (intra-ship, intra-station, or between docked craft) and while the buttons go from IN/OUT to STOP as usual, nothing moves.

No I didn't... Fix it that is. Welcome to the world of incomplete testing. It never, ever.... EVER....EVER occurred to me that a piece of code, meant to shed parts in a game with 6 degrees of freedom, wouldn't have it's directional vectors referenced in some way to the part. Nope. The part can have it's mass, force, AND DIRECTION of ejection specified, but that direction is relative to the UNIVERSE... I kept cheating my craft into orbit to test the direction of ejection, and once the panels blew OUT and not sideways thru the craft I thought it was all good. Later in game play I noticed it was still wrong - did some more complete testing, and found out that all I did was make sure the panels would travel Up and Down (relative to the camera in orbit mode) with no regard what so ever to the orientation of the service module. This module is used in many places where it would go unnoticed (engine shrouds for instance) but in the case of the LV-N engine, it can be noticed - and this in fact leads me to recall that this has been the case for a LONG LONG time. Seems rather stupid to me - heightened enormously by my embarrassment at not being more thorough and making assumptions.

YES PLEASE!!

@PART[ServiceModule25] { @MODULE[ModuleJettison],0 { @jettisonForce = 30 @jettisonDirection = 0 1 0 } @MODULE[ModuleJettison],1 { @jettisonForce = 30 @jettisonDirection = 0 -1 0 } } Requires Module Manger (and Making History of course), changes the panels to jettison OUTWARD as expected rather then laterally... NOTE: Does not address the whole "bay is open but parts think it's closed" bug NOTE: If craft is spinning when the panels are blown, you'll see some really odd behavior. Take one to orbit and roll before jettison; you'll see what I mean...

FWIW solar panel sun tracking tweak is still working in v1.8.1

That's another "helper" that ought to be stock.

Guys "look at what I can do under such difficult circumstances! Its easy!" To someone who is struggling is not helpful. I suggest some YouTube. Learn not so much ksp but orbits in general, scott Manley is good for this. Also consider installing mechjeb and just watch what it does. Then try the tutorials. You'll get your lightbulb moment went you pierce the mental barrier that is keeping you from "wrapping your head around it" Thats how I learned. That said, it is a real shame that something like navyfish's docking alignment indicator isn't stock. You still have to hand fly it, but it gives you some feedback on what's going on. Hell, Apollo had an eye piece and a target to hand fly their docking, it wasn't automatic and it wasn't "seat of your pants" like stock KSP.

Module Manager is the way to go. That way future updates won't stomp on any customizing you do. I wanted to make hull numbers so I whipped up some textures and made a cfg file to get them in the list of texture options. Slight correction tho: @MODULE[ModulePartVariants]{ ... } needs to be added around the VARIANT entries, else it won't work. Resulting in: @PART[sticker*]:HAS[#author[blackheart612]] { @MODULE[ModulePartVariants]{ VARIANT { name = Kerman displayName = Kerman themeName = Kerman primaryColor = #ADAFAD secondaryColor = #ADAFAD TEXTURE { mainTextureURL = MyFlags/Flags/kerman } } //More "VARIANT"s here if desired } } Took a second for me to figure out why my textures weren't appearing on the options. While I'm in here posting, //MODULE { name = FStextureSwitch2 in the cfg file results in nothing right? Because the MODULE is commented out, the following curly braces and their contents are in effect also commented out, if I understand correctly. If so, shouldn't that whole block be removed? It makes it a bit confusing - to say nothing of bad formatting/messy code.