4x4cheesecake

Members
  • Content Count

    1,670
  • Joined

  • Last visited

Everything posted by 4x4cheesecake

  1. 4x4cheesecake

    [KSP 1.5.*] Outer Planets Mod[2.2.1] [25 April 2018]

    The Kopernicus thread is here: [snip]
  2. 4x4cheesecake

    ISSUES UPDATING TO 1.6

    Yes, there is a way. AFAIK, you can get every KSP version since it was available on steam but it is a bit more complicated. Since this is not specific for KSP but possible with every steam game, there are a lot of tutorials on this topic. I like this one: https://steamcommunity.com/sharedfiles/filedetails/?id=889624474 but you can find more by looking for "steam old game version" or similar on google (Valve doesn't provide full download speed for old versions, so the download will take a lot more time)
  3. 4x4cheesecake

    ISSUES UPDATING TO 1.6

    KSP 1.6.1 is the latest game version, to upgrade your game to this version requires to set the BETA version to "none", but if you want for any reason to upgrade to 1.6.0, that's not possible via the BETA settings.
  4. 4x4cheesecake

    Structural panels gone!

    They are probably blacklisted: The panels are planned for a future release of restock. Try to add a whitelist file to your GameData folder. Create a textfile, name it however you want but put the extension .restockwhitelist on it, i.e.: "panels.restockwhitelist". Open the file in a texteditor to add the structural parts: Squad\Parts\Structural\structuralPanel1x1 Squad\Parts\Structural\structuralPanel2x2 Save the file, restart the game and check again. If it doesn't help, please upload a log file
  5. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Hm...including the dropwdown list, we already have: yellow: update available, incompatible, no override cyan: incompatible, override green: compatible (orange: kopernicus) <- not colored by AVC Not sure if adding more colors actually helps to understand whats going on. Maybe we can find a different way to differentiate between "incompatible" and "incompatible by choice". I probably just misunderstood you. Let's assume you set "1.4.2 to 1.4.5 ➜ 1.6.1" (combined, as I understand your suggestion), 1.4.2 would look like your MIN and 1.4.5 would be your MAX. But this would also affect mods which are compatible from 1.4.1 to 1.5.1 because 1.4.1 < 1.4.2. I would expect that this mod wouldn't be affected because the KSP_VERSION_MIN is not covered by the range of the combined version numbers but the KSP_VERSION_MIN from the .version file is not the same MIN from the combined version numbers. It's a bit confusing, regardless if you combine the numbers or not, but combining them will look like you got some borders around the range, which isn't actually the case. At least, this is how I understood your suggestion, please correct me if I'm wrong Sure, I can do it this evening. I also just found a bug in my regex pattern, I'll fix it as well.
  6. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    @linuxgurugamer during your last stream, you said that you thought about adding a toolbar button for the override GUI so it can be accessed from a running savegame and not just during the loading screen/mainmenu. Is that still something you want to do? Otherwise, I would consider it a bug that the override window is not destroyed after loading a savegame. I also had a thought about the new default toggles: How about moving them to the center box and treat them like a mod but just add the ▶ button to enable the version override, like this: (just a quick shot for better visualization so far, not functional) IMO, this would create a "cleaner" look. At least, I would like to add a toggle to the advanced settings to enable/disable the default values, regardless where they are displayed (visible by default).
  7. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    The arrow buttons were there before the toggles for 1.3.*, 1.4.*... were added. The point of the buttons is to quickly add the (max) version of a mod to the version override. Also, the purpose of the version override is to affect multiple mods. If you want to enable the override for a single mod, use the "always override" option instead. Could be normal and intended, or a bug...depends on the .version files of the mods. I had some issues before when refering to a version number which ends with 'zero', so just to be sure: Did you set 1.4.0 to be compatible with something different or 1.4.*? Also, please name/link the affected mods/version files Open the "advanced settings" and put the mod on the ignore list via the toggle button behind the mod name. You will notice, that the color of the mod name will change from cyan (active override) to yellow (incompatible) Sometimes, the displayed version number can be misleading, for example if a mod got VERSION_MIN 1.4.1 and VERSION_MAX 1.5.1. In this case, the UI will show 1.5.1 behind the mod name but it will be affected by a 1.4.*, 1.4.1, 1.4.2,... version override. Maybe...but I guess this would be even more misleading because it would not represent the min/max range...more like a max/max range. I removed the sorting for some reasons I cant remember... maybe worth a try to re-implement it^^
  8. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    I see...thanks @linuxgurugamer I'll send you a fix for this one
  9. [snip] I'll take a look at the log though edit: Get rid of DDSLoader and the old ModuleManager versions, especially version 2.5.10. DDSLoader doesn't work at all and throws a big pile of exceptions. ModuleManager should ignore old versions but 2.5.10 throws an exception anyway. Kopernicus itself seem to work fine and so should kittopia, just one little exception there regarding the log, you can try to clean the "Logs" folder. (Located in "Kerbal Space Program/Logs"). On a sidenote: There is a newer version of Kerbal Engineer: https://github.com/jrbudda/KerbalEngineer/releases/tag/1.1.5.7
  10. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Uhm...the actual bug here is, that the dropdown list shouldn't be there in this case. I thought, I fixed that issue already... Out of curiousity: Does the dropdown list appear while the frequency is set to -1?
  11. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    I've noticed two issues regarding the new default toggles: 1) The toggle doesn't become enabled after adding one of the default values manually. Just type in "1.4.*" and you will see 2) The reset button doesn't affect the new toggles. The version is actually removed but the toggle stays enabled. I guess, part of the issue is the initialisation of the toggle states during the Start method so if anything else changes the compatibility state, the toggles are not updated.
  12. A cloud service like dropbox, google drive, etc. would work fine
  13. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Tried it and failed, I'll probably leave this task to LGG^^
  14. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Had to shrink the button to fit there, but the titel of the box pretty much describes what the button does: @Stone Blue @MOARdV @DStaal @linuxgurugamer
  15. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    I've added the button for three reasons: 1) You may want to disable the override feature without loosing your settings ("Reset" does the exact opposite: keeps it enabled but you loose all settings). 2) The UI should prevent some manual config editing (It's still necessary to set up the update frequency but I consider this a different feature so it doesn't belong into the override GUI.) 3) Some thoughts I had after adding the button to open the GUI, details below. The answer actually is: There is no difference for the user but internal. While it is disabled, AVC runs like before but if you enable the override, AVC will constantly check if any incompatible mod becomes "forced compatible"(at least while the GUI is opened). Not necessarily two steps: You can also use the key combination "modkey + 2", which was my inital approach to open the GUI. At this point, it wasn't even possible to open the GUI at all if there is no incompatible mod. I've added the button because it was requested, but I get your point. I had some thoughts at this point: After adding the button to the bottom of the dropdown list, I thought it may confuses people, if this button only appears, if there is actually an incompatible mod installed, so I've decided to keep the button all the time and again, I was worried it would confuse people if nothing happens when they press the button, so it got some coloring (indicated the state of the AVC processing which need to be done) and the GUI will open all the time. Since the GUI can be opened now all the time, it required some indication about the "enable/disable" state, otherwise you may end wondering why there are no mods listed and nothing really happens if you do anything there (like you did when you didn't find the enable button) and at the same time, as soon as you notice that this is something that need to be enabled, you start looking around for an "enable" button and if still nothing happens or you don't like it, you may want to disable it again. So, I've added this button Probably, I thought too much about it or in a different way than other poeple, but that's basically why this button exists When I think about it, I should also add an label saying "no incompatible mods detected" or similar, if someone enables the override while it is not necessary... Thanks for your feedback though I'm too concerned to confuse people even more by removing the button at all but I guess it is a good solution to move it to a distinct location and display the additional popup window while the override is disabled, even though it adds one step to reach the GUI (at least on the first use).
  16. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    I've already started to do some adjustments (as you can see above). I'll be back home in ~2 hours and move the button in a distinct position as well.
  17. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    @Stone Blue That would be the position I had in mind but there would be still a chance to miss the button. I guess a separate window would be a better solution: If the override is disabled and you try to open the override GUI, this one will be displayed instead. If you click on "YES", the override get's enabled and the GUI is displayed. "NO" will just close the window and nothing else happens. Impossible to miss that window and also impossible to open the GUI while the feature is disabled. I've also renamed the "enable/disable" button to "OVERRIDE ENABLED" and "OVERRIDE DISABLED", colored in red/green so the color actually represents the current state. For now, I'll leave the button where it is, but I can still move it somewhere else. RIght now, there is a little bug when you disable the override and than try to close the window via the key combination but I have to leave for an appointment now, will fix it later.
  18. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    How about this? Hm...on top like: in line with the title (KSP Addon-on Version Checker...)? Not a fan of the idea, would kinda look strange IMO. I can also create a complete separate window which pops up if the version override is disabled and ask, if you want to enable it.
  19. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    @MOARdV There is actually a button to enable/disable the override via the GUI: Well, LGG missed that button as well when he tried it the first time...the PR isn't merged yet, so...how about coloring the button and labels to make it more obvious? That's something which already came to my mind during the stream yesterday: The entry you've found there is the one which can be used by mod authors to disallow the override for their mods via the .version file but it got the same "name" as the .cfg setting for AVC to enable/disable the override in general. Even when a mod author doesn't allow the override via .version file, it will be still listed in the GUI but you cannot do anything with it: An active version override doesn't affect the locked mod and you cannot put the name on the "always override" list. I'll change the names to make it more clear
  20. 4x4cheesecake

    How does the plasma blackout work?

    The "Physics.cfg" contains some informations about this: commNetQTimesVelForBlackoutMin = 500 // Minimum dynamic pressure * velocity for comms to start blacking out from plasma (if that option is enabled) commNetQTimesVelForBlackoutMax = 2500 // Maximum dynamic pressure * velocity for comms to start blacking out from plasma (if that option is enabled) commNetTempForBlackout = 1100 // Minimum shock temperature for comms to start blacking out from plasma (if that option is enabled) commNetDensityForBlackout = 5.0000000000000002E-05 // Minimum density for comms to start blacking out from plasma (if that option is enabled) commNetDotForBlackoutMin = -0.86599999999999999 // Minimum dot between velocity and link direction for comms to start blacking out from plasma (if that option is enabled) commNetDotForBlackoutMax = -0.5 // Dot between velocity and link direction for full blackout multiplier commNetBlackoutThreshold = 0.5 // Threshold blackout value below which comms are entirely blacked out (if that option is enabled). Value calculated as 1 - inverse lerp of QTimesVel * inverse lerp of dot So, it depends on the dynamic pressure and temperature, honestly no clue what the "dot" is meant to be.
  21. Odd... Do you mind uploading your log somewhere so we can take a look as well? Maybe you just missed something.
  22. 4x4cheesecake

    Ask the Mods questions about the Forums!

    it's actually still there You may need to hover the cursor above the right upper corner of the quote box to highlight it (probably you need to deactivate the cosmetic filter of UBlock Origin if you use it)
  23. AFAIK, it works in map view, the KSC and in flight. Just to be sure: You have kopernicus (+Modular Flight Integrator) and ModuleManager installed as well, and you know how to install a mod properly (no duplicate GameData folder or other crazy stuff)?
  24. The wildcards are NOT used in .version files. The upcoming feature (compatibility override) will allow you to tell AVC, that a mod is compatible, even though the .version file says something different. This is more a QoL feature to get rid of the (huge) "incompatible mod" list during game launch. The only thing that can actually be changed in the .version file, is an additional entry to disallow the override for a mod (for mods like kopernicus).
  25. How do you try to open it? Should work with "Ctrl + P"