flaming_monocle
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Posts posted by flaming_monocle
-
-
Everything looks fine, it correctly loads & maps skybox. Does skybox fail to replace in the main menu only or also in the game? Skybox replacement in the main menu doesn't work 100%.
Ingame as well as menu.
-
https://www.dropbox.com/s/fyetow0zbl0yuex/KSP.log Looks like it mapped the 'GalaxyTex_[...]' but I'm not the best at reading these.
-
Letter case matters.
Could you elaborate? I'm using the same lettering from the .zip containing the Texture Replacer version of Rareden's Skybox...
-
Wait, is that what I need to see visor reflections? Mine are still labelled "GalaxyTex_PositiveZ" etc.. or does the EVAvisor picture over-ride them anyway? I'm sorry, I'm so slow sometimes
I think the envmap ones are the visor reflections, but I'm not sure. I mean, it's kinda 50/50, so...
-
I might just be stupid, but I've tried installing Rareden's Skybox (the modified one that works with texture replacer) and I can only get the kerbals' visor refections to work, not the actual skybox.
I have the files under:
/texturereplacer/default/GalaxyTex_NegativeX
/texturereplacer/default/GalaxyTex_NegativeY
/texturereplacer/default/GalaxyTex_NegativeZ
/texturereplacer/default/GalaxyTex_PositiveX
/texturereplacer/default/GalaxyTex_PositiveY
/texturereplacer/default/GalaxyTex_PositiveZ
/texturereplacer/envmap/PositiveX
/texturereplacer/envmap/PositiveY
/texturereplacer/envmap/PositiveZ
/texturereplacer/envmap/NegativeX
/texturereplacer/envmap/NegativeY
/texturereplacer/envmap/NegativeZ
This is what I see in-game:
Notice how the kerbal's visor reflects Rareden's skybox, whereas the actual skybox is the stock one.
Could anyone tell me what I'm doing wrong?
B9 5.0 pre-release (with download)
in KSP1 Mod Releases
Posted
Quick question, are there any plans to make some changes to the HX1, HX2, and HX4 docking port systems, like
1) making them interchangeable? allowing 4 HX1 ports to connect to one HX4 port, etc
2) making them stock compatible? allowing stock 1.25m, 2.5m, 3.75m and 0.625m parts to dock to them
3) adding new 5m (a la KW Rocketry) docking ports?
4) adding connect nodes onto the HX2 and HX4 that reflect the number of docking ports? Right now, there's just one central node that limits assembly configurations.
And that's all that I could possibly nitpick from this amazing parts pack. Very well done!