Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to use standard controls in 4.0, visual and console bugs. #93

Open
aihaw opened this issue May 4, 2020 · 6 comments
Open

Ability to use standard controls in 4.0, visual and console bugs. #93

aihaw opened this issue May 4, 2020 · 6 comments
Labels
bug Software defects.

Comments

@aihaw
Copy link

aihaw commented May 4, 2020

Hi! Your update has been a great improvement! But I noticed a couple of things!
(I'd rather be honest with you I use the 1.8 version which seems to not be supported so I guess it might be the source of all my problems...)
-As I use an oculus rift, the controls are pretty buggy and I can't move in the editor. As for the flight mode, my yaw and stick works well but the throttle seems a bit buggy. I wondered if you could implement a keyboard setting or mode so we could play as usual and have the ability to wasd on the editor (for now my throttle keyboard controls does not work at all...).
-I also experience sometimes a black sky when reloading or relaunching the flight. When it happens all the blue tint of kerbin seems to go away and the view distance is reaaally low, especially in IVA (with through the eyes mod).
-The console menu is not opening when alt-f12 and it gets me to the desktop, making me select a software to open something, although every option is grayed out. (not closing the game though) so I can't see if any log happens in game...

Thank you so much for doing this it's a great feature I really appreciate your work.

@Vivero
Copy link
Owner

Vivero commented May 4, 2020

Thanks for the early feedback! I do expect plenty of bugs right now :)

(I'd rather be honest with you I use the 1.8 version which seems to not be supported so I guess it might be the source of all my problems...)

I have not tested KerbalVR 4.0 with KSP 1.8, some bugs might be explained by this further below.


As I use an oculus rift, the controls are pretty buggy

Yea unfortunately I do not have Oculus controls to test with, but I highly recommend tweaking the controls as needed in the SteamVR input bindings configuration, because I definitely needed to modify some things for the Valve Index controllers.

While running KSP, this is accessed through SteamVR Settings > Controllers > Show Old Binding UI. You should see KSP_x64 on this list. Click it, then click Edit on your current bindings.


I can't move in the editor

This is currently disabled, I am going to re-work the movement system in the Editor. So for now, there is no movement inside the Editor.


throttle seems a bit buggy

I highly recommend you look at the SteamVR input bindings config, this is one example of something I needed to tweak quite a bit before it felt "right".


(for now my throttle keyboard controls does not work at all...)

I will definitely add a setting to allow keyboard throttle control instead of VR controls. Right now the throttle control on the VR controller completely overrides the throttle, so that's why you are unable to use keyboard to control the throttle. I'd like to make this behavior something you can toggle on or off.


I also experience sometimes a black sky when reloading or relaunching the flight. When it happens all the blue tint of kerbin seems to go away and the view distance is reaaally low, especially in IVA (with through the eyes mod).

I'm 90% sure this is due to incompatibility with KSP 1.8. If you are able to, give 1.9 a try. I'll be
💯 honest with you, backwards compatibility is not on my list of priorities...


The console menu is not opening when alt-f12

Hmm... I have not encountered this behavior before... the console window has been working for me, and I definitely use it all the time while I'm testing new code for the mod. As far as I know, the mod shouldn't be interfering with KSP's UI, but we can never know what bugs like this can pop out :)

If you have any more details about that, maybe it might help. Does it never show when you press Alt-F12? Are you in fullscreen mode? Is there a specific scene where it doesn't show (flight, editor, main menu)?

@Vivero Vivero added the bug Software defects. label May 4, 2020
@Vivero
Copy link
Owner

Vivero commented May 4, 2020

and again, thanks for being an early tester, glad you're enjoying the improvements! (sorry for the new bugs that we have to put up with though)

@Jatwaa
Copy link

Jatwaa commented May 13, 2020

Hey Vivero, been a while. When I have the mod installed on 1.9.1 and I have a 360 controller in use, I can throttle up completely, but the craft goes nowhere. When I uninstall the mod the craft works fine. Beyond that, the environment is flickering its so so so close! I just updated my vid card so I can test this all a bit better now

@Vivero
Copy link
Owner

Vivero commented May 13, 2020

Hey @Jatwaa! Yes I remember you did a video with my mod a few years ago :)

About the flickering environment, yes this would occur if your Settings > Graphics > Render Quality was set to Simple or higher. If you set it to Fast or Fastest, the flickering is gone. However, I just managed to make a permanent fix for this, so that you will see no flickering regardless of the Render Quality setting 🎉

This fix will be available on the next pre-release (whenever that may happen).

And about the throttle problem, can you try to uncheck the "Enable Throttle Control" setting in the KerbalVR mod settings? When it is checked, you can only control throttle via VR controllers; if it is unchecked, you can control the throttle via keyboard or other input devices (hopefully your controller?)

image

@Jatwaa
Copy link

Jatwaa commented May 13, 2020

Odd, I have the latest Alpha 2 and its missing text and the third option.
KerbalVR-5-13-2020

@Vivero
Copy link
Owner

Vivero commented May 13, 2020

Oh that is crazy. Have not seen this bug appear before... Hmm. I'll look into it.

In the meantime, I think you can try this: edit the file \GameData\KerbalVR\Assets\Settings.json in any text editor. Change the "enableThrottleControl" setting to "false" like so:

image

Save the file and restart KSP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Software defects.
Projects
None yet
Development

No branches or pull requests

3 participants