Describe the bug
when i have Phys Mod Pro installed and I go to the cloth section and try to customize cloth it crashes

To Reproduce
Steps to reproduce the behavior:

1. Go to 'cloth setting'
2. Click on 'customize cloth'
3. crash

Expected behavior
to not crash

Screenshots
If applicable, add screenshots to help explain your problem.

Crashlog
https://pastebin.com/bt4ZgHrc

(please complete the following information):

• Minecraft Version: [1.21.1]
• EMF version [newest]
• Does the issue persist with only EMF installed? only mods installed are emf, etf and phys mod
• if applicable, provide your modlist or log:

• Entity Model Features
• Entity Texture Features
• Fabric API
• Physics Mod

Additional context
idk if this problem with emt or etf

also when just emf and etf and no other mods it give many errors:

[19:09:58] [main/WARN]: Error loading class: net/irisshaders/batchedentityrendering/impl/FullyBufferedMultiBufferSource (java.lang.ClassNotFoundException: net/irisshaders/batchedentityrendering/impl/FullyBufferedMultiBufferSource)
[19:09:58] [main/WARN]: Error loading class: net/irisshaders/iris/layer/InnerWrappedRenderType (java.lang.ClassNotFoundException: net/irisshaders/iris/layer/InnerWrappedRenderType)
[19:09:58] [main/WARN]: Error loading class: net/irisshaders/iris/layer/OuterWrappedRenderType (java.lang.ClassNotFoundException: net/irisshaders/iris/layer/OuterWrappedRenderType)
[19:09:58] [main/WARN]: Error loading class: dev/tr7zw/skinlayers/render/CustomizableModelPart (java.lang.ClassNotFoundException: dev/tr7zw/skinlayers/render/CustomizableModelPart)
[19:09:58] [main/WARN]: Error loading class: me/jellysquid/mods/sodium/client/render/immediate/model/EntityRenderer (java.lang.ClassNotFoundException: me/jellysquid/mods/sodium/client/render/immediate/model/EntityRenderer)
[19:09:58] [main/WARN]: Error loading class: net/raphimc/immediatelyfast/feature/core/BatchableBufferSource (java.lang.ClassNotFoundException: net/raphimc/immediatelyfast/feature/core/BatchableBufferSource)
[19:09:58] [main/INFO]: Initializing MixinExtras via com.llamalad7.mixinextras.service.MixinExtrasServiceImpl(version=0.4.1).

and warnings:

[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvDown], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [436.0, 132.0, 436.0, 208.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvUp], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [436.0, 208.0, 436.0, 132.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [436.0, 208.0, 436.0, 248.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [512.0, 208.0, 512.0, 248.0]
[19:10:08] [Render thread/INFO]: [ETF]: emissive suffixes loaded: {_e}.
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvDown], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [436.0, 132.0, 436.0, 208.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvUp], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [436.0, 208.0, 436.0, 132.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [436.0, 208.0, 436.0, 248.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [512.0, 208.0, 512.0, 248.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvDown], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [24.0, 72.0, 24.0, 88.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvUp], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [24.0, 88.0, 24.0, 72.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [24.0, 88.0, 24.0, 108.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [40.0, 88.0, 40.0, 108.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [32.0, 31.0, 39.0, 31.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [48.0, 31.0, 55.0, 31.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvWest], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [39.0, 31.0, 48.0, 31.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvEast], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [23.0, 31.0, 32.0, 31.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [24.0, 20.0, 28.0, 20.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [35.0, 20.0, 39.0, 20.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvWest], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [28.0, 20.0, 35.0, 20.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvEast], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [17.0, 20.0, 24.0, 20.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [32.0, 22.0, 39.0, 22.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [48.0, 22.0, 55.0, 22.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvWest], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [39.0, 22.0, 48.0, 22.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvEast], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [23.0, 22.0, 32.0, 22.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [26.0, 48.0, 34.0, 48.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [42.0, 48.0, 50.0, 48.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvWest], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [34.0, 48.0, 42.0, 48.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvEast], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [18.0, 48.0, 26.0, 48.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [10.0, 48.0, 18.0, 48.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [26.0, 48.0, 34.0, 48.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvWest], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [18.0, 48.0, 26.0, 48.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvEast], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [2.0, 48.0, 10.0, 48.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [10.0, 40.0, 18.0, 40.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [26.0, 40.0, 34.0, 40.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvWest], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [18.0, 40.0, 26.0, 40.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvEast], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [2.0, 40.0, 10.0, 40.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [26.0, 40.0, 34.0, 40.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [42.0, 40.0, 50.0, 40.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvWest], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [34.0, 40.0, 42.0, 40.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvEast], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [18.0, 40.0, 26.0, 40.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvDown], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [0.0, 0.0, 32.0, 0.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvUp], the V height should not be 0, its behaviour is extremely inconsistent between hardware: [0.0, 0.0, 32.0, 0.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvWest], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [0.0, 0.0, 0.0, 32.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvEast], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [0.0, 0.0, 0.0, 32.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvDown], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [96.0, 56.0, 96.0, 88.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvUp], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [96.0, 88.0, 96.0, 56.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [96.0, 88.0, 96.0, 108.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [128.0, 88.0, 128.0, 108.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvDown], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [96.0, 56.0, 96.0, 88.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvUp], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [96.0, 88.0, 96.0, 56.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [96.0, 88.0, 96.0, 108.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [128.0, 88.0, 128.0, 108.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvDown], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [196.0, 40.0, 196.0, 80.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvUp], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [196.0, 80.0, 196.0, 40.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [196.0, 80.0, 196.0, 128.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [236.0, 80.0, 236.0, 128.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvDown], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [116.0, 68.0, 116.0, 96.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvUp], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [116.0, 96.0, 116.0, 68.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvNorth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [116.0, 96.0, 116.0, 124.0]
[19:10:08] [Render thread/WARN]: [EMF]: Possibly invalid UV data for [uvSouth], the U width should not be 0, its behaviour is extremely inconsistent between hardware: [144.0, 96.0, 144.0, 124.0]
[19:10:09] [Render thread/INFO]: Created: 512x512x0 minecraft:textures/atlas/particles.png-atlas

i'm guessing you had a custom player model loaded in the physics mod pro version? as i cannot replicate with the normal one

by the looks of things this crash would need to be handled on physics mods end, they are not open source so I don't have many convenient options myself

also the pro versions are available here for free: https://www.patreon.com/Haubna

i'm guessing you had a custom player model loaded in the physics mod pro version? as i cannot replicate with the normal one

by the looks of things this crash would need to be handled on physics mods end, they are not open source so I don't have many convenient options myself

I don't think there's a custom player model in the pro version but I can try to replicate it again and send the files