Dolphin, the GameCube and Wii emulator - Forums

(09-28-2014, 12:17 AM)b.timofte Wrote: [ -> ]I have a black bar down the screen...wyf how I fix it ?

Short answer: you can't (yet).

The long answer is available at the wiki page under the section "Shader Generation Stuttering and the Black Bar".

I am on Bryyo planet for the 1st time and I see above some yellow diamonds and when I scan them it says I cant use them. Do I need to do something to use them now ?
I need to activate the satellite uplink -_-''

b.timofte: Just follow the game. Make sure hints are on, and look on the map to find your objective. If it's offplanet, you'll be notified to go to another planet to find it.

I am at the second turret and the damn fliers pull it back after I start working on the second lock... Its like a cat and mouse and I cant pull al 3 ...WTF !?! Is this a bug? I fought for 5 hours...and threw my wiimote -_-

Just look up a guide online...

I have run into a vicious bug. Having reached Bryyo, I have begun experiencing graphical issues that make it impossible to proceed. The visual feed completely blacks out, as does the HUD, with only the overlay visible if going into Hypermode or switching visors. The environment does render if I morph, but there is still no HUD, and morphing back makes the video vanish again.

I am using Direct3D, with 2x IR, no AA or AF, and EFB to RAM. Opening the graphics configuration and toying with any settings does nothing to resolve the issue once it sets in. Help!

EDIT: The issue appears to D3D exclusive—just played through the same section with OpenGL and experienced no such graphical problems, though I have caught another couple of issues:

The Scan Visor overlay is bright fuchsia in both backends, as opposed to the correct grey.

The game outright crashes under the software renderer, making diagnosing graphcial bugs...difficult, to say the least.

(10-22-2014, 06:02 AM)AutoFire Wrote: [ -> ]I have run into a vicious bug. Having reached Bryyo, I have begun experiencing graphical issues that make it impossible to proceed. The visual feed completely blacks out, as does the HUD, with only the overlay visible if going into Hypermode or switching visors. The environment does render if I morph, but there is still no HUD, and morphing back makes the video vanish again.

I am using Direct3D, with 2x IR, no AA or AF, and EFB to RAM. Opening the graphics configuration and toying with any settings does nothing to resolve the issue once it sets in. Help!

EDIT: The issue appears to D3D exclusive—just played through the same section with OpenGL and experienced no such graphical problems, though I have caught another couple of issues:

The Scan Visor overlay is bright fuchsia in both backends, as opposed to the correct grey.

The game outright crashes under the software renderer, making diagnosing graphcial bugs...difficult, to say the least.

Use the latest development, a change was pushed for d3d which fixes certain depth issues that perhaps fixes your issue.

(10-22-2014, 07:05 AM)Link_to_the_past Wrote: [ -> ]

(10-22-2014, 06:02 AM)AutoFire Wrote: [ -> ]I have run into a vicious bug. Having reached Bryyo, I have begun experiencing graphical issues that make it impossible to proceed. The visual feed completely blacks out, as does the HUD, with only the overlay visible if going into Hypermode or switching visors. The environment does render if I morph, but there is still no HUD, and morphing back makes the video vanish again.

I am using Direct3D, with 2x IR, no AA or AF, and EFB to RAM. Opening the graphics configuration and toying with any settings does nothing to resolve the issue once it sets in. Help!

EDIT: The issue appears to D3D exclusive—just played through the same section with OpenGL and experienced no such graphical problems, though I have caught another couple of issues:

The Scan Visor overlay is bright fuchsia in both backends, as opposed to the correct grey.

The game outright crashes under the software renderer, making diagnosing graphcial bugs...difficult, to say the least.

Use the latest development, a change was pushed for d3d which fixes certain depth issues that perhaps fixes your issue.

That didn't fix the issue at all. Worse, turns out it happens in OpenGL as well, rendering the game completely unplayable.

Screenshots of your settings please.

(10-23-2014, 05:02 PM)MaJoR Wrote: [ -> ]Screenshots of your settings please.

Seeing as that would mean 8 screenshots, here, have the inis instead:

D3D: https://docs.google.com/file/d/0By1uH7c4LapPU3RDWWZuWVJydlk/
OGL: https://docs.google.com/file/d/0By1uH7c4LapPNzdiYlI3aFZlQTA/

I don't THINK I have anything weird in the settings that would cause such an issue, but then, I'm no expert.