Dolphin, the GameCube and Wii emulator - Forums

Most of the hacks introduced in this fork are non deterministic and will completely fuck up netplay or recordings. All the async shader compilation for example.

Determinist stuff is a BIG HACK and is not planned to be merged at the momment, and ASYNC stuff is not related with that.

So when will Gecko OS loading be fixed?

I have some problems using the beta build in the first post.

Wind Waker with HD textures
DX11 async on/off, i get missing textures when moving the camera, like the sea in the distance turns black, or part of the island goes black.
Its fine in DX9 mode though.

Metroid Prime
DX11 with async on, I get a big black box around the "hold and charge" power beam shot.
DX9 no problems, but random crashes.

F Zero GX seems to crash with async on too, but lovely and smooth when working.

Any tips here?

Edit
F Zero seems to be running OK now with CPU access to EFB disabled.

The problem with Wind Waker and Metroid is the High Res textures, some dont want to work right for whatever reason, something to do with distance i think, since the power beam hold and shoot blast was a high res texture too. Also when you move the camera the black box disappears, same as in Wind Waker, moving the camera has the textures come back. So same problem in both, DX9 fixes it, but Metroid seems to crash in DX9 randomly. WW is fine in DX9.

(12-22-2014, 11:55 PM)jasjeet Wrote: [ -> ]I have some problems using the beta build in the first post.

Wind Waker with HD textures
DX11 async on/off, i get missing textures when moving the camera, like the sea in the distance turns black, or part of the island goes black.
Its fine in DX9 mode though.

Metroid Prime
DX11 with async on, I get a big black box around the "hold and charge" power beam shot.
DX9 no problems, but random crashes.

F Zero GX seems to crash with async on too, but lovely and smooth when working.

Any tips here?

Edit
F Zero seems to be running OK now with CPU access to EFB disabled.

The problem with Wind Waker and Metroid is the High Res textures, some dont want to work right for whatever reason, something to do with distance i think, since the power beam hold and shoot blast was a high res texture too. Also when you move the camera the black box disappears, same as in Wind Waker, moving the camera has the textures come back. So same problem in both, DX9 fixes it, but Metroid seems to crash in DX9 randomly. WW is fine in DX9.

can you link me to the textures that you are using so i can test the isues?

(12-22-2014, 07:30 AM)Skazzy3 Wrote: [ -> ]So when will Gecko OS loading be fixed?

will look to the issue as soon as i have some free time, year end is a full time work time for me

(12-23-2014, 05:48 AM)Tino Wrote: [ -> ]

(12-22-2014, 11:55 PM)jasjeet Wrote: [ -> ]I have some problems using the beta build in the first post.

Wind Waker with HD textures
DX11 async on/off, i get missing textures when moving the camera, like the sea in the distance turns black, or part of the island goes black.
Its fine in DX9 mode though.

Metroid Prime
DX11 with async on, I get a big black box around the "hold and charge" power beam shot.
DX9 no problems, but random crashes.

F Zero GX seems to crash with async on too, but lovely and smooth when working.

Any tips here?

Edit
F Zero seems to be running OK now with CPU access to EFB disabled.

The problem with Wind Waker and Metroid is the High Res textures, some dont want to work right for whatever reason, something to do with distance i think, since the power beam hold and shoot blast was a high res texture too. Also when you move the camera the black box disappears, same as in Wind Waker, moving the camera has the textures come back. So same problem in both, DX9 fixes it, but Metroid seems to crash in DX9 randomly. WW is fine in DX9.

can you link me to the textures that you are using so i can test the isues?

Sure
Hypatia’s Hi-Res Wind Waker Texture Pack and Metroid texture pack
http://onthegreatsea.tumblr.com/DOWNLOADS

Hi , I am Begginer.

Why Ishiiruka-Dolphin Custom Version is slower than Official Dolphin  4.02 ?

I want to play Zelda Twilight Princess (GameCube) on my pc by Dolphin.

Official Dolphin-4.02 give me 28 fps but Ishiiruka-Dolphin-f40ab1a.x64 give me only 22 fps.

Official version and Ishiiruka Build have Same setting.

Direct3d9 - 1920x1080 Full Screen - Internal Res 1.5xNative(960x792) -AA 4xSSAA - AF 8x - EFB Copies To RAM

and other Setting,  Hacks , Audio , ... are same.

Please guide me.

Sorry for my English.

(12-23-2014, 10:14 PM)zelda64 Wrote: [ -> ]Hi , I am Begginer.

Why Ishiiruka-Dolphin Custom Version is slower than Official Dolphin  4.02 ?

I want to play Zelda Twilight Princess (GameCube) on my pc by Dolphin.

Official Dolphin-4.02 give me 28 fps but Ishiiruka-Dolphin-f40ab1a.x64 give me only 22 fps.

Official version and Ishiiruka Build have Same setting.

Direct3d9 - 1920x1080 Full Screen - Internal Res 1.5xNative(960x792) -AA 4xSSAA - AF 8x - EFB Copies To RAM

and other Setting,  Hacks , Audio , ... are same.

Please guide me.

Sorry for my English.

with those settings you cant have the same setting in master as it does not have dx9 to compare. as for speed it will be better if you disable AF and AA and just set internal res to 3.0 or 4.0

Hi Tino.
Thanks For Help.

I Test Official version and Ishiiruka Build without AF and AA And set internal res to 3.0.

Direct3d9 - 1920x1080 Full Screen - Internal Res 3xNative(1920x1584) -AA non - AF 1x - EFB Copies To RAM

and other Setting,  Hacks , Audio , ... are same.

But Ishiiruka-Dolphin Custom Version is slower than Official Dolphin  4.02 in my System.

With Your recommend setting:

Official Dolphin-4.02 = 28 fps

Ishiiruka-Dolphin-f40ab1a.x64 = 16 fps


Please  guide me.

My System Specification:

OS   : Windows 7 64bit

CPU : Intel Core 2 Quad Q6600 @ 2.4 GH

VGA : NVIDIA GeForce 9600 GT - 1GB VRAM - DirectX10

RAM : 4GB DDR2 800 MHZ