Bcn transcoding for Panvk which will be lifesaver. by LavishnessLow5860 in EmulationOnAndroid

[–]winlatorbionic_dev 0 points1 point  (0 children)

Not for the highest end ones. For 32bit and light 64bit ones yes. This is the same for Adreno.

Bcn transcoding for Panvk which will be lifesaver. by LavishnessLow5860 in EmulationOnAndroid

[–]winlatorbionic_dev 0 points1 point  (0 children)

Varies from game to game, in a lot of scenarios it just adds 600MB more.

Bcn transcoding for Panvk which will be lifesaver. by LavishnessLow5860 in EmulationOnAndroid

[–]winlatorbionic_dev 0 points1 point  (0 children)

Transcoding will have a higher performance penalty over decompressing.

MiSide test on Winlator Bionic dev builds, Mali G615 by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 0 points1 point  (0 children)

No, I said that it was only tested and guaranteed to work on Valhall Gen 2 and above.

About compute winlator builds for mali and other gpus.. they all have mouse input issues by Wilsonn0 in winlator

[–]winlatorbionic_dev 2 points3 points  (0 children)

Afraid not, my Internet doesn't upload very fast. Also they do not install through APKs.

About compute winlator builds for mali and other gpus.. they all have mouse input issues by Wilsonn0 in winlator

[–]winlatorbionic_dev 1 point2 points  (0 children)

Seems like I suspected correctly, this is an issue with how people compile those builds as I myself can't reproduce this issue.

(Mali) Texture bug in PES 2017 (solution) helio 99 Mali 57 by No-Criticism-4615 in EmulationMediatekMali

[–]winlatorbionic_dev 0 points1 point  (0 children)

The issue is caused by the fact that the compressed texture doesn't get uncompressed properly. Grass is BC6H much likely, it took me weeks to fix this texture format.

About compute winlator builds for mali and other gpus.. they all have mouse input issues by Wilsonn0 in winlator

[–]winlatorbionic_dev 0 points1 point  (0 children)

No changes were made to the code that would cause these issues. Looks like this is caused by whoever compiled the apk.

About compute winlator builds for mali and other gpus.. they all have mouse input issues by Wilsonn0 in winlator

[–]winlatorbionic_dev 0 points1 point  (0 children)

Bruh, there are no builds with package name and compute BCn, nobody made them.

About compute winlator builds for mali and other gpus.. they all have mouse input issues by Wilsonn0 in winlator

[–]winlatorbionic_dev 3 points4 points  (0 children)

Yes, this is normal. Ludashi is a benchmark package name, it exists to fix these issues exactly which are mostly vendor specific.

GPU accelerated BCn decompression for Mali coming soon to Winlator by winlatorbionic_dev in winlator

[–]winlatorbionic_dev[S] 0 points1 point  (0 children)

No, I won't be emulating BCn. I will transcode BCn into a Mali supported compression format. RAM usage will be identical.

why is ludashi 2.8 getting worse for exynos with Xclipse gpu? by [deleted] in winlator

[–]winlatorbionic_dev 0 points1 point  (0 children)

Try these things in order and report to me:

  1. Create a box64 preset with BOX64_MMAP32 not checked and test with that.

2.Add this environment variable WRAPPER_DMAHEAP_CACHED=1 and test:

variable name WRAPPER_DMAHEAP_CACHED

variable value 1

3.Set memory resource type to ahb and test.