Project

General

Profile

Actions

Emulator Issues #2137

closed

Trying to reinterpret pixel data

Added by nexxus86 almost 15 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
GFX
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

What steps will reproduce the problem?

  1. interacting with objects like doors,sings, etc....
    2.
    3.

What is the expected output? What do you see instead?
On the real Wii when you click on an sign or house, the camera will zoom to
it and you can interact with items like doors,windows,plants or sings.
These objects also getting yellow when you hover the courser over it.
In Dolphin, all this does not work, you can hover the cursor on it, click
on it, nothing happens.

What version of the product are you using? On what operating system?
Dolphin r4950 X64, Windows 7 X64

Please provide any additional information below.
Tried with 32bit/64 bit version, JitIL and normal Jit, enabled and disabled
idle skipping, nothing helps.


Related issues 4 (0 open4 closed)

Is duplicate of Emulator - Emulator Issues #5405: Off-by-one error in encoded textures causes Another Code R issue (revival of issue 2137)Fixed

Actions
Has duplicate Emulator - Emulator Issues #4231: Interaction with objects in Another Code R does not workDuplicate

Actions
Has duplicate Emulator - Emulator Issues #4293: Yogi Bear problemsDuplicate

Actions
Has duplicate Emulator - Emulator Issues #4412: crashes with D3D9 & D3D11 on Rogue Leader (Rogue Squadron II)Duplicate

Actions
Actions #1

Updated by nexxus86 almost 15 years ago

also tried it with real wiimote, doesn't help

Actions #3

Updated by Anonymous almost 14 years ago

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

Actions #4

Updated by bsempai almost 14 years ago

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

Actions #5

Updated by corbofo almost 14 years ago

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.

Actions #6

Updated by hatarumoroboshi over 13 years ago

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).

Actions #8

Updated by Dante38490 over 13 years ago

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

Actions #9

Updated by hatarumoroboshi over 13 years ago

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

Actions #10

Updated by corbofo over 13 years ago

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 :-)

Actions #11

Updated by glennricster over 13 years ago

Issue 4231 has been merged into this issue.

Actions #12

Updated by Dante38490 over 13 years ago

and there is no solution?

Actions #13

Updated by Dante38490 over 13 years ago

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

Actions #14

Updated by Dante38490 over 13 years ago

still not working

Actions #15

Updated by skidau over 13 years ago

  • Status changed from New to New
  • Category set to gfx

Game name of the report above is: Another Code R

Actions #16

Updated by skidau over 13 years ago

Issue 4293 has been merged into this issue.

Actions #17

Updated by skidau over 13 years ago

Issue 4412 has been merged into this issue.

Actions #18

Updated by skidau over 13 years ago

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).

Actions #19

Updated by hatarumoroboshi over 13 years ago

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

Actions #20

Updated by hatarumoroboshi over 13 years ago

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...

Actions #21

Updated by david.abril22 over 13 years ago

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

Actions #22

Updated by thethodi about 13 years ago

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

Actions #23

Updated by markwest76 about 13 years ago

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?

Actions #24

Updated by gianx80 almost 13 years ago

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

Actions #25

Updated by tom.matern almost 13 years ago

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.

Actions #26

Updated by wordmanwords over 12 years ago

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?

Actions #27

Updated by DimitriPilot3 over 12 years ago

  • Status changed from New to Duplicate

Apparently fixed by r1587cb3738ee, thanks to the research done on issue 5405 (which is worth checking out).
I suppose this issue may be merged into issue 5405, since they're all about that one game (Another Code R).

Actions

Also available in: Atom PDF