HaloMods "Classic" Read-only Archive

if you have a dual core processor, sapien wont run correctly unless you configure it to run on only 1 core.

I am trying to make a long warthog (APC warthog)

I have messed with the original model of the warthog and now I cant use the original warthog collision model in the tag for it. I tried just exporting the model its self as a collision model, but it wont compile in tool. I have never done this before so I dont even know where to begin.

i tried deleting the geometry of the ocean plane that was directly below the stream plane, but that didnt work. i think that fog volumes extend infinitely out and down from the plane. which makes sense if you think about it. i think the fog plane is like a window into the fog volume and having 2 fog...

hmm if you are correct, then that does present a problem. any recommendations for a workaround of some kind?

but they dont intersect thats the wierd thing the river is halfway up a cliff. If I made the river turn into a waterfall and then attach it to the ocean would that work?

I am trying to make a level that has two water planes (i.e. a river and an ocean) whenever I compile the map, I get an error saying two fog planes intersect in a cluster. does anyone know how to fix this without removing fog from one of the water planes?

sorry about the wrong section

I do have a river and an ocean but they never intersect. the river way above the ocean (I plan to have a waterfall but that will come later.)

I am trying to make a level that has two water planes (i.e. a river and an ocean) whenever I compile the map, I get an error saying two fog planes intersect in a cluster. does anyone know how to fix this without removing fog from one of the water planes?

ESP: 0x0013CB68 EIP: 0x7C90EB94, C3 8D A4 24 ????? EXCEPTION halt in .\import_collision_bsp\build_collision_bsp.c,#387:global_plane_count<MAXIMUM_BSP3D_DEPTH any ideas? the map compiled fine before... then I scaled it up and tool said i had an open edge. then i made the ceiling higher and this happe...

actually i need to revise my discoveries a bit. to do what i wanted i would have to change the (camera_set *camera name* 100) command to (camera_set *camera name* 0) the 100 is the amount of time it takes to move from camera to another. the (sleep 50) creates a delay between the execution of command...

ok the script works now thanks for the help, but the camera still flys arund. i am trying to get it to jump from one camera point to another instantly. does anyone know how to do that?

hey guys, i am trying to learn how to make a cutscene. i v been through dhalo's cutscene tutorial and i am using his script(slightly modified) but he neglected to explain how to get the script into the map. is there a spot in guerrilla to attach scripts to or something? also, the result of his tutor...

long story short it wasnt the vsync. i went on a journey through the bowels of the nvidia drivers and and wound up just setting my computer back to the original way it was back when i had the low framerate and suddenly, magically, it worked. 50 frames relatively consistently. thanks for the help wit...

i did this tutorial and it fixed the tearing problem but now i get like teh awful frame rates. i have 2 sli-ed geforce 8400 gs cards and i get less than 30 fps, on halflife 2 i get like 40-50 fps. how does that work?

thanks for that link Patrickssj6
that fixed everything

tiger direct says so so maybe they have come out with one.
http://www.tigerdirect.com/applications ... =P450-8408

i recently had to upgrade my comp to a socket am2 system i have 2 gigs of ddr2 ram and dual sli-ed 8400 gs gpus. (i dont mean to brag...this is purely in the interest of seeing if the hardware is causing the problem) so halo, in theory at least, should run like a charm. but, not so much sadly. i do ...

grrr. didnt work

ok so at some point a small child found its way to my comp while i was working on some halo maps and fiddles and touches all kinds of things now when i compile any jms file with tool it compiles fine but when i try to open the scenario file sapien loads for like a quarter of a second and then closes...