Poodmund

Was one end of the strut connected to something previously?

Hey VITAS, is there a way of transferring ownership of a Spacedock entry if the original author is no longer active? I have been handling Outer Planets Mod for around 5 years now but the Spacedock entry is still left in the state that the original author, Capt Robau, left it in back in 2016. The current mod repository is managed by myself with Capt Robau as a collaborator (https://i.imgur.com/sLC928v.png) which was discussed and confirmed via forum private messages back in 2017. It would be useful to gain control over the OPM Spacedock entry to be able to update it. EDIT: Resolved.

Update? OPM has not updated as far as I am aware... and I should be aware! EDIT: For what its worth, the latest version of OPM is now available via SpaceDock. I still highly recommend installing it via CKAN and if downloading manually, doing it via GitHub first and then SpaceDock as a backup avenue... but at least its up to date and on there now.

No idea. I think its more pertinent to state that; no, we don't provide support compatibility patches for Tweakscale. If Tweakscale provides support compatibility for ReStock then that's Tweakscale's prerogative and you would probably have a more insightful answer by asking in Tweakscale's forum thread rather than here, as the mod maintainer and its users can provide a good answer.

All good! Licensing is one of those things where it feels kind of annoying at first but its there to protect mod developers and the community and you get to grips with it fairly quickly.

YES!

@OneSaltyPringle, I've just seen that you have released your volumetric EVE mod using OPM-VO, congrats! I have just a few things that I want to suggest: The mod bundles modified versions of the OPM-VO giant planet textures that are licensed under an All Rights Reserved license (as specified in OPM-VO) and as such violates the OPM-VO license. I would like to grant you express permission to include these modified textures within your mod under the following conditions: In your installation instructions, advise people to install the mod ZeroMiniAVC to counteract the fact that MiniAVC is bundled in the latest release of OPM-VO. State in your mod page on SpaceDock that I have granted you express permission to include these customised textures that are ordinarily licensed as All Rights Reserved. Include a license in your mod distribution package. This is a good place to start if you want to have a quick overview of your choices: https://forum.kerbalspaceprogram.com/topic/41210-license-selection-guide/. Be willing to list the mod on CKAN if/when EVE Volumetrics mod gets made publicly available. I encourage you to post your own thread in this development or releases sub-forum with as many screenshots and videos as possible. Looks real neat!

Yes, its the latest version, v20.4

No worries... thank you! The Module Manager Wiki is great: https://github.com/sarbian/ModuleManager/wiki

You can remove config nodes as they are patched, you'd do this by having your own compatibility patch called like 'PoodsOPMVOremoval.cfg' that would remove all OPM-VO EVE cloud layers and Scatterer configs: @EVE_CLOUDS:AFTER[PoodsOPMVO] { !OBJECT:HAS[#body[Sarnus]] {} !OBJECT:HAS[#body[Tekto]] {} !OBJECT:HAS[#body[Urlum]] {} !OBJECT:HAS[#body[Neidon]] {} !OBJECT:HAS[#body[Thatmo]] {} } @Scatterer_planetsList:AFTER[PoodsOPMVO] { @scattererCelestialBodies { !Item:HAS[#celestialBodyName[Sarnus]] {} !Item:HAS[#celestialBodyName[Tekto]] {} !Item:HAS[#celestialBodyName[Urlum]] {} !Item:HAS[#celestialBodyName[Neidon]] {} !Item:HAS[#celestialBodyName[Thatmo]] {} } } !Scatterer_atmosphere:HAS[@Atmo[Sarnus]]:AFTER[PoodsOPMVO] {} !Scatterer_atmosphere:HAS[@Atmo[Tekto]]:AFTER[PoodsOPMVO] {} !Scatterer_ocean:HAS[@Ocean[Tekto]]:AFTER[PoodsOPMVO] {} !Scatterer_atmosphere:HAS[@Atmo[Urlum]]:AFTER[PoodsOPMVO] {} !Scatterer_atmosphere:HAS[@Atmo[Neidon]]:AFTER[PoodsOPMVO] {} !Scatterer_atmosphere:HAS[@Atmo[Thatmo]]:AFTER[PoodsOPMVO] {} @EVE_TEXTURE_CONFIG:AFTER[PoodsOPMVO] { !OBJECT:HAS[#name[PoodsOPMVO/Textures/cloud]] {} !OBJECT:HAS[#name[PoodsOPMVO/Textures/gas]] {} !OBJECT:HAS[#name[PoodsOPMVO/Textures/sarnusStorm]] {} !OBJECT:HAS[#name[PoodsOPMVO/Textures/aurora]] {} } Then you instantiate all your patches after that. If you include this patch above in your mod, users should be able to install OPM-VO, then your mod alongside, without needing to have any additional textures and you can refer to the texture paths in OPM-VO. This way you get around any licensing issues with OPM-VO and you also retain the file structure integrity of the original mod which promotes compatibility and extensibility.

In your configs, could you just refer to the texture path within the OPM-VO folder? Then there would not be a case of additional, large textures being loaded taking up resources. Also seemed like the textures were horizontally flipped as the some of the cloud patterns appeared as if they were leading with the trails rather than the front edges (might have been an issue with my original textures or may be a DDS flip issue). For reference, the atmosphere on Thatmo is INCREDIBLY thin, even in my original implementation the atmospherics were too pronounced. There would definitely not be clouds, maybe just a small haze on the horizon, similar to what we saw with the Pluto New Horizons images.

If your mod is just configs i.e. you install OPM-VO and then install your configs mod over the top... then absolutely go ahead. Its your work! I couldn't stop you from doing so even if I wanted to. For full disclosure, please do so! I'd love to see it. In other news, my hard drive with all my OPM-VO work on it failed and its gonna cost a upwards of £400 to even attempt data recovery. This project may be officially a goner.

What would happen if you changed these values: https://github.com/ChrisViral/RealChute/blob/master/Output/GameData/RealChute/ModuleManager/Stock_RealChute_MM.cfg#L213-L216 To these: https://github.com/PorktoberRevolution/ReStocked/blob/master/Distribution/Restock/GameData/ReStock/Patches/Utility/restock-parachutes.cfg#L28-L31 Would that work?

Yeah, the reasoning behind that is that they do not have the ModuleCargoPart module. Probably something I could/should look into. Thanks for bringing it up. The KSP Part Volumes mod will work to fix this but, by default, it is set to not add this module to fuel tanks. You can change that in the mod settings, as listed in the mod's OP:

I'm dead. Apparently.

I prefer the Deep Star Map. These shots are incredible by the way, thank you for sharing.

Its literally like a few hours worth of work to resolve a lot of these issues by a responsible webmaster. Do we not have a dedicated forum webmaster anymore? There's been a few issues popping up over the past month(s) with no movement.

Uninstall Scatterer and the Scatterer-Default Config entries first, then install Spectra and Spectra Scatterer as its recommendation.

I can confirm this behaviour with the 1.875m Mk2 Pod. Stock 1.12.5: ReStock 1.4.3: You can see that with ReStock installed, the Mk2 Pod experiences a sharp 15-20 degree angle of attack pitch when not being occluded by the heatshield. It experiences this angle drift from retrograde all the way to the surface. Looking at the config files I can't see any reason as to why this would occur, the the models/transforms in Blender.

Ah, so it was the allure of a fuller vocabulary that drew you to Quenya, rather than any Middle Earth bias! I should have known – after all, even John Ronald Reuel knew that when you're picking an Elvish language, it's quality over Quendi-tity! ... I'll get my cloak.

You have some shady ass version of a Module Manager tampering library installed. Bin off that weird bootleg copy and only install the proper version: i.e. delete the following files and give it another go: Kerbal Space Program\PartDatabase.cfg Kerbal Space Program\Physics.cfg Kerbal Space Program\GameData\666_ModuleManagerWatchDog.dll Kerbal Space Program\GameData\ModuleManager.4.2.2.dll (you only need the latest version of MM installed, you can delete the old version) Kerbal Space Program\GameData\ModuleManager.ConfigCache Kerbal Space Program\GameData\ModuleManagerWatchDog (whole folder) Also I have no idea what patches you have in Kerbal Space Program\GameData\Custom_FARAeroData.cfg but its a good idea to get rid of it to test this. Then try it all again and that should effectively give you a fresh instance of KSP with only FAR and ReStock installed with the necessary dependencies.

Any comment on this? @ManeTI?

No more additional bodies, correct.

Well... if ScrapYard requires Contract Configurator as a dependency (which the above issue would suggest) then it would have been helpful if Zerokerbal could have stated as such on the NetKAN metadata when they last updated it in January. [snip] https://github.com/KSP-CKAN/NetKAN/commit/e058d3de5db4c7215dc3dee4bae12720bd7cc9d2

As its not an OPM issue but an AVP issue, you probably want to ask in that thread as you'll more likely receive support to resolve the issue.