Just Google it.

whats tool_pro ???

sweet where do i get it?

need a link plz.
Edited by Spectre_the_grunt on Sep 2, 2011 at 05:01 PM

it will cause your map to exception and close at random. it's worth taking the time to just find out about the problems then fixing them.

i dont have a lot of problems its just that tool said map out of space and i dont want to here that.

It says map out of space for a reason. Halo becomes unstable when the map size is greater than 128MB.

unstable heh. my computer can handle it.

Halo becomes unstable. Your comp might run crysis 2 on max settings but Halo still exceptions because it's not built to handle maps over 128mb.

will open sauce fix that when it come's out then?

i really just want to try it anyway what's the worst that could happen.

Just don't release any maps you compile with Tool Pro.

sure.

took me 30 seconds to find it using the words: Tool pro halo. Sigh.
*LINK REMOVED BY ADMIN - no linking to known virus infected files
Edited by Dennis on Sep 2, 2011 at 07:08 PM

lolz. thx man :)

ahh crap how do i use it? it pops up then blam it gone.
Edited by Spectre_the_grunt on Sep 2, 2011 at 06:20 PM

Put in halo custom edition folder. Than open command prompt and type in tool_pro than command. For e.g
tool_pro build-cache-file levels\test\tutorial\tutorial

You just use the same way as normal tool but I don't recommend using because of crashing sometimes

yeah Exception rofl.

ah i got a map to work yeah for me lulz. :)
a little lagy.
Edited by Spectre_the_grunt on Sep 2, 2011 at 06:44 PM

Tool_pro is probably the most useless thing ever.
It lets you surpass the limit, but then the map exceptions. So there's no point in that.

hey spartan314. i have a problem im testing out JMS xporter and it come's up with this error.

http://www.megapix.com/?p=51MO4HNE&expid=LOXRGCGDP&expind=6

MEGA PIX DONT FAIL ME NOW!!

add me on xfire ill show you

xfire:ninjahaloguy

i dont know how to add you.

Press the + button down the bottom of the xfire app and than search me (ninjahaloguy) than press add

ok got it. come to xfire :)

There seems to be a massive desire in the halo community to bypass the games engine recently, with all of this tool_pro and OS stuff, I really don't understand why people are going to so much effort to go above and beyond what the game was meant to do.

People just can't seem to accept the absolute.

Despite what some people seem to believe, Tool_Pro and other limit bypassers indeed have their use. I have experienced with it my fair share to know what's good and what's not. What you should remember using it is that these limitations exist for a reason and if you break them, you must accept to pay the price. Some stuff like tag limit will definitely exception your map. While other programs like Tool Star allowed to bypass things such as open edge, they again still give you an exception when you play in game. The one limit you can bypass for sure is the Total Cache size. Not Tag space. Cache Size.


Then again, depending on the map and the size exceptions are more likely to occur but if you look at RPG_Beta6.2, the cache file is 152mb big. That's quite a bit over the limit. I had to play with it some to get a ''Stable'' release however. I also happen to have a Bloodcreek build that stands at an astonishing 230mb. Where does this extra space come from? As I said before, Do not Ever go over the ''Max Tag Space''. The extra space RPG_Beta6.2 and Bloodcreek take and share is actually the amount of BSPs involved. As some may be aware, RPG_Beta6.2 features a Day, Night, Fog weather system. Weather in Halo is generally BSP Generated. Tag space beeing "Single Biggest BSP" Size + tag = 23MB max, My map doesn't breach any core Halo limit so to speak. Bloodcreek uses a semi dynamic sun that also takes numerous different BSPs with different lightmaps. Again, Never do they break the max tagspace and never, without OS, will Halo allow it.

Exactly. I've compiled and released two tool_pro-compiled maps (the updated AoTCR and the new Whiteout in the Adjutant Map Pack) and they don't crash - either on the host or client side. I've yet to test them via dedicated server, though.

But all of this has just been slightly bypassing the CACHE limit, not anything else. Simply bypassing the cache limit is ok to a certain degree, but don't try anything else with it, or Halo will indeed crash upon loading the map.

...Not that I've had experience with such crashes, I'm just saying...

128m: no exceptions
129m: some exceptions
200m: frequent exceptions
220+m: instand exceptions
...in my experience with Valhalla and some test maps.