05-08-2014, 09:36 PM
Skyges
05-08-2014, 09:44 PM
(05-08-2014, 09:36 PM)MaJoR Wrote: [ -> ]You're welcome. But you should have just posted it here...
Sorry wasn't sure how this all works, bit of a noob
Appreciate it though.
Poopsaurus
05-12-2014, 01:48 PM
Hi guys, I'm new to the forum but I have already several years on Dolphin. I read the whole thread and the Wiki page, and there is still the same problem: [color=red]error 2068 is NOT resolved ![/color]
It seems that Tiesto had the same problem as me, but you [color=red]IGNORED ALL[/color] his comments... ♥
I tried the old 3.0-421 revision proposed by the Wiki, but nothing works, the best I can get is a shifted double picture. (1st pic)
When they overlap I get the (bad) bloom that I had before, but over the thin part where they are separated, the picture is good. Basically all it takes is to remove the duplicated image.
Now I'm on the very last version (4.0-1569) and the best I can get (in term of proper emulation=no supa bloom) is EXTREMELY laggy. (2nd pic)
It's sort of a glitch, when I'm using OpenGL: first it's bloomy, then I open the Graphics Settings and it's starting to stutter hardcore, the bloom disappear, the image is perfect, but the game is playing at [color=red]1[/color] poor FPS.
And with D3D this glitch works even better ! I can play with a perfect image @30FPS but there is still a stripe (1/6 of the screen) which stays bloomy. (3rd pic)
I also tried to find another OpenGL shader (.glsl) to correct the gamma of the image but I haven't found anything conclusive.
[color=red]Otherwise, disregarding the bloom, the game runs perfectly at 30 FPS with IR x4 and 4x SSAA.[/color]
So we are very [color=green]close to perfection[/color], the only thing missing is the bloom and I will bless you for every hour of gaming if we can find the solution together.
Help me please, Almighty forum. ♥
PICS: http://hpics.li/3c40905
► [color=red]Check my specs on my profile:[/color] https://forums.dolphin-emu.org/User-poopsaurus ◄
It seems that Tiesto had the same problem as me, but you [color=red]IGNORED ALL[/color] his comments... ♥
Tiesto Wrote:Hello Guys. i have a problem with the bloom in MHTri. As the Wiki says the bloom effects already resolved in 3.0-421, but it isnt. It looks like the picture John Dovahkiin Doe postet. Too much bloom.
The ground at night looks like it is a sunny day. Dont know how to fix that. Tried already several builds. At the moment 3.5-1063, the latest caused a flickering screen... [...]
I tried the old 3.0-421 revision proposed by the Wiki, but nothing works, the best I can get is a shifted double picture. (1st pic)
When they overlap I get the (bad) bloom that I had before, but over the thin part where they are separated, the picture is good. Basically all it takes is to remove the duplicated image.
Now I'm on the very last version (4.0-1569) and the best I can get (in term of proper emulation=no supa bloom) is EXTREMELY laggy. (2nd pic)
It's sort of a glitch, when I'm using OpenGL: first it's bloomy, then I open the Graphics Settings and it's starting to stutter hardcore, the bloom disappear, the image is perfect, but the game is playing at [color=red]1[/color] poor FPS.
And with D3D this glitch works even better ! I can play with a perfect image @30FPS but there is still a stripe (1/6 of the screen) which stays bloomy. (3rd pic)
I also tried to find another OpenGL shader (.glsl) to correct the gamma of the image but I haven't found anything conclusive.
[color=red]Otherwise, disregarding the bloom, the game runs perfectly at 30 FPS with IR x4 and 4x SSAA.[/color]
So we are very [color=green]close to perfection[/color], the only thing missing is the bloom and I will bless you for every hour of gaming if we can find the solution together.
Help me please, Almighty forum. ♥
PICS: http://hpics.li/3c40905
► [color=red]Check my specs on my profile:[/color] https://forums.dolphin-emu.org/User-poopsaurus ◄
05-12-2014, 02:05 PM
It's a slow effect, it's working in OpenGL, albeit slowly. The only proposed way to speed it up currently is a speedhack; which no one is working on yet to my knowledge.
Because it's working in OpenGL, it's marked as resolved.
D3D has some strange problems in it; not completely sure why, but it seems to be some kind of offset present in other games too.
Because it's working in OpenGL, it's marked as resolved.
D3D has some strange problems in it; not completely sure why, but it seems to be some kind of offset present in other games too.
05-12-2014, 07:18 PM
I think there's actually not just one issue with bloom in Dolphin. One of them, the offset bloom which was especially strong in ZTP seems to be gone. But there's still this issue that has always been there and some devs said it had something to do with using multiple resolutions and there might not be any real way to fix it. Of course, projection hacks or whatever filters might help here...
![[Image: ee8w75wx.png]](http://s7.directupload.net/images/140429/temp/ee8w75wx.png)
![[Image: ee8w75wx.png]](http://s7.directupload.net/images/140429/temp/ee8w75wx.png)
05-12-2014, 11:39 PM
The bloom offset is a different glitch, though.
Poopsaurus
05-13-2014, 08:18 AM
JMC47 Wrote:It's a slow effect, it's working in OpenGL, albeit slowly. The only proposed way to speed it up currently is a speedhack; which no one is working on yet to my knowledge.
Because it's working in OpenGL, it's marked as resolved.
In absolute terms I do not agree with what you say, because the Wiki reports the problem solved by the 3.0-421 revision, however it is thanks to OGL on the 4.0-1569 revision that I get the perfect picture I posted, not at all with 3.0-421 !
Furthermore, Issue 2068 has been resolved by revison e58692653afd, and as you can see on the page, the log message says "D3D9 only".
Quote:Log message
PixelShaderGen: Use correct texel to pixel mapping when sampling textures
[color=red](D3D9 only)[/color]
Fixesissue 2068.
Fixesissue 5158.
[color=red]3.0-421 solves nothing.[/color]
► [color=red]Check my specs on my profile:[/color] https://forums.dolphin-emu.org/User-poopsaurus ◄
05-13-2014, 08:19 AM
The issue has only been resolved in D3D9 because it only occured in D3D9 to begin with. I even explained that in the page you linked to.
Poopsaurus
05-13-2014, 08:31 AM
I agree, but how is it possible that I get this with D3D9 on 3.0-421 then ?
Sorry if I act like a retarded but I feel I miss a big thing there.
Sorry if I act like a retarded but I feel I miss a big thing there.
05-13-2014, 12:45 PM
Because it skips emulation; some things in game don't work.