Blackbeard wrote:
2. convert the .obj to .bfxm using mesher.exe
What is an MTL file, and how do I generate one, or are they generated automatically, or what?
Blender generates one when you export to .obj (it actually creates two files).
You just have to edit it a bit with a text editor.
Blackbeard wrote:
3. add the textures to the MTL
I'm mostly confused with this one, because of the two methods of editing/adding textures with mesher and via xmesh.
If I want LODs, do I have to use xmesh? It just looks like a lot of work for what has to be done.
You can do it both ways, the easiest IMO is with the MTL file, since you can go directly from obj -> bfxm like that in one go. But obj files do not support LODs, so if you want LODs, you'll have to go through the xmesh format. obj -> xmesh, do the editing, then xmesh -> bfxm.
Honestly, these parts you can leave to the "pros". As long as you have and contribute the assets, someone else can manage all this complicated stuff. But you would do well in understanding it, it's not hard once you get used to it.
If you want to know how it goes, you can always convert some of the existing models to xmesh and take a peek.
Blackbeard wrote:
4. edit units.csv
I think I can handle this one, it's fair amount of editing, but it looks rather straightforward.
Don't underestimate this step. You have some complicated stuff here, like figuring out the exhaust coordinates and sizes, mount points, subunits, etc...
You should use blender to get coordinate numbers, btw. It's not magic, lots of people think they have to guess. Not so. You get the coordinate with blender, and put it in the units.csv
Blackbeard wrote:
5. do some testing of the unit in-game
The page says that the info is obsolete and being reworked, yet the info looks just the same as my save games... ?
Because there's an easier way. You edit data/missions/modelview.mission to use your ship instead of the llama, and invoke VS with that mission as argument: vegastrike modelview.mission. Voie-lá
Blackbeard wrote:
6. making the ship buyable
I don't understand part 2 of this. At all.
I think it amounts to editing the master parts list file to give your ship a price and category, and then, if you added it to a new category, you'd have to make that category part of the traded items for each base type. Because units.csv contains a column which specifies which kind of stuff a base will trade, you have to include your ship's category or it won't be traded anywhere. This step you can skip if your ship is placed on an already-traded category.
Blackbeard wrote:
7. giving the ship to npc
Need to do more digging on this one, looks relatively intuitive.
Very simply done, editing faction_ships.py, adding your ship's name to the appropriate tables (though it's a python script, you'll see quite prominent data tables, just follow the format and you'll do fine).
.
) ships with blender, and so far have modeled a fleet carrier with 15k polys, and a supporting fighter, with 33k polys. (The carrier is just at the starting point atm, I intend to finish up with about 60k polys)
What size is a battleship going to be? Or a carrier?
