Beta release version 2.5.2.0a

Discuss anything about DraStic here.
Exophase
Posts: 1714
Joined: Mon Aug 05, 2013 9:08 pm

Beta release version 2.5.2.0a

Post by Exophase » Tue Nov 26, 2019 2:42 am

Hi everyone,

I've pushed a beta release for version 2.5.2.0a. I'd like for it to undergo at least some amount of testing on different 32-bit and 64-bit devices before pushing it to production.

The main update is 64-bit support (AArch64 and x86-64), which was a requirement for any updates as of August. There is support for 64-bit ARM (AArch64) and 64-bit x86 (x86-64). Most of the performance should be of similar quality as their respective 32-bit versions, with a few edge cases where 64-bit is slightly slower and some others were it's slightly faster.

Full changelog is as follows:

Code: Select all

Android 10 support
Support for AArch64 and x86-64
Controller rumble support (only wired XBox controllers known working)
Per-game Slot2 pack option
Slot2 Motion Pack emulation (official + homebrew types)
Fix DQ5 incorrect detection as encrypted
Fix loading 7-zip archives to RAM
Add option to preload unzipped ROMs to RAM for devices w/enough RAM
Framerate Stabilizer setting to improve performance on devices with poor big.LITTLE CPU schedulers (set per-game as needed)
Various bugfixes
Please feel free to post in this thread or on the Discord if you encounter any issues, including any notable performance regressions or new compatibility problems, especially on 64-bit platforms. We've tested it fairly extensively internally but as this was a pretty massive coding overhaul there are probably things that have been missed.

I should have some time to work on fixes as necessary during the Thanksgiving weekend and the second half of December. I'd like to have the production release out before the end of the year, and xperia64 and I plan on moving to open source sometime in the first quarter of next year. Also expect updates for Linux and Windows PC builds at some point.

EDIT: Updated beta to revision 102:

Code: Select all

Fix for 16-bit rendering mode in ARM64 and x86/x86-64
Fixed fog glitches in ARM64
Dropped API target for now to get around scoped storage issues on Android Q
Some fixes regarding crashes/hangs on some devices

juju007007
Posts: 6
Joined: Tue Apr 07, 2015 11:22 am

Re: Beta release version 2.5.2.0a

Post by juju007007 » Tue Nov 26, 2019 11:47 am

There is an issue in Pokemon black 2 coloring when using 16-bit renderer some colors are swapped now (Pocophone F1@Snapdragon845)

Image
Image

Moneyrain
Posts: 3
Joined: Tue Nov 26, 2019 7:16 pm

Re: Beta release version 2.5.2.0a

Post by Moneyrain » Tue Nov 26, 2019 7:23 pm

After this update, dratic cant not load any game on my phone, keep the loading game persist for long tỉme. I use note 10 plus exynos android 10

Fefo
Posts: 257
Joined: Sat Oct 26, 2013 8:59 pm

Re: Beta release version 2.5.2.0a

Post by Fefo » Tue Nov 26, 2019 7:41 pm

The 16-bit issue is widespread from my tests.

---

Tried a few games quickly and found no issues at all, maybe a little shimmering I didn't notice before but I can't be sure without comparing. Performance on Pokemon Black 2 and Dragon Quest IX is slightly improved, about 10-20% faster unthrottled.

Game swapping feels jerkier than before; twice it kicked me back to the launch screen and it force closed once.

I'll play more extensively tomorrow and report any change i notice.
BE ATTITUDE FOR ENGRISH

Moneyrain
Posts: 3
Joined: Tue Nov 26, 2019 7:16 pm

Re: Beta release version 2.5.2.0a

Post by Moneyrain » Tue Nov 26, 2019 8:55 pm

I reinstall drastic nd get this mesage, dratic close after it

xperia64
Posts: 221
Joined: Fri Feb 28, 2014 7:41 pm

Re: Beta release version 2.5.2.0a

Post by xperia64 » Tue Nov 26, 2019 10:05 pm

Fefo wrote:
Tue Nov 26, 2019 7:41 pm
The 16-bit issue is widespread from my tests.

---

Tried a few games quickly and found no issues at all, maybe a little shimmering I didn't notice before but I can't be sure without comparing. Performance on Pokemon Black 2 and Dragon Quest IX is slightly improved, about 10-20% faster unthrottled.

Game swapping feels jerkier than before; twice it kicked me back to the launch screen and it force closed once.

I'll play more extensively tomorrow and report any change i notice.
Yeah, the 16-bit issue is a pretty easy fix.

The menu/game selection/Android Lifecycle stuff is tricky. I was able to replicate it once or twice yesterday, but now I just can't.

Jay Haru
Posts: 1796
Joined: Sat Aug 10, 2013 1:10 pm
Location: Pasig, Philippines

Re: Beta release version 2.5.2.0a

Post by Jay Haru » Wed Nov 27, 2019 12:52 am

from the way i see it, it just looks like everyone in pokemon is having an urge to puke...
Behold my mighty
Image

Exophase
Posts: 1714
Joined: Mon Aug 05, 2013 9:08 pm

Re: Beta release version 2.5.2.0a

Post by Exophase » Wed Nov 27, 2019 12:53 am

Moneyrain wrote:
Tue Nov 26, 2019 7:23 pm
After this update, dratic cant not load any game on my phone, keep the loading game persist for long tỉme. I use note 10 plus exynos android 10
Have you tried rebooting?

Moneyrain
Posts: 3
Joined: Tue Nov 26, 2019 7:16 pm

Re: Beta release version 2.5.2.0a

Post by Moneyrain » Wed Nov 27, 2019 2:27 am

i rebootwd a few time, but i think it a problem that dratic dont have permission of writing to internal memory ( because of changing in api?).
https://photos.app.goo.gl/7y9EUB47sVrFieZg6

xperia64
Posts: 221
Joined: Fri Feb 28, 2014 7:41 pm

Re: Beta release version 2.5.2.0a

Post by xperia64 » Wed Nov 27, 2019 9:57 am

Moneyrain wrote:
Wed Nov 27, 2019 2:27 am
i rebootwd a few time, but i think it a problem that dratic dont have permission of writing to internal memory ( because of changing in api?).
https://photos.app.goo.gl/7y9EUB47sVrFieZg6
Yeah, ok.

Google didn't make this moronic API change very noticeable or label it as breaking or anything from the Android Q changes page: https://developer.android.com/reference ... AL_STORAGE
In the past, these things have been labeled in changelogs explicitly as security changes, not casually as:

Code: Select all

In addition to introducing scoped storage
Also this:

Code: Select all

If you're aware of a specific location where files should be stored, you can provide the system a hint for where to store the newly-written files.
Excuse me? When I want to write a file, I don't consider it a suggestion where it should be written. Killing the concept of a filesystem is the death of Android.

Maybe star this issue if anyone cares to try to get Google to look at it: https://issuetracker.google.com/issues/128591846
But they don't care. Every real app is a basic image viewer or basic mp3 viewer. Or a pay2win game that doesn't even care about files.

But given what happened here I'm not hopeful:
https://issuetracker.google.com/issues/77406791
https://issuetracker.google.com/issues/144182682

The amount of incompetence and/or politics around file i/o on Android is staggering. With the above issues it's clear Google doesn't understand how anyone would ever consider using a file that isn't an MP3 or JPG.

I'm seriously looking at the Librem 5 now.

Rant over.

Post Reply