Fixed collision meshes

[Oberyn]

I understand nothing of this, technically, but is there a chance these more detailed meshes will have an impact on performance?

[[ptx]]

There shouldn't be.

[Silveredge]

Awesome.

[Vibe]

I understand nothing of this, technically, but is there a chance these more detailed meshes will have an impact on performance?

Collision meshes define where another object collides with the owner of the collision mesh (in this case the trees and doors). Dave made them smaller and more accurate to their 3d model.

[DaveUKR]

I understand nothing of this, technically, but is there a chance these more detailed meshes will have an impact on performance?

These meshes have a very small amount of faces if you compare them to real model. Other exterior objects (houses, castles etc.) have significantly bigger amount of faces so this will never affect performance but will only fix some of these invisible walls.

[Chort]

It would be nice to reduce the number of faces as much as possible. Collision meshes is used to detect collision on CPU, which is slower then GPU. There is a lot of factor that may affect to performance. It need to find a balance between face count and perfomance. At least remove some useless faces.

P.S. just a thought...

[Bjord]

Looking at the before's, I am mentally sighing at how the person in change were even allowed to stay at TaleWorlds. That is not even funny. Looks like 5 minute effort(in total).

[Vibe]

Looking at the before's, I am mentally sighing at how the person in change were even allowed to stay at TaleWorlds. That is not even funny. Looks like 5 minute effort(in total).

drew a cubical collision mesh over everything like boss


This also makes me wonder how the character hitboxes look...

[DaveUKR]

It would be nice to reduce the number of faces as much as possible. Collision meshes is used to detect collision on CPU, which is slower then GPU. There is a lot of factor that may affect to performance. It need to find a balance between face count and perfomance. At least remove some useless faces.

P.S. just a thought...

Palm collision mesh has the biggest amount of faces among others (78), the smallest amount is 6 (lol!). Just to compare: collision meshes of destroyed walls (currently used in strategus) have 400 faces (from 100 to 1500 faces actually) and that's just a destroyed castle wall.

And there are a lot of native trees with 50+ faces (even some with 100+) so generally it won't change anything, I just made it a bit more accurate.

[FRANK_THE_TANK]

What Dave isn't telling anyone is that he has gimped all the trees so that he can climb up the top of them and snipe us all like dogs.

Damn you Dave! DAMN YOU!

[Meow]

Palm collision mesh has the biggest amount of faces among others (78), the smallest amount is 6 (lol!). Just to compare: collision meshes of destroyed walls (currently used in strategus) have 400 faces (from 100 to 1500 faces actually) and that's just a destroyed castle wall.

And there are a lot of native trees with 50+ faces (even some with 100+) so generally it won't change anything, I just made it a bit more accurate.

Besides the part where I already told you that the destroyed walls are not supposed to be in game, what do you mean by "just a destroyed castle wall"?
Obviously there are more trees around than destroyed castle walls, especially during normal gameplay.
Back when they were made they were done for testing, why they were actually included for strat I do not know since not only the collision models need fixing.


How much testing did you do with your new collision objects?
Performance wise I mean.
Here are the stats for the faces:

Name:	Original	Edited
bo_snowy_pine_2	22	24
bo_portcullis_a	8	154
bo_tree_e_1	10	60
bo_tree_e_2	13	70
bo_tree_e_3	10	70
bo_palm_a	28	78
bo_tree_a1	34	23

Could potentially kill the game on old CPUs on tree heavy maps.

Might have been a good idea to talk to someone (not me) about the intentionally bigger hitbox especially in the places where there is foliage on the trees.
Seems reasonable arrows and bolts stuck / deflected and horses stopped by heavy branches next to the trunk.
Thought about how easy this will make it for any ranged player on maps like Battle on Ice if they remove the foliage?

Also, which native trees have 50+ faces collision objects again?
Or did you just check the regular models and took the faces of those, then compared them to your collision objects?

Don't mean to be a dick here just thought I'd keep the undertone of our irc conversation about this.

[Ozin]

Nice initiative, though some of those collision meshes could use some optimalization. Repeatable use of trees with "high" collision poly count is bad for server performance, so try to find a balance between accurate representation of the mesh and performance.

[DaveUKR]

Meow, it's impossible to kill CPU even with heavy tree maps. Open xtree_meshes_c, most of them have more than 50 faces, open xtree_meshes_b, some of them have hundreds of faces (checked the first one under the cursor - bo_tree_8_c, 240 faces, same for other xtree_meshes files. bo_tree_a02 has 126 faces in tree_f.brf and others, cba to paste here. Just have a look and then post such huges posts.

Nice initiative, though some of those collision meshes could use some optimalization. Repeatable use of trees with "high" collision poly count is bad for server performance, so try to find a balance between accurate representation of the mesh and performance.

Most of trees in native .brf have more faces.

[Ozin]

I'm talking about collision meshes. The server doesn't need to render the normal meshes, only calculate collisions. Thus, keeping the collision meshes as low as possible is important. If some native tree collision meshes are bad for performance, it shouldn't be used as an excuse.

[Meow]

Meow, it's impossible to kill CPU even with heavy tree maps. Open xtree_meshes_c, most of them have more than 50 faces, open xtree_meshes_b, some of them have hundreds of faces (checked the first one under the cursor - bo_tree_8_c, 240 faces, same for other xtree_meshes files. bo_tree_a02 has 126 faces in tree_f.brf and others, cba to paste here. Just have a look and then post such huges posts.

Most of trees in native .brf have more faces.

Also, which native trees have 50+ faces collision objects again?
Or did you just check the regular models and took the faces of those, then compared them to your collision objects?

So that part of my post was wrong, now answer the rest of it instead of ignoring it?
How much testing did you do?