Jump to content

JonnyOThan

Members
  • Posts

    1,314
  • Joined

  • Last visited

Everything posted by JonnyOThan

  1. OK, so I don't think anything has actually changed here. Are you sure that you weren't using the ASET MFDs previously? Oddly enough, the camera FOV is set in the MFD, not in the part - so the preview in the VAB is a complete lie. The RPM MFD has a max FOV of 20 degrees, and the ASET one is 90. The preview in the VAB always uses 60 degrees. I totally think it would make more sense to put the FOV in the partmodule itself, and make everything consistent.
  2. Thanks! I just noticed that one in someone's logs today too.
  3. New release! https://github.com/shadowmage45/TUFX/releases/tag/1.0.5.0 @HafCoJoe this has the button-hiding option for you! - Added a configuration option to hide the toolbar button (see TUFX/TexturesUnlimitedFX.cfg) - Updated default profiles: - All default profiles now use HDR, and the HDR-specific profiles have been removed - Disabled AO on most profiles since it causes banding - Enabled TAA on most profiles - Increased bloom intensity slightly - Map mode now defaults to using the tracking station profile instead of flight - Updated unity postprocessing stack to 3.0.3 to support VR - Fall back to default profiles if the old selected one is missing
  4. screenshots would also be useful, so we can compare to what is "normal"
  5. Did you install Reviva? You need to right-click the pod and select the IVA you want. Otherwise, post your ksp.log file.
  6. Good call on homeswitch, I hadn't thought of that. HebaruSan added the clouds as a separate ckan module that is recommended by the base mod, all should be well.
  7. helps to fix that. Doesn't this mean you're playing with 1/4th or 1/8th the texture resolution?
  8. If you can reproduce this easily, please provide the info Gotmachine mentioned and we can hopefully get this fixed.
  9. Awesome. But it looks like the recommendation for the base mod is wrong. GalaxiesUnbound-StockClouds is the identifier for the clouds module, but the base module recommends GalaxiesUnbound-Clouds
  10. Ahh, yeah it looks like the ckan metadata isn't set up to automatically install clouds. I'm not sure why. In any case you can do it manually by clicking on "Galaxies Unbound A Stellar Odyssey" then click the "Contents" tab in CKAN and then "Open Zip." The clouds files are in the Optional folder in there. Hey @ballisticfox0 and @HebaruSan - any idea if this was intentional? The GU cloud config is in the GU_Core\Optional folder in the zip. This could be a separate ckan entry but I'm not sure it does much good since you can't really opt into different clouds.
  11. Open up the settings.cfg file and change this line to false: https://github.com/KSPModdingLibs/KSPCommunityFixes/blob/af1dfc5d7958488e8b2117a7a4720fa97ad46d6e/GameData/KSPCommunityFixes/Settings.cfg#L37
  12. Sounds like it might be related to the partmodule index patch? If you disable that patch, does the issue go away?
  13. GU’s EVE configs also cover the stock system. It says in the OP that it is NOT compatible with other visual mods like AVP.
  14. KSP.log next to the executable. If you have file extensions hidden it’ll just be named “ksp” and has type text document.
  15. Are you on Linux? Does it look like this? https://github.com/JonnyOThan/RasterPropMonitor/issues/12
  16. Added command chair support: https://github.com/linuxgurugamer/Through-The-Eyes/pull/8 @linuxgurugamer
  17. This is caused by temporal antialiasing from scatterer. You can turn it off in the scatterer settings (and note that TAA from TUFX does not have this problem)
  18. Try 1.12.3? Also, this log ends 2 minutes after you launched the game, you might just need to wait longer. And it doesn't contain the error that you initially posted. It also may be useful to remove ALL your mods except TUFX and see if it still has the problem. You said you ran this on a fresh install, but this log has lots of other mods installed. For example, you have parallax installed, and this is your GPU (right) compared to the min specs for parallax (left):
  19. This could be caused by lots of things, if you need help please post the entire log file.
  20. It still might be a good idea. Any mod that depends on one of the settings should have it’s patch marked as final. The cfg emitted by the UI should not. When displaying the UI it could detect that the saved setting is not what actually what was loaded and infer that there was some overriding patch and notify the user in some way.
  21. New release available! https://github.com/JonnyOThan/KSA-IVA-Upgrade/releases/tag/v1.6.0 https://imgur.com/a/l50Elxb
×
×
  • Create New...