Davidian1024 Posted July 21, 2023 Share Posted July 21, 2023 (edited) Reported Version: v0.1.3.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Linux Ubuntu 20.04.6 | CPU: AMD Ryzen 5 3400G | GPU: NVIDIA GeForce GTX 1080 Ti | RAM: 16GB Specs: (Obtained from Steam via Help > System Information) Spoiler Computer Information: Manufacturer: ASUSTeK COMPUTER INC. Model: PRIME B450M-A Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: AuthenticAMD CPU Brand: AMD Ryzen 5 3400G with Radeon Vega Graphics CPU Family: 0x17 CPU Model: 0x18 CPU Stepping: 0x1 CPU Type: 0x0 Speed: 3700 MHz 8 logical processors 4 physical processors Hyper-threading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Supported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported AVX2: Supported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: Ubuntu 20.04.6 LTS (64 bit) Kernel Name: Linux Kernel Version: 5.15.0-76-generic X Server Vendor: The X.Org Foundation X Server Release: 12013000 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20230509.49499 Video Card: Driver: NVIDIA Corporation NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 535.54.03 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x10de DeviceID: 0x1b06 Revision Not Detected Number of Monitors: 2 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 3840 x 1080 Primary Display Size: 20.75" x 11.65" (23.78" diag), 52.7cm x 29.6cm (60.4cm diag) Primary Bus: PCI Express 16x Primary VRAM: 11264 MB Supported MSAA Modes: 2x 4x 8x 16x Sound card: Audio device: Nvidia GPU 82 HDMI/DP Memory: RAM: 15913 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 467875 MB Largest Free Hard Disk Block: 7146 MB Storage: Number of SSDs: 9 SSD sizes: 2000G,2000G,1000G,500G,63G,4510M,0B,0B,0B Number of HDDs: 0 Number of removable drives: 0 Severity: Low (This can be worked around, but it is rather annoying. I think on rare occasion it could cause the player to inadvertently send their vessel into an uncontrollable spin.) Frequency: High (This can always be reproduced when following the steps below.) Description: Capslock is the default keybinding for precise.vessel.control. Typically the state of capslock within the OS along with the light on the keyboard match the state of precise.vessel.control. If you change the state of capslock outside of flight mode (in the VAB for example) it can become out of sync with respect to precise.vessel.control. As the UI only indicates the state of precise.vessel.control while the keys are being pressed, this is confusing at best and rather irritating at worst. Steps to reproduce: Load a controllable vehicle in the VAB. Ensure capslock is on. Click the big green launch button to start a mission. Wait for the simulation to finish loading and for the vessel to become ready to be controlled. Observe the little green arrows above, below and to the right of the navball, that indicate roll, yaw and pitch input. Press and release the Q/E, A/D and W/S keys and observe that the little arrows move the entire span of their input indicator. This demonstrates that precise.vessel.control is off while capslock is on. Turn capslock off. Press and release the Q/E, A/D and W/S keys and observe that the little arrows move a small amount respective to the span of their little input indicator. This demonstrates that precise.vessel.control is on while capslock is off. This is counterintuitive. Normally, the state of precise.vessel.control should match the state of capslock. If you switch focus to another application, say a web browser for example, change the state of capslock, and then switch back to KSP2, the game notices the state change of capslock and updates precise.vessel.control accordingly. It seems to me that there is a simple way to fix this. Have the game check the state of capslock when the launch button is clicked, or as the simulation is starting up and set precise.vessel.control to match it. Another option might be to have the state of capslock checked with every press of the capslock key. If the game can learn the state capslock is changing to when a keypress occurs, it could change the state of precise.vessel.control to match the new state. As opposed to simply toggling it with every keypress, which seems to be the current behavior. Alternatively, the UI could provide some sort of visual indication about the current state of precise.vessel.control. In KSP1 I believe the arrow color indicated the state of precise.vessel.control. Actually, both of these changes would be great to have. Edited July 21, 2023 by Anth12 Link to comment Share on other sites More sharing options...
Davidian1024 Posted August 30, 2023 Author Share Posted August 30, 2023 This is still present in 0.1.4.0 Link to comment Share on other sites More sharing options...
Recommended Posts