Bugs that REALLY need Fixing.

[Pooky]

lol, you could always trick people in Halo PC by putting brackets around your name D:

[redsteven]

* like this* im sure is written while dead,

team channel when your typing has /team in front

WELL then. but how do we know what channel things are written in then? We don't, do we...

[rec0]

If you try to map the 't' key for ingame text chat, every time you type 't' it closes the text chat box. This is very annoying...

Additionally if you hit your team chat key while typing a regular message it will close the text box, and re-open a blank one for team chat. If you hit your team voice chat button it'll close any open text boxes too. Can't wait for these to be fixed so I can type messages with 'y', 't' and 'n' in them. Another really annoying keyboard-related bug is that after mapping crouch to left ctrl, pressing crouch while you already have any other key down on the keyboard does not register. I can only crouch if I release all keys I have down, then press it. Once it's pressed down I think I can hit any other key and it continues to work until I let off it again (so I can crouch-walk once I have ctrl down, but can't press crouch mid-walk).

I'm also a little puzzled as to why I get RAM warnings: I have 2gb, play with no other programs open, use all lowest settings and yet Vista frequently pops up "Your computer is low on memory". Also pretty annoyed that I get horrible framerate. It seems entirely CPU-bound; I can change the screen resolution to anything and I'm getting very little change in FPS. I have a single core AMD 3800+; is anyone getting decent framerate with a single core CPU? I'll upgrade shortly, it's just annoying that on lowest settings it looks worse than Halo CE and is running at a third of the framerate.

[et_cg]

That's weird, I've never experienced any of those problems. No low ram, no untype-able letters. It's all fine for me.

But one thing I have trouble with, since I always run Halo 2 in windowed mode, is the fact that I can't use my mouse on other programs sometimes, such as xfire, or 3ds max. It won't let me click out of Halo 2. I can Alt+Tab, but even if I do click, it selects Halo in the start bar, but doesnt bring it up to the front.

[Digikid]

just out of curiosity....WHY are you playing it in Windowed Mode?

[Linch]

^me too

[jahrain]

Additionally if you hit your team chat key while typing a regular message it will close the text box, and re-open a blank one for team chat. If you hit your team voice chat button it'll close any open text boxes too. Can't wait for these to be fixed so I can type messages with 'y', 't' and 'n' in them. Another really annoying keyboard-related bug is that after mapping crouch to left ctrl, pressing crouch while you already have any other key down on the keyboard does not register. I can only crouch if I release all keys I have down, then press it. Once it's pressed down I think I can hit any other key and it continues to work until I let off it again (so I can crouch-walk once I have ctrl down, but can't press crouch mid-walk).

I'm also a little puzzled as to why I get RAM warnings: I have 2gb, play with no other programs open, use all lowest settings and yet Vista frequently pops up "Your computer is low on memory". Also pretty annoyed that I get horrible framerate. It seems entirely CPU-bound; I can change the screen resolution to anything and I'm getting very little change in FPS. I have a single core AMD 3800+; is anyone getting decent framerate with a single core CPU? I'll upgrade shortly, it's just annoying that on lowest settings it looks worse than Halo CE and is running at a third of the framerate.

They have neglected giving the game proper keyboard/mouse support. Notice the mouse has no acceleration which is why it feels 'stiff' even at max sensitivity. Also the sensitivity doesn't increase for vehicles and turrets making the warthog and other vehicles nearly undrivable with the keyboard/mouse.

Also vista and/or halo 2 vista probably has memory leaks I guess. I use 1 gig of ram and for some reason, halo 2 just fills it right up after just a few minutes of gameplay since vista is constantly using nearly half it at all times. If this port was done more professionally with more effort put into making it run more efficiently, its quite possible that this game could only need the same minimum requirements as Halo PC, as they were both originally developed for the same 2001 era hardware. Btw, a dual core processor won't help your game performance at all. Halo 2 takes no advantage of multicore CPUs. I notice only up to 50 to 52% of my CPU being used when playing.

[rec0]

Btw, a dual core processor won't help your game performance at all. Halo 2 takes no advantage of multicore CPUs. I notice only up to 50 to 52% of my CPU being used when playing.

Yeah I understand that; there's no way they'd make the game fully multithreaded in a port. Most new processors are multicore so I was differentiating older and newer CPUs based on their core count. While not exhaustively accurate, it's a solid association for the majority of cases. ;p

So I'm still wondering if anyone else with a similar CPU (around the 3800+ range) is having FPS issues; most people I talk to don't seem to, but everyone I have talked to has a newer processor.

[jahrain]

On my older PC, I have a Athlon XP 3600 1.4 ghz, and I get 3 to 5 FPS ingame.

[Patrickssj6]

I have an Athlon X2 3800+ and 2GB and GeForce 7600 but....I don't have Vista...hehe