anyone in this forum have a copy of Toolio that they could give me?

I want to use it so that I can edit some halo 2 and 3 maps

with the map editor

You'd honestly be better off using regular tool. Toolio and Tool++ both tend to bypass things that end up breaking the game and giving mass amounts of errors/exceptions

I know that, I just want to compile it to see what happens, besides its a halo 3 map, so there can't be that many problems with it, it was made by bungie

ask killzone then you wont want to do it

No, I assure you, I want to do it, no matter what anyone else says, I just want to compile some halo3 maps, so that I can edit them, with the map editor

PROPOGANDA, lies...

I have been using the program tool pro for a while now and never had exeptions that weren't my fault, hell you know the program bigass was compiled with, tool pro. and no one complains about that map exeptioning...

Since all links are dead, here is one I uploaded

File Name :	tool_noob.exe (File not down)
File Size :1754021 byte
File Type :application/x-dosexec

MD5:1180ed09c11c4daef225489c7a5af18d
SHA1:c97e1bb0ce9d40f63570a7f58654a35dc3c1d729
Scanner results

Scanner results:12%Scanner(s) (5/39)found malware!

Now we just have to wait for dennis to remove it, because there once was a troll version wich could give some guy acces to your pc.
Edited by Dennis on Oct 8, 2014 at 04:08 PM

That's because it all depends on how you use it.
As far as I know Bigass doesn't have any open edge errors or the sort. I'm pretty sure the decision to use tool pro in the first place was because of the map file size limit.
If you're gonna use tool pro like a nub then of course there's bound to be issues. And it's always the people that can't be screwed fixing the issues themselves that have problems.
As it's always said, there are limits to these things for a reason.

Oh poo you guys are party poopers. Do what you want and see what happens. Take what these guys say you into consideration but continue with what you want until they say "I told you so". More fun (an embarrassing) that way.



Play safe.
Edited by Spiral on Oct 8, 2014 at 02:27 AM

look you guys, I KNOW what the problems with compiling this sort of thing are, this is not a thread for the dangers of Toolio, this is simply a I want to see what happens how bad can it be does anyone have a copy thread. Also, I already have tool pro, as far as I know, tool pros only difference is the removed file size cap, tool pro can be downloaded legitly from the halo demo mods website.

If using toolio causes halo ce to crash and burn who cares? its not the end of the world, but your cautionary tales are not going to help.

Now please, does anyone have a copy!?

(also, id like to note that most of the BSP's im trying to compile are halo 2 not halo 3)
Edited by Jobalisk on Oct 8, 2014 at 04:07 AM

well use Opensauce that's all you need well if you would like biger maps and better looking textures well that what I use it for
Edited by DOOM899 on Oct 8, 2014 at 09:04 AM

ive tryed open sauce, but it just dosn't cut it, I need toolio.

how big is your map when you use os tool to make the map?

Its not a matter of big, its a ripped halo 2 map, that's the problem, In order to compile it I need to have something that will ignore all the coplaner surface geometry errors.

FYI nearly coplanar geometry errors do not prevent maps from compiling. My guess is that the H2 geometry is not sealed, since H2 used different sealed world rules than H1 did.

yes, that is what I mean. also, I have ensured that the world is sealed.

actually, I have found that they export fine as models, that works and allows me to import them into sapian. of course this means that id need to make some very interesting BSPs entirely covered in sky texture to accommodate for the lack of collision models but...

Edited by Jobalisk on Oct 9, 2014 at 06:26 PM