well i got tool++ tryed it figured it would save time but it starts up i go to build-cache-file select it then pree run and it goes for ever and doesnt work? i have vista 64bit with lotsa ram.

A lot of people say that about TOOL++. My self do not care for the program. I like the comand prompt.

Sorry! No help fixing the problem other than use the tool program that comes with HEK.

P.S. I do have a tip: copy and paste your command prompt .exe application in your Halo CE directory. The CMD.EXE application file is located in your system32 folded in windows.

krispy1001

ya thats what i have been doing and will stay with it

Did you put the Tool++ file in the Halo:CE directory??? Cause if not, it won't work.

Tool++ is ok when you're beginning to learn how to map, and you use it for compiling maps. But when you need to compile bitmaps, models, and animations, it's best to go back to the original tool.

I would also like to get Tool++ working on my 64bit Vista pc.

It runs fine, but when I specify a command and click start it just takes forever - I have a suspicion that it's something to do with administrative permission, but not sure.

Any help would be appreciated. I have tool++ in the CE directory, along with tool. I made a link to tool++ on my desktop and a shortcut for cmd.exe, which I copied to the CE directory.

Tool++ speeds up the map compilation process by removing the need to keep typing loads of stuff!

Please help. Plaese do not suggest that I use tool, I know how to use tool, but it's much quicker to use the tool++ GUI.

Just make a bat file if your to lazy to type.

omg, it's not about being too lazy - its quicker!

And for those that say they'd prefer not to use a GUI and continue using a CLI - they're probably the same people who are still listening to crackly old vinyl records.

There is no difference in speed between Tool++ and Tool. All Tool++ does is run Tool with the info you entered.

Sure, it might be a bit easier. But Tool++ can be buggy. Above all, Tool++ forces you to wait until the command is finished to see its output rather than outputting the info in real time.

When you're doing things like lightmaps which take a long time, it makes you impatient not seeing the progress right in front of you.

Just use .bat files with a "pause" command so it doesn't close right when it's finished. With batch files, you can just type the command in once and run it. In the future, all you have to edit are the parameters, save, and then run it again. Much easier.

Also, nice stereotype - we do it because Tool is meant to run in a Command line, not because we refuse to keep up to date or something.

Funny though, I actually do have many LPs at my house, including Abbey Road. We never play them anymore, though.
Edited by Me KS on Aug 16, 2009 at 07:03 PM

The difference is that you have easy to click buttons, and you browse to the .scenario file, while using the command prompt requires you to type out the scenario location. I don't know about you, but it seems more like laziness, and not speed.

Using the command prompt also is helpful, and during certain situations, it tells you to abort BEFORE you finish compiling.

Ugghh, sometimes I wonder why a lot of guys don't just give up!

I said : ''Please do not suggest that I use tool, I know how to use tool, but it's much quicker to use the tool++ GUI.''

I am well aware that tool++ is simply a 'graphic user interface' which just sends the commands that you 'type' in to tool. Therefore, you take 'time' to type in and is prone to 'mistakes'.

Using a GUI is quicker. There are no 2 ways about it - but if you prefer your command line interface method, you just keep right on a banging that ole keyboard, just please don't reply to this post!

I wonder if you have actually used tool++? When you have selected a tool command using tool++, anthing that tool does normally is also done - including all those 'helpful' little messages! and Tool++ has a little 'Abort' button too, which is helpful.

If you don't have a solution to the posters problem - To get Tool++ working on a vista based pc - please don't post!

Oh, and I have some vinyl records too - I just prefer to use CDs now. It was an analogy not a stereotype.
Edited by Black Crypt on Aug 17, 2009 at 04:50 AM
Edited by Black Crypt on Aug 17, 2009 at 04:51 AM

Tool++ doesn't show the output until it's done. And when your doing lightmaps, that could be a problem

I have used tool++ in the past. It's useful for beginners, but later on, for many other tasks, it fails. Try compiling bitmaps or sounds using it. It never does it exactly the way you want it.

The reason why you need tool++ is to compile maps and do other tool stuff. The solution to fix this is to use the original tool. That way, you can compile maps and do the other tool stuff. If you don't like it, then that's not our problem. The command line interface is also used in many other things. If you don't like it for compiling tool, then you should stay away from other tech things such as changing your IP, configuring DWM, etc.
Edited by Gamma927 on Aug 17, 2009 at 02:15 PM

Tool++ never did lightmaps. I always used tool to do the lightmaps.

The reason I want to get tool++ working is because I prefer to use a GUI.

I never had any problems compiling bitmaps or sounds using tool++.

I made this map using tool++ : http://hce.halomaps.org/index.cfm?fid=4665. Never had any problems on my xp system. So i'm guessing it's an OS related issue.

I don't consider myself a beginner. Intermediate maybe, but that's irrelevant.

I want to get tool++ working on my vista pc. If you have a solution or any advice on how to achieve this please post a reply.

If you want an easy to use GUI, why don't you use the one built into HEK+?

Because I prefer tool++.

If you have no suggestions to help us achieve our goal, why do you keep posting here?

I can't argue against personal bias. If you need to compile a map, you could use the original tool. If you want to use a GUI, you could use HEK+. But as you are biased towards tool++, for unknown reasons, I can't help. Your goal is to compile maps using an easy to use GUI, but you won't use HEK+ for reasons unstated. I'm posting, because I'm listing alternative options as to what you could be using, but as you won't use them, then that's not my problem.

lol did u set the CE directory in tool++? go to options>properties>and set the directory. this happend to me and this worked

Thanks, that was the first thing I checked when it didn't work first time, but you are spot on!

On Vista there are 2 program files directories..

Program Files
Program Files (x86)

I have set the Tool++ CE directory to...

C:\Program Files (x86)\Microsoft Games\Halo Custom Edition

Now tool++ seems to work just fine.

Thank you darkassassin14 :)

Note: change C: to your hard drive's letter and there is a space between 'Files' and '(x86)'.

o i dont hav vista its just that that happend to me. i try compiling somthing and nothing happend so i start lookin around the menu bar and thought it mite be som settings and wat do u now directory wasnt set lol