150 réponses à ce sujet

[Renzatic]

Bannor Bloodfist wrote...

The apply to all bit can cause serious issues for you as you get more detailed/complicated in your objects. For instance, the wok/walkmesh, must be set as a walkmesh, not a trimesh. Beyond that, your helpers should not be changed from what they are currently assigned as. IE the model base should not have anything like a trimesh assigned to it.

VICTORY! BOUT DAMN TIME!

The last bit was the problem. I had my trimesh modifier attached to my helpers. Once I got rid of that, the model showed right up in NWNE no problems.

Well, almost no problem. My textures look like they've been downscaled and desaturated a bit, and the alphas have huge black borders surrounding them. That might just be the NWNE renderer though.

I'll export the depot and see what it looks like.

edit:

Ahahahahahaha!



Dunno why it never occured to me to put the whole building on one tile. But it did. And I did it. And now it works.

This has been an absolute bastard, but I'm finally getting the hang of it.

Modifié par Renzatic, 19 décembre 2010 - 05:16 .

[Michael DarkAngel]

Renzatic wrote...
VICTORY! BOUT DAMN TIME!

WOOHOO!!!

Renzatic wrote...
Well, almost no problem. My textures look like they've been downscaled and desaturated a bit, and the alphas have huge black borders surrounding them. That might just be the NWNE renderer though.

Concerning alphas...

In the MDL Trimesh Parameters rollout you'll see "Transparency Hint".  Change the value in the spinner to 1 for any mesh whose texture has an alpha.  If you scroll a little further down that rollout you'll find the "Material Data" group.  Check "Over-ride Mat Values" and then you'll be able to change the Ambient/Diffuse/Specular colors and Shininess value of the textures.  What you see in the color boxes are the default values.  You can also change the self-illumination color of any mesh by changing the value of that color box.  Black meaning NO self-illumination.  NWN accepts a Diffuse map only, and a lot of the settings that you can change via the Material Editor are not considered by NWMax upon export.  Most settings are made via the various modifiers.

[EDIT]I should add changing/setting any of the values of the modifiers have no visible effect in Max, you need to export and view in either NWNExplorer or in-game to see what your settings have done[/EDIT]

Whenever you're ready I'll give you the run-down on creating a valid walkmesh and then getting your tile(s) into game.

Great work so far


  MDA

Modifié par Michael DarkAngel, 19 décembre 2010 - 05:41 .

[Renzatic]

Michael DarkAngel wrote...

WOOHOO!!!

YEAHHHH!

Concerning alphas...

In the MDL Trimesh Parameters rollout you'll see "Transparency Hint".  Change the value in the spinner to 1 for any mesh whose texture has an alpha.  If you scroll a little further down that rollout you'll find the "Material Data" group.

That helped a bit, but there are still problems. I'm assuming some of what I'm seeing is the dreaded cookie cutter effect...

I'll mess around with it a little more, and see how it turns out.

 

Whenever you're ready I'll give you the run-down on creating a valid walkmesh and then getting your tile(s) into game.

I think I'll wait on that til tomorrow on that. I've been spending 4+ hours a night on this for the last week. I'm wanting to turn in early at least once here.

Thanks for the help so far. You've all kept me from pulling my hair out and going bald from frustration on more than one occasion.

edit: one question that just occured to me: smoothing groups. Do they work in NWN?

Modifié par Renzatic, 19 décembre 2010 - 06:25 .

[Zwerkules]

Yes, smoothing groups work in NWN. You can have up to 32 smoothing groups.

[Renzatic]

Excellent. That'll help out tremendously.

I decided to take a day off, but tonight I'm going to get this all ingame, with walkmeshes and properly working alphas, and everything else that needs to be done. From what I've seen and read, the walkmesh doesn't seem to be too difficult to do (which probably means it'll be hard as hell and take me three days to do), but I'm still kinda confused about the alpha heirachy bit.

Oh, I also made some edge tile cliffs to test out. They're 10x10 on X and Y, but to get them looking like cliffs, I had to go 18 meters on Z. From what I've learned, that's alright as long as the walkmesh doesn't extend up that far, right? What I plan is for it to follow the contour of the ground about halfway into the tile then shoot straight up about a couple of meters when it reaches the base of the cliff. It doesn't need to be any higher than that, since there won't be anything behind it.

Modifié par Renzatic, 20 décembre 2010 - 08:51 .

[Bannor Bloodfist]

Actually, the "Z" value is pretty well limitless, but there things to consider as well. The game allows you to "raise" tiles, one level at a time. Each level is controlled by two entries in the beginning of the .set file.

HasHeightTransition=1
Transition=5

You MUST create ALL the tiles necessary to make the connections though. And this means the base tiles need to be created all at once, as the engine will not allow you to raise ANY tile unless all the possible connections for that tile exist in the .set file and the .mdl exists.

Anyway, you can easily set the top of your Cliffs higher than the default raised height, so you could easily go to 18 meters, You CAN create them without walkable space above (at cliff top height) or you can create them with walkable space up there, of course you would have to create tiles that provide a path to the top as well.

Generally, in Bioware sets, the cliffs are NOT raised per se' and the walkmesh stops about the 5 meter height, while the actual visible faces of the cliffs extend as high as needed. However, that walkmesh MUST extend to all 4 corners of the tile. So, your cliff top faces on the walkmesh would be set to either type 2 (recommended) or type 7.


Walkmeshes are fairly easy to create.  Sometimes, I just duplicate other objects, and attach them all together, weld verts where necessary and it's done.  
Remember these things though: 
1) A walkmesh must be a single object.
2) A walkmesh can NOT have overlapping faces.
3) A walkmesh can NOT have gaps (missing faces)
4) A walkmesh MUST extend to all 4 sides and all 4 corners.  IE, it must have an edge all the way around the tile.
5) A walkmesh can NOT have any faces that extend over another face.  IE, your cliff can NOT extend outwards over the walkable grass section at the base.  In other words, a walkmesh has a single "Z" that is useable in game.  This sounds a little confusing, but it means that you can NOT walk under a bridge and also walk over that same bridge.

There are likely a few other things you will run into, but doing and learning will be best for those.

Modifié par Bannor Bloodfist, 20 décembre 2010 - 09:26 .

[Renzatic]

Easy enough. And to get it attached to the model, all I do is add an Aurorabase, set it to walkmesh, and export it by itself with a certain name. Like say tctt_wa01_01. That'll correspond to tctt_a01_01. Then the entry in the .set file, it'll look something like this:

[TILE01]
Model = tctt_a01_01
Walkmesh = tctt_wa01_01
TopLeft = Woods
TopLeftHeight = 0
TopRight = Woods
TopRightHeight = 0
BottomLeft = Woods
BottomLeftHeight = 0
BottomRight = Woods
BottomRightHeight = 0
Top =
Right =
Bottom =
Left =
MainLight1 = 0
MainLight2 = 0
SourceLight1 = 0
SourceLight2 = 0
AnimLoop1 = 0
Animloop2 = 0
Animloop3 = 0
Doors = 0
Sounds = 0
PathNode = A
Orientation = 0
ImageMap2D =

So if I've got this right, as long as the walkmesh closely matches the intended walkable surfaces on the main tile, everything should work fine ingame.

Now for the cliffs, doing a walkmesh for it isn't too difficult. If I've read you right, the end result should look like a square block on half the tile, with nothing overlapping. I guess I gotta look at it like it's reading the mesh from a top down perspective, so anything that overlaps on Z will confuse the engine.

The only thing that confuses me is how to write it into the .set file. The wood tiles are easy, they just attach to other wood tiles, but the cliff always has to attach to other cliff tiles. So assuming the cliff is facing south, the set file should look like this...

[TILE05]
Model = tctt_c01_01
Walkmesh = tctt_wc01_01
TopLeft =  Cliff
TopLeftHeight = 0
TopRight =  Cliff
TopRightHeight = 0
BottomLeft = Woods
BottomLeftHeight = 0
BottomRight = Woods
BottomRightHeight = 0
Top =
Right =
Bottom =
Left =
MainLight1 = 0
MainLight2 = 0
SourceLight1 = 0
SourceLight2 = 0
AnimLoop1 = 0
Animloop2 = 0
Animloop3 = 0
Doors = 0
Sounds = 0
PathNode = A
Orientation = 0
ImageMap2D =

If I got this right, I think I'm beginning to understand how set files work. There are still alot of entries I draw a blank on (like crossers, terrain entries, and how to determine height), but I believe I'm getting there.

And if anyone wants to see it, this is the current state of the tileset. I baked AO in around the bottom of the depot to make it fit in a little better. The upside is it looks pretty neat, the downside is I had to add two unique .tga files into the scene. It isn't too bad, because downsizing the base ground tile textures to 512x didn't cause me to lose too much quality. So all four of those tiles now take up the memory of 1 of the original 1024x textures.

Modifié par Renzatic, 20 décembre 2010 - 09:56 .

[Bannor Bloodfist]

Some quick additional notes:

1) Create the wok/walkmesh as a seperate object inside the same file as the main tile. Set it to walkmesh, then attach to aurora model base.

to get a cliff into the set, you will need more than one tile.

one where you have plain grass level.
One where you have a half tile wide cliff on right side
One where you have a half tile wide cliff on left side
One where you have a full cliff.


That is what I meant when I said you have to create everything at once, or the game won't allow you to paint them.

topleft = cliff and topright = woods
topleft = cliff, and topright = cliff
topleft = woods and topright = cliff


so, three complete tiles.

You will also have to adjust the terrain count in the .set file up by one, and add the additional terrain definition for cliff.

It can get real complicated, really fast, the more terrains you add the more work you have to complete to make them work together.
xxx

Modifié par Bannor Bloodfist, 20 décembre 2010 - 11:39 .

[Michael DarkAngel]

Renzatic wrote...
Easy enough. And to get it attached to the model, all I do is add an Aurorabase, set it to walkmesh, and export it by itself with a certain name. Like say tctt_wa01_01. That'll correspond to tctt_a01_01. Then the entry in the .set file, it'll look something like this:

[TILE01]
Model = tctt_a01_01
Walkmesh = tctt_wa01_01
TopLeft = Woods
TopLeftHeight = 0
TopRight = Woods
TopRightHeight = 0
BottomLeft = Woods
BottomLeftHeight = 0
BottomRight = Woods
BottomRightHeight = 0
Top =
Right =
Bottom =
Left =
MainLight1 = 0
MainLight2 = 0
SourceLight1 = 0
SourceLight2 = 0
AnimLoop1 = 0
Animloop2 = 0
Animloop3 = 0
Doors = 0
Sounds = 0
PathNode = A
Orientation = 0
ImageMap2D =

So if I've got this right, as long as the walkmesh closely matches the intended walkable surfaces on the main tile, everything should work fine ingame.

Um, no.

If we return to our simple tile from above I'll continue where we left off.  This time without pictures as I think you have a pretty good handle on what's going on.  However, if you or anyone wants them, I'll add them later.

Select the mesh we have created.  From the "Plus" rollout of NWMax Plus click on the "Clone Selected" button.
Right-click in the current viewport and select "Unhide All".  Press "H" on the keyboard to open the "Select Objects" dialog.  Select the object named Clone_______  (fill in the blank with the name of your original mesh).
With the "Modify" tab selected, open the "Modifier List" dropdown and select "Aurora Walkmesh".  Once applied you should notice the color of the mesh change to brown in any viewport that has "Smooth + Highlights" checked.  Your walkmesh is now set to "Dirt".  To change this, from the Modifier Stack, expand "Editable Mesh" and select the "Face" sub-object.  [Based on my simple tile from above I want to change all my faces to grass.]
Hit "Ctrl-A" on the keboard to select all faces.  Scroll through the rollouts under the Modifier Stack until you see "Surface Properties".  You'll see a group labeled "Material".  You'll want to use the up/down arrows of the "Set ID" spinner to scroll through the available options.  I think someone posted them earlier, but I'll post them here again.

 1 -- Dirt
 2 -- Obscuring
 3 -- Grass
 4 -- Stone
 5 -- Wood
 6 -- Water (walkable)
 7 -- Nonwalk
 8 -- Transparent
 9 -- Carpet
10 -- Metal
11 -- Puddles
12 -- Swamp
13 -- Mud
14 -- Leaves
15 -- Lava
16 -- Bottomless Pit
17 -- Deep Water (non-walkable)
18 -- Door
19 -- Snow
20 -- Sand

Select the value suitable for your use [mine is 3] click in an empty space of the viewport to de-select your faces [I always like to de-select prior to leaving sub-object mode].  Click on "Face" in the Modifier Stack to leave sub-object mode.
Link your newly created walkmesh to the modelbase.

Because we have cloned the original mesh we need to re-apply the "Aurora Trimesh" modifier.
Select your original mesh and add the "Aurora Trimesh" modifier and reset any necessary parameters.
Now export your tile as above.  You should notice an increase in size of both the .mdl and .wok files.

When adding your tile to the .set file the "Walkmesh=msb01" line of each tile never changes.

Next up; Getting it in game


  MDA

Modifié par Michael DarkAngel, 21 décembre 2010 - 01:36 .

[Renzatic]

Sorry about taking so long to get back to you on this. I've been kinda swamped these last couple of days.

Thanks to your instructions, everything went through quite easily. I'm a bit confused about some of the specifics of the naming schemes, but I'll get to that later. For now, I'll walk you through what I did step by step, so you can see if I did anything wrong.

This is the entire mesh for the scene...



The ground is snow, the ramp up is sand (because I didn't have a gravel option, I figured it'd be the next best thing), the rails are metal, the tracks and porches are wood, and the main building itself is obscuring. The mesh is divided into 4 different objects, each pertaining to a specific tile. The only goofy bit is the roof, but I don't think that'll matter unless someone shoots an arrow up there. 

The first tile I exported was the bottom left tile with the entire depot attached. The walkmesh only covers one quarter of the building, but if I'm following you correctly, that shouldn't be a problem when I attach the scene to the other 3 tiles.

To get more indepth, my first step was to import my walkmesh on top of the first tile and make sure everything lined up. It did. So I hid everything else, added the walkmesh modifier, and defined each surface with the appropriate material. From there, I unhid my tile, linked the walkmesh to the tile in much the same way I'd tether a tile to an aurorabase. Then I went back in, made the aurorabase with the usual settings, linked those, and added a trimesh modifier to just main tile geometry. I assumed I've done everything correctly here, because the mdl file was larger, and it's the first time I've had an export pass a sanity check without giving me any errors. It even showed up in NWNE no problems.

Now the only bit I'm vague on is naming. Do I have to name the walkmesh clone_insert_base_mesh_name_here, or can it be anything as long as it's linked? And lastly, is every walkmesh named msb01 in the .set file regarless of the model?

I think I'm close to getting this. Once I figure out how to get it ingame, and adjust my alphas, I think I have the basics down, and can start my tileset in earnest.

Edit: One last question regarding the aurorabase helper. I can put it anywhere on the mesh, as long as it's sitting at 0 on Z, right? I put it down near the bottom left half of the tile for easier access instead of as near to the center as I could.

Modifié par Renzatic, 24 décembre 2010 - 12:54 .

[_six]

Renzatic wrote...

Do I have to name the walkmesh clone_insert_base_mesh_name_here, or can it be anything as long as it's linked?

It can be anything - heh, most of mine end up being called Object09 or Plane04 (or "walkmesh" if I'm feeling particularly generous).

And lastly, is every walkmesh named msb01 in the .set file regarless of the model?

Yes. There are quite a few quirks in NWN like that where features written into file formats were ultimately taken out or replaced with a simpler solution.

One last question regarding the aurorabase helper. I can put it anywhere on the mesh, as long as it's sitting at 0 on Z, right?

Each aurorabase must be positioned at 0,0,0 in relation to each individual tile. So if you have a 2x2 group of tiles where the whole group is centered at 0,0,0, your four aurorabases should be at -500,-500,0 / -500,500,0 / 500,-500,0 / 500,500,0. So there's one at the centre of each 10 metre chunk.

This is because every NWN tile (even tiles that are part of groups) are individual entities that are exported using the central point of the model as a base - this way it's easy for the toolset to arrange, rotate, position them etc. The order the tiles are specified as part of a .set group defines their position when painted as that group. For instance, if you had a 3x1 group, you'd have three 10x10 metre tiles, with the centre of each placed 10 metres to the right of the last by the toolset.

Modifié par _six, 24 décembre 2010 - 01:27 .

[Renzatic]

_six wrote...

Each aurorabase must be positioned at 0,0,0 in relation to each individual tile. So if you have a 2x2 group of tiles where the whole group is centered at 0,0,0, your four aurorabases should be at -500,-500,0 / -500,500,0 / 500,-500,0 / 500,500,0. So there's one at the centre of each 10 metre chunk.

Grand. Now I gotta figure out how to peg it right at the dead center of my tiles in Max. There's an easy way to do this, right?

edit: figured it out. I set up the snap toggle and moved it right to the center of the tile. I'm about 99% sure it's dead center, though I don't know how to check coordinates in Max just yet.

Got yet another question though. My tile is set just a tiny,tiny hair above Z. It's one of those situations where it's at 0.06 blah above, and it won't snap it to the appropriate position on the grid even with snapping enabled. Will that make any difference with the aurorabase being set at 0?

Modifié par Renzatic, 24 décembre 2010 - 02:27 .

[Bannor Bloodfist]

Use F12

That will open an window where you can set the position of things. Then just select any item you with to screw around with.

You do the same with the aurora base, etc, any item on the scene that you can select.

Edit:  Oh, be sure to set your system units AND your display unit scales to metric, that will help a bit with getting more normal numbers.  You can also adjust your snap settings.

Modifié par Bannor Bloodfist, 24 décembre 2010 - 04:11 .

[Michael DarkAngel]

Renzatic wrote...
This is the entire mesh for the scene...

Looks good

Renzatic wrote...
From there, I unhid my tile, linked the walkmesh to the tile in much the same way I'd tether a tile to an aurorabase.

This part bothers me.  Not sure if you stated it wrong or not, but your walkmesh should be linked to the aurorabase not the tile.

Aside from that, sounds like you did everything correctly.


  MDA

[Renzatic]

Bannor Bloodfist wrote...

Use F12

That will open an window where you can set the position of things. Then just select any item you with to screw around with.

You do the same with the aurora base, etc, any item on the scene that you can select.

Edit:  Oh, be sure to set your system units AND your display unit scales to metric, that will help a bit with getting more normal numbers.  You can also adjust your snap settings.

Whew. Thanks. I tried and tried looking for all the numerical entry stuff in Max, but couldn't find a single damn thing. And even worse, because Max is so prevelant around the internet, unless you search for exactly what you want down to the smallest excruciating detail, you'll end up with a billion and one different googles that are similar, but ultimately don't help you out at all.

The only way I could fix it was exporting it back to Modo, and that killed off all my modifiers, Had to redo everything. Oh well, it's good for practice at least.

Michael DarkAngel wrote...

This part bothers me. Not sure if you stated it wrong or not, but your walkmesh should be linked to the aurorabase not the tile.

Nope, you read me correctly. But if you're bringing it up, then it means I must've misread you at some point. It's an easily fixed problem though. So it's no big deal.

 Now from here on out, most of the work required getting my tiles ingame revolves around editing text files, right?

[Michael DarkAngel]

Renzatic wrote...
 Now from here on out, most of the work required getting my tiles ingame revolves around editing text files, right?

Not only text files.  Yes, the .set file is text and if needed .2da files are text.  However, the other necessary tileset file, xxxxxpalstd file is an .itp file which is GFF (Generic File Format) based.  A binary file format.  There are tools which allow you to easily edit these files, so it won't be too much trouble.  Just learning how to use a new tool .


  MDA

[Renzatic]

Michael DarkAngel wrote...

...allow you to easily edit these files, so it won't be too much trouble.  Just learning how to use a new tool .

Hey, from what I've already slogged through, a couple new tools shouldn't be any problem.

And speaking of slogging, I've come upon a little problem here. Out of my four tiles, 2 of them fail the sanity check with this error:

Sanity Check done threw a monkey wrench my way with this...

Checking node tcsw_d04_01
Checking node ignore_NGon01
Checking node tcsw_d04_01ml1
Checking node tcsw_d04_01ml2
Checking node Depot_Tile_4
Checking node D_Walkmesh_4
Bad Edge: 150 Vert pair: [-500.025,0,759.795],[-500.025,-250,759.795]

Bad Edge: 151 Vert pair: [-500.025,65.5,759.795],[-500.025,0,759.795]

Bad Edge: 159 Vert pair: [-500.025,65.5,537.75],[-500.025,65.5,759.795]

Bad Edge: 165 Vert pair: [-500.025,65.5,111.25],[-500.025,65.5,537.75]

Bad Edge: 171 Vert pair: [-500.025,83.5,0],[-500.025,65.5,111.25]

Bad Edge: 177 Vert pair: [-500.025,250,0],[-500.025,83.5,0]

Bad Edge: 178 Vert pair: [-250,500,0],[-500.025,500,0]

Bad Edge: 183 Vert pair: [-500.025,500,0],[-500.025,250,0]

Bad Edge: 195 Vert pair: [-500.025,-500,759.75],[-250,-500,557.563]

Bad Edge: 196 Vert pair: [-500.025,-250,759.795],[-500.025,-500,759.75]

I can't exactly see what it's telling me here, but on a semi-educated guess, I figured it might be the 2cm vert issue I've been warned about. I go back into Modo, check for any unwelded verts, and do a distance weld for any within that range. It did catch a few, and I figured that'd be it...but...it wasn't. It gave me the same error.

With that exhaused, I'm drawing a blank. From the coordinates, it looks like whatever the issue is lies somewhere near the center of the tile, but everything looks pretty good there from what I'm seeing.

Any idea what's going on here?

[Michael DarkAngel]

Renzatic wrote...
And speaking of slogging, I've come upon a little problem here. Out of my four tiles, 2 of them fail the sanity check with this error:

Sanity Check done threw a monkey wrench my way with this...

Checking node tcsw_d04_01
Checking node ignore_NGon01
Checking node tcsw_d04_01ml1
Checking node tcsw_d04_01ml2
Checking node Depot_Tile_4
Checking node D_Walkmesh_4
Bad Edge: 150 Vert pair: [-500.025,0,759.795],[-500.025,-250,759.795]

Bad Edge: 151 Vert pair: [-500.025,65.5,759.795],[-500.025,0,759.795]

Bad Edge: 159 Vert pair: [-500.025,65.5,537.75],[-500.025,65.5,759.795]

Bad Edge: 165 Vert pair: [-500.025,65.5,111.25],[-500.025,65.5,537.75]

Bad Edge: 171 Vert pair: [-500.025,83.5,0],[-500.025,65.5,111.25]

Bad Edge: 177 Vert pair: [-500.025,250,0],[-500.025,83.5,0]

Bad Edge: 178 Vert pair: [-250,500,0],[-500.025,500,0]

Bad Edge: 183 Vert pair: [-500.025,500,0],[-500.025,250,0]

Bad Edge: 195 Vert pair: [-500.025,-500,759.75],[-250,-500,557.563]

Bad Edge: 196 Vert pair: [-500.025,-250,759.795],[-500.025,-500,759.75]

Any idea what's going on here?

That would be the "Weld to Nearest cm" check.  Which, the name is slightly mis-leading.  It really doesn't have anything to do with welding.  But it does check to make sure all of an objects verts are positioned to the nearest full cm (ex. Bad Edge: 196 Vert pair: [-500.025,-250,759.795],[-500.025,-500,759.75] the verts should be positioned at Vert pair: [-500,-250,759],[-500,-500,759])


  MDA

More on this later...

[Renzatic]

Hmm. This doesn't sound like something that'd be easy to fix. I'd have to track down each one of these verts, and move them by fractions of a millimeter.

It did give me the option to ignore the error while I was exporting. Is this something I can do? If I can't, I guess I'll have to set each plane of verts to absolute coordinates. It'd almost be quicker (and a helluva lot less messy) just to redo the mesh, if that's the case.

edit: actually, it'd be fairly easy to fix if I had a way to track down each individual vertex point. It gives me a number, so there has to be a way to find it.

Modifié par Renzatic, 24 décembre 2010 - 08:03 .

[Michael DarkAngel]

Renzatic wrote...

Hmm. This doesn't sound like something that'd be easy to fix. I'd have to track down each one of these verts, and move them by fractions of a millimeter.

It did give me the option to ignore the error while I was exporting. Is this something I can do? If I can't, I guess I'll have to set each plane of verts to absolute coordinates. It'd almost be quicker (and a helluva lot less messy) just to redo the mesh, if that's the case.

edit: actually, it'd be fairly easy to fix if I had a way to track down each individual vertex point. It gives me a number, so there has to be a way to find it.

There is a button in the "Plus" rollout -->> "Clean Model" with check boxes above it.  At the moment it is kind of broken (as in "Does not work as intended").  However, there is a work-around to make it do what you need.

Turn off shadows for ALL meshes (under the "MDL Trimesh Parameters" of the AuroraTrimesh modifier make sure the "Shadow" option is unchecked).  Uncheck all options under the "Clean Model" group of the "Plus" rollout except "Desparkle".  Select the modelbase of the tile you wish to fix.  Press the "Clean Model" button and it should round all your verts to the nearest cm.  Don't forget to turn shadows back on as necessary.  And check your edge verts on your walkmeshes to make sure they were rounded properly.


  MDA

Sorry for the short posts previously, but they were breaks between xmas wrapping and the wifey was keeping me on a short leash.  Now its time for sleep

[Renzatic]

Thank God, that did it. Every single one of these evil damn tiles are now exported with walkmeshes.



MDA, I greatly appreciate you waiting up on me. Go to bed knowing you, once again, saved a little bit of my sanity.

[_six]

Just a side note, you can also bring up text input for position, rotation and scaling in Max by right clicking on the position, rotation and scaling buttons on the taskbar respectively.

[Renzatic]

_six wrote...

Just a side note, you can also bring up text input for position, rotation and scaling in Max by right clicking on the position, rotation and scaling buttons on the taskbar respectively.

What I really need to do is read a basic Max tutorial. It looks like I'm gonna be spending a goodly amount of time in it, so I might as well learn to use it for a bit more than setting up scenes.

So here I am. At the last little bit. I'm following Mr. X's tile tutorial Zwerkules linked me to about a week ago. So far, it's all pretty straightfoward stuff. I'm adding the depot into the default NWN forest tileset, so I named the set to ttf01.set into the override folder, guessing that it'll add the extra entries to the default one inside NWN. The entries themselves look something like this...

[TILE168]Model                              =   tcsw_d01_01Walkmesh                      =   msb01TopLeft                            =   ForestTopLeftHeight              =   0TopRight                          =   ForestTopRightHeight            =   0BottomLeft                    =   ForestBottomLeftHeight      =   0BottomRight                 =   ForestBottomRightHeight   =   0Top                                      =Right                                   =Bottom                              =Left                                      =MainLight1                       =   1MainLight2                       =   1SourceLight1                   =   1SourceLight2                   =   1AnimLoop1                       =   1AnimLoop2                       =   1AnimLoop3                       =   1Doors                                   =   0Sounds                                =   0PathNode                          =   AOrientation                       =   0ImageMap2D                   =

(okay, the forum must've had an embolism or threw up or something. I'll post a picture instead).



...and the rest follow suit, going up to 169, 170, ect. I added the group in as...

[group28]Name=DepotRows=2Columns=2Tile0=168Tile1=169Tile3=170Tile4=171

(pretend this is in decending order)

Pretty easy so far. Next up, I extracted the .itp file, and opened it with ITP Tools. This is where I start getting vague. The tutorial only has instructions for adding one tile, whereas I've got 4 tiles in my little group. It says to leave the element ID blank, but to put in 2 for Number of Element Data Items. I'm thinking this is to correspond for his tile and walkmesh. So this mean I put in 8 there? I'll try it out, but I'd like to know exactly what I'm doing here for future posterity and all that.

Modifié par Renzatic, 25 décembre 2010 - 03:41 .

[Bannor Bloodfist]

Pretty easy so far. Next up, I extracted the .itp file, and
opened it with ITP Tools. This is where I start getting vague. The
tutorial only has instructions for adding one tile, whereas I've got 4
tiles in my little group. It says to leave the element ID blank, but to
put in 2 for Number of Element Data Items. I'm thinking this is to
correspond for his tile and walkmesh. So this mean I put in 8 there?
I'll try it out, but I'd like to know exactly what I'm doing here for
future posterity and all that.

Nope, wrong, entirely.


You only add one tile into the itp, and you add it to the specific set of groups/features already in that itp.

Typically, for Bioware standard type tilesets (The new castle rural does NOT count but the forest should) you have 3 main entries.

1st one is for 'features' these are single tile features, that show up in toolset in the features sections.

2nd one is for 'groups' and these also only have a SINGLE entry for each group, regardless of the size of the group.

3rd one is for entire new terrains, or crossers.

Each entry in the actual sub-list for groups, has several lines... Each main line should be numbered, and anything you add to the list should be added to the bottom of the list as a new number..   This is where that bit about adding two for the number of data elements comes from.

Each of those entries has 2 sub entries as well. One is either a Name or a Strref (Name if you enter your own name, a strref that points to the tlk file if you wish to use the tlk table.)
he second line is the RESREF, Cresref, which is the actual tile mdl name. In your group case, this would be the mdl of the first tile in your group.


Note:  I use this TlkEdit by EwaldTheUnimaginative, as it will edit any of the gff files, and it is soooo much easier to use.

Modifié par Bannor Bloodfist, 25 décembre 2010 - 03:50 .

[Renzatic]

Bannor Bloodfist wrote...

Note:  I use this TlkEdit by EwaldTheUnimaginative, as it will edit any of the gff files, and it is soooo much easier to use.

Looks like something I'd like to use, but Java isn't cooperating with me at the moment. Since the latest update, I've had garbled text in random java applications. Some work fine, and some don't. TLKEdit looks like it doesn't, and as far as I know, there's no way to easily fix it. I guess I'm stuck with IPTTool for now. : \\\\

Okay, so taking what you said into account, and checking out the folders inside of ITPTool (wish I had another choice here), it looks like the second folder is for groups. The first, according to the tutorial, is for individual tiles, and the 3rd looks like features (opening up element=0/List List gives me a bunch of names such as cliff, stream, road, instead of generic tile names). Going by what you said and the tutorial, my entry should look something like...



It looks somewhat flipped upside down compared to the rest. My tile entry is on the bottom, and the top is the name. Dunno if that makes a difference, but it shouldn't be too hard to fix if it does cause problems.

I'm still kinda vague on it, though. The way it looks, UINT32 STRREF = ##### points towards a specific name buried in some table, whereas mine adds the name in regular text. RESREF RESREF points towards the file itself, and adds it to the editor, which then leads to the .set file, and assembles the group from there to put ingame. Sound about right?

edit: I poked around in it a little more, and it doesn't look like the .itp file has entries for every single tile, just the basic archetype. Like say the forest has 50 different cliffs. It only has one cliff entry. So that means all my variations are linked together somehow in the .set file, and the .itp is just there to get the entry "cliff" into the features box.

Man, this crap's harder than calculus.

Modifié par Renzatic, 25 décembre 2010 - 04:51 .