Jump to content

Jomo

Members
  • Posts

    7
  • Joined

  • Last visited

Reputation

1 Neutral

Profile Information

  • About me
    Curious George
  1. KSP Version - Steam Build ID: 10624168 Operating System and version (Windows 10, Windows 11) - Windows 11 Pro (10.0.22621 Build 22621) CPU and GPU models, any other system information which could be relevant AMD Ryzen 9 5900X 32GB RAM GeForce RTX 3070Ti (Driver 528.49) Running 1440p Description of the bug. Expected Behavior - If I leave a flight in orbit and return to the VAB to build a new one, I shouldn't be able to revert my previous flight in orbit. I should only be able to revert if I'm actively flying the craft Observed Behavior - I can revert flights in orbit when I've returned to the VAB Steps to Replicate Launch Craft Hit Escape Select 'Return to VAB' Once in VAB, hit escape Select 'Revert to VAB' Flight is removed from orbit and returned to the VAB Fixes / Workarounds (if known..) Don't do this A list of ALL mods. If the list is long, please consider using a spoiler window. None Other Notes / Screenshots / Log Files (if possible..)
  2. KSP Version - Steam Build ID: 10624168 Operating System and version (Windows 10, Windows 11) - Windows 11 Pro (10.0.22621 Build 22621) CPU and GPU models, any other system information which could be relevant AMD Ryzen 9 5900X 32GB RAM GeForce RTX 3070Ti (Driver 528.49) Running 1440p Description of the bug. Expected Behavior - Collapsing groups only keeps that specific group collapsed. If I collapse the methane fuel tank group (Group 2 under tanks), it should not collapse Solid Boosters (Group 2 under engines) Observed Behavior - If you collapse one group of parts in a category and then move to a different category, the same group will be collapsed. Steps to Replicate Navigate to the VAB Navigate to the Fuel Tank Category Collapse the Methane Group Navigate to the Fuel tank Category Observe that Solid Fuel Booster is collapsed as well Fixes / Workarounds (if known..) None A list of ALL mods. If the list is long, please consider using a spoiler window. None Other Notes / Screenshots / Log Files (if possible..) A video would be best to show this and I don't have the means to record that right now
  3. Piggy backing off this one since I had run into this as well: KSP Version - Steam Build ID: 10624168 Operating System and version (Windows 10, Windows 11) - Windows 11 Pro (10.0.22621 Build 22621) CPU and GPU models, any other system information which could be relevant AMD Ryzen 9 5900X 32GB RAM GeForce RTX 3070Ti (Driver 528.49) Running 1440p Description of the bug. Expected Behavior - Searching for any term related to a part shows it in the search results Observed Behavior - Several parts do not show when searched for a term in their description Clamp - Does not show launch clamps Mount - Shows only 3 out of the 5 total engine mounts, and shows cockpits and fuel tanks instead? Cockpit - Shows 1 pod (5 man Cockatoo) and 4 out of the 5 cockpits Stabilizer - Shows 1 out of 5 that exist in the category Steps to Replicate Navigate to the VAB Type in the above terms (and likely more, I did not exhaust them all) Fixes / Workarounds (if known..) Manually searching A list of ALL mods. If the list is long, please consider using a spoiler window. None Other Notes / Screenshots / Log Files (if possible..)
  4. Correct. In my post I reference that point. But if we're not allowed to do something we should be prevented to altogether or be given an error message stating that this action cannot be taken. Right now it appears to just do nothing.
  5. Actual Result: When viewing screenshots of 'Workspaces' in the load workspace screen, the images are pixelated to the point that you can barely make out what the craft is Expected Result: Images are at a high enough resolution to make out what the craft is Reproducibility: 100% Steps to Reproduce: Load the game Head to the VAB Select the 'Open' option for Workspaces Look at the resolution This one is fairly straight forward. The one extra detail I will add here is that I am running the game at 1440p. I have tested this at other resolutions and it does not get better there either
  6. Actual Result: When in the 'Load Workspaces' screen, there is an option to delete workspace at the bottom of the screen. This can be used on any workspace, even the stock workspaces. Using it on stock workspaces results in the command appearing to execute, but the workspace never deleting Expected Result: Either allow us to delete the stock vehicles or prevent us from doing it Reproducibility: 100% This was something I came across while working on a craft. I decided to load an older version and found that there were stock vehicles present. I went in, loaded a few and then saw the delete option at the bottom. I went and attempted to delete them, and it didn't error out but the craft never left the list. I went and deleted one of my craft and it did remove it from the list. It appears you want to prevent us from deleting stock vehicles, so it would great if either that option is not selectable or provides an error when the user attempts to delete a stock vehicle. Side note, I had zero idea there were stock vehicles anywhere. So just some general feedback that I don't think you highlight this enough.
  7. Actual Result: When given a warning in the Engineering Report of "Vessel has a command pod and no parachute. Command Pod may not survive Kerbin Landing", clicking on the error takes me to the command pods category which has no chutes. Expected Result: Clicking the warning should go to the part category that I need to resolve that issue. In this case 'Utility' Reproducibility: 100% This was something I came across while working on a craft I was going to send to Jool. I opened the Engineering report to try to find some TWR info, and noticed the warning above along with an error about my TWR being less than 1.0. Mousing over them highlights them, as if they were clickable/actionable. I clicked on the TWR warning and it took me to engines which could be used to resolve the warning. I clicked on the parachute warning and was taken to command pods, which has no parts to resolve my issue. I logged this as a bug instead of a suggestion because the UI takes an action already. It's just the wrong action.
×
×
  • Create New...