I've created a couple of custom placeables by loading up an area model(in Gmax) and deleting everything except the object I want. Every thing works fine except that I can now pass through the object.
Is there any way to keep this from happening? You can't walk through other placeables in the game.

Keep in mind I am not a modeler and only have basic Gmax skills.
TIA.

I've created a couple of custom placeables by loading up an area model(in Gmax) and deleting everything except the object I want. Every thing works fine except that I can now pass through the object.
Is there any way to keep this from happening? You can't walk through other placeables in the game.

Keep in mind I am not a modeler and only have basic Gmax skills.
TIA.

You'll need to create a Walkmesh file for your placeable that defines where characters cannot move. The .PWK file should be named the same as the MDL/MDX files for the placeable model.

I'm not sure how easy it is to create new walkmesh files from scratch, so if you can find an existing placeable that has roughly the same shape as your new one you can recycle the PWK file from that model.

You need a .pwk file (object walkmesh). You can make your own but if you don't want to go through the trouble, you could also pick one from an existing object that has about the same shape as your custom object.


Edit: meh...stoffe has beaten me to it :p

Hmm.. I don't think anything in the game is as large as what I have. So how would I go about creating a .pwk file or editing the size of an existing one?
I have an ugly work-around but it makes my module take longer to load.
TIA.

EDIT: It only needs to be a large rectangular area. Maybe enlarging a workbench .pwk.

You'd need to do this in Gmax but I wouldn't be able to tell you the details but I think Oldflash and t7 made some. A large rectangle shouldn't be complicated.

If you created a custom placeable, cant you just alter it, keeping the shape and export it as a dwk or pwk files?

OR In the .Utp file there is a block PC box. Tick or untick that to see what happens ;)

Actually the .pwk was not that difficult to make.
I was able to get one into Gmax but I didn't know how to export it back.
So here is what I did:

1. In Kotor Tool, I opened plc_reptab1.pwk with the PWK/DWK editor.
2. Save as ASCII.
3. Open my model in Gmax.
4. Open plc_reptab1.pwk(ASCII) in Gmax.
5. Open plc_reptab1.pwk(ASCII) in a text editor .
6. Under "verts"(in the text editor) I started manually changing coordinates
by small values then saving the file.
7. in Gmax I kept reloading plc_reptab1 to see the changes
until it covered the same perimeter of my model.
8. In Kotor Tool open the PWK/DWK editor an select "Open ASCII PWK"
and re-open my edited plc_reptab1.pwk(ASCII). And then I select "Save as Binary". Rename it the same as my model file, then save.
Note: While saving, when the PWK/DWK editor asks you for the walkmesh parent, just click OK for the default.

The only problem now is that my model is tall, so If I'm close to it(facing it), and I spin around, my POV will pass through it. At certain angles it's invisible.
I'm working on a new area and I'm using the placeable to block out certain part of the area model to sell the "Illusion" of a new area.
So hopefully someone might have an idea how to make it more like a wall or wall locker. Those force your POV foward when you spin your orientation and doesn't clip through them when your close to them.
TIA.

Let's see. You want a rectangle walkmesh.
Let's take a rectangle walkmesh, like one which is used for beds on telos station. Those beds are placeables and has walkmeshes and most important are rectangles.
So, start KotorTools and locate BIFs=>models.bif=>Praceable Object Walkmesh=>plc_bed1.pwk (http://oldflash.125mb.com/wm/01.html)
Doubleclick on that. By doubleclicking you will start PWK/DWK Editor (http://oldflash.125mb.com/wm/02.html).
Hit File menu and select Save as ASCII... (http://oldflash.125mb.com/wm/03.html).
A small window will prompt you for a custom file name (http://oldflash.125mb.com/wm/04.html) but there just hit OK button.
Now start GMax (sorry, all tests are made under 3dsmax but shoud be the same for gmax), and under NWmax panel select plc_bed1.pwk (to see that file you need to select "All Files (*.*)" on "Files of type:") (http://oldflash.125mb.com/wm/05.html).
Now look at This picture. (http://oldflash.125mb.com/wm/06.html) I've marked with 1,2,3,4,5 and 6 the intrested areas.
One reclangle plane will be imported. Select that one(1) and in modify panel(2) hit "Build WOK Data" button(3). Some values will show up in "Boxes".
Lick on first row with values ans some infos will appear(5). Bring again PWK/DWK Editor and have a look to values on "Verts" section(6).
As you see on PWK Editor there are 3 columns. Focus on first two columns.
There are 4 values: 2 positive and 2 negative (6)
Also in gmax there are 4 values (5) pretty much like those from PWK Editor.
On "Editable mesh" (http://oldflash.125mb.com/wm/07.html) select vertex and move to another possition.
Hit again on AuroraWalkmesh, hit "BuildWOK Data", select first values row from "Boxes" and read the new values showed on "BL:" and "TR:".
Open plc_bed1.pwk with notepad and go to "verts 4". Under that there ar 4 lines with floating values (originals) which need to be replaced with the new values (in my example I replace -1.46323 with -2.2788).
Save the file opened with notepad.
Open again PWK/PDK Editor window by doubleclicking plc_bed1.pwk (under KT).
Now in file menu select "Open ASCII PWK...", select the one which was edited with notepad and again in same menu select "Save as Binary". (http://oldflash.125mb.com/wm/09.html)
Now there just 2 more important steps:
1 rename pwk file to have same name with your placeable model
2 put renamed pwk in override directory (folder).
That is all.
I case you want to know what is relation between placeable and walkmesh import plc_bed1.mdl (http://oldflash.125mb.com/wm/10.html) and plc_bed1.pwk (http://oldflash.125mb.com/wm/11.html) in same gmax session.

I did notice the "Build walkmesh data" section, but I didn't know what those values were. That simplifies what I did, thanks for the tip.