STILL having the floating weapon parts bug

[Starwight/ttv]

So when changing the size of weapon blades on various swords, 2h swords, and some polearms, we STILL have this bug that has existed for several months.

TW--you KNEW about this bug. It's been posted on your forums. I know because I have commented in several of them. You *knew* about this issue, and yet it has released in full and has yet to be fixed.

A recent post from a couple days ago on your forums and you act as though it's something you never knew existed! Acting like it's the first time you are hearing about it. How??

This basically breaks smithing for people. Who wants to use a weapon with a floating freaking blade? It is unimersive and makes you not want to craft weapons for yourself. Why is this still an issue? How have you known about this for several **months** now, prior to the full release of the game mind you, and it still remains ignored??

This shouldn't have even made it to the full release of the game, and it blows my mind how this has not been hotfixed yet. PLEASE, for the love of GOD, fix this bug already!

[Clovis Sangrail]

Originally posted by Starwight/ttv:

This basically breaks smithing for people. Who wants to use a weapon with a floating freaking blade? It is unimersive and makes you not want to craft weapons for yourself.

No, this breaks smithing for you and the rest of the 'immersion' fanbois who lack the imagination to overlook it.

It doesn't break smithing for me because I can just ignore it. Or just not fart around with the blade and handle lengths.

Filed under WGASA because there are a lot more things this game needs than fixing a little gap in a blade.

Important things like feasts and the glaring lack of pirates.

[Benelor]

Originally posted by Clovis Sangrail:

Originally posted by Starwight/ttv:

This basically breaks smithing for people. Who wants to use a weapon with a floating freaking blade? It is unimersive and makes you not want to craft weapons for yourself.

No, this breaks smithing for you and the rest of the 'immersion' fanbois who lack the imagination to overlook it.

It doesn't break smithing for me because I can just ignore it. Or just not fart around with the blade and handle lengths.

Filed under WGASA because there are a lot more things this game needs than fixing a little gap in a blade.

Important things like feasts and the glaring lack of pirates.

Awesome. You managed to make 0 sense and contradict yourself in one post....
The point of playing a video game is to escape reality and enjoy something else. If i have to use my imagination to overlook issues i can use said imagination and play something inside my head and don't need to play game in the first place.

It does break smithing the same way a game about tanks would break the gameplay if the turret of the tank is not attached to said tank but floats 2 feet above the rest of the vehicle.

For the smithing glitch you call people immersion fanbois yet argue about a feature that serves no purpose other than immersion "feasts" and the glaring lack of pirates (not sure what that even means)

If the glitching smithing parts are something immersion fanbois have to accept according to you. Then you following your own logic has to accept that "feasts" is something you have to ignore or you being in the same boat as the "immersion fanbois"

[Firelock]

I agree, I hate it when my sword blade starts 4 inches from the hilt. This is a new problem that I never saw before official release.

[Starwight/ttv]

Originally posted by scott2978:

I agree, I hate it when my sword blade starts 4 inches from the hilt. This is a new problem that I never saw before official release.

It's been a thing since at least 1.7, the posts on TW forum about it go back many months. I think it has gotten worse since official release, though. Or more noticeable at least.

Originally posted by Benelor:

Originally posted by Clovis Sangrail:

No, this breaks smithing for you and the rest of the 'immersion' fanbois who lack the imagination to overlook it.

It doesn't break smithing for me because I can just ignore it. Or just not fart around with the blade and handle lengths.

Filed under WGASA because there are a lot more things this game needs than fixing a little gap in a blade.

Important things like feasts and the glaring lack of pirates.

Awesome. You managed to make 0 sense and contradict yourself in one post....
The point of playing a video game is to escape reality and enjoy something else. If i have to use my imagination to overlook issues i can use said imagination and play something inside my head and don't need to play game in the first place.

It does break smithing the same way a game about tanks would break the gameplay if the turret of the tank is not attached to said tank but floats 2 feet above the rest of the vehicle.

For the smithing glitch you call people immersion fanbois yet argue about a feature that serves no purpose other than immersion "feasts" and the glaring lack of pirates (not sure what that even means)

If the glitching smithing parts are something immersion fanbois have to accept according to you. Then you following your own logic has to accept that "feasts" is something you have to ignore or you being in the same boat as the "immersion fanbois"

You articulated better than I did, since the TaleWorlds lapdogs police here removed my reply. But yes, exactly this right here.

And bear in mind, I left a positive review of this game and LOVE this game, but if criticism is deserved, it's deserved. And in this case it absolutely is.

[Kohle]

For me, if you don't adjust the blade size the sword is normal. At least for me, it looks like the mesh is not getting scaled properly.

[Starwight/ttv]

Originally posted by Kohle:

For me, if you don't adjust the blade size the sword is normal. At least for me, it looks like the mesh is not getting scaled properly.

Yeah that's exactly what triggers the bug--increasing the blade size. You know, the thing that actually makes the blades you craft potentially better than the ones you can buy or find?

I love this game, but it is incredible that Taleworlds somehow did not fix this problem that's been a thing for literal months leading up to full release.

[Serious Business]

I'm more worried about the constant crash to desktop issues every time there's a minor update. Getting straight NullPointer exceptions from the default modules isn't good.

[Starwight/ttv]

Originally posted by Chadimir Putitin:

I'm more worried about the constant crash to desktop issues every time there's a minor update. Getting straight NullPointer exceptions from the default modules isn't good.

I haven't had any crashes yet in 1.0, outside of some mods that didn't update their dependencies.