Latest build cannot be opened #11404
Comments
|
Latest build does not work on my phone, I tried to build v1.6.3-483-g1f881d790 but it can't be opened and just returned to the menu, but version v1.6.3-468-gad6938de5 works fine test on Imo S78 |
|
Can you remove line 41 |
|
Oh, that one is probably not a good idea indeed. |
|
according to https://en.wikipedia.org/wiki/MediaTek it's an 1GHZ single core CPU and according to this https://en.wikipedia.org/wiki/Comparison_of_ARMv7-A_cores all should we change it back to |
|
Not sure we made a decision to require NEON but it's pretty safe nowadays. We dropped support for pre-ARMv7 devices a long time ago, and I only know of one ARMv7 device that doesn't have NEON support, the early Tegra tablet. |
|
this is what @unknownbrackets did say:
-vfpv4 was added by me and is supported according to the list on 2013 and later (ARMv7) I think, my two cents on this is -> support on any earlier neon and floating point architecture should be dropped |
|
Well I still try to keep PPSSPP running on Sony Xperia Play just out of a matter of pride :) And I don't think it support VFPv4. |
|
Ok :) here is the pull #11405 |
|
Is it working now? -[Unknown] |
|
they are all very fast in reporting 🏎, but very lazy to get back, tell if it's working and close the issue ! 😴 |
|
Working but new problem, graphic glitch on gameplay here screenshot [url=https://ibb.co/jJaQu9][img]https://thumb.ibb.co/jJaQu9/SC20180922_204913.png[/img][/url] |
|
Are you very sure that this is on the latest build? A few builds ago, things were a bit broken, but it was fixed in the actual latest one avaiable right now. Just to make sure. |
|
of course I try from v1.6.3-487-g92b857ceb to v1.6.3-497-gead4946fd but the results are the same |
|
Could you try exporting a GE debugger dump on PC? To do this, open the game and select Debug -> GE debugger..., then when it's displaying the scene, press Record in the top right. After a second or so, it'll finish and save a trace of the drawing activity. After that, check the memstick/PSP/SYSTEM/DUMP folder and it'll have created a file named something like "ULES12345_0000.ppdmp". You can zip that and then drag and drop it into a reply here. -[Unknown] |
|
No I don't have PC |
|
@endrare the graphics glitch only happen in one game? or more? because I have the same issue as yours in the latest build started in v1.6.3-483 (Because Of Implementing Vertex Range Culling) but I found a solution for this issue in my phone GPU Mali-450 MP using GLtools :) |
|
@Emulatorer not just one, I tried the Valkyria Chronicles 3 but only a white screen with normal audio, |
|
See my settings of GLtools #11393 (comment) |
|
Hmm, Valkyria Chronicles 3 is working on a Pixel in GLES, at least. I wonder if this is not handling nan correctly on w. -[Unknown] |
|
PowerStone Collection suffer the same issue as Valkyria Chronicles 3 and I tried to use Catlog to capture the activity log of ppsspp hope this can help note: rename log to txt |
|
That's a straight up GLSL compiler error, unfortunately we're not logging enough code to tell where the error is. That I'm gonna fix soon. Is that from the very latest build, unknownbrackets recently fixed a bug? |
|
Im currently using build v1.6.3-500-gee62e19c6 |
|
Try the latest git - I found another mistake which is fixed in a newer build. I wish drivers on the devices I used were less forgiving. -[Unknown] |
|
another reason to roundtrip GL shaders through glslang+spirv-opt I guess... |
|
latest build are now working well :) |
![https://thumb.ibb.co/jJaQu9/SC20180922_204913.png[/img][/url]](https://thumb.ibb.co/jJaQu9/SC20180922_204913.png%5B/img%5D%5B/url%5D){kind=link}
ghost
mentioned this issue
What happens?
What should happen?
What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.
The text was updated successfully, but these errors were encountered: