[GC] Pokémon Colosseum

[linkhimura]

That's weird, because I had a x64 disc once, and it said that I couldn't install it. Maybe it was broken? I will try to get another one.

So, assuming I can get my hands on a 64 bit windows, and I can install it, I think I won't get a super speedup (since I will still have the same PC that runs it at 45 fps). What can I do, what options can I touch, to make it run faster, if it's possible? Will I get a speedup with the recent versions?

[NKF98]

x64 disc...

windows beyond XP don't have seperate discs for each install

and you will see an incredible speedup

[KHg8m3r]

(08-31-2015, 08:59 AM)NKF98 Wrote: x64 disc...

windows beyond XP don't have seperate discs for each install

and you will see an incredible speedup

There are separate image files for 32bit and 64bit installs, but a lot of retail disks have both.

x86 is the architecture, 32/64 is the differentiation. You can download Windows 7 x64 legally from Microsoft with your key, and it should install no problem with your license.

[VampireFish]

Hey guys, this problem has probably already been solved. I just cant find a fix anywhere. I've been playing Pokemon Colosseum and Pokemon Gale of Darkness. and on both games. I'm stuck because each time I go into the next awaiting battle. it doesnt continue. it just sits there saying that I have thrown out Espeon and Umbreon/ Eevee.. and the camera just spins. I cant actually battle and carry on with the game. Wondering if there was a fix at all.

[Skywolf]

Does anybody else have this issue?:



A similair thing happens to other Pokémon aswell (usually missing eyes). Playing on the NTSC-U version and already checked the checksum to see if it is a bad dump (which it isnt). Tried both Direct3D and OpenGL with different settings and both still have this issue.

GCI file (go left, then up then up again into the door that isnt blocked and fight Venus until she sends out Milotic.
Savestate file (load using build 4.0-7862, starts in the middle of the fight right before she send out Milotic).

[Kurausukun]

Yes, that happens to me too, and I honestly have no idea what causes it. It can't be the texture cache because that's already set to safe, and I tried EFB2RAM, but it didn't help. I suppose it's possible it's an XFB issue--have you tried enabling virtual or real XFB? That's one thing I don't think I tested.

[JMC47]

Looks like a lighting issue to me, where it's getting blown out.

3 frame fifolog on latest build of Dolphin with EFB2RAM set, please.

[Skywolf]

(10-02-2015, 06:54 PM)JMC47 Wrote: Looks like a lighting issue to me, where it's getting blown out.

3 frame fifolog on latest build of Dolphin with EFB2RAM set, please.

Here you go: Link. Recorded around the same time as shown in the screenshot in my previous post.

I dont think it's a lighting issue though. It persists through the entire time an affected Pokémon on the field. Milotic missing its entire body texture is an exception. Usually it are just the eyes. Which sometimes do appear correctly when fainting or sleeping when the eyes are "closed".

[JMC47]

Confirmed to work on software renderer -> https://fifoci.dolphin-emu.org/result/706385/

[Skywolf]

(10-02-2015, 10:01 PM)JMC47 Wrote: Confirmed to work on software renderer -> https://fifoci.dolphin-emu.org/result/706385/

Confirmed to fine on OpenGL aswell:

*Dramatic turn*
Or does it?


For some reason does it work when using a Fifolog but when playing the game normally it fails. And yes, both the screenshot and the .diff file are taken from the same moment. Using build 7876.

Savestate before a battle where Milotic is send out: link

Some more affected Pokémon (other than Milotic):

• Barboach
• Treecko
• Grovyle
• Sceptile
• Shuppet
• Lombre
  

Edit:I think it's related to UV-mapping. When enabling Texture Format Overlay and running the fifolog (correct texture placement) Milotic is for the most part normal with some white squares from the overlay. But when seen from the game the model is completely white. It seems all uvs get placed on the top-left corner of the texture. Screenshots