Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yu-Gi-Oh! Tag Force Series: Name and Attribute at the top of the Card is cut off #5470

Closed
DragonNeos opened this issue Feb 15, 2014 · 18 comments

Comments

@DragonNeos
Copy link

...when summoning a monster (Normal or Special Summon). This problem appears in every game in the series. This issue started appearing after hrydgard merged this Pull Request: (#2721) Before this Pull Request was merged, PPSSPP was not able to show the cards correctly (misaligned cards, cards displayed in black, etc.). After this Pull Request, cards are shown correctly except for cases when a monster is normal or special summoned (Name and Attribute are cut off from the top of the card that is in focus). When the effect of the monster is activated, the name and attribute of the card is shown.

OS: Windows 7 SP1 64-bit
PC: AMD Phenom II X4 810 @ 2.6 GHz, 8 GB DDR3 RAM, ATI Radeon HD 4200
Revision: PPSSPP v0.9.6-789-g3d3b0b1 64-bit

EDIT: @raven02 Save State Link for Tag Force 6: https://drive.google.com/file/d/0BxgBKNNFcTaAbjBCMUUtaW9hMzg/edit?usp=sharing

screen00000

EDIT: Refer to the most recent issue (#7501)(only the first picture).

@thedax
Copy link
Collaborator

thedax commented Feb 15, 2014

What platform, what version of PPSSPP, and what device?

@unknownbrackets
Copy link
Collaborator

And which versions of the game have you tested?

Can you follow these instructions for the missing part of the card?

https://github.com/hrydgard/ppsspp/wiki/How-to-find-a-graphic-issue-with-the-GE-debugger

-[Unknown]

@dbz400
Copy link
Contributor

dbz400 commented Feb 16, 2014

Just tried here on windows platform .Not too sure if it is specific card .May be you can provide a savestate here (F2)

screen00021

@dbz400
Copy link
Contributor

dbz400 commented Feb 16, 2014

Looks like it is really card specific , i also can reproduce it using the savestate provided by @DragonNeos

softgpu also renders the same issue.

screen00042

@unknownbrackets
Copy link
Collaborator

Does the GE debugger have anything to say about the issue? Maybe this is a rounding issue somewhere.

-[Unknown]

@DragonNeos
Copy link
Author

I'm not too sure if I did this correctly, I was pretty tired last night.
untitled200
untitled201
untitled202
untitled203
untitled204
untitled205
untitled206
untitled207
untitled208
untitled209
untitled210
untitled211
untitled212
untitled213
untitled214
untitled215
untitled216
untitled217
untitled218

@unknownbrackets
Copy link
Collaborator

Interesting. I wonder if it's alpha test related, then... since it seems to have the full card, and depth/etc. tests are all disabled. Also, seems clearly to be a render-to-texture effect, which might be relevant as well.

Does this work in the software renderer (even if it does, it's not a solution, just gathers more info... it will be very slow)? If yes, it may be stencil related.

-[Unknown]

@DragonNeos
Copy link
Author

The card still isn't displayed correctly when the Software Renderer is used.
screen00000

@hrydgard
Copy link
Owner

Does it cover the correct area of the screen? Could be a UV coordinate issue so that it's slightly stretched vertically so that the top doesn't fit in the drawn region.

EDIT: Never mind, just looked at the first pictures in this thread and it's not that.

@unknownbrackets
Copy link
Collaborator

Has this improved in the latest git build with "simulate block transfers" enabled?

-[Unknown]

@thedax
Copy link
Collaborator

thedax commented Jun 16, 2014

It's been fixed for quite some time now, I believe. I'll double check in a little bit.

@thedax
Copy link
Collaborator

thedax commented Jun 16, 2014

I don't know if it really is card specific or what-not, but I don't see it in Tag Force 3, and as I don't have Tag Force 6, and the savestate is months old by now, I think it might be safe to close. However, feedback from @DragonNeos or @raven02 would be handy.

Screenshot 01

@metaasza
Copy link

metaasza commented Dec 9, 2014

Sorry to ask this but I can't solve this problem yet even though i use the latest build of ppsspp. Can someone help me please. Thank you very much for your attention.

v0.9.9.1-1133-g363b4fd on Galaxy S III

@DragonNeos
Copy link
Author

@hrydgard @thedax Can you reopen this issue? This issue hasn't been fixed. There hasn't been any regressions between my last post and this one (PPSSPP v1.0.1-118-gc3f38f3). Here is an example of a video (Yu-Gi-Oh! GX Tag Force 3 - Beginning Story Mode Basement) from YouTube: https://www.youtube.com/watch?v=H8BBG7KjAEM&feature=youtu.be&t=23s
Between 0:23 - 0:26 in the video, I'm trying to normal summon a monster and the name and attribute of the card is cut off. On my opponent's turn, at 0:35 - 0:39 he tries to normal summon a monster and you will notice that the name and attribute of the card is cut off as well. At 0:40 in the video, the opponent activates the monster's effect and the whole card is shown.

@unknownbrackets
Copy link
Collaborator

Having multiple issues open for the same thing will only make it take longer to fix. Would you still like it to be reopened?

-[Unknown]

@thedax
Copy link
Collaborator

thedax commented Mar 6, 2015

@unknownbrackets: Wouldn't it make more sense to reopen this issue for the cut-off card problem, and then rename the other issue for the missing text problem? We don't even know if the two are related right now.

@DragonNeos
Copy link
Author

@unknownbrackets Can you reopen this issue?

@unknownbrackets
Copy link
Collaborator

I don't really think so. But sure, let's reopen all the issues so that we make sure things don't get fixed. I'm certainly not going to mess with things that have duplicates and no clear information.

Oh well, I'm going to ignore Yu-gi-oh from now on, don't like dealing with crap like this.

-[Unknown]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants