HaloMods "Classic" Read-only Archive

if youve been reading my posts here, and on the gbx forums, (in editing) you would probably realise that me and quite a few others are trying to figure out why only the a_ bsp works and how to get it working, Xhzjang is getting quite far into actually editing the bsps themselves!!

what im requesting is a team, probably me, a coder, guy who has gmax etc. you know....



anyways, without mono, i guess well have to do everything ourselves now! lol

other bsps work other than the a..........

Show us screenies of this then please....

actually, no other bsps work than a_ ones at the moment, becuase of dependancies, and i have confirmed this, there are hundreds of dependancies in the b_ one as i have posted on the gbx forums, read xzhangs posts

if u look in the files forum there are conversions of b40_b and b40_c

yeah, but not all maps can have _b and farther bsp parts.

but if they DID get the b40_b and _c to work... that means they either used the way that mono used for library... or they did it using HMTv3.5 and this means, _b and _c doesnt have any dependinces linked into _a, or they somehow got just the dependinces from _a into _b and _c and relinked them.

dilinator wrote:erm, i dont think netcode supports this trigger!

but, there are two choices, we try and import a trigger into mp halo, (very unlikely) OR, we find a way to either, merge the bsps together, either, a+b or a+c or if needed a+b+c and then put them into a map.

OR (even better)

find the global information form the a_ bsps and import them into the other bsps if possible.

halo's netcode doesnt support any trigger.

merging the bsp would lag the game, but it sounds like it could work in theory.

yeah this is a great idea, find the dependencies that r in _a and smack 'em into _b.

which ones got converted? examples, also, i found TONS of dependancies in the spsb.xml file, read the gbx forums for the exact values

Voided wrote:

dilinator wrote:erm, i dont think netcode supports this trigger!

but, there are two choices, we try and import a trigger into mp halo, (very unlikely) OR, we find a way to either, merge the bsps together, either, a+b or a+c or if needed a+b+c and then put them into a map.

OR (even better)

find the global information form the a_ bsps and import them into the other bsps if possible.

halo's netcode doesnt support any trigger.

merging the bsp would lag the game, but it sounds like it could work in theory.

yeah this is a great idea, find the dependencies that r in _a and smack 'em into _b.

no, it wouldn't work because you would hacve to add a shitload of data from the scnr file. I discovered that the actual BSP file somehow doesn't contain the actual points, because I extracted the same BSP (one from the original level and one from a sp>mp, which had many fucked places where there were random spikes and whatnot), and used the comp command in dos. then I fixed all the differences, and reinjected the bsp, but the sp>mp still had those fucked points. HMT messes the scnr file up, not the actual bsp.

http://www.gearboxsoftware.com/forums/s ... o=&fpart=1

read, already been sorted

WOOOHOOO, mono steps in and sorts it, I knew this would happen if we all kept moaning about the problem lmao