[BUG] - 3D Games Bug

---

It seems to me that a large number of the more 'graphically intensive' 3D games often have many visual errors, or simply dont work. For me i cannot play Backbreaker, NFS shift, Speedx 3D or even finish a quadrant test.

Backbreaker and NFS just don't start.
Speedx 3D starts but graphics are messed
Quadrant gets to the 2D test but then just stops and goes back to the menu when it should be doing the 3D benchmarks.

Am I the only one experiencing these issues?
Thanks for any cooperation

Originally Posted by bratfink

It seems to me that a large number of the more 'graphically intensive' 3D games often have many visual errors, or simply dont work. For me i cannot play Backbreaker, NFS shift, Speedx 3D or even finish a quadrant test.

Backbreaker and NFS just don't start.
Speedx 3D starts but graphics are messed
Quadrant gets to the 2D test but then just stops and goes back to the menu when it should be doing the 3D benchmarks.

Am I the only one experiencing these issues?
Thanks for any cooperation

Quadrant is a known issue, and it's because it's not written to support Gingerbread yet.

I just played a few minutes of Speedx 3D without any apparent issues.

NFS:Shift took a long time to load, and then it Force Closed, but once I said "report" and sent the report to Google, it reloaded itself and I was able to play the tutorial without any issues.

Both games looked pretty good and ran smoothly.

SpeedX 3D and NFS shift work flawlessly for me. Quadrant hasn't been updated yet to support Gingerbread/Nexus S, but that will happen shortly.

From what you're reporting, and if you're on a stock and unrooted ROM, it seems like a faulty PowerVR SGX 540 GPU. See if you can exchange it.

the issue with NFS is that it doesnt keep the screen awake

Originally Posted by slowz3r

the issue with NFS is that it doesnt keep the screen awake

Doesn't seem an issue for me. I played the tutorial track for much longer than the screen timeout on my phone is set for. Am I misunderstanding what you're saying?

Originally Posted by distortedloop

Doesn't seem an issue for me. I played the tutorial track for much longer than the screen timeout on my phone is set for. Am I misunderstanding what you're saying?

It may be because you are touching the screen ie breaking, and gas.

play a track without breaking or using gas or touching the screen in general

Originally Posted by slowz3r

It may be because you are touching the screen ie breaking, and gas.

play a track without breaking or using gas or touching the screen in general

I'll try again later on, but I wasn't breaking or gassing, or touching the screen for any other reason. I was just cruising along at the default speed in the tutorial. Maybe it's because it's the tutorial.

Originally Posted by distortedloop

I'll try again later on, but I wasn't breaking or gassing, or touching the screen for any other reason. I was just cruising along at the default speed in the tutorial. Maybe it's because it's the tutorial.

Ya iono, ive heard of other people having this issue,

Originally Posted by slowz3r

the issue with NFS is that it doesnt keep the screen awake

no problem here

but that is maybe because my default sleep time set on system wide was 2 min

the race is usually over in 2 min

i do not brake, or nitro

the game is soooooooooooooo easy compared to PC version

Hmm

---

Im glad to know quadrant isnt just me and i think iv sussed why NFS isnt working, i used the app data from my desire which iv heard causes problems so i have deleted and am re downloading the data through the application. Speedx is still giving me problems unfortunatly. And can anyone please test backbreaker? Thanks