Printable View
No matter what I do, I am making Tool screw up.
I'm so frustrated right now because it's not accepting the shaders I've defined no matter what I do. This is for a simple, 2- material BOX MAP what the heck?
E: Sel helped me out, now I know (kinda) what to do. I'm going to revisit this tomorrow b/c I'm too annoyed to continue lol.
You sure you converted it to an editable mesh before exporting?
I'm using editable poly. Does Tool not compile meshes or something?Quote:
Originally Posted by Limited
I think when exporting, bluestreak prefers mesh, blitzkreig does not care.
What I usually do is convert to editable patch, then mesh, then export. Be sure to save before you do so, it unhides every edge.
Yeah I managed to get it so that it SHOWS the bsp in game, now the problem is that the map comes out completely white lol.
Then you (most likely) don't have properly set-up shaders.
Make sure your BSP is referencing shaders that have actual bitmaps referenced in them (check in guerilla).
Why doesn't it just autocreate the shaders and compile my bitmaps? Or does it do that and I'm just missing something?Quote:
Originally Posted by teh lag
Shaders are a pain in the ass.
what you need to do is set up a multimaterial, and use that to texture the BSP. Name each one of the sub-materials to the shader you want it to use. Once you export and run it through tool, it will auto-search your /tags folder for the shaders to use.
Halo's engine was made in 2000. What do you expect? Nothing next gen of course. You have the run the commands to convert the tifs to bitmaps, go into guerrilla and create your shaders. Long procces, but it works and is worth it.Quote:
Originally Posted by Dwood