Known bugs & issues:
- All layer textures are kept in memory, which can be bad for performance when many layers of large textures (> 4K) are used. If you have big textures, use the "unload textures" option in the advanced menu to avoid this problem at the expense of a short delay when re-loading.
- Joystick trigger buttons are read as an axis for compatibility with more controller types, which means when both are pressed, they cancel out
- NVidia cards may eat more CPU if the "Threaded Optimisation" option in the NVidia control panel is not turned off. You can get around this by disabling VSync and using the FPS limit instead. (This is more a driver bug than a RahiTuber bug but I'm putting it here for visibility) - see https://gamedev.stackexchange.com/questions/136816/why-this-simple-sfml-app-prod...
- Window size can gradually increase when swapping from fullscreen to windowed mode, when using high DPI monitors (or, using a scaling factor on your monitor's display settings).
- The window size can become stuck at a larger size if RahiTuber is used on the same monitor as a game which is using "Exclusive Fullscreen" display mode and is running at a lower resolution than your monitor's usual.
- To solve this, you can delete config.xml to have it regenerated with default values.
- To avoid this, don't run games in "Excludive Fullscreen" mode on the same monitor as RahiTuber. Prefer "(Windowed) Borderless" instead.