tool.exe/command prompt what am i supposed to do!

Discuss HaloCE modding with the HEK tools here. For help, go to the Help Desk forum above.
Post Reply
User avatar
viperxp





Posts: 25
Joined: Mon May 23, 2005 9:01 pm

tool.exe/command prompt what am i supposed to do!

Post by viperxp »

ok i've finished exporting my map w/ blitzcrieg, how do i do the tool.exe/command prompt part, what do i enter and what is this part for? on the video tutorial it does not explain it at all...
Signature exceeded 500x120 pixels.
Katarn





Posts: 1638
Joined: Tue Mar 02, 2004 10:18 am
Location: http://www.videotuts.net/
Contact:

Post by Katarn »

I can't explain exactly how to do it, but i can tell you what it does. After you have your bsp exported, tool makes it into a file that the game can understand, then compile into a playable map.
Excalibur: id hunt him down and jerk him off
Excalibur: and drink the gallons of cum that come out
User avatar
Excal




Socialist Pyre

Posts: 1779
Joined: Fri Jan 02, 2004 9:55 am
Location: Bronx, NY

Post by Excal »

Go to the start menu and click on Run.... Then type cmd and hit enter. Then type "cd C:\program files\microsoft games\halo custom edition\" (without quotes). Now type "tool structure levels\mapname mapname" without quotes. I'm kinda rusty, so if it doesnt work tell me.
Image
User avatar
viperxp





Posts: 25
Joined: Mon May 23, 2005 9:01 pm

a new question lol

Post by viperxp »

ur not rusty at all Excalibur, but now that i typed it in it says "choose type for the shaker 'vipclif_ground' (vipclif is my lvl name) so i believe it's asking about the base or ground of my lvl, but i'm confused cause it has 9 choices for shaders of vipflic_ground 1.shader_environment 2.shader_model 3.shader_transparent_generic, and it goes on and on with shader_transparent stuff... which one should i choose?

Ok, here is what it says:

C:\Program Files\Microsoft Games\Halo Custom Edition>tool structure levels\vipcl
if vipclif
Couldn't read map file './toolbeta.map'
building intermediate geometry...
choose a type for the shader 'vipclif_ground':
1. shader_environment
2. shader_model
3. shader_transparent_generic
4. shader_transparent_chicago
5. shader_transparent_chicago_extended
6. shader_transparent_water
7. shader_transparent_glass
8. shader_transparent_meter
9. shader_transparent_plasma
choice (1-9):
Signature exceeded 500x120 pixels.
User avatar
Excal




Socialist Pyre

Posts: 1779
Joined: Fri Jan 02, 2004 9:55 am
Location: Bronx, NY

Post by Excal »

Don't go through with that. Go to your tags main folder and delete the shader that tool made. Then go to your maps folder in the tag directory and create a folder called shaders. Then make a new shader environment tag in Guerilla. Link it to the bitmap for your level ground and save the shader in the shader folder you just made but make sure you name the shader the same name you named the ground texture in 3ds max. Hard to explain, =\.
Image
User avatar
viperxp





Posts: 25
Joined: Mon May 23, 2005 9:01 pm

Post by viperxp »

OK I deleted the tags that it made.... but I couldn't figure out the next part where ur supposed to linke the vipclif_ground to the enviromentshader thing
Signature exceeded 500x120 pixels.
PDummy





Posts: 126
Joined: Mon Jul 05, 2004 3:07 pm
Location: NC
Contact:

Post by PDummy »

ok open up gurellia and go to file>new

now find shader_environment

choose simple under flags

go to base map and click the 3 dots and find the bitmap u exported for the map and choose it

now save the shader as 'vipclif_ground.shader_evvironment in the folder of the map ur making

(do this for all bitmaps in the level)

then try to export again in tool
Image
CS:S name-Kill
User avatar
viperxp





Posts: 25
Joined: Mon May 23, 2005 9:01 pm

Post by viperxp »

Ok i think i got passed the intermediate geometry now it's saying something is wrong with my collision geometry...

C:\Program Files\Microsoft Games\Halo Custom Edition>tool structure levels\vipcl
if vipclif
Couldn't read map file './toolbeta.map'
building intermediate geometry...
building collision geometry...
### ERROR couldn't update edge #14 (red).
### ERROR couldn't update edge #0 (red).
### ERROR couldn't update edge #7 (red).
### ERROR couldn't update edge #7 (red).
### ERROR couldn't update edge #5 (red).
### ERROR couldn't update edge #28 (red).
### ERROR couldn't update edge #21 (red).
### ERROR couldn't update edge #26 (red).
### ERROR couldn't update edge #31 (red).
### ERROR couldn't update edge #34 (red).
### ERROR couldn't update edge #37 (red).
### ERROR couldn't update edge #23 (red).
### ERROR couldn't update edge #18 (red).
### ERROR couldn't update edge #40 (red).
### ERROR couldn't update edge #39 (red).
### ERROR couldn't update edge #36 (red).
### ERROR couldn't update edge #41 (red).
### ERROR couldn't update edge #45 (red).
### ERROR couldn't update edge #42 (red).
### ERROR couldn't update edge #46 (red).
### ERROR couldn't update edge #43 (red).
### ERROR failed to build collision geometry.
### ERROR failed to import collision bsp.
Signature exceeded 500x120 pixels.
Post Reply