Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits)

Edit for any thread-readers - this was the bug that led to the v14.52 update, so it's fixed now!
---------------------------

the movement-based tracking gravitates the mouse towards the "neutral position" set in the tracking tab. You might need to manually set that neutral position if you've never changed it, it could be set to "-1,-1“ behind the scenes which should automatically deduce it from your monitor size but maybe that failed.

Also you might need to restart RahiTuber after setting it. 

Please let me know if any of that helps. I only have the one computer and mouse to test with 😅

Main display is 3440x1440 and I disconnected my smaller 2nd display just in case and messing with the values myself bears no fruit.

Could there be anything I can provide to narrow it down? The only difference I noticed is the entire model would shift slightly to the right or down if I set either axis to -1 though only one at a time can be set to that value.

Troubleshooting did include restarting Rahituber. It feels as though RawInput does work just some value is off. Most of my states have custom tracking values so I tested with both global and individual values.

(1 edit)

the movement-based tracking always gravitates the simulated mouse towards the global neutral position, it's the only way to make sure the model behaves the same if other layers have custom neutral points.

I'm not clear on something. could you follow these steps exactly:

- reset the global neutral position and distance factor (it should say half of your monitor resolution here, if it displays -1 then that's part of the problem)

- add 1 to each value (or set to anything above 0 if it's saying -1) with a manual edit

- save your layer set

- restart RahiTuber