Here's my question. I have been working on a mod for the xbox version of Halo for a pretty long time now. And I have a continuous problem I have yet to fix. No matter if I use a full, clean, tagset with no modifications whatsoever, I always run into the same problem, on any single player level. The level loads... you can play the level just as you would normally and everything works EXCEPT for when you get to the first checkpoint or where it would normally say "loading..." and then the game just freezes... it happens on every single player map always at the first checkpoint. Any ideas about how I could fix this? I could post a video of a couple different maps if need be... (though I have no idea what use it would be)

how's your ram?

You need to download more RAM.

They're halfway right. You might need a console that has more ram (devkit or solder job). The other problem could be your map (compare your sha-1 to the stock campaign map and if it's different then you probably have some kind of problem) Is the map compressed? Are you on NTSC or PAL or NTSC-J?
Edited by Banshee64 on May 1, 2013 at 05:13 PM

Pmed you!

what version xbox?

--- crap, should've edited my old post, delete this one maybe?

Edited by OrangeJuice on May 1, 2013 at 08:05 PM

Well, I have many different scrap xbox consoles laying around, so I suppose I could upgrade the RAM, as my current console is TSOP flashed and I have a soldering kit laying around somewhere, but that doesn't help me much if I ever want to release my campaign mod.

And yes, the maps are different, I guess it's something weird with the way Arsenic compiles maps, but it does compress them though. I'm not sure about the NTSC, PAL, or NTSC-J, but I know for a fact I am on either a v1.0 or 1.1 xbox, if that helps any.

If you are playing as anything other than Master Chief like a grunt or an elite or something like that the game will freeze at checkpoints.

Changing maps from NTSC, PAL, or NTSC-J can be done with HEX Edit easy.

If maps are to large. They don't work right on the Xbox with out a mod.
If you are building a sp moded version of the game you may want to download the moded coop version of the game from halomods and mod that.

Its been forever sense I moded halo on xbox. and even when I did it was all mp mods. or Halo CE to Xbox halo 1 conversion I should say.
You may want to take a second look at all your HUD tags.

A xbox360 DEV kit or other box. is much more practical for a project like this.

RAM Has nothing to do with your problem what so ever.
Edited by jackrabbit on May 3, 2013 at 06:33 AM

Okay, so I guess the first thing I need to figure out is what version of Halo I have. NTSC, PAL, or NTSC-J. Because if my map was compiled for NTSC, but I have the PAL version, you're saying it would freeze like this, right? So basically all I need to do is find out what version of Halo I have, and then change the map accordingly?

If that's true, then how do I go about checking my version of Halo to see if it is PAL or NTSC?

I honestly don't remember but you could open the XEX with a hex workshop.

But anyway I don't think the map would even load up in the first place if your Region
was wrong.

what xex mods are you running anyway?

It should say It next to the DVD badge on the disc you backed up from.
Let's hope you have a disc, hence this forums' rules about stuff like that...

tsop..... Have you deleted the cache and formatted X Y and Z?

Edit> tsop..... And halo doesn't like BIOSes that are bigger than 256k!
Edited by OrangeJuice on May 3, 2013 at 10:47 PM

Yea, I have a disc, two actually. lol. Ones scratched to hell and will never work again though, and the other I let a friend borrow. I bought them both from gamestop, one right after the other broke. So I would assume they would be NTSC, right? I bought them here, so it seems only natural that it would be an NTSC version. So I think it's pretty fair to say it's NTSC.

On the note of the TSOP, I think I have iND-BIOS flashed that is maybe 256k, not sure, I will have to look when I am home next. (I'm at my dorm right now, and I get out for summer break next week) But what are Halo's "symtoms" if I were to have a BIOS larger than 256k? Because right now my main problem is that it won't load maps that I compile with Arsenic past any checkpoint (or at least that's how it seems). But the stock maps work fine with no problems. There's only a small different between the maps I compile with Arsenic and the maps that came with halo, usually only a few megabytes difference if not less.