RE: R-Type Command
Sorry for the delay. Now that I check the logs, it seems like the error code matches up pretty well with what is happening! Desynch shots (uncloaking enemies) works fine I
think, but desynching your ships (cloaking them) ALWAYS produces the following lines when it black screens.
The first red box is when I start fresh with a loaded state and preform the desynch, it actually has more yellow lines (including the "render to texture" line) which are not
included if I load the state AGAIN and preform the same bug. It's strange how starting PPSSPP fresh, loading a state, and preforming the bug gives more errors than loading the
state a second time and doing the same. Is this a common problem?
01-05-2014, 05:50 PM Post: #18
[Unknown]
Top Contributor
Posts: 1,563
Joined: Nov 2012
Reputation: 49
RE: R-Type Command
Certain warnings it logs only once per run of PPSSPP.
Those are just warnings. They may cause rendering problems but theoretically should not break emulation. It seems to be reusing the depth buffer as a framebuffer though, not
sure if that's a problem or not.
-[Unknown]
01-08-2014, 02:41 AM Post: #19
Black Wires
Junior Member
Posts: 4
Joined: Oct 2013
Reputation: 0
RE: R-Type Command
(01-05-2014 05:50 PM)[Unknown] Wrote:
Certain warnings it logs only once per run of PPSSPP.
Those are just warnings. They may cause rendering problems but theoretically should not break emulation. It seems to be reusing the depth buffer as a framebuffer though, not
sure if that's a problem or not.
-[Unknown]
Please read some of the posts to see the problem I am talking about. In a nutshell on a action that causes those yellow warnings, the screen instantly goes black even though
everything else runs fine (you can still move/hear the interface noises etc). This buffer issue you are talking about very well may be the issue. Maybe it's trying to load a
visual that effectively does not exist? Kind of like trying to display a null value. Regardless, do you have any idea how I could fix this, or what more I could do to
troubleshoot the issue?
01-08-2014, 03:15 AM (This post was last modified: 01-08-2014 03:15 AM by [Unknown].) Post: #20
[Unknown]
Top Contributor
Posts: 1,563
Joined: Nov 2012
Reputation: 49
RE: R-Type Command
Well, if you try the software renderer, we can probably verify that theory. It will be very slow (you will not like it probably), but if it works there then it's probably
something like that (which would be useful to know.)
If it does the same thing there as with OpenGL, the issue is probably somewhere else.
-[Unknown]
01-08-2014, 10:39 PM Post: #21
Black Wires
Junior Member
Posts: 4
Joined: Oct 2013
Reputation: 0
RE: R-Type Command
(01-08-2014 03:15 AM)[Unknown] Wrote:
Well, if you try the software renderer, we can probably verify that theory. It will be very slow (you will not like it probably), but if it works there then it's probably
something like that (which would be useful to know.)
If it does the same thing there as with OpenGL, the issue is probably somewhere else.
-[Unknown]
You are right! Software rendering worked flawlessly (if not looking horrid and displaying at 1 FPS.) There was nothing at all in the event log for the "bug action". What is the
next step in troubleshooting? Is there anything I can tweak to temporarily fix the issue for myself, or is this something that has to be patched by a developer?
01-09-2014, 01:28 AM (This post was last modified: 01-09-2014 01:28 AM by [Unknown].) Post: #22
[Unknown]
Top Contributor
Posts: 1,563
Joined: Nov 2012
Reputation: 49
RE: R-Type Command
It's something that will need to be changed in the code.
But it's not so simple as just changing something.
-[Unknown]
