Please post bug reports in here - you can also report them as issues on the GitHub repository (linked in the project info)
hmmmm we are noticing that if we flip ignore axis on it prevents the axis from being bound to the hotkey but we still can't bind a button on that controller until we center the axis. Also, we're noticing some frame rate issues with the new version that idk is related. We have a 165hz monitor but when we open the program it seems to shunt our entire display down to 120 which it runs without v sync and 60 with the vsync enabled. the media keys thing is working good though!!!
check out this video we made (which youtube has decided is a short)
our issue is the checkbox prevents an axis from being bound when its on, but if we want to bind a button we still have to go through the process to center out a bunch of axis even with the box ticked, essentially with the box ticked and an axis is being detected it will block all binding completely (we checked and this behavior works the same when you hold an axis maxed while trying to bind a button on a standard controller) also we really really appreciate you going through the effort to set this up since we know its a pretty edgy edge case just in case we come off as entitled!!!!yes!!! it works!!!! thank you so much!!!!!! best day ever this will speed up our setup times so much!!!
Sorry to hear that. When the menu is showing you should see some squares in the corners which can be used to resize it, and while making it larger this won't visually be updated until you let go.
In the future I can add some options to choose the type of window into a more standard resizable Windows-style one.
In the mean time, you can also set the window size by editing the config.xml file.
Very sorry I can't help more right now, but I'll test and make sure everything's working as it should, and add the extra window options soon!
I can't seem to record directional pad button press on my controller for states, all the other buttons seem to work fine. Looking my controller settings, it seems that the dpad is read as the Point of View Hat (I'm pressing up on the dpad here) and not as a numbered button, which might be the reason why.
I'm using a PS4 controller if it matters, I also tried with a 360 controller and that also reads the dpad as point of view hat
Ah ok, That probably would work, my controller seems to have a tiny amount of joystick drift, so when I try to record without disabled axis input, it immediately records the joystick. I may just need to look into a different controller or do some maintenance. Thank you for the help, I appreciate it!
Hi, sorry to hear that.
It may be a bug introduced by the changes to the states menu since you last updated. Deleting and re-creating the state might help, if you want to try that.
If that doesn't work, please can you post a screenshot of the state you have set up to do the switching, and a screenshot of the state's entry (written as a "hotkey") from your layer set xml file?
Cheers!
Hi, do you have any non-english letters in your installation path? There's a known bug with that which can cause unexpected issues like this.
If you put RahiTuber in the location C:/RahiTuber and place your image sprite files in the same folder, that particular problem should be avoided.
If the issue still happens let me know!
I think the mouse movement being jumpy is a result of the game grabbing your mouse and forcing it to move to the center of the screen (or some other similar thing, games all do different stuff with the mouse and it's hard to account for).
RahiTuber directly translates your mouse's position on the screen into a position co-ordinate for the layer, so if the layer jitters, that means the mouse jitters. I'll try to add something to smooth any sudden jumps.
I had this bug where the last layer I was tinkering with would go to the bottom after clicking in an empty part of the layer manager, and I've managed to find what causes it.
It seems like the last layer stays somehow selected after clicking it and holding the mouse button for slightly too long made it as if I moved it to the bottom:
Hi, sorry to hear that. You can contact me via discord @rahisaurus or at rahisaurus@gmail.com to share more details.
If your friend is using the Linux version, spout2 support isn't there yet (and won't be until spout2 offer it themselves) - but on windows, see if the different architecture builds (RahiTuber.exe and RahiTuber_64.exe) have different results? Maybe it has to match whatever architecture OBS is using.
Hi Rahi!
My friend is using the windows version, both architectures return the exact same lack of an output in Spout2.
I have friended you on discord, if it’s possible for you to contact me there, this problem can be resolved in a quicker amount of time than if it were done through Itch or emails.
Much appreciated for the timely response.
This is a weird one, especially since there's no code in RahiTuber that connects to any audio output device. It's possible there's some confusion behind the scenes where something considers the headphones and the microphone to be the same device, but that really shouldn't be the case... I'll see if I can find anything, but I'm not sure I will because I don't have a headset that produces this problem.
Thanks for letting me know, I'll keep you posted.