You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, this is the ModelReplacementAPI developer.
I was testing an upcoming first person viewmodel feature on mods like Lethal Phones when I realized an issue that doesn't have an immediate solution.
This is selecting the 3, and is one of the better examples
Because my mod works by copying rotations, but not positions to prevent model warp, models with different proportions inevitably result in situations like this where it is difficult or impossible to use the phone dial feature.
A potential solution to this issue would be having an optional cursor, or red circle, or whatnot that indicates where you are aiming.
I have reviewed the source code of your mod, and given the complexity of PlayerPhone.ManageInputs() I don't think I would be able to patch this myself, but if you implemented the toggleable cursor I could manage the activation and deactivation of that cursor on my end when it's necessary.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the feature
Hello, this is the ModelReplacementAPI developer.
I was testing an upcoming first person viewmodel feature on mods like Lethal Phones when I realized an issue that doesn't have an immediate solution.
This is selecting the 3, and is one of the better examples
Because my mod works by copying rotations, but not positions to prevent model warp, models with different proportions inevitably result in situations like this where it is difficult or impossible to use the phone dial feature.
A potential solution to this issue would be having an optional cursor, or red circle, or whatnot that indicates where you are aiming.
I have reviewed the source code of your mod, and given the complexity of
PlayerPhone.ManageInputs()
I don't think I would be able to patch this myself, but if you implemented the toggleable cursor I could manage the activation and deactivation of that cursor on my end when it's necessary.The text was updated successfully, but these errors were encountered: