I have a problem with my new PS3. When I put in a PS2 game, 90% of the time I get audio, but no video. By hitting enough buttons, and getting past the starting screens/video, I can hit the "PS3" button in the middle of the controller, and it will bring up the PS3 quit screen (which I can see). If I cancel out of it, I can then see the regular game screen.

As an example, I am currently playing Disgaea, and I can hear the audio track, and if I remember the button sequence to start/load a game, I can hear the audio for that as well, but no video. This has happened on 3-4 other PS2 games that I have as well. (Lego star wars, SotC, Ratchet and Clank)

I only have one PS3 game (NGS) and that loads correctly without problem, and I have played multiple blu-ray and regular DVD movies as well, without incident.

I am running HDMI to my 1080p-capable JVC RP, and have the PS3 to output 1080p. Audio is optical to my pre/pro. This is a bit odd, I searched for simlar problems, but didn't come up with anything. Since I can output blu-ray movies in 1080p fine, that seems to rule out the TV and cable. I can also watch up-converted DVD movies on it fine as well, so it shouldn't be a DVD issue.

The only thing I can think of is some sort of weird handshake HDMI issue with PS2 games??? I did try changing the video output to 720p and 1080i to see if that did anything, but it didn't help.

Any ideas?

Thanks.

Did you try changing the scaling options of your games before you play them? Ya never know - it might work. I'd hate to see someone be separated from Laharl and his friends - I know that game is addictive as hell.

I know there are a few games like Disgaea output a variant of 240p rather than 480i, which has given fits to some displays. Can you try hooking up via component or composite and see if you can get a picture?

I found out the problem.

Newer JVC 1080p RP TV's were having a handshake problem with HDCP over HDMI. I found a few threads on Sony's website about it, and then searched the AVS thread on my TV, and found the same thing.

Using component inputs would have fixed it, but version 1.8 of the PS3 firmware fixed this, so I have upgraded my firmware to the current rev. The problem seems to be gone now.

Just in case anyone has this problem and comes across this thread.