Stone Blue

So what version of KSP are you on, are you using the latest version of KS, with the all the fixes posted above? DO you have any other mods installed?... Have any screenshots? DId this just happen once, or does it CONTINUE to happen? Upload your KSP.log & output_log.txt somewhere on the web, & post links...

Ahhh... My bad... I didnt connect that you wanted it for 0.90, which is pre-DDS.... The current version has .dds textures... I've got the 1.0 version of this mod for KSP 1.0...It should work for 0.90, as it wasnt converted to .dds till v1.1... I'll PM you a link to it... (I'll host it on my GoogleDrive for a couple days, then I'll take it down... So grab it quick) Doh!... I forgot DDSLoader could be used as well...

OK to include GPS constellations with KerbalGPS (Figaro)?

Yup...Me three...

http://forum.kerbalspaceprogram.com/index.php?/topic/100469-kspblender-blender-addon-for-importing-craft-files-now-with-complete-mod-support/

Hmmm... OK, so this "mod", really ISNT a "mod".... But more like a collection of welded subassemblies? It might be better to remove "Mod" from the name and OP, and have a moderator move this to The Spacecraft Exchange forum... ???

Hmmm... I'm still not sold on a 500km orbit, but thats just me My rationale for a 1000km orbit, is that 4 Comm16s (2500km range): are just under max. range to talk to each neighbor (2262km), leaving a little bit of room for drift... their sphere of coverage, almost completely envelopes Kerbin.. (So sats within 70-100km orbits, with high inclinations should still be covered, as well as ALL of Kerbin LKO: from Kerbin's surface to almost to KEO...) they cover out to just a hair past KEO (2863-2869km), so no other antennas needed, once you expand out to KEO with the network SO all that, with just 4 tiny, 7-10 part sats, and all done with ONE launch... AND, if I have unlocked the Comm32, I skip the LKO network and Comm16s, and go straight to 4 or 6 sats in KEO, and consider my LKO network DONE...

Dont need the DP-10 on each sat... Just ONE DP-10 on the LAUNCH vehicle... On manned flights, I usually put it on the command pod (which will be re-entering and landing), or for unmanned launches, I usually put it on the 1st stage (just make sure you have at least a Comm16 or someother antenna on the part of the craft that will go to orbit) To get the spacing right (and Snark and I obviously have different methods), that is what using resonant orbits is for: If you release a sat at the same point on each orbit, the spacing will automatically be correct (IF you have the proper resonant orbit for the amount of sats you want to deploy, in a given orbit)... Again, that website I linked like 4 times will GIVE you the proper res. orbit (basically just the height of the PE you need)...

NIce... Would be kewl if someone replicated that for KSP's Kerbol system...

DP-10 range is WAY too small for relay use... You would need a LOT of them, (like 14 sats in a 400km orbit), and coverage would only be for a (relatively) narrow band... For probably less cost, time & effort, you could get better coverage with just 4 Comm16 sats... Have you looked at the Visual RT Planner site that both I & Alshain have posted? The main window shows pink circles, representing the range coverage of selected antennas... You'll see the DP-10 is only good for (relatively) very short distances... Sorry, I cant really answer about necessary dV right now... I'm too lazy to do dV calcs, or even to use KER for it, wen I build craft... So I typically over-build my craft a bit, as far as fuel & propulsion... I usually tweak them as needed once I've launched a couple of times, and see how far my 1st setup gets me, and/or how much fuel is left over, or too short... I'm sure Alshain, or someone can post up actual numbers...

1. Yes... Just make sure you have a Comm16 on each sat 2. That orbit is way too low for relay network... For Comm16, I would place them in optimal orbit of 1000km... So you would go to 1000km, circularize, release 1st sat, then drop PE to 441.5km.... Then on each orbit, when you hit AP (1000km), you release a sat, until all 4 are deployed... They should be deployed @ 90° at that point... And youre done... If you look at the website I posted ( Viual RemoteTech Planner ), you can see in the very bottom, left box, it shows both the upper and lower resonant orbit for your target orbit. For example, on the right, enter: Body: Kerbin; Count: 4 (sats); Altitude: 1000 (km); Antenna: Comm16 You'll see in the Multiple View window at the bottom, the lower resonant orbit for this setup is 441.5km Also, the Night View window shows how much battery storage you need... The Multiple View window is the one that shows the upper & lower resonant orbits... (Use the Lower one when you can, as it requires less dV to "fall" into it from your target orbit, than to "climb" into the upper orbit from your target orbit...) 3. I pretty much covered this in 2. Except you release each sat at AP, if you are in a LOWER resonant orbit...Release at each PE ONLY, if you are in an UPPER resonant orbit... As to circularization, theres two ways to do it: As the launch vehicle reaches release point (AP or PE), circularize the WHOLE craft into target orbit, then release the sat, which is now in the proper orbit, burn launch vehicle back into resonant orbit, warp to next release point and repeat till all sats are deployed As the launch vehicle reaches release point (AP or PE), release the sat, switch vessel to the sat, circularize the sat, switch back to the launch vehicle, warp to next release point and repeat till all sats are deployed The difference between the two, is that in #1, your launch vehicle does all the burns that puts the sat into its target orbit... Thus you can have smaller, cheaper sats because they have no fuel or propulsion In #2, each sat must have its own fuel and propulsion to circularize itself. Personally, i use #1... I DO put the small toroidal LFO tank, and the smallest ANT motor on each sat, for fine tuning each sats orbit, as well as for future correction when the sats drift...

I would recover the craft, go to VAB, place a DP-10, and relaunch...

Have you TRIED the current version?...This is a relatively simple mod, and may be backwards compat that far, or even earlier...

Yes dishes are considered antennas... However, at this stage in your game, i would NOT be using dish antennas... Just stick to omnis until you start sending craft out to Minmus or beyond... If you have a dish currently on the craft you are launching, then it needs to be activated, AND it needs to actually be set to target the craft in KEO... But again, dishes are not best for inner Kerbin SoI... If it were me, I would pull all the dishes and replace with omnis...

dbl post Moderator, pleeze delete this post...

It sounds like you have NO antenna on your probe?...Or it is not activated...?? IF you are on the pad with launch stabilizers, you should ALWYAS have a hard-wired connection to KSC... If you are on the pad WITHOUT stabilizers, then you need SOME kind of antenna, properly activated/targeted/powered, whatever... Depends on the antenna...

Most people place a DP-10 antenna (500km) on all their launch vehicles...This will connect the ship to KSC, until it goes around the curvature of Kerbin and loses line of sight (LoS) to KSC... Once THAT happens, thats where your 4 LKO comm sats take over... With 4 sats in LKO (700-1000km), they WILL rotate around Kerbin, and none will be permanently DIRECTLY above KSC, but there will ALWAYS be at least one or two that will be over the horizon, within LoS of KSC...

Ummm... Well, first, I find dishes to be either overkill or useless for Kerbin SoI... Also, Comm16 does not have the range to reach Kerbin surface from keostationary, AND you would need to place at LEAST 5 to get decent overlap at KEO... Also, I guess I'm not sure what you are trying to accomplish? Being new to RT, here are two links that should be helpful: RemoteTech Player's Guide and Visual RemoteTech Planner Your best bet for your 1st, starting network, is to get 4 small sats, with ONLY Comms16 in an LKO, spaced 90° apart, between 700km-1000km.... Save putting anything in KEO til later...And THOSE are where you should put your dishes, which, IMHO, are best for use BEYOND Kerbin SoI... Since these should be extremely small sats (7-10 parts), I usually place them using a single launch... Using a resonant orbit, which the Visual Planner shows, you can deploy them in the proper spacing (90°) around Kerbin...

^^ I'll just add that VOID is also a nice, "lite" informational display mod, as it doesnt have all the dV calaculators in the editors, or the advanced functions of KER, or the auto pilot modules, flight computer, or maneuver planners of MJ. It DOES display amost as much info, and has several customizable HUDs available. It is also PARTLESS... VOID - Vessel Orbital Information Display

@gamerscircle Not sure this will help with your current issue, but being new to RemoteTech, maybe this will help you in the future. Its an online website that helps plan your networks, orbits, and necessary battery storage. It also shows resonant orbits for deploying multiple sats from one delivery vehicle (You can use resonant orbits to get the proper spacing between sats): Visual RemoteTech Planner for KSP

Open the error.log file and at the top, it shows the RAM usage when KSP crashed...

just do a Google for like " kerbal surface nav lights " and it should come up....

@WolfAngriff You can write yourself a simple .cfg patch, that uses Module Manager, that can basically make ANY part you want RT compatable... Which modded part is it that you want RT compatable?... There may already exist a .cfg file for it....

Thats why I mentioned Google... You can specifically search JUST the Kerbal forums, by adding this into the search field with your search term: site:forum.kerbalspaceprogram.com I mentioned the forum search, cuz someday it MIGHT actually get fixed...lol Either way, my point was, new members also need to actually do some footwork and do some actual SEARCHING (HOWEVER they do it), before posting...

If you're on Windows: techpower GPU-z