Making Surs for 3dbs

Gisteron

the vanilla model of the nomad fighter is a 3db. my animated version of it as cmp is working with a copy of the 3db’s sur file. dunno whether ther is however difference, but i know that i can be hit by gun and collide with solars and spaceships and that there is nothing the spew complains about.

? Offline

When I tested using cmps as asteroids, the game always CTDed so I’m trying 3ds now. At least it doesn’t crash anymore…

StarTrader

Can you not resize the standard asteroid .3db’s and .surs to make new sized ones? Shape should not matter so much?

Sorry if I’m missing anything, just jumped in to suggest this.

Sushi

Aigle-Imperial wrote:
Plain asteroid models. What were your settings? Oh and they are single group.

Ya, they have to be single group or they won’t work. As for the settings, I always have to play around with them to get the optimal result. Upload the models and let me have a go with them.

? Offline

Here’s one of them (the one I’m testing with, going by the principle that once I get this one working, I can do all the others in exactly the same way.)

http://bsgcrossroads.net/Static03.3db

Sushi

See if this works? Haven’t tested it myself but used settings that made a decent hitbox.

cata123

I had this problem too with surs for custom 3db asteroids and the problem is in sur root group.
If you dump a vanilla asteroid sur you will see that the root group is replaced by 00 00 00 00 .
So open the custom sur with a hex editor and replace all occureces of2D8F6812with```
00000000

? Offline

@ Sushi: I tested it with the same results as before, detects hits from time to time but very unreliable. What were your settings?

@Star Trader: Tis basically a very good idea, the only problem however is that you cannot create any new and extraordinary shapes this way.

@cata123: Thanks for the hint, I’ll try it out.

Edit: Works indeed, thanks again!

? Offline

Hmm, after extensive tests I have found the scheme to be reliable but not 100% reliable. Using only one asteroid model with one single part sur, there are still some asteroids that don’t detect hits, although other asteroids that use the same model and sur and are only 50 metres from the described ones are working properly.

cata123

Increase the collision detection check -```
common.dll 0EDB44 0.01f = collision detection min check distance (increasing this will fix issues with the sur collisions on objects > 130k from center of system) ~w0dk4

? Offline

I tried to implement that hack with 0.05f, 0.5f and 5.0f, neither one helped. Error logs aren’t much help either.

cata123

One curiosity : you can test the model changing the type of sur .
Types of sur are :

02 - scenery
03 - weapon/ammo/damage object
04 - ship /station
This is how it’s named in FLModelTool .
I wonder if you try with another type of sur , what is the result.
The type is at 6C offset in each single mesh sur ; you can change also with hex editor.

? Offline

Had a look at it, seems that stock FL asteroid surs use 02, whereas LS’s sur builder gives you 00. Now testing.

Edit: the offset appears to be C rather than C6, at least that’s what I have to change if I want Flmodeltool to recognise it.

? Offline

Alright, tested it and still no luck. I’ll try it again tomorrow, maybe I am more lucky then.

adoxa

cata123 wrote:
One curiosity : you can test the model changing the type of sur .

That is misinformation - it is not type but the count of tags within the first sur part. I think this was discussed in one of the sur generator threads. Use SurDump to view the structure of a sur (or turn on logging in the MilkShape importer).

cata123

I see .

This is from lancer solurus`s sur format explanation from digital brilliance.
So what is with this sur tag about .

adoxa

The tag is one of !fxd, exts, surf, hpid; the count (what FLMT erroneously called type) is how many of those occur. Why don’t you download my SurDump and have a look at its source?