[Bug] Player's head disappears with repeated log errors "[Render thread/ERROR]: Invalid entity rotation: NaN, discarding."

[MartyX98]

Current Behaviour

The player's head disappears when I control the game using a controller. When I start using keyboard and mouse, the problem disappears, but returns back the moment I start using controller again. Alongside it, repeated error messages in game's log appear.

Expected Behaviour

To not have this bug happen.

Screenshots

Using controller;

Using keyboard;

Logs from Modrinth App

Reproduction Steps

Environment

• OS: Windows 11 Home (24H2)
• Controller: PS5 DualSense controller, connected via USB.
• Minecraft 1.21.4 (Fabric) through Modrinth app with mods;
  • Controlify (2.0.2+1.21.4-fabric)
  • Fabric API (0.115.1+1.21.4)
  • YetAnotherConfigLib (3.6.2+1.21.4-fabric)

Logs

...
[02:38:45] [Render thread/ERROR]: Invalid entity rotation: NaN, discarding.
[02:38:45] [Render thread/ERROR]: Invalid entity rotation: NaN, discarding.
[02:38:45] [Render thread/ERROR]: Invalid entity rotation: NaN, discarding.
[02:38:45] [Render thread/ERROR]: Invalid entity rotation: NaN, discarding.
[02:38:45] [Render thread/ERROR]: Invalid entity rotation: NaN, discarding.
...

Mod Version

Controlify (2.0.2+1.21.4-fabric)

Controller

PS5 DualSense Controller

Bluetooth

• [ ] Yes

Operating System

Windows

ARM

• [ ] Yes

Additional Information

No response

Just to make sure...

• [x] I have made sure I am using the latest version of Controlify for the latest version of Minecraft.
• [x] I have made sure there are no other issues describing the same problem on the issue tracker.

[hecktexk]

the same thing is happening to me

[DoggoNako]

Same issue here:

This only happens with a controller, at first I thought it was my Java installation but GraalVM and OpenJDK install give the same issue.

• PrismLauncher
• Windows 11 & Arch Linux 6.13.1
• Xbox One Controller via bluetooth
• Minecraft 1.20.1 w/ Fabric 0.16.10
  • Controlify v2.0.2+1.20.1-fabric
  • Fabric API 0.92.3+1.20.1
  • YetAnotherConfigLib 3.6.2+1.20.1-fabric

logs here

Without moving camera:

Breaking Blocks without moving camera:

Also in video: https://youtu.be/Kf1uftDOnO0

Hope it helps !

[DoggoNako]

~~A friend of mine doesn't have this issue with Forge, I'll try to reproduce on other modloader than Fabric~~ edit: nvm NeoForge is only up to 2.0.1, Quilt is the same...

[apple8404]

latest.log

more logs for the log gods. same issue, win11, minecraft 1.21.4, xbox core controller via bluetooth

[xXANTIHERO259Xx]

Just came back to the game after a 4 month break and it started happening, if possible i might downgrade to an earlier version and see if the bug is still happening

[xXANTIHERO259Xx]

alright i downgraded to 2.0.0+1.21 and the bug isn't there if your controller is supported on that version and it fits the mod pack you're creating/playin then play on that instead

[DoggoNako]

For me, I don't have this issue when downgrading to 2.0.1+1.20.1 on Fabric

[Greenknight9000]

Glad to see I'm not the only one suffering with this issue. It's happening on Fabric 1.21.1 using the latest version of the mod

[DrSex420]

alright i downgraded to 2.0.0+1.21 and the bug isn't there if your controller is supported on that version and it fits the mod pack you're creating/playin then play on that instead

Can confirm, 1.21.4 Steam Deck OLED, downgrading to 2.0.1 got rid of the log flood

[EssGeeEich]

This bug is solved in the very last version of Controlify.

While such version is not available on the various mod stores, you can download an updated build that's automatically generated from the Github CI here:

https://github.com/isXander/Controlify/actions/runs/13444067998/job/37565214600

On the left side, select your Minecraft version, open the "Run actions/upload-artifact" task and you'll find a download link there with the very last changes.

[nonbinary]

I'm playing on fabric, minecraft version 1.21.7, and this issue is still here. So I'm guessing it's reappeared?

Edit: It appears when I have my right stick deadzone to 100%. I use a steam controller, and don't use the right stick as a stick, so I tested that. Setting the deadzone to 98% fixed the issue.