Battlefield 2 - 1.5 Patch & PR V0.85 - Read Me

[SocketMan]

I sacrificed one PC for the patch and it worked with PRSP (single only - no coop servers visible,same with PRMP) played 2 maps,no problems.
Won't connect to the current PR servers (from the favourites):"You have a newer version" message and the official test server is passworded - obviously.
Could also watch Battle Recorder file from PRMP 856
I am not sure 100% but there seems to be a performance boost -the FPS went up to 700 in the menu,have not seen it that high,usually about 100-200 (lower in game)

The readme.txt

=================
XI. VERSION NOTES
=================

============
Update v1.50
============

FEATURES
- Additional support for Windows Vista.
- Added Highway Tampa as a required map.
- Added a new map called Operation Blue Pearl.

GAMEPLAY TWEAKS
- Changes made to both the J10 and F35B to make them more balanced. Please note that the J10 is a superior dogfighter to the F35B and as such these two aircraft will never be equally matched.
- AA targeting tweaked to make it more effective.
- Added checks to prevent "runway grieving".
- Various changes made to prevent cheating.
- Tweaked the hit detection, hits will be more accurate to the model.
- Added support for the Novint Falcon controller.

SPECIAL THANKS
- Special thanks to Blackbird at the TV2 community www.battle.no


https://www.realitymod.com/forum/f11-off-topic-discussion/9948-dice-announces-bf2-1-5-patch-changelog.html

[Snares]

Don't forget that if you set it to a widescreen resolution you need to manually open all the various *.con files and set it back to a standard resolution, when you go back to 1.41, or BF2 and PR will crash. I had to also start PR through vanilla BF2, exit, remove the custom +szx and +szy from the target, start it again, close it, then finally put back the custom resolution. It kept crashing until I did all that

I don't think it's even worth using the ingame widescreen resolutions, it seems to be the same (or possibly worse) than using a target modification.

[LithiumFox]

Don't forget that if you set it to a widescreen resolution you need to manually open all the various *.con files and set it back to a standard resolution, when you go back to 1.41, or BF2 and PR will crash. I had to also start PR through vanilla BF2, exit, remove the custom +szx and +szy from the target, start it again, close it, then finally put back the custom resolution. It kept crashing until I did all that

I don't think it's even worth using the ingame widescreen resolutions, it seems to be the same (or possibly worse) than using a target modification.

well if it's ingame that means it should automatically switch out the widescreen, meaning you shouldn't have to edit the .con's

[Tim270]

Yea, Im pretty sure its the same as using the szy xxxx etc, not true widescreen.

[LithiumFox]

Yea, Im pretty sure its the same as using the szy xxxx etc, not true widescreen.

what they should do is, you know, ADD widescreen support...

wait a minute...

o.o could WE add widescreen support?

I mean i know they have the "Widescreen Fixer"

._o but that only fixes FOV, not the ICONS... i don't believe at least....

i hope they fix that issue... before the final...

[Snares]

well if it's ingame that means it should automatically switch out the widescreen, meaning you shouldn't have to edit the .con's

Well it didn't work Don't you see? You set the widescreen ingame in 1.5, then go back to BF2 1.41.

BF2 1.41 reads Video.con that has 1680x1050@60hz (because you have the ingame option for 1680x1050 in 1.5, and set it to that), and says "huh?!" and then crashes.

Try setting Video.con to 1680x1050 in a profile, then try logging into the profile; it will crash every time.

[Mora]

You dont need to change any setting in 1.5 you can just use your own modified bf2 shortcut. The only thing the new resolution settings do in the 1.5 patch is this.

[Zoddom]

now what about the beta and PR? Will the dev wait untill the final release to release a >hotfix< or even 0.9 ?

[Snares]

You dont need to change any setting in 1.5 you can just use your own modified bf2 shortcut. The only thing the new resolution settings do in the 1.5 patch is this.

That's what I figured (You can always hope that they actually fixed the hud though!)

now what about the beta and PR? Will the dev wait untill the final release to release a >hotfix< or even 0.9 ?

I'm sure they will. There's no use to release a hotfix for a patch that doesn't really change much game physics or code (pertaining to PR) and is still in beta. As soon as the official version is released I'm sure they will release a hotfix, but who knows how long it will be before the official -- possibly 2 or 3 months considering DICE's schedule.

[$pyker]

The bf2 producer has hinted several times that this wont be the last patch. Apparently they've concentrated on stopping hacks in this patch. Also there's a few features that they plan to include in the final 1.5 patch release, that wont be in the beta - eg widescreen support, disabling mouse acceleration etc

ahaha lol when i typed bf2 1.50 patch into youtube guess what came towards the toP?? aimbot hacking on blue pearl lol

[hiberNative]

seems like the beta is out.
not trying ;D

[00SoldierofFortune00]

Just read this about the patch.

"Tweaked the hit detection, hits will be more accurate to the model."

Hopefully, if everything turns out right and we are allowed to use it with PR, it may fix some of the hit detection problems we currently have ingame. No one knifing or shooting people twice in the head to get a kill.

[bazza_1964]

If a PR server out there would try running the 1.50 Beta patch, then we could see, at a beta level anyway, how much work would be needed BEFORE EA gets the official patch out...n'est pas? Unless I'm mistaken....

[dtacs]

If a PR server out there would try running the 1.50 Beta patch, then we could see, at a beta level anyway, how much work would be needed BEFORE EA gets the official patch out...n'est pas? Unless I'm mistaken....

it doesn't work with the beta. i tried logging on PR after i had patched and i couldn't, screws up; i had to do a system restore which meant i couldn't play 1.41 cause i keep getting DC'd without an error message, but i can still play PR fine. not worth my time sorting the vBF2 problem, however.

lol...aimbots were actually updated in the first 5 minutes of the patch release.

[wuschel]

I just read on the FH2 pages that the 1.5 patch might include SECUROM software. Now, while I did accept punkbuster on my hard drive with some aching heart, I really do not like to see that piece of trojan software on my notebook.

Can anyone verify that the 1.5 patch will have SECUROM in it? If yes, I might sell my BF2 CDs right away and not come back to this beloved game anymore.. although, I might try to get a glimpse at 0.85 as long as the 1.41 patch is still the one in use..

[ScarySquirrel]

I just read on the FH2 pages that the 1.5 patch might include SECUROM software. Now, while I did accept punkbuster on my hard drive with some aching heart, I really do not like to see that piece of trojan software on my notebook.

Can anyone verify that the 1.5 patch will have SECUROM in it? If yes, I might sell my BF2 CDs right away and not come back to this beloved game anymore.. although, I might try to get a glimpse at 0.85 as long as the 1.41 patch is still the one in use..

The only thing I HAVE heard is that installing this patch means you will not need your CD in the drive to play anymore. Which is a bonus!

[Zoddom]

The only thing I HAVE heard is that installing this patch means you will not need your CD in the drive to play anymore. Which is a bonus!

yeah thats the same they all are saying ... never read something about securom and 1.5

[dtacs]

I just read on the FH2 pages that the 1.5 patch might include SECUROM software. Now, while I did accept punkbuster on my hard drive with some aching heart, I really do not like to see that piece of trojan software on my notebook.

Can anyone verify that the 1.5 patch will have SECUROM in it? If yes, I might sell my BF2 CDs right away and not come back to this beloved game anymore.. although, I might try to get a glimpse at 0.85 as long as the 1.41 patch is still the one in use..

I doubt EA is going to make the effort to do that.

Cracked versions don't even work online, plus the fact that BF2 is a discontinued game, new versions are inCREDIBLY hard to find.

[Megagoth1702]

ahaha lol when i typed bf2 1.50 patch into youtube guess what came towards the toP?? aimbot hacking on blue pearl lol

Oh dear, just watched the vid, poor BF2v players... I just hope that not too many of those hackers come to PR, which is nearly impossible since more then a lot of BF2v newbies come to PR every day.
It is no problem as long as they WANT to learn the game, but if they just keep crashing and kit-stealing... <.<

[hiberNative]

version 2 of the beta is out

mirror if someone's interested:
Fileplay | Download Battlefield 2 v1.5 Beta Patch 2 (BF2_Patch_1.50-Beta2.exe)

ea feedback section
[Beta 2] Patch v1.5 Feed Back - Electronic Arts UK Community

Since Beta 1 this is what we have changed, updated and fixed:

* Consensus to revert to 0.3 second delay between jump and prone - Fixed
* Mouse wheel acceleration on jeeps and APC’s - In Test
* Mouse wheel acceleration on parachutes - In Test
* Falcon controller prevents joystick controls being assigned to work especially on jets and helicopters. Falcon always acts as primary controller for pitch and roll. Resets to Falcon at the start of every round. - Fixed
* The jets on Highway Tampa were replaced with attack choppers in 1.50 - Fixed, Highway Tampa is now as it was in 1.41
* The graphics for Highway Tampa are the same as Mashtuur City on create a local match in the menu and load screen. - Fixed
* Picking up the kit of a player who disconnected causes crashes - In Test
* Audio settings do not always save after clicking APPLY - Fixed
* Registry Version remains at 1.4 after Update 1.5 is installed - Fixed
* BF2OpenAL.dll was version 1.1.1.0 - Fixed - Updated to version 2.1.8.1
* ch_gas_station collision mesh on Dragon Valley was inconsistent with other gas station buildings - Fixed
* MEC artillery piece on Operation Clean Sweep changes to the USMC's control when they capture the Airfield flag - Fixed
* Challenger2 HUD icon was incorrect showing M1A2 HUD icon instead - Fixed
* Road to Jalalabad has PLA FAV spawn in place of a MEC FAV - Fixed
* Dragon Valley Chinese artillery used default respawn time instead of 360 seconds as other artillery uses - Fixed
* Bizon (PP-19) had no delay time after weapon switch - Fixed (this now has a delay of 0.666)
* F35B had a lock delay of 1.5 compared to 1 second lock delay of other aircraft - Fixed
* Incorrect camo Humvee was being spawned in Taraba Quarry - Fixed
* UH-60 (Black Hawk) guns had 0.25 splash damage setting, down from 3 making it difficult to hit infantry. - Fixed (this is now set to 1.5 to improve the UH-60's usefulness while not allowing it to dominate)
* It was impossible to pass a claymore unless an engineer disarmed it first. - Fixed (players can now go prone to pass the claymore)
* Allow BF2.exe to use more than 2Gb RAM on machines that support it - Fixed

how can they fudge up so much other stuff when trying to create a small patch? seriously.
and some of these changes are so basic they should have been patched long ago.

looks like a joke compared to what the pr developers have achieved...