Star Wars Force Unleashed: Bottom half of screen does not render gfx properly

[GoogleCodeExporter]

1) Did the game ever work correctly (i.e. not have this problem) on the
Official PCSX2 build or an earlier version of PCSX2 playground?
(If so, please specify the latest pcsx2-playground or Official revision
that last worked.)
Unsure, I don't believe so.

2) What steps will reproduce the problem?
1. Launch and get in-game

3) What exactly happens when you experience this issue (listing any console
errors or screen output you receive)?
Major gfx corruption in game.

4) What version of PCSX2 are you using? On what operating system? Plugins?
Win 7 x64, r5326

5) Please provide any additional information below.
- Works correctly in Software
- Tried every possible setting (while using GSDX), intepreters, all hacks, etc. 
Nothing affects the broken gfx.
- ZZOGL - Bottom half of screen is just smeared gfx from top
- ZeroGS - Best harware renderer for game. It does have major issues though 
with certain effects (like laser strikes). But the majority of gfx work fine. 
NEEDS Tex Alpha Hack to get rid of black stripes.

6) Attachments.  *IMPORTANT!*  We have a limited storage quota on
GoogleCode, so please keep attachments to UNDER 200k!  Do not upload
blockdumps!  Do not upload MP3 dumps or screenshots in BMP format.  Try to
use 3rd party image hosts for screenshots when possible.
http://imageshack.us/photo/my-images/171/56701406.jpg/ 

Original issue reported on code.google.com by wespipe...@gmail.com on 22 Jul 2012 at 7:29

[GoogleCodeExporter]

Note:
- The HUD still doesn't render correctly in Software - you have no idea how 
much health you have, etc.
- Same results with the old 0.9.6
- These gfx issues have been confirmed on the forums

Original comment by wespipe...@gmail.com on 22 Jul 2012 at 9:32

[GoogleCodeExporter]

Actually, got my hands on a NTSC disc and found out that this version is 
literally perfect, so this is only a PAL issue. Very strange how big of a 
difference a region can make sometimes.

Original comment by wespipe...@gmail.com on 23 Jul 2012 at 4:27

[GoogleCodeExporter]

Yes, we know.  Attempts to find and fix the root cause have been unsuccessful, 
currently I'm thinking that major planned work needs to be done then it can be 
re-evaluated if the bug's still present.

Original comment by sudonim1 on 14 Aug 2012 at 4:45

• Changed state: Backburner

[GoogleCodeExporter]

The issue is still present in the latest build (both official and SVN 
versions). 

Original comment by el.zwier...@gmail.com on 20 May 2013 at 4:58