Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - scorpio16v

Pages: 1 [2] 3 4 ... 11
Miscellaneous / Re: NullDCe apk
« on: December 18, 2013, 11:56:10 AM »
@ stodag

You must create /dc/data yourself and put the correct renamed files in it.

<a href="" target="_blank" class="new_win"></a>

The gamepad layout isn't optimal and I haven't figured out how to map gamepad buttons to the emulator's button layout.
But it runs amazingly good with clear sound.  :)

General Discussion / Re: Major fixes to gles2rice plugin
« on: November 03, 2013, 06:17:59 AM »

fog enabled:

fog disabled:

You can see that the fog gives the background a banding look.

Same result on my N7 (2013)

Semms a common problem of Snapdragon GPUs.

General Discussion / Re: 2.3.0 Release Candidates
« on: May 22, 2013, 11:03:27 AM »
Yes, it's definitely worth to release.
Speed on Nexus 4 is OK now. Glide fixed many things in MM 2 (flickering background), Shadowman (lights are shining through walls), Conkers BDF (gras did appear as blocks).

Other thing that should have priority in development should be to fix the junk graphics in Rice, because many graphics are broken that have worked since month.

One example in this thread:

Dont know if it needfull for other games, but the menue option "fast texture loading" for Rice seems not necessary anymore. That option fixed the spot in Conkers BFD intro (was shown as square ). But the graphics are fine on the latest builds, even if the option is deactivated.

On Pilot Wings, the messed graphics didn't only affect the border, even the main screen is messed up.

That picture is from Playstore version on Nexus 4.

On my Onda v812, the bug looks different.

Support / Re: HTC one FPS
« on: May 20, 2013, 11:35:03 PM »
Can confirm, the no-wait-test fixed the lag on Nexus 4 completely. I've used my same test configuration from my last test run and both devices are running in sync.  :)

Support / Re: HTC one FPS
« on: May 20, 2013, 02:45:37 PM »
Both tests don't bring realy better results.
Same config, like in my previous posted video. Plugin was rice now. Other settings are default, only framecounter and stretch screen added.
If I run the intro of smash bros. till the point where the start screen appeares, the difference  to my tablet as reference are ~15 seconds.
On the old video with glide plugin the difference was nearly 20 seconds that the Nexus 4 performes the test.

Support / Re: HTC one FPS
« on: May 20, 2013, 12:34:30 AM »
OC the device doesn't bring better performance on my Adreno 320 powered Nexus 4.
The N4 is clocked to max/min 1512 MHz / governor "performance".
The other device is my Onda v812 clocked to max/min 1200 MHz / governor "performance".
MP64+ae version is the latest test build with glide plugin. Benchmarked the intro sequence from "Super Smash Brothers".

The device runs with stock kernel, so I can't test GPU OC.

General Discussion / Re: New Cheat Feature
« on: May 18, 2013, 01:42:51 PM »
Sorry that I bring these old thread up again.

On Daedalus, there is a cheat.config that fixed the wrong shadows on Pilot Wings that are visible on mupen64+ae, if we are using gles2n64 or glesglide64.

As I understand the config patched some values of the ROM with another value. Is it possible that we can use these cheats in our cheat.config to fix these problems ?

Daedalus.cht in the attachment:

General Discussion / Re: Glide64 Bias Factor Test
« on: April 22, 2013, 09:02:03 AM »
Yes, the config file bring a solution for the flickering on PowerVR.

n64_z_scale = 1 reduced the flickering to a minimum.

But I'm still searching a good value. Carpet is nearly stable, shadows too. But the Carpet and the frame at the castle's entrance are still flickering. In the castle the stars at the doors disappear  sometimes.

General Discussion / Re: Glide64 Bias Factor Test
« on: April 20, 2013, 01:26:06 PM »
I don't know if the logcats containing any helpful output for you.
But just in case.

General Discussion / Re: Glide64 Bias Factor Test
« on: April 20, 2013, 12:56:02 PM »
I'm using the carpet in the entrance hall of the castle in SM64 for my tests.
On my other devices, I can see a difference and Mario appeared over or under the carpet if I change the values. But not on PowerVR.

Shadow and carpet are always flickering like in the attached picture.

General Discussion / Re: Glide64 Bias Factor Test
« on: April 20, 2013, 12:08:27 PM »
Does disabling the input plugin have any affect?

No, I've disabled touchscreen and controller, but the sound stutters sometimes if graphic activities are increased.
That doesn't happen on the other plugins, even without frameskip.

Try 1000 or -1000 and work down from there for PowerVR.

Yes, but if I should try all values, including 3 digits after comma, that'll be a 24/7 job  :-\
The problem is, that low and high values mostly don't produce (visibly) changes. So it's nearly impossible to track down the search area to a small sector.

General Discussion / Re: Glide64 Bias Factor Test
« on: April 20, 2013, 09:37:38 AM »
Acer A511: GL Renderer " NVIDIA TEGRA 3 " - Bias Factor: 0.2
Nexus 4: GL Renderer " Adreno (TM) 320 " - Bias Factor: 0.007
Onda v812: GL Renderer " PowerVR SXG 544MP " - Bias Factor: ????

Can't find a good setting for PowerVR.  :(

Besides this, interestingly the hardware with the worst performance (stuttering sound and sometimes graphics) is the Nexus 4 with the most powerful hardware.  :o

General Discussion / Re: Glide GL ES 2.0 Port (WIP)
« on: April 03, 2013, 09:01:41 PM »
Some remark about the black screen on N4. It doesn't seem related to the plugin.
If I switch the volume buttons up or down and the loudness bar is faded onscreen, the graphics are visible.

General Discussion / Re: Glide GL ES 2.0 Port (WIP)
« on: April 02, 2013, 11:44:23 PM »
Test on Super Mario 64:
On my tablet with A31 CPU, graphics are messed like in the old version.
On Nexus 4, I can see only only the "Super Mario64" screen for a second. After that, the screen is black again.
If I go back to menu, the graphics is shown for a second. Same as the first test, but the graphic looks fine now.
If you can solve the black screen issue, maybe that could be the right setting for this hardware.

Pages: 1 [2] 3 4 ... 11