+- RPCS3 Forums (https://forums.rpcs3.net)
+-- Forum: PS3 Commercial Games (https://forums.rpcs3.net/forumdisplay.php?fid=4)
+--- Forum: Ingame (https://forums.rpcs3.net/forumdisplay.php?fid=6)
+--- Thread: Sniper: Ghost Warrior 2 [NPEB01002] (/showthread.php?tid=200380)
Sniper: Ghost Warrior 2 [NPEB01002] - GrantKane - 04-13-2019
RPCS3 v0.0.6-7972-df3b46a6 Alpha | HEAD
Quote:·F 0:24:40.223562 {PPU[0x1000017] Thread (RenderThread) [0x01214e68]} class std::runtime_error thrown: Trap! (0x1214e68)
RE: Sniper: Ghost Warrior 2 [NPEB01002] - Ani - 04-14-2019
Upload TTY.log too, it writes a lot of stuff to TTY
RE: Sniper: Ghost Warrior 2 [NPEB01002] - GrantKane - 04-14-2019
Here it is.
RE: Sniper: Ghost Warrior 2 [NPEB01002] - Asinine - 04-14-2019
RPCS3 v0.0.6-7972-df3b46a6 Alpha
Bad report this goes to ingame, have you tried interpreters?
(Although it still goes to ingame with recompilers for me, seems to need interpreters for audio.
RE: Sniper: Ghost Warrior 2 [NPEB01002] - GrantKane - 04-14-2019
Same result with both interpreters, white screen only without any logo and
Quote:·F 0:00:40.279566 {PPU[0x1000017] Thread (RenderThread) [0x01214e68]} class std::runtime_error thrown: Trap!BTW, don't call my report "bad" just because the game works for you and doesn't work for me. My congrats if it goes ingame for you, but reports are created for reporting bugs on any hardware.
(in file c:\projects\rpcs3\rpcs3\emu\cell\ppuinterpreter.cpp:3146)
RE: Sniper: Ghost Warrior 2 [NPEB01002] - Asinine - 04-14-2019
Not related to hardware, its a race condition. I had the same trap error on first run. And yes, invalid tests are "bad", because it can waste hours of developers time.
You can view it as rude or whatever you wish, but the fact is that after creating at least over 50 invalid reports by now whether it be from dodgy releases/invalid dumps, corrupt files, not trying interpreters/other settings mentioned on the other ID's for a game or whatever it may be. It does use a lot of our time. I have mentioned this in PM before that I had to have people retest dozens of your tests because of these issues.
Examples:
https://forums.rpcs3.net/thread-200004-post-303134.html#pid303134 - PM'ed to retest as it should've been ingame
https://forums.rpcs3.net/thread-199330.html - Retested myself as it should've been ingame/playable
https://forums.rpcs3.net/thread-199882.html - I dumped then retested US id just to test if the game regressed, it didn't but required Vulkan to reach intro.
https://forums.rpcs3.net/thread-199104.html - I retested then found out that it was just your game dump was bad, there was no issue with RPCS3 in your original test, you had missing/modified game files.
https://forums.rpcs3.net/thread-199698.html - Another game I retested because the test was questionable
https://forums.rpcs3.net/thread-199649.html - And another...
https://forums.rpcs3.net/thread-199402-post-300496.html#pid300496 - And another....
https://forums.rpcs3.net/thread-199334.html - I retested this because I knew it should atleast reach intro, it does with spu loop off.
https://forums.rpcs3.net/thread-199440-post-300610.html#pid300610 - Got Deminating to retest this one for me because I was busy.
https://forums.rpcs3.net/thread-199087-post-299735.html#pid299735 - Didn't test with interpreters
https://forums.rpcs3.net/thread-199756.html - PM'ed to retest as it needed interpreters as mentioned in other threads
https://forums.rpcs3.net/thread-199957-post-302891.html#pid302891 - PM'ed to retest this as it should've been ingame
That's not even counting all the bad Playable reports though, for instance South Park the Stick of Truth which you played for maybe 1 minute before saying it was playable. After ~2minutes of gameplay you have to input your character's name and the keyboard functionality doesn't work.
https://forums.rpcs3.net/thread-189155.html
Or other games which ran at 5fps for you but you still reported them as "playable"
https://forums.rpcs3.net/thread-196832-post-296569.html#pid296569
The worst part is, I only spent about 6 minutes looking for these "bad" reports, I know there is a lot more.
Feel free to call me out if I ever do a bad report, but to my knowledge after two years of tests I haven't put any games into Nothing/Loadable/Intro when they actually progressed further.
The nothing category in particular is very important to test everything all settings with multiple times.
RE: Sniper: Ghost Warrior 2 [NPEB01002] - GrantKane - 04-15-2019
Quote:The nothing category in particular is very important to test everything all settings with multiple times.I've checked another version and saw it was intro. I've launched the game and got this error. I've tried to get the intro and launched it about 20 times with various settings, but there was the same result - white screen with "Trap". I made the report that conforms to the rules (https://forums.rpcs3.net/thread-196671.html) and posted it. It's a fact. Calling it as "bad" or "invalid" or something like this is just a value judgement, nothing more.
Yes, sometimes I get these race conditions and start 2 or 3 times for getting further, but not this time, so, I can just make report wiithout knowing that it may be ingame for somebody. And I assume that if I launch this game 20 times again, there will be the same result.
And after going ingame, you could just tell "This game works for me" and move it to ingame, that's all. But you've preferred to lay my old bad reports on me, many of that we've already discussed in PM and forums.
Quote:The worst part is, I only spent about 6 minutes looking for these "bad" reports, I know there is a lot more.That's funny that you're telling me about wasting 6 minutes looking on them now, cause they're not even relevant to this particular report. So these ad hominem attacks will get you nowhere.
Yes, I've made many mistakes for years of testing, but I've already excused for them, to you and other people. So trying to shame me for them for the second time is not even rude, it's misconduct.
Quote:Feel free to call me out if I ever do a bad report, but to my knowledge after two years of tests I haven't put any games into Nothing/Loadable/Intro when they actually progressed further.If your report doesn't conform the rules, I'll call it bad and write why, as you before in PM. If your report conforms the rules and don't match mine (it's not important you go further or me), I will not call it bad. If I make any mistake, I excuse. But I prefer to ask and try to get to understand the situation fully, not to lay dirty laundry out. And I expect the same from others.
"Actual" state of the game for me was that the game doesn't work after 20 launches with various settings. I don't know is it regression, bug, race condition or something like this. I've just made correct report, you made your one, but you try to guilt me without asking more details like Ani did (respect him for that).
If developers want to get any more details, I will help them and do what they need to get this. Even if this is not a bug, I'll listen why without any accusation of all the mortal sins.
P.S. We've already discussed similar case here (https://forums.rpcs3.net/thread-199650.html).
RE: Sniper: Ghost Warrior 2 [NPEB01002] - Asinine - 04-15-2019
The whole reason I brought up the previous reports is because I'm quite tired of moderating these forums with all false reports being made, resulting in games being moved to the wrong category. I used to spend ~10 hours a week retesting games that you or other people tested and a large portion were put into the wrong category. This was another one of those same instances which is why I mentioned it, to hopefully help you realize how important it is to try more settings, verify your game dumps, run multiple times in case of race conditions etc. I view any test resulting in a game being moved to the wrong category as "bad", and so would any of the other moderators because if we don't retest it and find that it's in the wrong category than a developer could easily waste many hours testing a game just because the report was bad. This has happened a lot in the past already, which is why I put so much time into retesting other people's questionable reports. And it also obviously results in users thinking a game doesn't work when it does and an incorrect statistic on the compatibility page. The Playable category in particular is painful to moderate, there wouldn't be many people out there willing to put in the amount of effort I have in the past just verifying questionable reports and retesting.
(04-15-2019, 01:00 AM)GrantKane Wrote:I never said i "wasted 6 minutes", I brought up how it didn't take me long to find some bad reports of yours to emphasize how there has been a lot of games being moved to the wrong category. Why? Because this was yet another instance of the same thing happening, I had hoped by bringing it up and explaining how much time it takes to retest that you would test more carefully in the future. They are relevant because it's the same issue repeating itself.Quote:The worst part is, I only spent about 6 minutes looking for these "bad" reports, I know there is a lot more.That's funny that you're telling me about wasting 6 minutes looking on them now, cause they're not even relevant to this particular report. So these ad hominem attacks will get you nowhere.
(04-15-2019, 01:00 AM)GrantKane Wrote: Yes, I've made many mistakes for years of testing, but I've already excused for them, to you and other people. So trying to shame me for them for the second time is not even rude, it's misconduct.It was hardly intended to shame you, more like pointing out how many bad reports there have been because I didn't want history to repeat itself again and again because I have better things to do than retest reports all the time.
(04-15-2019, 01:00 AM)GrantKane Wrote:As stated before, I brought up the other reports because retesting dozens of questionable reports is not what I would consider as fun anything to help push users to test more carefully works for me. I don't see any need to get so upset about me calling a report "bad" when it was moved to the wrong category, I would have no issue if you or anyone else called a report I made "bad" if i put it in the wrong category.Quote:Feel free to call me out if I ever do a bad report, but to my knowledge after two years of tests I haven't put any games into Nothing/Loadable/Intro when they actually progressed further.If your report doesn't conform the rules, I'll call it bad and write why, as you before in PM. If your report conforms the rules and don't match mine (it's not important you go further or me), I will not call it bad. If I make any mistake, I excuse. But I prefer to ask and try to get to understand the situation fully, not to lay dirty laundry out. And I expect the same from others.
There would be nothing I'd love more than not having to moderate other user's reports and putting my complete faith that everything was checked properly, but as you can see from the examples, that isn't the case which is why I've been more inactive lately, which is sadly resulting in the playable statistic becoming more inaccurate than usual. On-top of having to write the progress reports and edit videos for the YouTube channel, help people in the Discord support forum and help developers test their Pull Requests... Moderating the forums properly has become a task that I can't find time for anymore I also stopped helping write the progress reports towards the end of last year because it was becoming too much work which is why those are being delayed yet no one is volunteering to help write them which is becoming stressful and I end up helping finish them off anyway. There's no way i would be able to do this much work for free if i wasn't in a good financial situation with lots of free time.
To my knowledge we never even issued you a forum warning despite all the bad reports you have made, especially the playable reports which are extremely important to test properly. We are the ones who take flak from having games in the Playable category when they're not actually Playable. And it could easily waste a lot of users time if they go to play a game only to find out it can't even get past the first minute of gameplay or runs at 5fps.
(04-15-2019, 01:00 AM)GrantKane Wrote: I've checked another version and saw it was intro. I've launched the game and got this error. I've tried to get the intro and launched it about 20 times with various settings, but there was the same result - white screen with "Trap".None of your logs show precise interpreters being tested though.
And yes, ani did ask for more info but he's also the one who asked our testers to retest a game we didn't have because it was another questionable report.