Halo Patch for Mavericks + New Lobby

[[CV]314sec]

I'd like to thank you for fixing that 10.9 problem. I play a lot of Halo multiplayer and was going to have to start dual-booting windows to continue.

[Guest]

Let me confirm through testing that it is an active DisplayLink driven monitor that crashes Halo. Unplug the DisplayLink USB port and Halo will run fine. I cannot verify that three monitors will also crash Halo if those monitors are on real physical video ports.

[franio]

Had a nondescript crash before your patch (running 2.0.4):


After applying your patch with the contents of `/Applications/Halo.app/Contents/MacOS` now being:

Code: Select all

Halo
HaloUB
mavericks_patch.dylib

I receive the same error. There is unfortunately no crash report information. What can I do to help isolate this problem?

[nil]

Can you try this version of our patch and report back whether or not the error still occurs? I am trying the modification Guest suggested earlier (for technical details: nopping branch instructions at virtual memory offsets 0x2B46CB and 0x2B482E)

Also, are you by chance on a multi-monitor set up?

[franio]

Can you try this version of our patch and report back whether or not the error still occurs? I am trying the modification Guest suggested earlier (for technical details: nopping branch instructions at virtual memory offsets 0x2B46CB and 0x2B482E)

Also, are you by chance on a multi-monitor set up?

Unbelievable, yes this worked! And yes, on a multimonitor setup. THANK YOU!!!!!!!!

[AndrewMiner]

Thanks for the patch! Unfortunately, it doesn't seem to be working in my case. Here's a paste bin of my crash log (though it does't have any symbols): http://pastebin.com/3cYtGrPY. Happy to provide any further information that would help.

Thanks!

[nil]

Thanks for the patch! Unfortunately, it doesn't seem to be working in my case. Here's a paste bin of my crash log (though it does't have any symbols): http://pastebin.com/3cYtGrPY. Happy to provide any further information that would help.

Thanks!

Please update to 2.0.4 before applying the patch. You're on version 2.0.3. So I'd revert the patch, update to 2.0.4, then try to reapply the patch.

[nil]

I updated the original post with a download that uses the new lobby from Halo PC 1.10.

[[CV]314sec]

Do I wait until May 31 (or June 1) to do this? I ask because I play multiplayer every day and am not sure the new patch will include the gamespy lobby.

Also, thanks for doing this - there are a few of us in the clan that have Macs and this is a life saver.

[nil]

Do I wait until May 31 (or June 1) to do this? I ask because I play multiplayer every day and am not sure the new patch will include the gamespy lobby.

Also, thanks for doing this - there are a few of us in the clan that have Macs and this is a life saver.

I think the appropriate time is to wait until the official 1.10 patch comes out on the PC for all the masses. The new patch does not include the servers on the perishing gamespy lobby.

[nil]

Ok. It looks like although I put up a patch to use the new master server, it is filtering for the wrong version (1.09 instead of 1.10), due to some (unnecessary IMO) string change (01.00.09.0620 to 01.00.10.0621). Until I happen to find a way to change this, you'll basically have to resort to using direct IP, unless SAPP servers choose to still broadcast to 1.09.

[nil]

Problem has been resolved. If you had downloaded the patch with the new lobby before I made this post, please re-download and apply the patch again. This patch now shows 1.10 servers. In addition, I allowed it to be able to show 1.09 servers as well since it was trivial to do so.

Also Bungie has officially released 1.10 so now may be a good time (or in a day or two) to apply the update.

[sodium.777]

Thanks a million! i can finally join games without need to type in the ip D:D:D:

Today was a good day. Got halo after a week of bullshit and got an awesome GAMSAT result

[Guest]

18th of May today... im getting error contacting gamespy server. I'm using the new serverlist though.

[Guest]

18th of May today... im getting error contacting gamespy server. I'm using the new serverlist though.

I tried the old serverlist thats going to shutdown and it works fine ATM