Topic: OP+ shiplist 2.2 now up!

[Auron]

There is no NEED to include the models at all, just the directories to put them in and the proper pointers in the shiplist.  Use .bat commands to copy the current models into the new directories.  So to a player that didn't want anything to do with custom models would show no difference at all but for the custom modeler he/she could enjoy the game even more.

[dderidex]

Wouldn't even need a .bat file.

The WISE installer software can create an install script that renames and copy folders just fine.

That's why I used for the SFC3 9-ship mod pack.

[FireSoul]

Quote:
There is no NEED to include the models at all, just the directories to put them in and the proper pointers in the shiplist.  Use .bat commands to copy the current models into the new directories.  So to a player that didn't want anything to do with custom models would show no difference at all but for the custom modeler he/she could enjoy the game even more.  

I don't like that method.


What if the installed directory isn't the default?
What if the user doesn't know where the SFC directory is on the HD? (not to mention the models)
What about ease-of-use I have just introduced in version 2.2?
What about the models.siz file?

Everyone seems to have a unique and different way of doing this. I'd like to do it my own way, with the same criticism I have given myself with the shiplist so far. Do you realize this is turning into a full-fledge mod? Please let me attend to this my own way..

-- Luc

[FireSoul]

Quote:
Wouldn't even need a .bat file.

The WISE installer software can create an install script that renames and copy folders just fine.

That's why I used for the SFC3 9-ship mod pack.  

I have used WISE in the past. It's a nice commercial installer software kit..
.. but I don't work there anymore since that employer went under a few years ago. Like in 2.2, I intend to use the NullSoft NSIS kit.

[EmeraldEdge]

Heh, so now I'm working on two sets.  One out of my imagination (but using a somewhat SFC style) and one trying to conform a little closer to SFB.  So much the better for the community, eh?  Hopefully I'll be relatively done with both tugs sometime this weekend.  I miffed the textures on one, way too orange, but that's neither here nor there.  Heck, I'll post the one Doug is talking about.

 

This is one that is made up of a Kitbash that Attibat and I did, and all new "pods".  The SFB style one will have pallets and will be based off the LCA hull so it will look much different (just need to un-miff the textures).

And for those who do not like it, it's not anything mandatory, just something I'm doing to help give some variety for when the OP+ supports new model directories. I'm not aware of that many tug models out there (especially for races other than the big 3) so I figured I'd give it a go.    

[FireSoul]

Folks, I think there are a few things you need to know about the next version and how I will include models..

1- The current shiplist kit is around 250kb. Modem users LOVE that. I intend to maintain support to these users. That means I will probably have 2 downloadables.
2- Arguing about how I'm going to do it is not going to help since I already made up my mind how.
3- Which models I will use will be carefully picked. I won't mix styles too much unless it makes sense.
4- Not everybody will be happy with the results. That's also why I will have 2 downloadables.

[dderidex]

WISE has a free version, so I will answer with that in mind:

Quote:
What if the installed directory isn't the default?

Allow the user to specify the installed directory.

Quote:
What if the user doesn't know where the SFC directory is on the HD? (not to mention the models)

The models will always be in the same folder under the base SFC folder.

The base SFC folder information is stored in the registry, and WISE can read that and use it as the default.

As I did with the SFC3 mod pack.

Quote:
What about ease-of-use I have just introduced in version 2.2?

Just clicking 'Next' a bunch of times seems pretty easy to me.

Quote:
What about the models.siz file?

I am unfamiliar with what that is?

[FireSoul]

I was discrediting .bat files, not the WISE installer.
.. as for the WISE installer, I already started with NSIS, so what's the point?

-- Luc

[FireSoul]

Anyways.. Please enjoy the current version of the shiplist. Dwelling on the next one's stressing me out right now. I have a nasty headache. Let me take care of it, my own way, the way I find it to work right.

-- Luc

[Mr. Hypergol]

 

Quote:
 Please let me attend to this my own way..
 

I'm sorry.  I thought you were soliciting input.....my bad.  I really like the way "your way" has turned out so far.  Keep up the "your way".  

[FireSoul]

Quote:

Quote:
What about the models.siz file?

I am unfamiliar with what that is?  

The model.siz file was introduced as an anti-cheat measure. The sizes of models from one side must match to the size of the models on the other. This file can also be used to resize models. It is checked during multiplayer games just like shiplists and other essential files are.


Before model.siz was introduced to SFC2 (thanks to Khoromag), the ability to cheat was easy.
ie: un unmodded player flew with an unmodded copy of SFC2. The enemy would hang back at range 30, pounding at him as if he's at range 0. The player did very little damage to the enemy. (range 30 being what it is)
The opponent would have a modded model for the ship in question.. .. something of the size of 30 like a planet for example. The player's model edge would be very close to the other ship while its center is still at around range 30 away.

If i am to handle models, I have to modify model.siz also, in the right way.

-- Luc

[FireSoul]

Quote:
 

Quote:
 Please let me attend to this my own way..
 

I'm sorry.  I thought you were soliciting input.....my bad.  I really like the way "your way" has turned out so far.  Keep up the "your way".  

Heh.. I was merely *HINTING* about what I have already started on..  I have it in hand, but there's a LOT of work to do, yet.

[MadElf]

Quote:
Folks, I think there are a few things you need to know about the next version and how I will include models..

1- The current shiplist kit is around 250kb. Modem users LOVE that. I intend to maintain support to these users. That means I will probably have 2 downloadables.
2- Arguing about how I'm going to do it is not going to help since I already made up my mind how.
3- Which models I will use will be carefully picked. I won't mix styles too much unless it makes sense.
4- Not everybody will be happy with the results. That's also why I will have 2 downloadables.

FS, you kick butt man, do the models in whatever manner you like!  GREAT SHIPLIST TOO!  Love the B racks on the X1, just makes em look better as well as fight better, and the new ships are cool too.  Heck, there are even a few klingon ones I'd be seen flying    

[FireSoul]

Hey MadElf, try out the new Boom arcs on the F5s. Don't trust the UI graphics. They're still FAL/FAR like before, except they fire down the rear of the ship too.

[Klingon Fanatic]

Quote:
Heh, so now I'm working on two sets.  One out of my imagination (but using a somewhat SFC style) and one trying to conform a little closer to SFB.  So much the better for the community, eh?  Hopefully I'll be relatively done with both tugs sometime this weekend.  I miffed the textures on one, way too orange, but that's neither here nor there.  Heck, I'll post the one Doug is talking about.

 

This is one that is made up of a Kitbash that Attibat and I did, and all new "pods".  The SFB style one will have pallets and will be based off the LCA hull so it will look much different (just need to un-miff the textures).

And for those who do not like it, it's not anything mandatory, just something I'm doing to help give some variety for when the OP+ supports new model directories. I'm not aware of that many tug models out there (especially for races other than the big 3) so I figured I'd give it a go.      

Yeah! More Ships!

Thank you Firesoul, EmeraldEdge and company.

KF

[dderidex]

Quote:
1- The current shiplist kit is around 250kb. Modem users LOVE that. I intend to maintain support to these users. That means I will probably have 2 downloadables.

That's why I was pushing for just copying the existing folders and leaving it up to modders to work with or not.  Only 1 download needed, then, and it would still be small.

I wouldn't want to see 2 downloads of different shiplists (one with new models, one without).

Not if it can be avoided.

I mean, really, how many D2 servers are running the OP+ pack right now?  A few?  And you want to divide that up even further between 'OP+ with extra ship models' and 'OP+ without'?

As it is now is...okay.  If you wanted to break out the hull types more, I'd really rather you just copy the existing model folders used, and use those - so a single shiplist could be used for all.

[Holocat]

How about:

  The first installer install OP+, and the *structure* needed to add models, ie, the directory trick that's being talked about here.

  The second installer not install OP+, but just the models that will be produced to support OP+, meaning that it would fill the structure created by the first installer.  So long as the default models in use now match up in size to the models that replace them, I'm hoping that the siz file won't have to be adversely affected.

Other than HD size requirements expanding, this should allow peaceful intergration of OP+, OP+ with models, maintain the newfound ease of installation, and allow them both to play on the same dynaverse/gsa without problem.

A simple suggestion,

Holocat.

[Cleaven]

That suits me. All I want is a couple of models to differentiate the Romulan Kestrels from the Klingon ships.  

[FireSoul]

Quote:

Quote:
1- The current shiplist kit is around 250kb. Modem users LOVE that. I intend to maintain support to these users. That means I will probably have 2 downloadables.

That's why I was pushing for just copying the existing folders and leaving it up to modders to work with or not.  Only 1 download needed, then, and it would still be small.

I wouldn't want to see 2 downloads of different shiplists (one with new models, one without).

Just let me do my stuff.

There's going to be 2 downloadables.. and the two will have EXACTLY the same shiplist.txt, etc.. and will be fully compatible to each other. Yes, the small one would be copying Models files from the current SFC stuff to compensate.

This is already happening, so please don't try to convince me otherwise.  

[FireSoul]

Quote:
How about:

  The first installer install OP+, and the *structure* needed to add models, ie, the directory trick that's being talked about here.

  The second installer not install OP+, but just the models that will be produced to support OP+, meaning that it would fill the structure created by the first installer.  So long as the default models in use now match up in size to the models that replace them, I'm hoping that the siz file won't have to be adversely affected.

Other than HD size requirements expanding, this should allow peaceful intergration of OP+, OP+ with models, maintain the newfound ease of installation, and allow them both to play on the same dynaverse/gsa without problem.

A simple suggestion,

Holocat.  

Hey Holo..
.. I have the installers already figured out... and working.