CMP to SUR Conversion Tests
-
LancerSolurus wrote:
**Hold your horses old man, it will be ready when it’s ready. BTW did you get that hedge trimmer I sent you?Just for you, a model from Freeworlds, the X Wing (courtesy of Sushi), as you can see it isn’t a perfect fit. If you want a form fitting sur, then you will need to build it by hand. This is a general purpose tool and isn’t meant for perfectly fitting sur files unless the model is prepped for it.
We’re going to be making a bunch of “server side” hitboxes, to improve performance, and from what I see there, the hitboxes your program is making is perfect for that. I really cannot wait to use it
You are doing an amazing thing for the FL Community, LS, I cannot say that enough!!**
-
ST puts his white-bearded face round the door…
Still no sign of LS’s multi-part sur generator.
-
Sushi wrote:
We’re going to be making a bunch of “server side” hitboxes, to improve performance, and from what I see there, the hitboxes your program is making is perfect for that.Does that work? Server and client having different .surs?
-
If it does work then it opens yet more cheating.
Does it?
I’m keen to try it out! lol
While I’m waiting for LS’s generator!
-
Yup. However it will only affect the NPC ship hitboxes as well as how they perceive hitting a player ship. PvP interaction will be unchanged. The reason why we’re doing this is that we’ve suspected more polygons in a hitbox ––> more calculations —> increase CPU usage ----> drop in performance.
-
**Thanks for the encouragement, still doing alot of tests and trying different layouts for the sur file. Multiple meshes in a single cmpnd part is being the problem. This is a by-product of the way the model is exported. Thinking about making a cmp modifier so it can split the mesh properly into parts. This is due to that the models that are modular in design wrap tons better than an all in one mesh.
Note to model converters, regroup your models before exporting to make the overall shape similar to a sphere, cube or cylinder for each group…**
-
Roger, Wilco!!
-
StarTrader peeks round the door again…
-
Scratches scruffy white beard in puzzlement…
-
**Sorry for the delay but I have a feeling this may be worth the wait….
I am in the process of designing a group separator for the CMP files. This means that you can simply export all of your groups in 1 group and this will rebuild the CMP file with as many groups as you originally intended, in the process breaking the 18 group barrier limit. In the meantime it will build new VMeshRef and Cmpnd sections to match, you know how I am, click a button and it’s done
The reason I’m doing this is that I have found that individual meshes take hits alot better than one big mass mesh. There is a good chance it will be integrated at the beginning on the sur creation process so it will be fully transparent to the sur building process. Plus I never much cared for the 18 part limit and this is an easy way to remedy it.
So keep your spectacles on old man, it’s coming soon.
On a side note, I did test how surs work and found something interesting. Surs can have holes in them. This opens the possibilty of attaching surs inside of surs simply by creating an opening. Anyways, enough experimenting, back to the grindstone.**
-
That is phenomenal news, LS! I think many of us are on the edge of our seats watching your sculpt your masterpiece
-
LancerSolurus wrote:
I am in the process of designing a group separator for the CMP files. This means that you can simply export all of your groups in 1 group and this will rebuild the CMP file with as many groups as you originally intended […].That means that it will make all groups from milkshape separate? What about parts consisting of 2 or more meshes (maybe because of texture)? That would also generate multiple surs for example one wing…that means i can’t just use it as [CollisionGroup] because each part of the wing would be a separate destructible component…
edit: by the way - has anyone of you taken a look on co_base_rock_large01.cmp and its sur? It has a multiple part sur for the root!!!
-
@ Quark - It will split meshes up into parts only if they contain more than 1 mesh. It is determined by the VMeshRef. I will make it optional. The main reason is because I haven’t got the bits linkage part worked out yet and the separate mesh part is already fully working. I will continue to work on figuring out how it’s designed so hopefully I can get the multi-part working (multiple meshes in 1 sur part). Tests show that without the linkage it uses the last sur with the same crc. As in if there are 10 parts named Root, only #10 will be used for collision.
-
ST thinks this is well worth waiting for and buys boxes of dried crackers, pull-to-open cans of bully beef and bottled water…
-
… added some chocolates and Nutella today…
-
ST… washed and dried his sleeping bag today, it was getting a bit smelly from the dampness in this unused room…!!
-
(grabs a pom pom… stands next to ST)
Lancer Lancer… he’s our man… he cant do it… noone can…
L.A.N.C.E.R. (shakes pom poms)… dam not enough for a human pyramid yet… oh well back to the start…
