Jump to content

Thomas P.

Members
  • Posts

    384
  • Joined

  • Last visited

Everything posted by Thomas P.

  1. Thats interesting. The SpaceCenter uses FlattenAreaTangential instead of FlattenArea, so maybe using that instead works better? I have distant memories of FlattenArea being messed up, but I could be wrong.
  2. Feel free to take a look at the KittopiaTech code, I have a basic planet thumbnail generator there. I cannot guarantee proper lighting, it seems to work fine just after the main menu scene was loaded, so KittopiaTech generates them there and caches them. https://github.com/Kopernicus/KittopiaTech/blob/master/src/UI/PlanetSelector.cs#L131-L168 https://github.com/Kopernicus/KittopiaTech/blob/master/src/RuntimePreviewGenerator.cs Solid bodies and gas planets work fine, Stars are very... white
  3. The calculation is the following: Your input variables are: latitude of the desired point (lat) longitude of the desired point (lon) altitude (above sea level) of the desired point (alt) radius of the planet (rad) I am going to assume that the sin and cos functions accept degrees instead of radians. lat = lat - 90 x = (alt + rad) * -1 * sin(lat) * cos(lon) y = (alt + rad) * cos(lat) z = (alt + rad) * -1 * sin(lat) * sin(lon) X, Y, and Z are the three values of the position vector you need to enter. And if you are a terribly lazy person like I am you can just do this: FlattenArea { Position { latitude = <latitude> longitude = <longitude> altitude = <altitude above sea level> } }
  4. I'd appreciate if you could ship your fork with a version number that the mainline Kopernicus probably will never reach (like 1.4.5-105 or so). Just to avoid confusion when I make an actual 1.4.5-5 release. I will look at your PR as soon as I got time, thank you!
  5. Replacing System.cfg is an absolute no-no and makes uninstalling your mod nearly impossible, or really hard at last. The users would have to reinstall Kopernicus completely, which might be difficult (especially when you are using CKAN). Thats why every planet pack that exists uses ModuleManager to modify the system. It's changes are not persistent and can be mixed with other packs or modifications. Also, RSS should already be compatible with the 1.4.* builds of Kopernicus, since the config layout didn't change since 1.3.1-7 (the version that is linked in the OP). So it might be easier to just submit your patches back to the RSS upstream instead of releasing your own fork.
  6. And we have Kopernicus & Kittopia 1.4.5-4 (+ Kopernicus-Backport 1.3.1-13) which should fix even more issues with LandControl (some of them were introduced by the last release), which mainly caused this: @Drew Kerman I am not sure, but it looks like your issue could have been caused by the same bug, so there is a chance that 1.4.5-4 fixes it.
  7. Kopernicus and Kittopia Tech 1.4.5-3, as well as Kopernicus-Backport 1.3.1-12 have been released. Changelog: - More fixes to LandControl - Fixed the custom period setting - Added the possibility to set a custom orbit icon (`Orbit { iconTexture = ... }`) - Fixed an issue with the Kittopia exporter that prevented exports on windows. (thanks to Gameslinx for actually sending me a logfile)
  8. We can't help you if you don't help us. If you don't want to help us then you don't want us to help you. Simple as that.
  9. Press "Export Body" on the bottom of the body editor window and take a look at GameData/KittopiaTech/PluginData/<body name>/<timestamp>/<body name>.cfg
  10. Unfortunately, I cannot find any issues in your cfg.. I also have no idea why the bug you described occurs.
  11. Probably that he was banned there after he repeatedly copied the textures and configs of others. Also, I can't join your discord dm or whatever, I am not in a server where you are too so DM'ing probably won't work. Just make your bugreport here in the thread and I will take a look at it.
  12. Those messages might read like an error but they aren't actually harmful. They only say that something tried to access an unloaded texture when Kopernicus didn't expect it to be accessed, so it has to hotload them. Normally Kopernicus checks for certain situations and loads the required maps automatically. Only the error message is a bit... verbose.
  13. I released Kopernicus & KittopiaTech 1.4.5-2, as well as Kopernicus-Backport 1.3.1-11. They should fix the bug that was introduced by 1.4.5 (or 1.4.4? No idea), that caused every planet that had "createColors" set to "false" in the LandControl config. For some reason Squad decided it would be a good idea to set them to true automatically, and therefore ignoring the value of the variable completely. Further changes include a logger overhaul that should harden it a bit (thanks to Corfiot!) and an experimental setting to specify a custom orbital period (Orbit { period = ... }) (thanks Sigma!)
  14. I released Kopernicus 1.4.5-1 and Kopernicus-Backport 1.3.1-10, as well as the first version of the new KittopiaTech on Github. (Links are in the OP as always) - Updated to KSP 1.4.5 - Integrated the Kittopia logic into Kopernicus code - Completely rewrote Kittopia to display windows based on the Kopernicus loaders - Added a new normal map generation algorithm, thanks to Sigma88 Additionally, the backport should include the correct MM version now. Over the past months I have been working on moving the features of the old KittopiaTech into the core code of Kopernicus, and preparing it's loader classes so they could be used to generate a complete planet editing UI. The reason for that is that I have often forgot to update or bugfix KittopiaTech, simply because I mostly concentrated on Kopernicus. The consequences of this are: First: A rewritten KittopiaTech that uses the Unity 5 UI system and should work much better and less buggy than the old one. Yay, I guess? Since all the actual functions are moved to Kopernicus, they will change with Kopernicus updates. KittopiaTech is just a generic UI-generation shim that uses the Kopernicus loading classes and their attributions to show you an UI. It is now less likely that KittopiaTech breaks, even if I do major Kopernicus changes, since there are only a few points where it interacts with Kopernicus directly, as opposed to the old version. Due to KittopiaTech using a different UI framework now, the look and also the behaviour have changed. Instead of a split window with occasional popups for editing colors etc., everything is a popup window now. Those windows can only be closed by clicking the button that opened them. Thats simply a limitation of the PopupDialog and DialogGUI classes I had to use (i.e. KSP's wrapper for the Unity 5 UI. I could have used the UI directly, or kept using the old GUI system, but that would have probably made me abadon the project after two weeks. :/). A workaround is to open the Kittopia Window Manager by pressing Ctrl + T, and closing the windows from there. I hope that everyone can work with this, because I really had no alternative to this wonky behaviour. (all this stuff was the reason for the delay btw, I didn't want to delay this even more)
  15. I think its time for some status update from me here... Unfortunately I doubt that I am going to have the time or the motivation to work on this mod at the moment or in the future. I mainly made this as a proof of concept to show that such a mod is possible and never expected that a lot of people would play with it, so I never cared as much as I cared for Kopernicus. Also, some of the limitations of KSPs planet system are a real time killer. (Regenerating the whole system cache if you want to test one thing etc.) If anyone out there wants to adopt this mod, either just to maintain it, or to add some cool features to it, feel free to do so. If you need any help with understanding what it does, and how it does it, feel free to shoot me a message in the Kopernicus Discord server, or send me a forum PM.
  16. When everyone stops asking for it ref-returns are a C# 7 feature, which means you need VS 2017 to compile them. If you don't want to upgrade your installation (I can understand that, last time I tried my system got cursed), you can remove the refs and add this to your GameData to make sure the native byte array method isn't used and cannot cause memory leaks: @Kopernicus:FINAL { %useManualMemoryManagement = False }
  17. https://github.com/Kopernicus/KittopiaTech-Legacy Updated the OP too
  18. The two vectors are for scale (first one) and position (second one) of the image. I haven't experimented with the position value, you can simply leave that as (0,0). However, by setting the scale of the image to (0,0) you are shrinking it to a size of 0x0 pixels. Setting the scale to (-1, -1) would stretch the image to fill out all available space, setting positive values sets a fixed amount of pixels in width / height. The color parameter can be used to display the same texture in different shades. It is essentially a mask that is applied to every pixel of the texture, by multiplying the channels with each other. So, if a pixel has the color (1, 0.5, 1, 1) and you pass (0.25, 2, 0, 1) as the color parameter, the final color that is rendered would be (1 * 0.25, 0.5 * 2, 1 * 0, 1 * 1) = (0.25, 1, 0, 1).
  19. You mistyped Material. Unrelated: I really don't see the need for three threads for the same mod tbh.
  20. Thats called Kopernicus OnDemand Loading, it unloads the textures that are not visible or required to build the terrain - but the planet packs have to support it.
  21. We are excited for your contribution then. On the other hand, you want to contribute to so many mods on the forums, that you might run into time issues there.
  22. That place is called GitHub issues, sadly most people don't use it EDIT: Kopernicus 1.4.3-2 and Kopernicus-Backport 1.3.1-9 have been released! Changelog: - Fixed a huge FPS drop when Kopernicus is installed - Fixed cbNameLater breaking orbit line colors - Added the ability to remove launch sites added by MakingHistory (removeLaunchSites in the Kopernicus node) - Readded and fixed the PQSCity modloaders
×
×
  • Create New...