Poodmund

As someone who tweaks the EVE configs for the planets, can I just completely delete the mod checking part of this pack as it keeps throwing hijinks about and my OPM planets revert back to stock as I guess it can't detect which pack to use?

When attaching my SRBs I stick them on the decoupler, then offset the SRB so that the top of the SRB is touching the decoupler then offset the decoupler up higher in the stack. This is pretty much the same as said above.

I am getting this output to the log just before a crash upon load. Is this generated by OPM or by another mod (ATM?) conflicting with OPM? [EXC 22:12:05.722] NullReferenceException: Object reference not set to an instance of an object ActiveTextureManagement.ActiveTextureManagement.SetupLoaders () ActiveTextureManagement.ActiveTextureManagement.Start () [WRN 22:12:05.752] Cannot find preset 'High' for pqs 'Arane' [WRN 22:12:05.787] Cannot find preset 'High' for pqs 'Dhar' [WRN 22:12:05.804] Cannot find preset 'High' for pqs 'Es' [WRN 22:12:05.836] Cannot find preset 'High' for pqs 'Flo' [WRN 22:12:05.869] Cannot find preset 'High' for pqs 'Nuu' [WRN 22:12:05.901] Cannot find preset 'High' for pqs 'Oorma' [WRN 22:12:05.934] Cannot find preset 'High' for pqs 'Phoe' [WRN 22:12:05.966] Cannot find preset 'High' for pqs 'Putto' [WRN 22:12:05.999] Cannot find preset 'High' for pqs 'Rheis' [LOG 22:12:06.014] MFIManager Start Post RemoveModuleOfType. Current modules coVesselModule : JSI.RPMVesselComputer active=True order=0 ModularFI.ModularFlightIntegrator active=True order=0 PilotAssistant.FlightModules.AsstVesselModule active=True order=0 SolverEngines.SolverFlightSys active=True order=0 [WRN 22:12:06.422] Cannot find preset 'High' for pqs 'Hale' [WRN 22:12:06.439] Cannot find preset 'High' for pqs 'Ovok' [WRN 22:12:06.471] Cannot find preset 'High' for pqs 'Slate' [WRN 22:12:06.487] Cannot find preset 'High' for pqs 'Tekto' [WRN 22:12:06.519] Cannot find preset 'High' for pqs 'Polta' [WRN 22:12:06.534] Cannot find preset 'High' for pqs 'Priax' [WRN 22:12:06.550] Cannot find preset 'High' for pqs 'Wal' [WRN 22:12:06.566] Cannot find preset 'High' for pqs 'Tal' [WRN 22:12:06.582] Cannot find preset 'High' for pqs 'Thatmo' [WRN 22:12:06.598] Cannot find preset 'High' for pqs 'Nissee' [ERR 22:12:06.598] [PQS]: PQS already marked as started during Start() method. This is probably wrong! [ERR 22:12:06.598] [PQS]: PQS already marked as started during Start() method. This is probably wrong!

When you disable a contract pack, am I correct in thinking it removes any Active Contracts that you may have that are associated with the said contract pack that has just been disabled? If so, is there any way to counteract this?

The parts for this mod do not seem to be assigned to the Life Support category that Kolonization adds in the VAB. Am I correct in thinking this and can they be assigned to that same category for consistency?

Does the inclusion of the: ControlAntennaWithoutConnection = True ... line in the setting config file now render the RemoteTech XF redundant? Does it do the same thing?

Would rather that they wait and just release a more polished bug-free 1.1 solely for the modding communities sanity.

It seems like this may be the case, I am glad that I have raised a pertinent issue... even if I can't help with the solution. If I can get some spare time over the next few days I will test with Pluron-Khato and see if it works. The hardest part I expect will be getting the contract to generate; will probably just edit the persistent save file to get the contract to be honest.

The contract was just to point the antenna at that body/barycentre. Could it have been that the body, in this case Duna, being in the way and covering line-of-site of the Barycentre as it resides inside Duna and therefore blocking coverage? I appreciate that this is a RemoteTech and contract module issue also but I felt that it was best discussed here as the binary system feature was raising the issue.

I have also noticed that contracts generated from RemoteTech contract packs have trouble determining the "Coverage %" when aimed at a Binary System. For example, using: RemoteTech Contract Configurator Contract Pack: RemoteTech or Contract Pack: RemoteTech-Lite If you try to complete a contract that either points at DunaIke, or for myself with OPM, PluronKhato, the contract dependency of gaining i.e. 20% coverage of that system stays at 0% even when covered by a suitable antenna in Kerbin's SOI. Could this possibly be to do with the Barycentre's 'ghost' size being so large that the antenna is not actually covering any of the Barycentre? I'm not quite sure of the ins and outs of this issue but you may be able to have a better idea of what could be causing the coverage of the Barycentre to stay at 0% coverage, and thus causing the contract to not complete. I can always go into the debug menu and force complete the contract right now however by using Alt+F12 (Right-Shift+F12 for Linux) for anyone having a similar issue.

The latest Pluron-Khato update to add OPM compatibility seems to be working fine on my end. Thanks a lot!

That's cool, no need to worry. Happy to help out by spotting things that look erroneous. Thanks for the quick fix, in the time you turned it around, I don' think I could have got out there and back anyway.

With the hot-fix and now with 0.8.1 my Pluron & Khato are located quite a bit outside of OPM's, Neidon's orbit but the barycentre PluronKhato is located just outside of Jool's orbit. Is anyone else finding the reproducible? http://imgur.com/a/7oQ95 It seems the Pluron system is not moving at all. Running OPM and Trans-Keptunian hence the many orbital bodies.

No problem. I use CKAN and it was showing the latest release was downloaded but AVC kept on saying otherwise. I didn't want to touch the files in case CKAN stopped auto-updating it so I'm glad to see you released the hotfix as 1.0.2 on KerbalStuff as CKAN should now pull this down to fix it.

The version file included with 1.0.1 is still showing as 1.0.0 and therefore AVC is throwing up that it isn't the latest version upon KSP launch. Nothing breaking but may be confusing for some.

The config settings are specified under the ProceduralGasGiant module as shown in the example of Neidon below: ProceduralGasGiant { rampTexture = OPM/KopernicusConfigs/OuterPlanets/Textures/Neidon_ramp cloudSpeed = 60 hasStorms = false stormFrequency = 0 stormThreshold = 0 seed = 23871 distortion = 0.007 frequency = 6.218 lacunarity = 1.189 gain = 0.848 } The variables are specified there but the direction of rotation I don't think can be changed as its within the .dll hence why you can't get your tilted Urlum to work. Maybe the expansion could be changed to allow for different inclinations of rotation?

I would not remove EVE's cloud layers if the expansion is installed as I posted above, they can be made to complement each other's workings very well. With regards to Sarnus' rings, I do have the expansion installed, yes. Sarnus also gets a bit laggy when zoomed right in with the camera in and around the rings. I have not done this before with the camera so cannot comment as to whether its a new occurrence but something to be mindful of. I don't expect I would ever do that with the camera in game though unless landing on Ovok or Hale.

I fear that by changing the way Sarnus' rings work, this is now happening where the rings are overlaying EVE's cloud layers. I've been editing my EVE configs to tone the cloud layer Alpha channels down a bit so that the procedural generation is slightly visible underneath them. It complements it really well as you get the large cloud textures working on top with the Kopernicus Expansion working underneath to make the planet look different all the way round at all times. Real nice!

Also thank you SO much for putting this feature in. It makes searching through contracts to find one that you actually want to do a hell of a lot easier.

The stock contracts stay toggled off as intended, sorry for the lack of specificity. It seems it is the Contract Configurator Group contract packs that re-toggle themselves but it is only when going from the Space Centre to either the VAB, SPH, Tracking Centre or Launch Pad but not the Contract Building, R&D, Astro Complex or Admin Building. It would seem then it only happens when vessels are reloaded on scene change? Granted, this is on my modded install so I will do a fresh install later tonight and try to replicate the issue and if it still persists I will post a log and save folder. If it doesn't persist, I will see if I can track down a culprit mod.

I really appreciate the Contract Configurator Settings panel that was added, however, is there a way to get it to save the toggled contract groups as they all seem to toggle on when there is a major scene change?

I'm experiencing an issue with the "Ant" LV-1 where it is throwing up: [Exception]: NullReferenceException: Object reference not set to an instance of an object NullRefs in the VAB and then on launch the engine staging icon is not listed in the staging order. When launching a vehicle with an "Ant" LV-1 included the craft gets to around 300m/s and the camera zooms out and then this happens again periodically at higher instances of speed. The craft will eventually (around orbital velocity) instantaneously explode and accelerate up to crazy high velocity. I've also encountered heating issues with craft that include this engine where parts around it will rapidly overheat. The part in question is the "microEngine" and this was testing on a clean install with the latest build of VSR using commit 694e845ba2 26th Aug and occurs running at x86 and x64. To replicate this on a clean install I started a new Sandbox, then built the following craft, Mk1 Command Pod > FL-T400 Tank > LV-1 Ant Engine > TR-18A Stack Decoupler > FL-T800 Tank > LV-T45 Engine, with all the fire-able stages in separate stages. Also note that I first noticed this issue/bug when using my heavily modded install so it seems the problem persists at the clean install level. I noticed in the config file that there is a fairing jettison module for this engine relating to a tankbutt but I am not sure if a tankbutt is included on this engine, could that be the module culprit? Anyway, would someone please verify this issue too? P.S. I have also raised an issue on GitHub.

Did you realise that you can return to the current ship in Map View by pressing "Backspace"?

I've been getting exactly the same issue recently on scene change like yourself with the same line output to the log. I'll catch them next time it happens and upload them here too for reference.

Now that RLA has been released as a full version, I would like to second this request suggestion.