[Q] FPSE and N64oid?

[Zzim]

Has anyone here been able to set these up so they run smooth? N64oid has major slowdowns in Zelda and other resource intensive games. I am on HD reveloution where software rendering is disabled so its using the full PowerVR GPU. The Nexus has specs similar to the Galaxy S II and should not perform as slow as it is now.

Also in FPSE the analog sticks dont work and are not centered where you put you finger on the screen. Any ideas?


Also why does using the Microboes or bubbles live background lag the UI soooooo much.

 

[Stadsport]

I haven't used FPSE, but I've used n64oid quite a bit over the last few days. It's not 60fps but it's playable, depending on the game. That's not to say it's without bugs...
-Most games seem to randomly experience extreme slowdown and 3+ second hangs. This makes MarioKart and Starfox virtually unplayable at times.
-Sometimes it will sometimes completely freeze at these points of extreme slowdown, to the point where the game needs to be reset. This has gotten me into the habit of saving states FREQUENTLY.
-In Zelda OoT, the camera doesn't move at all in the courtyard of Hyrule castle, so you're effectively stuck at that point, since you can't see where you're going as soon as you walk off-screen. Obviously this isn't specific to the Gnex, but it's worth mentioning for the dev's information

I'm using a bone stock LTE 4.0.2 Galaxy Nexus.

 

[Zzim]

I haven't used FPSE, but I've used n64oid quite a bit over the last few days. It's not 60fps but it's playable, depending on the game. That's not to say it's without bugs...
-Most games seem to randomly experience extreme slowdown and 3+ second hangs. This makes MarioKart and Starfox virtually unplayable at times.
-Sometimes it will sometimes completely freeze at these points of extreme slowdown, to the point where the game needs to be reset. This has gotten me into the habit of saving states FREQUENTLY.
-In Zelda OoT, the camera doesn't move at all in the courtyard of Hyrule castle, so you're effectively stuck at that point, since you can't see where you're going as soon as you walk off-screen. Obviously this isn't specific to the Gnex, but it's worth mentioning for the dev's information

I'm using a bone stock LTE 4.0.2 Galaxy Nexus.

Under the development options in android see if there is a "Force GPU rendering" option and if there is check it and let me know if there are any changes.

I notices if you disable fog and stretch to fix screen on N64oid you see a HUGE performance increase.

Im hoping the dev for FPSE fixes the analog issues soon.

 

[thirtynation]

Like others, it seems to depend on the game. Metal Gear Solid is virtually unplayable on psx4droid, and doesn't even load on FSpe. Intelligent Qube works fine on FPse but doesn't load on psx4droid. As for N64oid, MarioKart actually works fine for me outside of a few audio skips here and there, it's pretty responsive. F-Zero X works flawlessly.

One thing I find troubling though is that when I hook up the MHL to HDMI adapter games that once played fine take a noticeable hit in performance. MarioKart becomes unplayable once I hook up the adapter. Does anyone know if the adapter demands more resources (GPU/CPU/RAM/etc)? I would imagine it does since the phone doubles the output instead of redirects it (phone display and MicroUSB out) but I also am not technical enough to really know how this stuff works. It's crummy, cuz playing the N64 and PSX emulators on my projector with a PS3 dual shock controller was one of the major things I was looking forward to with this phone. I see videos on youtube of people doing this on their GSII and it works fine. What gives? Is it ICS?

 

[dwang]

No its because the gn is pushing 2.4x more pixels than the gs2 and a less powerful gpu.

1280x720 vs 800x480

 

[b15love]

No its because the gn is pushing 2.4x more pixels than the gs2 and a less powerful gpu.

1280x720 vs 800x480

That has yet to be fully determined. Some ppl hv smoother frame rates than other on the same game but different rom. Though it could be software and hardware related. We need to reach out to the dev (yongzh) and let him know

 

[Stadsport]

Under the development options in android see if there is a "Force GPU rendering" option and if there is check it and let me know if there are any changes.

I notices if you disable fog and stretch to fix screen on N64oid you see a HUGE performance increase.

Im hoping the dev for FPSE fixes the analog issues soon.

Forcing GPU didn't seem to make a difference, and actually seemed to crash some emulators. I've kept stretch off because N64 games aren't widescreen, and toggle fog made a VERY slight difference.

 

[b15love]

Mupen64Plus seems to be running a tad faster than n64oid. just set autoframe skip and max frame skip to 5. BUT the on screen controls keep disappearing and are rather tiny.

 

[Stadsport]

Mupen64Plus seems to be running a tad faster than n64oid. just set autoframe skip and max frame skip to 5. BUT the on screen controls keep disappearing and are rather tiny.

You're right, it's definitely running faster than n64oid. But the disappearing controls are obnoxious, and I think the emulator itself needs a little bit of polish. For example, if you lock the screen and wake it back up, it closes the emulator completely. Same if you get a call or something.

 

[@rbiter]

Has fpse implemented sixaxis controller app yet? Or using sixaxis or usb contoller period?

Crazy world, ay?

 

[thirtynation]

I've been using PS3 dualshock via sixaxis for FPse just fine since I've had the phone. Just have to map it out in the settings.

 

[@rbiter]

I've been using PS3 dualshock via sixaxis for FPse just fine since I've had the phone. Just have to map it out in the settings.

Ok. I tried recently and it did not work completely. Any suggestions where i might've messed up?

Crazy world, ay?

 

[thirtynation]

Use the free sixaxis pairing app to assign the bluetooth address of your phone to the controller (requires hooking your controller up to your computer with a usb cable). Once you've done that, use the paid sixaxis app to actually pair the controller to the phone via bluetooth. Then, within FPse go into settings, input, hardware keys, and just map the buttons. I know you've probably done some of the beginning of that already, but I'm not really sure where you're having problems.