Halo 1 & 2 for PC
This topic has moved here: Subject: Test patch 1.09 for compat fixes
  • Subject: Test patch 1.09 for compat fixes
Subject: Test patch 1.09 for compat fixes
  • gamertag: [none]
  • user homepage:

r : w )

Hi all,

Last night I decided to sit down and fix the problem where 64-bit machines with >4GB of RAM complained that you have 0 RAM. That was easy. Then when I tried to test the fix, I discovered the compat problem with the recent IE security fixes, and saw the threads here suggesting that people uninstall them.

That's no good, right?

So I put together a fix for that, too. I'd like you guys to try it out on your various systems and make sure that (a) it fixes those problems, if you had them , and (b) doesn't cause any new ones.

NOTE!!!!!!
This will *not* have any impact on gameplay. All the changes are finished happening before the MGS logo movie even plays! Every time there's a patch, there are always a few people whose internet connections happen to get flaky that day, and they assume there's a correlation. This patch won't change the game. It's your imagination. Really.

This patch is only for HaloPC, not for CE yet. If a little time passes and no one can convince me that the patch is buggy, I'll port the changes over to CE and release both.

This version will network with 1.08 in the same game, it doesn't break compat.

Try it out, reinstall your missing IE patches, and post your results here. If anyone is still running Win98SE (gasp!) let me know if it works as well as previous versions.

Thanks!

1.09 Beta patch

  • 08.19.2009 6:03 PM PDT

Alright... I copied the contents in the .zip archive into my Halo PC folder and I exceptioned on start up.

Problem signature:
Problem Event Name: APPCRASH
Application Name: halo.exe
Application Version: 1.0.8.616
Application Timestamp: 4a8c98eb
Fault Module Name: halo.exe
Fault Module Version: 1.0.8.616
Fault Module Timestamp: 4a8c98eb
Exception Code: c0000005
Exception Offset: 0022a217
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Using the command parameters -console -screenshot -window
Gamespy not installed.


Here is my Computer Config:
------------------
System Information
------------------
Time of this report: 8/20/2009, 02:37:11
Machine name: LAPTOP
Operating System: Windows Vista Home Premium [64 bit] (6.0, Build 6001) Service Pack 1 (6001.vistasp1_ldr.090302-1506)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Studio XPS 1640
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A08 .
Processor: Intel(R) Core(TM)2 Duo CPU T9550 @ 2.66GHz (2 CPUs), ~2.7GHz
Memory: 4090MB RAM
Page File: 2098MB used, 6280MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 10
DX Setup Parameters: Not found
DxDiag Version: 6.00.6001.18000 64bit Unicode

---------------
Display Devices
---------------
Card name: ATI Mobility Radeon HD 4670
Manufacturer: ATI Technologies Inc.
Chip type: ATI display adapter (0x9488)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_9488&SUBSYS_02721028&REV_00
Display Memory: 2807 MB
Dedicated Memory: 1018 MB
Shared Memory: 1789 MB
Current Mode: 1366 x 768 (32 bit) (60Hz)
Monitor: Generic PnP Monitor
Driver Name: atiumdag,atidxx32,atidxx64.dll,atiumdva,atiumd64.dll,atiumd6a .cap,atitmm64.dll
Driver Version: 8.14.0010.0655 (English)
DDI Version: 10.1
Driver Attributes: Final Retail
Driver Date/Size: 5/10/2009 13:27:36, 3837440 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-D7C8-11CF-1771-7822A1C2C535}
Vendor ID: 0x1002
Device ID: 0x9488
SubSys ID: 0x02721028
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_A ModeMPEG2_C
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled


-Supersniper-


[Edited on 08.19.2009 11:57 PM PDT]

  • 08.19.2009 11:32 PM PDT
  • gamertag: [none]
  • user homepage:

omg Sawnose you rock!

  • 08.19.2009 11:54 PM PDT
  • gamertag: [none]
  • user homepage:

Posted by: SuperSonic007
omg Sawnose you rock!
QFT

  • 08.19.2009 11:55 PM PDT

Please test this out so he can get info.
Thanks in advance.

  • 08.19.2009 11:57 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Just tried this out, the game loaded up and I joined a server. Killed a few people and I'm guessing about 20 seconds in got this exception.

http://img200.imageshack.us/img200/7177/wellytw.jpg

I'm tired now but I'll fool around with it more tomorrow. Also, system:

Processor: AMD Phenom(tm) II X2 550 Processor (2 CPUs), ~3.1GHz
Memory: 4GB DDR3 RAM
Graphics: ATi Radeon HD4850 512MB
Operating System: Windows 7 Ultimate 64-bit (Build 7100)
Motherboard: Gigabyte GA-MA770T-UD3P AM3 AMD


  • 08.20.2009 12:04 AM PDT
  • gamertag: [none]
  • user homepage:

r : w )

Thanks for the bug reports. The first one is a problem I'll have to track down; the crash while playing seems very odd to be caused by this patch.

Unfortunately, I can no longer access the "Send data to Microsoft" data, so I'm troubleshooting blind here.

  • 08.20.2009 12:07 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Decided to try it again, hopped in a bloodgulch server and played for at least over a minute this time. Any other information about my computer you'd need to see what the problem is?

I also know there is a ton of junk running in my first picture there, but that is the norm for me and I never experience problems with it.

  • 08.20.2009 12:23 AM PDT
  •  | 
  • Elder Legendary Member

Yes, I am a hypocrite, and I'm sorry. I really do mean well, but I'm not running on all cylinders.

Everytime someone buys a copy of Halo 2 Vista, a puppy dies.

Locked up hard after 20-30 seconds on a CTF server, using XP Home SP3.
After killing the halo.exe process, trying to restart it results in an exception.

Thanks for all your work, sawnose!

[Edited on 08.20.2009 12:55 AM PDT]

  • 08.20.2009 12:53 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Could I suggest that instead of a "1.09 patch" this just be a compatibility fix deal? Such as the Windows Vista Compatibility Fix for Halo Custom Edition 1.07 that was released awhile back? When version numbers change they seem to break a lot of our third party applications!

I haven't installed PC for years, but as soon as these fixes and updates start coming to CE I'll be all over it!

Thanks for the tip on activating Anisotropic Filtering on all the new graphics cards by the way!

[Edited on 08.20.2009 1:05 AM PDT]

  • 08.20.2009 1:03 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Exception after more or less 30sec of play, using -console and -vidmode 1680,1050,60.

CPU : Core i7 920 @ 2.93ghz
Ram : 3 x 2 gig. DDR 3 G.Skill
GPU : ATi 4870 512Meg.
Mobo : Gigabyte EP45-UDP3
OS : Vista Home Prenium 64 Bit

Greetings from France, keep the good work coming sawnose.

EDIT : it seems that halo no longer shows the spec. of my pc =( http://img190.imageshack.us/img190/9695/sanstitre1u.gif

[Edited on 08.20.2009 5:11 AM PDT]

  • 08.20.2009 1:46 AM PDT

I also exception after about 30 seconds.

Operating System: Windows Vista Home Premium (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.090302-1506)
Language: English (Regional Setting: English)
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Core(TM)2 Duo CPU E4700 @ 2.60GHz (2 CPUs), ~2.6GHz
Memory: 2046MB RAM
Page File: 1586MB used, 2747MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 10
DxDiag Version: 6.00.6001.18000 32bit Unicode


Thanks for making updates!

[Edited on 08.20.2009 3:16 AM PDT]

  • 08.20.2009 3:15 AM PDT
  •  | 
  • Exalted Legendary Member
  • gamertag: Btcc22
  • user homepage:

It crashed on XP2 after about a minute of gameplay with an access violation. Tried to note down the details for you but the window went blank and froze up too quickly.

Started it up again and it crashed on the menu. Here's the full error report:
http://touringnet.co.uk/misc/hpc109/xp - It decided not to provide a dump file.

I was going to attach a debugger during gameplay to get an idea of what was crashing it, but Halo refuses to start up at all anymore unless I use 1.08. It'll probably work again after a reboot, but I can't restart the machine yet.

Tried it on Vista Ultimate 64 bit SP1, but it crashes as soon as I try and start it. Here are the files for that crash. Hopefully of more use than the one from my XP machine:
http://touringnet.co.uk/misc/hpc109/vista

Hope that helps.



[Edited on 08.20.2009 6:34 AM PDT]

  • 08.20.2009 6:19 AM PDT

The game just freezes after a few seconds and I have to kill it with task manager.

CPU: AMD Phenom(tm) II X4 955 Processor (4 CPUs), ~3.2GHz
GPU ATI Radeon x1900 256 MB
Mobo: MSI 770-C45
OS: Windows XP Professional x64 SP2

  • 08.20.2009 6:50 AM PDT
  •  | 
  • Elder Heroic Member

Join the Modacity Forums - a community focusing on the modding abilities of Halo PC, Halo CE, and Halo 2 PC.

While comparing the 1.08 executable with the 1.09 beta, I was surprised to find that this was not just a simple patch, but rather a whole new build of the game. My assumption is that you are going to release the final build through the automatic updater for any users who have any version less than 1.09 in the registry, while keeping the internal version number as 1.08 to avoid breaking compatibility with older servers and clients.

However, because this is a new build of the game entirely, and it will probably be the final build ever (for real this time), there's a request that the entire community has had since the initial release of Halo PC. When Gearbox was developing the PC version, they were forced to leave out their netcode by Microsoft. At that time, dial-up was still commonly used because broadband was not as widespread and adopted as it is today. Practically everyone who plays Halo PC/CE today has a broadband connection, but we all still suffer because of the dial-up support. Gearbox was rumored to have completed their netcode, then to have dropped it at the last second before release. It would be absolutely nothing short of a blessing to the community if their netcode could be tested by the community and eventually released as a 1.09 or 1.1 update to the game.

The netcode patch would bring Halo up to date with the other games today. Additionally, the only changes would be between the client and the server. The Gamespy integration should not need any change at all - just the executables and dlls. A 1.1 update would also greatly help unify all the older versions because it would have the update we have always requested.

I'm sure no one expected Halo PC be as resilient as it has proved to be. Over six years since release, the game is still alive and kicking. Across the versions, Halo on the PC (including CE) has thousands of players online at a time. The number of projects in development for Halo CE and the complexity of them is astounding. It is truly awesome to see how the game has been turned inside-out and on its head, doing things with it no one even imagined would be possible. Even if we don't get an SDK or any extremely fancy tools that only the developers would really use, it would be fantastic to receive a netcode update that EVERYONE can enjoy.

  • 08.20.2009 9:14 AM PDT

I agree, I've always want to see a better NetCode for Halo PC/CE.
And to see how it has grown over the years even after it was dropped in support, only goes to show that this community is :awesome:

I agree 100 percent with Jcap.

  • 08.20.2009 9:58 AM PDT

Posted by: Nessy

The bungie.net community is the halo PC community that is renowned for being unbelieveably sucky.

Well it didn't take long before the netcode complainers showed up.

Time to get over it guys.

  • 08.20.2009 10:48 AM PDT

Your not worth the response.
just gtfo thank you.

[Edited on 08.20.2009 11:03 AM PDT]

  • 08.20.2009 11:02 AM PDT

Daodan Latency at 65%

I would disagree. It is very very hard to get good netcode. That is such a huge project to revamp all the existing netcode that right now it is not feasible.

  • 08.20.2009 11:23 AM PDT

Posted by: Dirk_Gently
I would disagree. It is very very hard to get good netcode. That is such a huge project to revamp all the existing netcode that right now it is not feasible.

The netcode already exists, from the Halo PC Beta. Gearbox was forced to remove their netcode in order to support 56K. Below is a link to a copy of a post by Randy Pithford, an employee at Gearbox. The original post was was either deleted from the Gearbox Forums, or lost when they moved their database to vBulletin.

http://forum.teamxbox.com/showthread.php?t=303941


[Edited on 08.20.2009 12:01 PM PDT]

  • 08.20.2009 12:00 PM PDT

Daodan Latency at 65%

Right now it does not make sense to ugrade the netcode to Halo PC. With only Roger working on it, this could take a while to test out fully and I don't think right now that bungie has the time or resources to allocate to retesting a multiplayer system that they know works right now. I have 2 or 3 friends that play halo, but due to where their live, or financial situation they cannot afford/get anything higher than a 56k connection. Granted that they may be few in the total Halo PC population, it is something to think about that currently upgrading and retesting netcode is not an option for a 1 man team.

@anyone that can answer:

If I install this patch on a system that is not affected by these problems will I be experiencing exception errors, or will it function normally? I run Halo PC through Crossover Games and sometimes I get errors saying that I have no VRAM ( in truth it is because the Geforce 9600M GT on this laptop shares the system RAM with the video cards, but I have 4GB of DDR3 so it is no big deal) but I really do. Would this be covered in this patch?

  • 08.20.2009 12:16 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Indeed, if the netcode were to be fixed it would be a blessing for all the remaining halo players and could even bring back some of the people who left the game because of its buggy nature. Please look into this.

  • 08.20.2009 12:48 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Double post by accident.

[Edited on 08.20.2009 12:50 PM PDT]

  • 08.20.2009 12:50 PM PDT

FTW

I concur with h2oblade's opinion. Halo PC would regain popularity and perhaps increase the number of people buying the game.
I'm a strong proponent for reviving Halo 1 as competitive PC game.

  • 08.20.2009 2:10 PM PDT

Posted by: Nessy

The bungie.net community is the halo PC community that is renowned for being unbelieveably sucky.

Posted by: AsK Magic
Your not worth the response.
just gtfo thank you.


Ok 2 day old member. "Fixing" the netcode arguments began in September of 2003 when the game launched. We've all been down that thread complaint road before many times around here. And allow me to throw some basic logic towards you, if M$ "fixed" the netcode and made the game unplayable to people who legitimately paid for the game during the 2003-2009 period, there would be hell to pay. However retarded the netcode is, you can't just change it nearly 6 years later. From the moment the game shipped with official 56k support, it was never going to change.
There are lots of other things that could be worked on without breaking the game for people, so let them focus on those things.

  • 08.20.2009 2:27 PM PDT