Page 1 of 1

Weapon model resize fiasco

Posted: Wed Jun 04, 2025 3:20 am
by Irontusk

Weapon is after a few seconds resizing as if I am a Large modeled character. So, if a Steel Greataxe is reduced 50% in size to one hand it, my medium sized character is two handing a 50% sized steel great axe.

I was playing on an Ogre, now I'm playing on my Bugbear (Normal reward +7% sized character model). Ogre is using a great axe and shield to tank, a colossal axe to damage. Bugbear always uses greataxe. Other than that, simply playing both characters.

Bugbear's axe should be normal sized.

Bugbear's axe is tiny.

The size the axe should be:
Image

The size the axe is:
Image

Reference to visual FX effected by sizing bug in PGCC:
Image

I was messing with a tank build idea on an Ogre, then went back to my Bugbear.

Underdark

PC

Additional Info:
I just noticed a couple threads down that it seems to be happening game-wide. Glad it isnt just me. :c Can lock this if ya want, don't need two threads on the same issue.

Messing around with build ideas in PGCC, it seems to be doing it to all characters I make now. I.E: I'm trying out a human spear user, and the spear is shrinking in my hands. Bug might be account specific. Possibly some kind of spill over from playing a Large modeled character.

Small modeled characters are having the opposite bug. Weapons are too big and causing FX issues you'd assume would be the inverse to my Medium sized characters.

Can confirm it is across all of my characters.


Re: Weapon model resize fiasco

Posted: Tue Jun 10, 2025 10:13 pm
by Irontusk

Just saw a fey with a battle axe larger than my Half Orc's greataxe. :|

Noticed the weapon is no longer rescaling, and simply smaller. Weapon FX are still bugged out.

And on a personal note, the first time the models were scaled down, everyone hated it. Myself included. It was understandable then because Colossal weapons were being added and they needed to truly seem colossal. If that's what is in the pipeline with these resizing it's a bad idea.

Anyway, it's obvious it isn't a bug but a Dev cooking something up. Thread can be locked.