Dolphin, the GameCube and Wii emulator - Forums

Hope this is the right place to put it, but I'm having trouble with Beach World Level 2, mainly with the Steam Controller. Before I'd set "Swing Down" to Button B on the controller and had no problems continuously rolling, nor slowly and un-continuously slamming the ground. But I arrived at a platform where I had to continuously swing back and forth, but I have no idea how to setup a configuration that would allow me to do so, either with the controller or on keyboard. If anyone could send me their configuration (a photo) within dolphin, that'd be appreciated, thanks.

(07-04-2016, 09:35 AM)Pepperooney Wrote: [ -> ]Before I'd set "Swing Down" to Button B on the controller and had no problems continuously rolling, nor slowly and un-continuously slamming the ground. But I arrived at a platform where I had to continuously swing back and forth, but I have no idea how to setup a configuration that would allow me to do so, either with the controller or on keyboard.

Try setting the right trigger to "swing up" and then mash both buttons.

(07-05-2016, 03:18 AM)noggersurf Wrote: [ -> ]Try setting the right trigger to "swing up" and then mash both buttons.

Forgot to mention, but it worked! I don't know how but it did, thanks.

I've been having an ongoing issue in getting past the loading screen (i.e., the screen of the clouds loading the world map). It happens when I start a new game or even load an existing file. This seems like an issue older versions of Dolphin used to have, and I'm even using Dolphin 5.0.

Any idea what I might be doing wrong?

Is this glow effect the way it is supposed to be? I guess the way it does look on native means it might be as intended.. Is this is a bug or do some effects just not work well with higher resolutions?

native


4x

It's probably a thing that doesn't work well at higher resolutions.

Yeah, it's that good old bloom issue that nothing can't be done about, it seems (even Cemu seems to have it now with its high res options).

Here's what happens inside Embedded Framebuffer (EFB):
Shader process for bloom like fx:

1st stage (3xIR | 1xIR resized to 3x):
 

2nd stage (3xIR | 1xIR resized to 3x):
 

3rd stage (3xIR | 1xIR resized to 3x):
 

4th stage (3xIR | 1xIR resized to 3x):
 

From the images you can understand the process. 
1. Get our image..
2. They basically change Gamma. 
3. Then do the 1st pass of something like motion blur.
Actually they move the image left of center, make copy move right move right, make copy move further left and then the same for farther right.
All these with transparency blending.
For offsets, they probably calculate it from EFB resolution. That's why in 3xIR the distance is 3 times.
4. They do the same vertically.
5. Then the last EFB copy, they blend it to original image and vualah! Bloom fx!

The shader maths, were made and tied to original resolution and were not feature proofed to work in whatever resolution.
You can also see that camera zoom plays a lot of play here. Enable freelook in graphics option and zoom in: The fx is nice. zoom out: you see bigger differences.

I think that Dolphin can internally change shaders to fix these cases. 
An example (for 3xIR) would be that for the 3 last steps to have 1x resolution and then bilinear upscale it to 3xIR.
Or it can divide the offset of steps 3 and 4 by 3. (sth like offset/dolphinIR or change the w and h for the offset calculation).

I can't pinpoint the shader though :/ Even if I delete the cache it still creates countless shaders inside.

Interesting! That means it should theoretically be possible to fix the offset bloom issue, eh?

For this title probably. But this can break other titles with good bloom algorithm. So it needs to have a per title switch.