![]() ![]() I don't usually make requests for things, But how hard would it be to add the ability of this mod to also allow changing the stock sunflare texture? in the assets files the texture in question is called "Sun_Flare.tex" and normally looks something like this: ![]() If there's no license included in your post, it will be assumed to be CC-BY (can be reused, as long as credited) Make sure that you upload it as a png or some other non-lossy format Add a GUI for changing NavBall texture in-game.1.1 - Fixed issue preventing NavBall texture from being changed if the vessel doesn't have an iva view.Folder can now be renamed and/or moved anywhere, as long as it's under KSP's GameData dir 1.1.a - Fixed working directory issue when KSP is launched by an external program.1.2 - Fixed an issue that caused only a single instance of the flight and iva NavBall to be changed.1.3 - Fixed a rare bug somebody had once removed some debug code that caused unnecessary log spam each time the plugin loaded.1.6 - Updated for 1.3 changed logging system.The texture will replace both the fl ight and IVA view unless the appropriate option is disabled You can edit the color (RGBA floats) and/or supply your own emissive texture. The stock IVA navball uses an emissive texture to make it a little more readable. For example, if you put your custom skin inside the skins folder and called it "mySkin.png", you would set TextureUrl = mySkin or TextureUrl = NavBallTextureChanger/Skins/mySkin The texture urls can be fully qualified or relative to the skins directory. Edit the config file inside NavBallTextureChanger/PluginData/NavBallTextureChanger/settings.cfg to your liking. Place the NavBallTextureReplacer folder into your GameData folder It works all areas where you could see a NavBall (flight, map, IVA) and easily allows you to substitute your own replacement. You can now change it to any texture you please through this simple plugin, originally made by continued by yours truly. It greatly simplifies the coding required in a mod to support one or both toolbars, it gives the player the flexibility to decide how to control the buttons, and, moving forward, makes maintaining a mod much easier.No longer do you have to kee p the same boring NavBall texture. And in this case, I felt that it was well worth my time to convert all the mods that I support to this new method. Keep in mind that modders do this as a hobby, and, to "scratch an itch" in other words, a modder will make a mod because the core game is missing something that HE/SHE wants. And, since I'm the one doing the work, it's my decision as to whether it is worth the time or not. The effort it takes to convert a mod from using the stock toolbar to using the ToolbarController is usually about 15 minutes work, except in a few strange cases. What I am questioning though is it really worth his time to continue a mod and then have to develop an extra dependency that needs to be applied to other mods for the sake of managing some UI buttons? We all appreciate the time and effort that LGG has sacrificed from his personal life so that we can continue to use these mods. If you see ckan errors you did not correctly remove the blocks, try again from your backup being mindful of removing exactly what is specified below, including the commas. You should get exactly two results, both of which need to be removed along with some of the lines around them, see the examples below. Search for "GameData/FShangarExtender/settings.txt". Make a backup copy of it just in case.Ĥ. Using a text editor like in a text editor like Sublime or Visual Studio Code, open the registry.json file.ĥ. Find your ckan registry.json file located in your CKAN folder, probably something like c:/Games/Kerbal Space Program/ CKAN/registry.jsonģ. To resolve you need to edit your registry.json file and remove the references to the original files:Ģ. So if you removed the original HangarExtender manually CKAN still thinks it is installed. If you are getting an error message like the above it is because CKAN still thinks that the original "Hang arExtender" (note not the new Hang erExtender, notice the " a" vs the "e") is installed because CKAN keeps a registry of everything it has installed. * HangerExtenderExtended wishes to install GameData/FShangarExtender/settings.txt, but this file is registered to HangarExtender * HangerExtenderExtended wishes to install GameData/FShangarExtender/FShangarExtenderIconShrink.png, but this file is registered to HangarExtender HangerExtenderExtended wishes to install GameData/FShangarExtender/FShangarExtenderIconExtend.png, but this file is registered to HangarExtender The following inconsistencies were found: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |