.obj -> .sur converter

@ST: Pardon me? I’ve already done enough grunt work to know how it is. I don’t need no lessons from you, as much as I respect you as a modder. Feel free to defend your point, but personal attacks are unnecessary.

Now. Reading your post, it would appear everybody’s fine with broken tools and halfway done SURs. I re-read the entire topic and I cannot surmise what made you say that. Throughout, people are congratulating Schmack on making the tool and that’s about it really.

And here’s the party crasher: it’s almost certain all the vanilla SURs were built by hand. If you’re looking for a tool that’ll reproduce them perfectly, tough luck. Computers have a hard time doing models and I don’t expect they’d have any easier time making SURs for those models. If you want an automated solution, LS’s tool is as good as it gets. If you want truly optimized SURs, then you’ll need to do them by hand, just like how the devs did.

Schmack’s tool is fantastic in that as long as your geometry works, you’re guaranteed to have a working SUR. No fiddling with fucking MS3D trying to understand why it unwelded 34212 vertices and messed up your import. Just export to OBJ from your favorite graphics program and bingo!

Furthermore, it wouldn’t be a stretch to imagine a simple change to support drag and drop. Schmack, I think it’d be nice if you could add support for a configuration file that stores all the options the GUI offers and thus allows people to just drag and drop the OBJ file onto your EXE to produce a SUR file. The process is equivalent to using a command-line tool and typing the name of the OBJ file as the first argument, so it’s simple and it’d streamline the process even further. It then becomes a matter of export, drag, done.

Finally, ST, you set the guidelines and specifications, right? I don’t recall them being approved and you hiring Schmack or any such thing. You told what you wished to see, nothing more. You’re free to be a sad panda if you so desire, but don’t come in like that and say it doesn’t meet the “guidelines”.

this is turning out to be a really good tool.

i tested this out on two models. the first one was a normal poly model (1200 verts, about 2300 poly’s) sur file was generated and turned out rather good looking too.

the second model was higher poly model, about 11,000 verts, and about 9000 poly’s. it took a while but it did generate it. i had to redo it because i forgot to remove the hp poly’s. so i removed them and attempted to redo the sur generation, however this is where problems started. from this point forward the application throws a out of memory error 9 out of 10 times while the other 1 out of ten times it simple hangs on the generating tree … method. and it now does not matter the poly or vertex count, it just simply stopped working.

also you may want to consider multi threading the application. specially the routines that are the heart of the app.

cheers though mate, good job so far.

I’d argue that you shouldn’t be using a 10k+ polygon model for a SUR file. It should be like a fifth to a tenth of whatever normal model you’re using. At that point, multithreading would have little use because the generation would already be fast enough whatever the case.

I’d much rather see bugs fixed and features implemented

At 13000+ poly it gives a memory leak waning and freezes .
Yes it makes very nice surs, i tested with a solar with 6k poly with holes and worked very good.

anyone tested how it behaves with baydoors of dockables?

Downloaded the sur converter, opened MS3D, imported a ship cmp, exported as .OBJ. Was kinda confused when I fired up the converter but common sense always prevails. Left the 1st block at 5. Checked the 2nd and 3rd. Typed in the HP’s for the ship, hit go.

The sur it spit out looked beautiful, but kinda large, about 140KB….

So I fired up the dev server, launched FL, undocked. To my delight, no crash!! No server errors, no spew errors. Fired up 2nd pc and began shooting the hell out of it. Registers gun hits, missles and torps, flawlessly. Unmounted my shield and bumped it about 100 times, still going. I have seen the same behavior with single group surs I made using sur builder. They worked great just shooting at them, but under stress test about 18 out of 20 I made using it crashed between 10 mins to an hour.

I shut down the server, set zone to spawn 30 npcs and let it run. 2 factions both flying the same ship with the new sur, and a base shooting at them both. 2 hours now, no crash.

All I can say is EXCELLENT WORK!!!

The only problem I saw was the memory leak. Oh and since my girl has been out of town all week, she will want to kill you when she gets home today as its now 6:30am and I been up all night playing with sur files…

schmackbolzen, can you extend your sur program with the option to make sur for 3db-s also (the 3db sur dont have root group , its replaced with 00000000 instead of 2D8F6812).
It could be a box checked for example .
Those types of sur are used in all space scenery objects (asteroids) and it`s annoying to replace every time with the hex editor.

Schmackbolzen:

Very good results so far. Here’s my Avioki capital ship in space dock, with a new sur I can fly through all the gaps including the rear boom “nugget”, and collide with all body parts as it should. I was unable to fly through any body surface.

Good work, thanks.

Looking forward to the next step.

I’ve a problem with you tool, I open a cmp to obj model, I say 15 use convex hull,… I click go and the tool says invalid file name.
vulkorasdesolator.obj is the file name, what can I do.

there shouldn’t be any error if the file exists with exactly that name and if its truly a obj file and not just something with an “obj” extension.

Wow! You think I’m so idiot… ( No of cours, I’m kiding) I export at wavefront obj exporter, so it can’t be aan error from me, I will test somthing els to solve that.

StarTrader wrote:
Schmackbolzen:

Very good results so far. Here’s my Avioki capital ship in space dock, with a new sur I can fly through all the gaps including the rear boom “nugget”, and collide with all body parts as it should. I was unable to fly through any body surface.

Good work, thanks.

Looking forward to the next step.

can you detail how your cmp is done please ?
multipart ? exported with the 0.21 or 0.3 exporter ?

no offense, m8
its just obvious something’s wrong either with the naming or with the direction or with the file itself. it would work otherwise, wouldn’t it? you’ll get it, for sure.

It works, just an error of manipulation.

Freestalker means it was “Finger Trouble” - we all get it.

Hi Mirkha. It’s multi-part, 23 groups. I’ve attached it for you and anyone else who wants to see it, with its new sur and the .mat file.

The “nugget” ( actually I should call it “doughnut” ) is made in 4 parts - top, bottom and 2 sides. I could have made it in 6 or 8 parts to be more form-fitting, but it’s good enough.