Porting PewPew

[mcobit]

Btw, just downloaded and played pewpew1 on the ipad and I have to say, that, even if the framerate is of course much higher and makes the game smoother, the controls are just uncompareable. The nubs are so nice to play this game!!!

 

[sebt3]

Online features still not working though I wasn't expecting that to be fixed in this build.

Yes I havent worked on this... I've barely any network when the SGX is heavyly used...

[ 4674.546386] pvr: pewpew2: cleaning up 2147 unfreed resources
Could that mean there's a resource leak, or is that just normal?

It's at the end of the game (when quitting). No real leakage, just as the system clear all the memory when the program finish, why would you do it object by object ?


also I spend more time trying to reproduce that lockup in the menu, no luck (depending on the point of view )

 

[Neelix]

hehe..


I haven't reproduced it yet either... I rather suspect it's going to be a couple more days before I can, i.e. as something that happens in the sgx drivers over hours of operation... my system had had about 4 days of uptime before I finally rebooted it.


- Neelix

 

[mcobit]

Ok, here my logs from ssh:


before it crashes I get a lot of those:

Spoiler

[ 5798.894989] pvr: pewpew2: IOCTL 69 failed (13)


[ 5798.996551] pvr: pewpew2: IOCTL 69 failed (13)


[ 5799.098144] pvr: pewpew2: IOCTL 69 failed (13)


[ 5799.199707] pvr: pewpew2: IOCTL 69 failed (13)


[ 5799.301147] pvr: pewpew2: IOCTL 69 failed (13)


[ 5799.402770] pvr: pewpew2: IOCTL 69 failed (13)


[ 5799.504241] pvr: pewpew2: IOCTL 69 failed (13)


[ 5799.605926] pvr: pewpew2: IOCTL 69 failed (13)


[ 5799.707489] pvr: pewpew2: IOCTL 69 failed (13)


[ 5799.808746] pvr: pewpew2: IOCTL 69 failed (13)

After killing it via ssh and trying to restart, it fails to start with:

Spoiler

[ 5800.847808] sched: RT throttling activated


[ 5801.087341] input: nub0 as /devices/platform/omap_i2c.3/i2c-3/3-0066/input/input10


[ 5801.110595] input: nub1 as /devices/platform/omap_i2c.3/i2c-3/3-0067/input/input11


[ 5801.527496] SGX Hardware Recovery triggered (from SGXOSTimer)


[ 5801.527526] EVENT_STATUS = 0x20000000


[ 5801.527526] EVENT_STATUS2 = 0x00000000


[ 5801.527526] BIF_CTRL = 0x00000000


[ 5801.527557] BIF_INT_STAT = 0x00004002


[ 5801.527557] BIF_MEM_REQ_STAT = 0x00000000


[ 5801.527557] BIF_FAULT = 0x01972000


[ 5801.527557] CLKGATECTL = 0x00212120


[ 5801.527587] HW Recovery dump generated at 1340287582872955


[ 5802.128997] HWRecoveryResetSGX: recovery failed (34). Disabling the driver


[ 5854.275878] keyboard: can't emulate rawmode for keycode 139


[ 5854.438842] keyboard: can't emulate rawmode for keycode 139


[ 5865.486480] aufs test_add:261:mount[7127]: uid/gid/perm /mnt/pnd/pewpew2 1000/1000/0755, 0/0/0777


[ 5865.652343] input: nub0 as /devices/platform/omap_i2c.3/i2c-3/3-0066/input/input12


[ 5865.671325] input: nub1 as /devices/platform/omap_i2c.3/i2c-3/3-0067/input/input13


[ 5867.069641] input: nub0 as /devices/platform/omap_i2c.3/i2c-3/3-0066/input/input14


[ 5867.090057] input: nub1 as /devices/platform/omap_i2c.3/i2c-3/3-0067/input/input15

 

[notaz]

[ 5802.128997] HWRecoveryResetSGX: recovery failed (34). Disabling the driver

If I had reliable way to reproduce this one, I could try some ideas to 'kick it harder' to reset it.


There is nothing I can do with hardware recoveries in general though, those are coming from binary/firmware blobs or hardware itself locking up.

 

[mcobit]

As most people, even with 256mb Pandoras can't reproduce this, I am starting to think, that some sgx chips might be bad. I always thought, that the 3d stuff is a bit unstable on my unit where others don't have problems.


Edit: Notaz, if it would be helpful, I can throw anything you give me at this I was never able to play pewpew2 for more than 4-5 levels without this behaviour.

 

[mcobit]

Ok, I now set the clockspeed down, like notaz told here. to 150. I played and the as expected, the framerate was lower, but I was able to play for 30 mins without a single lockup. There are still HW recoveries, but they never seem to fail and are not as many as before. The whole game seems to run smoother, but slower.


Is it possible, that some sgx chips already have problems with the normal 110mhz clock?

 

[huniper]

Ok, I now set the clockspeed down, like notaz told here. http://boards.openpa...gx/#entry161701 to 150. I played and the as expected, the framerate was lower, but I was able to play for 30 mins without a single lockup. There are still HW recoveries, but they never seem to fail and are not as many as before. The whole game seems to run smoother, but slower.


Is it possible, that some sgx chips already have problems with the normal 110mhz clock?

Wow good find!

Currently there is a "safe" way to under/overclock it by changing system (L3) clock in latest firmwares:

sudo /usr/pandora/scripts/op_sysspeed.sh X

where X can be any value like:


332 -> 166MHz RAM, 110MHz SGX (default)


300 -> 150MHz RAM, 100MHz SGX


...


DM3730 has this set at 400 for 200MHz for both RAM and SGX (using a new divider 2 that's not in OMAP3). OMAP3 works at this setting too (SGX ends up at 133MHz because 3 is the lowest divider there) but is not stable.


As for changing SGX divider, you have to modify the driver because it overrides the divider before turning on the chip each time.

Have you tried changing it to 300? Then the SGX would only run 10MHz slower than stock. Maybe that would be enough to ensure stability without losing much framerate.

 

[mcobit]

Well, I still got hangups with 200. Also in IRC sebt3 said, that he had his first lockup when he downclocked the sgx. So maybe this will lead to nothing in the end...

 

[gruso]

Thanks Jyaif and sebt3 for this. Really dig it. I haven't experienced any lockups. Relevant info:

• Playing 5-10min sessions
  
• Silver Rebirth Pandora
  
• SZbeta5 (not 5a)
  
• Still running the first PewPew release (didn't get around to updating it yet)
  

Two issues I did have:

• Severe framerate drop when the first segmented snake things appear
  
• Managed to flip the screen upside down when finger scrolling vertically (through options menu IIRC). Couldn't undo or reproduce. Clearing appdata fixed it.
  

 

[Magic Sam]

Hi,

• Severe framerate drop when the first segmented snake things appear
  

Same thing here, on a "classic" Pandora though...


Bye, Magic Sam

 

[Askarus]

Freeze, Freeze, Freeze.


I never had a game with so mich freezes.


Last freeze deleted my scores.


Please fix this.


The game is great.

 

[Neelix]

The screen orientation is an option on the settings screen, which can be reached by hitting esc unil you get to the main menu then choosing settings... I tried playing with it upside down, but as the contols are not also inverted it becomes somewhat more challenging than I was willing to deal with so I changed it back pretty quickly.


Is there any chance of unpausing on nub movement? As the game is designed for touchscreen control the pause function kicks in if you stop touching the screen with the messge 'resume playing to unpause' and tapping the screen again only unpauses until you stop touching it. I discovered it is possible to unpause with an action buton, but given the message, being able to unpause with the nubs would be ideal.


I have not had any further lockups in the new version myself.. (except for once because I forgot to disable synergy and accidently moved the mouse cursor on and off the screen. no sgx errors for that one though)


@Askarus Which build of pewpew2 are you using and which OS version?


- Neelix

 

[Askarus]

@Askarus Which build of pewpew2 are you using and which OS version?

I'm using PewPwe 1.0.0.3


Os: SuperZaxxon Beta 5a

 

[Neelix]

Hrm.... same version and OS as me... but I can no longer reproduce the issue and I don't understand why...


Is there any program or game you typically run/play before playing pewpew2? have you tried playing pewpew2 on a fresh boot?


- Neelix

 

[Askarus]

I've redownloaded the PND once again.


My scores are gone so I'll also delete my appdata folder.


After Univesity I'll try it again (with a reboot before).

s there any program or game you typically run/play before playing pewpew2

Nothing I can remember.


More info tomorrow.

 

[pmprog]

Not sure if this will make a difference - but are you running from XFCE, or the MiniMenu?


Edit:


Out of curiosity, how come there's no glow in this? Is it just to save on processing time? Only because rRootage has glow on the Pandora, but interestingly didn't when I ran the PC version.

 

[milkshake]

as far as I can see from official videos of pewpew2 running on different devices on youtube pewpew2 doesnt have the glow but pewpew one does.

 

[pmprog]

as far as I can see from official videos of pewpew2 running on different devices on youtube pewpew2 doesnt have the glow but pewpew one does.

Ah, was I looking at the wrong screenies/vids? I just remember following the original link and seeing glow, then not seeing any in the game.

 

[sepp256]

I'm using the latest PewPew2 from the repo (1.0.0.3) and I noticed that the game/system locks up when you press ESC after playing for a little while and I need to do a hard reset.


I went back and tested some more, and ESC works when I'm in the PewPew menu before starting a game. Right after I start a game, ESC brings up the in-game menu. After bringing up the in-game menu a couple times, the background music stopped. The next time I pressed ESC, the system locked.


I'm using a 256MB Pandora on SZb5a and launching through XFCE. Also, I'm using the default clock of 500MHz.


Btw, except for the described lock-ups, this game is awesome on Pandora!