.obj -> .sur converter

Schmackbolzen - please contact me via PM if you would like to, I am tired of these argument-hunters. They can give out piss and sarcasm but can’t take it. I am only interested in your development of this tool, if you can then I will be delighted, if you can’t then I understand. Many thanks as always.

StarTrader wrote:
Hi Schmackbolzen

The holidays are in full swing as far as I know, and hopefully you are enjoying your free time too.

If you will continue with the converter to make it multi-group, and maybe add the basic hardpoint shapes that the original exporter already puts in (but this is not essential for this converter as long as the HPIDS are included), then you will have two dedicated and grateful fans.

Only 2, because clearly nobody else is interested, no-one else has said so here or anywhere.

So clearly they do not want it and will not use it even if you do complete it.

As you know I have been criticised by several members for being selfish in asking for it before, since nobody else really wants it, so it is only for me and now Ezekiel also said he wants it.

Nobody else said they want it.

Not FF, not W0dk4, not the Discovery developers, not any other team developers, and not anybody else either.

So nobody else needs it.

Not for their current mod, and not for any future mod either.

So this means all your work will be only for me and for Ezekiel.

Yes, I am rubbing their faces in it.

So I have an idea - I might be able to pay you a moderate commission to develop it only for me and for Ezekiel, since nobody else wants it.

In this case of course, you and I will own the rights to the converter, and I will not release it to anyone else, only to Ezekiel, under a no-distribution agreement, and I will ask you to not release it to anyone else without my permission too.

But if you do not want to continue with it in the next month or so, then no matter - but please say so now, so that I don’t continue to hang around waiting any more.

After all, only I and Ezekiel really want it.

And my need is for my personal use only.

So I await to know if you will continue shortly please.

I know that when the next term starts (or if you start in a job) you will not be able to work on it.

Many thanks.

Why would anyone develop anything if they don’t see adequate support for it?

This is what I wrote. Yes I prodded and poked a bit, to encourage the others of you silent ones who are also waiting to say so.

The antagonistic response of some of you was ridiculous.

Incessant? Since when? And I am not the one to be accused of slander, FF. Go read.

You have developed a habit of responding badly to me, no matter the subject. This is biased and immature, I don’t care if I am in your “bad books”, you have a really bad attitude problem not only with me but also with several other people and it is unwarranted, and it’s all yours to grow up and resolve. Stop threatening that it’s your server and that there will be repercussions, this really is childish.

ST you can sepparate the sur into multiple groups manually with a hex editor if you really need to make the multi-part sur, its a little more time-taking but will work (i made for a 2-part turret, when the sur builder failed to make the 2 parts properly).

Thanks Cata123, I know, and there are of course other ways to do this too.

But we need a tool that will do all of this, because of the time the other ways take.

Since using this sur maker, I’ve come across a error that I don’t understand. When ships run into each other, there is a large amount of lag or the game crashes all together. The same happens in mission against the ships. Here they are if someone would look into it for me. Note: They use vannila weapons.

Alucard, do your surs use the Hpid hardpoints section? If so, you’ll need to remove them or you get that lag you’re describing. FW:ToW had a similar problem.

Schmackbolzen wrote:
No, he is not using the section. I was about to recommend the opposite, like Gibbon posted to add HpMine01, HpCm01 and HpThruster01. The question still is, which HpId is needed to avoid crashes, which is the whole purpose why I added this feature for now. The goal still is to read them from a .cmp and add the corresponding simple geometry.

You also should test collision for each ship with a vanilla ship (if you have not done so yet) and report back. That would make things easier to pinpoint.

These are cap ships, so they don’t have a mine, thruster, or countermeasure. I am not following on “The goal still is to read them from a .cmp and add the corresponding simple geometry.”

Here is what I have done.

I have ran/shot into them with a vannila ship. Full collision, no problems there. They move fine till they run into another ship using a sur from your builder. They vannila shoot at them fine as well. I have made more surs for fighters and have the same problem.

I’ll try and add the hpid’s to the sur builder for the fighters, but for the caps, I kinda lost on what to do.

The point Sushi was making is that you should only add HpMine01, HpCm01 and HpThruster01 (obviously numbering as many as required if you have more than one of those). Adding others was the cause for our lag issue at least.

Thank you Schmack, very much appreciated.

it’s great !

Looks sweet mate. Thanks for your great work.

Woo! That looks epic!

Shiny

A very big “Thank You Schmack” for You
It’s Outstanding

Many questions, few answers (yoda^^^)

If you looking for a ship with more parts and big parts, take a look at the Atlantis City model ( there are few on the net )
I use an atlantis city that a friend have modeled, and your tool crash if the milkshape DX tool indicte more than 10 000, if i take down the count below 9000- 10 000, your tool make a good SUR.
Don’t know if it helps you.

Good luck

I think the most important point here is that the tool should first of all handle vanilla models and create surs for them as perfectly as possible, because many custom models are poorly made, exceed the maximum poly counts, and have non-standard naming of parts and groups.

Many large custom models have been “cobbled together” from two or more cmp files. This is not a good criteria to judge or debug the tool.

Once it operates seamlessly on large vanilla surs (there are many battleships and landscapes etc) then it can be used against custom models and if real bugs are found (not due to imperfections in the model) and can be reproduced, they might be fixed.