Phineas Freak

@2willian2probably your problem is that you are using KSP 1.1.0 with a Kopernicus distribution for KSP 1.1.2: [WRN 06:41:23.920] [Kopernicus] Detected incompatible install. Current version of KSP: 1.1.0. Supported version of KSP: 1.1.2. Also, pinging @KillAshley (the god of Kopernicus) with some small issues: Venus & Mars use the "AerialRampKerbin" material for the atmosphere fog but Kopernicus complains that it is not valid. Venus also has a "05_NORMAL" rock material that was not replaced (probably missed). I am getting two exceptions regarding wrong atmospheric light colors. Judging from the location of the exceptions these are targeted to the Pluto and Charon atmosphere fields (might be wrong though): Log file Tested on KSP 1.1.2.1260 with the following mods installed: Kopernicus [1.0.3] Real Solar System [11.1.0] Real Solar System Textures [10.4.0] Edit: ninja'ed by @Blacks for the first issue.

You tell me! I was trying for approximately 5 hours yesterday to try and eyeball the DV maneuvers and the gravity assist. Without proper tools it is a recipe for frustration .

@rollsall RO engines are surface attachable. You do not need to use the procedural thrust plates (known sometimes for it's wobbling abilities). And, for the record, the type of the procedural side does not matter.

Unfortunately, the available images for the outer are either taken from far away (like Hubble) or with outdated technologies (Voyager 2 Vidicon). Still, NASA has a nice close - up of Uranus, shortly before closest approach: http://photojournal.jpl.nasa.gov/jpeg/PIA00032.jpg

@Whitecat106some more feedback: As @Qwarkkmentioned, it not possible to set a Station Keeping resource, even if the craft itself includes it and even after re - selecting it. The propellant selection, as noted by the messages, is recognized though. The above notification message does not occur when selecting a propellant while in flight view (example: setting the option right after a successful launch into a stable orbit). Although, as i understand, the propellant selection is meant to be done from the Space Center or the Tracking Station. Still, it would be nice to have that while in flight. Any debris on a sub - orbital trajectory are deleted if they get unloaded (outside of the physics range). Suggestion: a check for the vessel situation before removal. I got a lot of NullRef exceptions, to the point that i got 1 CTD and one runtime exception (half-CTD). Removing temporarily Orbital Decay stopped it. Logs and save file are provided at the end of the post. Still, a must-have mod ! Log file Save file Tested on a Windows 7 x64 installation with KSP 1.1.1230 (64 bit runtime) and the following mods installed: FAR [0.15.6.1] Kopernicus [1.0.2] ModularFlightIntegrator [1.1.3.0] Real Scale Boosters [0.12.3] Real Solar System [11.0.0] RSS Textures [10.4] RSS Time Formatter [1.0.1.0]

@d.frisonyou can get the ROMini from the official RO GitHub repository: Link (right - click on the page and save it as "ROMini.cfg" inside your GameData folder). It should be OK for the current version of RSS.

@FITorionfor the Saturn rings: navigate to the "GameData/RealSolarSystem/RSSKopernicus/Saturn/Saturn.cfg". The values for the parameters at the lines 109 & 110 should read "2500" and "1250" respectively.

@AlphaAshif that helps, there is a point at the code that specifically asks for "Kerbin": KK source code

Kerbal Konstructs probably expects the homeworld name to be "Kerbin" but in RSS this is changed to "Earth". The weird thing is that the latest version of KK for KSP 1.0.5 did not have this problem... Edit: more specifically: [ERR 16:34:24.561] KK: Couldn't find body "Kerbin"

Yes, each texture pack includes it's own configs to add the textures to the list.

I did a test run with some of the required and recommended part mods, along with 8K planet textures and a beefed up version of RVE (8K main cloud textures, 8K cloud details, separate cloud textures for every planetary body with atmosphere) and it was using approximately 10 to 11 GiB. So, 16 GiB would cover almost everything (excluding something like "install all the mods!"). Remember that: The OS might allocate more RAM blocks than the minimum required (to have some headroom against "RAM surges"). Unused RAM is useless RAM. Try to use as much as you can without exceeding the physical limits (SSD/HDD caching will destroy your performance).

@Gaiidenthere will be absolutely no reason to use the x86 version of KSP 1.1 with RSS/RO/RP-0 (and the amount of physical RAM that @PTNLemayhas installed clearly indicates that there will be no problems using the x64 KSP version). But this is getting off-topic now. @Lacksince we have a Ranger-like probe core, would it be possible to include a foldable solar array (non-retractable after use and non-rotating) for it? Something like the original Ranger solar array.

@Tricky14open the "000_zRealPlume.cfg" file (under the GameData/RealPlume/000_Generic_Plumes path) and remove the following line: @description ^= :$: Plume configured by RealPlume.: That will take care of your issue.

@sidfuRSS works fine with Kopernicus 1.0.2, even without it's binaries (and recompliling it for KSP 1.1 is not difficult). But you probably meant that the initial (1.0) Kopernicus release had bugs and that's true... Still, if @Whitecat106wants to provide an early release that would be not a problem. It may give it in fact a chance for testing before any official release of RSS.

@NecroBonesdid some more debugging with the latest RSB version and KSP 1.1: Graphics: Some flag decals with transparent backgrounds (like the stock NASA flag) have transparency problems when hovering the mouse above them, with the background disappearing. Affected parts include: Agena-D Upper Stage (RSBtankAgenaD) Atlas V 400 Interstage (RSBinterstageAtlasCentaur400) Atlas V 500 Interstage (RSBinterstageAtlasCentaur500) Ariane V Payload Fairing (RSB_PLF_ArianeV5m) Atlas V 500 Long Payload Fairing (RSB_PLF_AtlasV500_3) Atlas V 500 Medium Payload Fairing (RSB_PLF_AtlasV500_2) Atlas V 500 Short Payload Fairing (RSB_PLF_AtlasV500_1) Atlas V 500 Procedural Fairing (RSBfairingAtlas500) The flag decal for the Saturn V S-IVB is missing (the option for toggling it exists though - [Warning]: [FlagDecal Warning!]: Flag quad object is given as flagDecal, but no object found in model with that name). Part modules: The "Atlas V 500 Procedural Fairing (5m/3.81m)" base throws an exception while loading (not sure what is the problem with this part, the ModuleProceduralFairing is not different than the one from the stock 3.75m fairing base): [LOG 10:19:16.038] PartLoader: Compiling Part 'RealScaleBoosters/Parts/Etc/RSBfairingAtlasCentaur381/RSBfairingAtlasCentaur381' [WRN 10:19:16.042] PartLoader Warning: Variable RSBclass not found in Part [EXC 10:19:16.053] NullReferenceException: Object reference not set to an instance of an object ModuleProceduralFairing.WipeMesh () ModuleProceduralFairing.OnAwake () PartModule.Awake () UnityEngine.Object:Instantiate(GameObject) PartLoader:CreatePartIcon(GameObject, Single&) PartLoader:ParsePart(UrlConfig, ConfigNode) <CompileParts>c__Iterator4A:MoveNext() [LOG 10:19:16.057] PartLoader: Part 'RealScaleBoosters/Parts/Etc/RSBfairingAtlasCentaur381/RSBfairingAtlasCentaur381' has no database record. Creating. [EXC 10:19:16.061] NullReferenceException: Object reference not set to an instance of an object ModuleProceduralFairing.WipeMesh () ModuleProceduralFairing.OnAwake () PartModule.Awake () UnityEngine.GameObject:SetActive(Boolean) DragCubeSystem:SetupPartForRender(Part, GameObject) <RenderDragCubesCoroutine>c__IteratorB:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) <SetupDragCubeCoroutine>c__IteratorD:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) <CompileParts>c__Iterator4A:MoveNext() [LOG 10:19:16.065] DragCubeSystem: Creating drag cubes for part 'RSBfairingAtlasCentaur381' The decoupler FX is missing from some parts. Affected parts include: Agena D tank (RSBtankAgenaD) Castor 30 SRM (RSBengineCastor30) Castor 120 SRM (RSBengineCastor120) Saturn V S-IC tank (RSBtankSaturnSIC) The Castor 30, the Castor 120 and the RL10B-2 do not generate any surface FX ([ModuleSrfFX]: No IThrustProvider module found at index 0!).

@PTNLemayassuming that you don't use the x64 bit hack with 1.0.5, you are going to have problems with the 3.5 GiB memory ceiling of KSP. No amount of physical RAM can overcome this problem. With KSP 1.1 all these memory problems will be gone (until you reach your physical RAM limit).

@softweirthe PF base is not the issue, the problem is that @TK421dis using the "Fuselage" sides (that don't decouple) instead of the "Fairing" ones.

@TK421dyour "staging" issue can be replicated pretty easily, you just have to use the correct fairing type: The fairing bases themselves do not do anything to decouple the side walls (nor they include any kind of payload decoupler).

Slight increase in thrust, better VACISP, less exotic (read: dangerous, though not applicable) fuels, higher reliability, increased burn time, multiple restarts. If you are designing a custom upper stage then start by picking the "must have" feature(s) that you want to incoporate and work from there.

@Combatsmithenyep, perfectly! You won't find many mods listed yet although (that's to be expected).

@Reloading_thank you very much for the debugging, really appreciated! They will be fixed for the next release of RO.

The Atlas V CCB also has the ability to be transferred without a full length support trailer but true, not many rockets can manage this.

Unity 5 supports PhysX with two different ways, via the CPU (software) and via the GPU (CUDA hardware acceleration) but you have to explicitly enable the GPU option for your game. KSP devs decided that enabling GPU acceleration would be bad for any players that use AMD cards and do not support the second option. So it is normal that you see 0% utilization on the second GFX card. For more information: High-performance physics in Unity 5

@przybysz86, @corbett when all the required mods are updated (approximately 20 mods, 8 already updated) and RO itself is updated (SoonTM). On a more serious note, just wait. KSP 1.1 was released 11 hours ago and not every modder has time to update his/her mods. Also, remember that Nathanael is part of the dev team and his modding time is currently limited.

@Kirk0007go into your KER installation and copy the "Settings" folder somewhere else. Then, after you install the newer version, copy the folder back. Be careful: i do not know if a new (or a missing) setting or option does can cause a problem to a newer version.