Emulator

also tried it with real wiimote, doesn't help

Please respond if this issue is still valid, or it will be closed.

I can confirm this is still a problem, making the game unplayable.
Tested in r6567.

Seems like it didn't work cause of multi 3D scenes on screen.

Interaction with character work and the mesh highlight on cursor over.

But when zooming the screen cut in two 3D scenes and it's impossible to "point" an object. No highlight.

Tested in r6717.

Unfortunately few people seem to be really interested in this very underrated game, it's a shame because the game-emulation could be perfect if only the zoomed enviroment had the yellow hot-spot.
Anyway, if it can be of help, I have to report that when you start the game with DX9 plugin, an emulator message box appears saying: "trying to reinterpret pixel data with unsupported conversion tyupe 1" and then when you click on "OK" the game starts;
with OpenGL this message doesn't appear but then the screen is halved (you see only the top half part of the screen - anyway the hot-spots do not work in OpenGL as well).

this problem is still not fixed, yet it works, how to fix it, we can not play because of it, too bad, otherwise the game runs really well

But is there someone who really knows the "source" of this somewhat wierd problem?

My advice is cause of the scene split in 2 scenes.
One with objects on the left.
And the other with the character on the right.

Perhaps, there is a ray-tracing to know witch object is under the cursor ... and this ray-tracing isn't in the good scene.

In an other place in the game with only one 3D scene, it's possible to with the cursor select a character to talk to.

I'm bet on ray-tracing, cause it's too precise to be a bounding-box ...

Thanks for the project :-)

Issue 4231 has been merged into this issue.

and there is no solution?

if we could find a solution, this game is really good

still not working

Issue 4293 has been merged into this issue.

Issue 4412 has been merged into this issue.

The message "Trying to reinterpret pixel data unsupported conversion type 1, 4" are caused by the game switching between 16bit z compression formats and the normal z buffer format (24bit).

And that is why interaction with objects in Another Code: R doesn't work?

With the texcache-rewrite version of Dolphin the message "trying to reinterpret pixel data with unsupported conversion type 1" doesn't show up starting Another code: R, anyway the game is still not playable due to the missing interaction with objects...

the same here with r7671... no interaction with objects. The games runs pretty well indeed.

tried it with the new build 7719 but still not possible to play it properly, hope somebody will find the solution soon!

Can't this be a similar z-buffer problem like the one PCSX2 has with the game Fatal Frame where in hardware mode you cannot interact correctly (blue circle not showing up) with objects and ghosts?

Same problem here too, please, fix this bug :(

Is there somewhat an idea, how this can be solved? As far as I understand, the Wii is using framebufferaccess from CPU to make pointing features possible. But somehow in that special case the cpu cannot detect the pointer over the scene. Maybe someone can look over this, but i don't think many games uses this kind of pointer detection. So far I know, this problem is unique.

Has any of the devs confirmed that this issue is related to the "reinterpret pixel data" message? Since the message occurs only once on startup (far far away from the bug) and since hatarumo said the texcache-rewrite version of dolphin avoided the message but didn't fix it, it looks pretty unlikely to me. In that case, perhaps the issue's title should be changed to reflect that we don't know what causes the bug?

I tried digging around in the code myself (I'm not a dolphin dev) but didn't have any luck figuring out what could be causing this bug.
Did anyone more qualified than me take a look at this issue and found possible leads?