Hi MonkeyGrass,
That's strange, as we had the same "feeling" about the lag.
I didn't play in 720p since the lag has started to be reduced in 1080 resolution, a couple of updates ago.
In the tournament, I didn't experienced lag on MM and BK in 1080i (on the contrary, I find that the ball goes crazy now, i.e. hard to control, like in 720p).
In 1080i, CFTBL has some lag (but a lot less than before), I will check in 720p.
I'm talking about timed cradle shots, where you are trapping the ball and then let it roll down the flipper until the end... I either have to "guess" early, or risk the ball rolling off the end of the flipper half the time. Beyond the trapping - it's almost impossible to react to a ball flying down the inlane in time, I lose balls like this constantly in TPA and rarely does that happen on a real table
The "improvement" I saw was in 720p, and it's still far from perfect. I still have yet to see anything get truly better at 1080 in regards to the flipper lag.
It's really more about learning the repeatable behaviour aspects of the tables and exploiting that for high scores, IMO.
They must have some "magic" PS3 that doesn't show bugs lol.... wish I had that model!!
I still cannot play the game in 1080. Ball action (and flying around the table) are physics engine tweaks, not flipper lag. Perhaps we are talking about two different things? I'm talking about timed cradle shots, where you are trapping the ball and then let it roll down the flipper until the end... I either have to "guess" early, or risk the ball rolling off the end of the flipper half the time. Beyond the trapping - it's almost impossible to react to a ball flying down the inlane in time, I lose balls like this constantly in TPA and rarely does that happen on a real table - the flipper just will not react fast enough to hit or toss it to the other flipper. Also, trying to respond to a slightly off post-pass or anything that requires using both flippers to "juggle" the ball is nearly impossible because every stroke is *just* a hair late, and when you are talking about saving a ball or juggling it like that, the lag is obvious.
The "improvement" I saw was in 720p, and it's still far from perfect. I still have yet to see anything get truly better at 1080 in regards to the flipper lag. Some tables are fine, some OK, and some flat out unplayable (for me) - just like it has always been. Then again, I know I'm rather attuned to it. I play and maintain real pins every single day and I use a lot of flipper manipulation as part of my game. I lose about 20-30% of my "skills" because none of that translates to TPA very well...
Replicated the same problem. Game freezes when activating White Water with PS3 output set to 1080p--setting to 720p fixed the issue.
Same for me! I did have strange problems with a complete freeze after saving the score with the previous updates (since 1.06 I believe) but the table was playable at least. Now the PS3 freezes even after selecting the table! Fairsight still deny that there is any problem but the fact is that there are a bunch of people like me having this issues and they're just not able to fix this since more than 6 months. This is not a bugfix, this is a bug ADDING feature and totally sucks. This is even more annoying because it was one of my most favourite table because I like playing it on the original.
Edit: I admit that it's working in 720p and it also seems to save the score without a freeze (didn't try this with previous versions before in this resolution until I found this thread). It really seems that there is a general lack of ~200 Milliseconds after pressing the L1/R1 buttons but it seems that it's not depending from the resolution. At least for me it's the same lack with 1080p or 720p, tested with another table (Attack from Mars). Glad that I can play this table again...thanks guys! I'm hoping for a 1080p fix nevertheless.
It was tann who put Sony at fault earlier in the thread. And in some ways it is true. The problem is that they can't replicate it if they just start throwing code at everything without knowing the cause then nothing good will come of it.
I'm almost convinced that Sony has two different chips et throughout all their revisions. Otherwise I wonder what different system configs might be causing this. And it could be some ridiculous sounding difference like is the machine connected via wireless or not, or some other setting that could seem unrelated.
I somehow doubt that everyone who has said it's running fine is only running at 720p. And while that seems to be the workaround it needs to be clearly stated.
First thing people should check if they can is to find out if it works on the PS3 default settings and if maybe different firmwares are being used. Anyone feel like factory reset? Is it possible without wiping the drive contents? Clear cache? They will need some guidelines on system configs, revisions and whatnot so they can set their systems up to recreate this.
Did anyone affected with the white water crash experience this screen after the patch?
View attachment 103
Did anyone affected with the white water crash experience this screen after the patch?
View attachment 103
Did anyone affected with the white water crash experience this screen after the patch?
View attachment 103
No and even deleting the savefiles doesn't help. Unfortunately you can't delete or deinstall part of the game/tables. You have to uninstall and download the whole game once again! I didn't try that yet but I don't think that will help since Fairsight still claims on Facebook that they can't reproduce this issue. So we still have to wait until they get one of the affected consoles for testing. Isn't there anyone who could send an affected PS3 to their studio?
There are less drastic things that can be done first that I recommended someone try when this issue first came up. No one seems to be willing to do it and I'm not having the issue. In the PS3 recovery menu there are two options that I'd like to see someone try. They are #3 Restore File System and #4 Rebuild Database.
If I was having the problem I would have already done these and then we'd know but I don't so I didn't and we don't know.