Yu-Gi-Oh! GX Tag Force Card summoning (card cut-off / cropped)

[metaasza]

When the card is summoned, its appeared that the head of the card is disappear as in #5470 and the duel point table's text is also missing. I was trying to find the solution already but it seems that I cannot find anything that can solve my problem. Sorry if this post was annoying but I don't know how to do as I am a very newbie.

Thank you

I use Samsung Galaxy S III (GT-i9300)
http://www.gsmarena.com/samsung_i9300_galaxy_s_iii-4238.php

latest build PPSSPP v0.9.9.1-1042-gff68e32

[D8174]

I'm curious why you closed this. For me these issues still exist. The missing text one is especially annoying.

[hrydgard]

Do the errors happen only on Android or also on Windows, for example?

[D8174]

They happen on Windows too.

[DragonNeos]

@hrydgard @syrobee The text doesn't show up on the Duel Bonus and New High Score Bonus screen if you use the fonts that come with PPSSPP. If you use the PSP fonts, the text does show up on those screens on Windows (don't have an Android to test with).

[D8174]

@DragonNeos Oh okay, I didn't know that was a thing. Thanks.

[lordemort]

i also got some problem here, for Yu Gi Oh Tag Force
when i save the game via the map it stuck in "checking memory card..."
others,like sound,animation, is still working normally, only the checking memory card screen just stuck there,also when i want to change my deck name it didn't show the alphabet keyboard on gray-background,so i just press change deck name and nothing happened

and also here is the log,
if i save via map,it stopped in "...wrong dialog type"
http://pastebin.com/0LHfj30b -->save via map
http://pastebin.com/gb31gANS -->deck name

sorry for the long post and my english
i don't know how to fix it
Thank you

i'm using ppsspp for windows

[daniel229]

A little change since #8130 ,the card is moving to the top,not in the centre.

before

[unknownbrackets]

Okay. Now that really explains why the top is cut off, right? It's right up against the edge. So clearly something about being flipped was happening wrong here - maybe it still is positioning it wrong.

In Core/Reporting.cpp, find:

    bool ShouldLogOnce(const char *identifier)
    {
        // True if it wasn't there already -> so yes, log.
        return logOnceUsed.insert(identifier).second;
    }

Change to:

    bool ShouldLogOnce(const char *identifier) {
        return true;
    }

Also please change this:

    bool IsEnabled()
    {
        if (g_Config.sReportHost.empty() || (!currentSupported && PSP_IsInited()))
            return false;
        // Disabled by default for now.
        if (g_Config.sReportHost.compare("default") == 0)
            return false;
        return true;
    }

To:

    bool IsEnabled() {
        return false;
    }

To avoid spamming it, heh, with that change.

Then, what does it log as far as any transfers during this?

-[Unknown]

[daniel229]

just spamming this

38:38:664 user_main    W[G3D]: GLES\StateMapping.cpp:908 Unsupported depth range test - depth range: 50000.000000-10000.000000, test: 0.152590-0.76295
1

[unknownbrackets]

Oh, sorry, well in that case try changing all the WARN_LOG_REPORT_ONCE and WARN_LOG_ONCE in GPU/Common/FramebufferCommon.cpp to just WARN_LOG. You'll have to remove the first argument too, like before.

-[Unknown]

[daniel229]

Still don't see it log other things
the log.
https://gist.github.com/daniel229/ef9d884f5dbf7abaa9ff

[unknownbrackets]

Relevant lines:

49:48:880 user_main    I[SCEGE]: Common\FramebufferCommon.cpp:417 Creating FBO for 00088000 : 480 x 272 x 3
49:48:880 user_main    W[G3D]: Common\FramebufferCommon.cpp:608 Memcpy fbo upload 04488000 -> 04088000

49:48:989 user_main    I[SCEGE]: Common\FramebufferCommon.cpp:417 Creating FBO for 00160000 : 128 x 272 x 3
49:48:989 user_main    W[G3D]: Common\FramebufferCommon.cpp:608 Memcpy fbo upload 04560000 -> 04160000
49:48:989 user_main    W[SCEGE]: Common\FramebufferCommon.cpp:453 FBO reusing depthbuffer, 00160000/00110000 and 00088000/00110000

49:49:055 user_main    I[SCEGE]: Common\FramebufferCommon.cpp:417 Creating FBO for 00000000 : 480 x 272 x 3
49:49:056 user_main    W[G3D]: Common\FramebufferCommon.cpp:608 Memcpy fbo upload 04400000 -> 04000000

I hope it's not an effect from before that save state. Does disabling the block transfer setting have any effect? If it doesn't, I guess it must be render-to-texture.

There are three textures after all so that does seem likely. I guess the 128 x 272 x 3 one is likely being used for the card.

-[Unknown]