ParticleEffectForUGUI VS InputManager

I use this for my UI particles. It's free, open source and works great! https://github.com/mob-sakai/ParticleEffectForUGUI

mob-sakai's UI Particle

I am currently only using it during a loading screen for a minimal amount of particles so it isn't performance critical. I found another UIParticle library that is apparently faster than the UI Extensions one but I have yet to try it https://github.com/mob-sakai/ParticleEffectForUGUI

Thank you for sharing, this looks awesome! I have also found this on github that works amazingly well! https://github.com/mob-sakai/ParticleEffectForUGUI

But I agree with the other commenter: use a particle system. This package adapts particle systems to UI. It will be much more performant and easier to maintain.

The only two packages I have on is TextMesh Pro, and a UI Particle package (This one: Mob Sakai Particle Effect For UGUI)

In my last project we used daemon3000/InputManager for rebinding with the old input system. Worked well, but it's been refactored heavily since the version we shipped with (now supports local multiplayer better I think).

If you're using an engine, you should find a plugin that improves their gamepad support to handle gamepad mapping, switching, active detection. There's often free, open source solutions like InputManager for Unity, baton for love2d, etc.

I don't believe so, but i don't have much experience with this input system because i found it unintuitive. If you happen to give up on in too, I'm currently using this much easier alternative: https://github.com/daemon3000/InputManager/wiki/Getting-Started

For this project I am already making a VirtualJoystick object that will clean up inputs to be read by other parts of the program as well as store previous input states to be looked at later to help determine if the player has done things like double tapped a button or done a particular motion input. I will also be using a custom input manager (possibly this guy) to allow players to reassign keys at run time as well as handle some specific needs of the project.

However, this whole system is annoying to work with, doesn't support multiple controllers well, and doesn't support runtime remapping so people have stuff like InputManager to work around it -- by generating input settings for every possible input (like joystick_1_button_3) and creating an API to map strings against those inputs (which can be changed at runtime).

Yeah, I use this open source one for runtime rebinding in the old input system. Although I'm on an older version that assumed single input and have made a bunch of changes.

See this C# example (uses Unity but you could replace InputManager_Unity.cs with an implementation that queries engine api). Or here's one in lua.