First Person Model compat

[SamuelUlep]

Other parkour animations, such as rolls and vaults, support first-person view. However, during the dive animation, when using the first-person model, the player’s back becomes visible during either the dive animation or the sky-diving animation.

[SamuelUlep]

I'm not sure whether to make this an parcool compat issue or a first person model compat issue

[SamuelUlep]

There's another issue that I found while playing the game, having a shield on the offhand slot while also clinging to a cliff causes the player to spaz out while in first person view.

[alRex-U]

Thank you.
I'm thinking fixing way now

[alRex-U]

Please try 3.4.1.5-1.1

[SamuelUlep]

I updated to the latest version of the mod, issues regarding the player view not following the position of the players third person model view is still an issue i.e. seeing the players back during the dive animation, and the shield spazing out when holding a shield while also clinging to a cliff so I believe this issue shouldn't be closed @alRex-U, I could provide logs and more information of my game if need be.

Edit: The issue isn't with parcool messing up, it seems to be a not enough animation issue.

[SamuelUlep]

According to tr7zw(the dev for both the not enough animation and the first person model mod), the issue for the shield animation is a limb ownership issue.

Since it's NEA, the best fix would be if you register an animation via https://github.com/tr7zw/NotEnoughAnimations/blob/main/src/main/java/dev/tr7zw/notenoughanimations/api/NotEnoughAnimationsApi.java that just claims ownership of all limbs and the body rotation while a parcool animation is playing. Then NEA shouldn't interfere with anything anymore.

For the dive animation issue is also just an camera offset issue.

For the diving you need to offset the model to the camera, probably(there is an API for that https://github.com/tr7zw/FirstPersonModel/blob/main/src/main/java/dev/tr7zw/firstperson/api/PlayerOffsetHandler.java).

[ShepoPL]

is there any progress in addressing this issue?