Please wait, your content is loading

1UP Network: 1UP | EGM | GFW | FileFront | GameVideos | MyCheats | GameTab     Site Statistics: Over 1.5 million files totaling 48+ TB of space



Steel Beasts Pro PE v2.328 Patch


Steel Beasts Pro PE v2.328 Patch

Steel Beasts Pro PE v2.328 Patch
Filename SBProPE2_328Update.zip
File Size 9.94 MB (10,424,716 Bytes)
Date Added Tuesday, January 23, 2007 07:47 AM
Downloads 63 (This week: 1)

Embed



Share this File on Facebook
Send this File to a Friend







Short Description
This is a incremental patch - you need to have 2.304 installed before you install this.

2.328 Update:

This is a incremental patch - you need to have 2.304 installed before you install this.

This release started out as a emergency release to fix some problems with collisions, but many other things ended up being resolved as well. Special thanks goes out to all the testers and volunteers who took the time to test and give feedback on the 24 revisions since the last official one.

In order to run this version, you will need to install DirectX 9c, December 2006 Edition. If you have a older DirectX 9c install, it will not work.


Changes since 2.304:
-Fixed bug (dismounted engineers' squad icon)

-Fixed bug (Helicopters now only switch off engines after a proper landing)

-Fixed bug (Fire on burning church is detached from the building)

-Fixed bug (Improved thermal signatures for Bunkers)

-Fixed bug (Hotkey X makes HIND move forward)

-Fixed bug (Breaking up platoons and merging the sections later now results in proper unit designations)

-Fixed bug (improved aiming for more vulnerable spots or targets)

-Fixed bug (using the tree scatter tool on forest areas now results in tree replacement)

-Fixed bug (Improved movement of troops within built-up areas)

-Fixed bug (vehicles now continue reloading in multiplayer sessions if left alone by the player)

-Fixed bug (M1 TCs hatch now locks in proper position)

-Fixed bug (Sound of interrupted cal .50 reload process not properly synchronized)

-Fixed bug (M1 TIS reticule pixel error)

-Fixed bug (adjusted Mercedes GD240 vulnerability, espe-cially to small arms fire)

-Fixed bug (Improved thermal signatures for many vehicles)

-Fixed bug (adjusted rules for RPGs fired from within buildings)

-Fixed bug (levitating vehicles in network sessions)

-Fixed bug (SB PRO PE crashed to desktop when using the "Position" drop down menu while controlling infantry)

-Fixed bug (reduced cal .50 muzzle flash)

-Fixed bug (Tweaked collision model; a human operator must be in control of at least one of the colliding vehicles; collisions of computer-controlled vehicles with static environmental objects are less likely to result in severe damages)

-Fixed bug (transient noise artifacts in multiplayer sessions)

-Fixed bug (Manual steering from F8 position of multi-crewed vehicles now enabled)

-Fixed bug (RPGs are exploding on the inside of walls of the buildings from which they are fired.)

-Fixed bugs (Driving behavior improved especially for road marches)

-Fixed bug (Network sessions: The ammo levels in PCs can get out of sync between clients and hosts)

-Fixed bug (Network sessions: Client computers lose control over their organic dismounts.)

-Fixed bug (M2/M3 Bradleys were too tough to kill)

-Fixed bug (The CV90 tutorial dealing with UGV caused a crash to desktop)

-Fixed bug (Deploying a UGV inside of a house made the building collapse)

-Fixed bug (Network sessions: AAR event messages were timing out, making the AAR look very incomplete for clients)

-Fixed bug (engines would turn themselves on frequently, even after stopping and having no contact with enemy and no orders)

-Fixed bug (Network sessions: Client owned vehicles did not get repaired. The timer will eventually expire for them, but whatever is broken will stay that way.)

-Fixed bug (Engineers would not mark breached lanes)

-Fixed bug (Consistent tree collapse in network sessions, irrespective of host or client ownership)

-Fixed bug (small rock clusters now require top speed collisions to cause serious damage)

-Fixed bug (Computer-controlled BRDMs would not open fire on ASLAVs unless human observer was present)



Screenshots



Comments
Post Reply
pages: previous1 2 3 4 5 6 7 8next
  • #2865212
    by: Very nice site! Good work. (Visitor) Very nice site! Good work. [reply|quote] Wednesday, February 28, 2007 06:49 AM
  • #2865524
    by: Very nice site! Good work. (Visitor) Very nice site! Good work. [reply|quote] Wednesday, February 28, 2007 07:10 AM
  • #3263320
    by: Nice site you have! (Visitor) Nice site you have! [reply|quote] Sunday, March 11, 2007 11:28 PM
  • #3263472
    by: Nice site you have! (Visitor) Nice site you have! [reply|quote] Sunday, March 11, 2007 11:33 PM
  • #3349885
    by: Du musst ein Fachmann sein - wirklich guter Aufstellungsort, den du hast! (Visitor) Du musst ein Fachmann sein - wirklich guter Aufstellungsort, den du hast! [reply|quote] Wednesday, March 14, 2007 01:44 PM
Post Reply
pages: previous1 2 3 4 5 6 7 8next
Submit Comment
Re-enter this code:   turing test  
You are currently not logged in. Please either log in to the right or fill out the form below to post an anonymous comment.

Your Name:
           
Editor
Click to Preview

 
login
General Behavior
Treat other members with the respect they deserve. Please do not flame or insult other users.

Posting Behavior
  • Please do not spam. When you make a post, please ensure it is in the relevant section and is clearly titled.
  • Please refrain from making multiple posts in a row.
  • Use the edit button function as this helps keeping the forums look tidy.
  • Do not post threads in all capitals since this is considered akin to shouting and is not necessary.
  • Please do not use profanity.


  • Advertising and Pornography
    Advertising of other sites/services or posting links to pornography or illegal content is strictly forbidden.

    Warez & Piracy
    Requests for illegal content will be treated as piracy. This includes requests or provision of CD keys, cracks, serials, and pirated software, movies, or music that is protected under copyright law.


    Note: If you are intending to respond to a comment, please ensure that you click 'reply' next to that comment.