Graphics bug 4.0-771 / Metroid Prime?

lodgedger · (This post was last modified: 02-02-2014, 05:30 PM by MayImilae.)

version < 4.0-771 in the development version do not suffer this issue.

**DJBarry004** · 02-02-2014, 07:16 AM #2

Post graphic configs, please. Put them as screenshots.

lodgedger · (This post was last modified: 02-02-2014, 08:59 AM by lodgedger.)

Actually this issue started happening in 4.0-765.

'Merge pull request #11 from degasus/VertexLoaderCleanup"

sure please view below.

**DJBarry004** · (This post was last modified: 02-02-2014, 09:00 AM by DJBarry004.)

Why you disabled EFB copies? And try with Progressive Scan enabled.

lodgedger · 02-02-2014, 09:08 AM #5

v4.0-765 - the below has been enabled and still experiencing the same issue.

I do not recall.

(02-02-2014, 08:59 AM)DJBarry004 Wrote: Why you disabled EFB copies? And try with Progressive Scan enabled.

**Link_to_the_past** · 02-02-2014, 05:02 PM #6

I think that you open your graphics config after you run the game and have efb copies disabled by default, that's why you get that box. You revert the default value of efb to ram for this game.

***MayImilae*** · 02-02-2014, 05:30 PM #7

Just so you know, that's METROID PRIME, not Super Metroid.

*uses magic moderator wand on the thread title*

**degasus** · 02-02-2014, 06:58 PM #8

Just don't disable PanicAlerts, so you would have seen the issue Wink

I've broken D3D, but it's fixed now.

lodgedger · 02-03-2014, 10:48 AM #9

To all I have reset everything to defaults and done everything that is suggested.

Prior to version 4.0-765 Merge pull request #11 from degasus/VertexLoaderCleanup , everything works.

(02-02-2014, 06:58 PM)degasus Wrote: Just don't disable PanicAlerts, so you would have seen the issue
I've broken D3D, but it's fixed now.

**degasus** · 02-03-2014, 10:51 AM **#10**

Oh, so it still happens on current development versions? If so, does it also happen on OGL backend? Can this bug be triggered by a fifo log?