CMP to SUR Conversion Tests

Amazing LS, simply amazing.

This work will make everyones life so much easier with modding. I cannot wait to see what else you can do with this (or is there anything else??)

Sushi, W0dk4 -
Sorry, must have confused that mehtod with the other “zomgbay thing” that grouped all ship groups into the 1st group and used dummy groups!

I’ll download it and have a look at yours now.

LS -
I notice that the saucer is shown in dull white whereas the other parts of the NX-01 are bright white. HardCMP also showed “good” sur parts in bright white, and “suspect” and non-working sur parts in dull white, can you how did it do that?

StarTrader wrote:
Sushi, W0dk4 -
Sorry, must have confused that mehtod with the other “zomgbay thing” that grouped all ship groups into the 1st group and used dummy groups!

I’ll download it and have a look at yours now.

LS -
I notice that the saucer is shown in dull white whereas the other parts of the NX-01 are bright white. HardCMP also showed “good” sur parts in bright white, and “suspect” and non-working sur parts in dull white, can you how did it do that?

That’s the multi-part SUR. The Freeworlds guys are so insane they have 100k+ models and needed a technique for CMPs, too

FriendlyFire wrote:

StarTrader wrote:
…
LS -
I notice that the saucer is shown in dull white whereas the other parts of the NX-01 are bright white. HardCMP also showed “good” sur parts in bright white, and “suspect” and non-working sur parts in dull white, can you how did it do that?

That’s the multi-part SUR. The Freeworlds guys are so insane they have 100k+ models and needed a technique for CMPs, too

What do you mean FF, I don’t understand either part of your reply old friend?

LS’s utility (this one) will make the sur from the cmp, no?

But my question is how HardCMP showed good sur parts in bright white and bad ones in dull white/grey.

It seemed consistent. It was a good clue when my surs were going to be bad even before I tested them. So I thought it was a deliberate method in HardCMP and maybe LS had done the same?

What I meant is that the technique you described with dummy models that put all parts in the root group is for large SURs, not CMPs. The Freeworlds people had to develop a technique to work around both SUR and CMP group limits, but the CMP workaround doesn’t change how groups work (if there should be 36 groups, there will be 36 groups, which means that the models will work fine with LS’s utility).

great, keep going LS

FriendlyFire wrote:
What I meant is that the technique you described with dummy models that put all parts in the root group is for large SURs, not CMPs. The Freeworlds people had to develop a technique to work around both SUR and CMP group limits, but the CMP workaround doesn’t change how groups work (if there should be 36 groups, there will be 36 groups, which means that the models will work fine with LS’s utility).

Ah, right - but they also modified the cmp in the same way to add the dummy parts that matched the sur names, no?

Anyhow, yes the Freeworlds cmp method obviously is better and those cmp’s can hopefully then be used directly by LS’s 1024-group generator!

Wunderbar!

Well - come on then, LS, where is it?! Eh?!

Hedge trimmer - nope!

But don’t send a replacement yet, I’ll just blunt it!

Yep, that’s pretty good.

For myself I would make the engines and weapons separate groups to get a close-fitting sur for it.

Tip - Could also remove the weapon groups and export a temporary cmp so the weapons would not generate sur parts, then restore the original cmp for the game. As long as you don’t change any group names all should be well.

Ah - don’t forget my optional shield bubble thingy, huh? (Don’t worry about what anyone else wants, I don’t care, they’re all inferior!)

Just filling in time…
“Infamy! Infamy! (They’ve all got it in fer me!)” - Kenneth Williams, “Carry on Cleo”

Like it? Oh. OK, here’s another then:-
“Arabs are very intense people - they do everything in tents!” - Charles Hawtrey, “Carry on, Follow That Camel”

And one more for the record…
“No offence meant, just feeling a gay person - Uh-oh… yep, he sure is offended!” - StarTrader, “Avin’ a Laff!”

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.

Roger, Wilco!!

StarTrader peeks round the door again…

Scratches scruffy white beard in puzzlement…