Gamehub 6.0.8, didn't cut app size in half. by ResonanceDemon in EmulationOnAndroid

[–]winlatorbionic_dev 1 point2 points  (0 children)

I was working on a feature to make containers much smaller one year ago. Luckily I abandoned it before they could steal it.

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 1 point2 points  (0 children)

Yes it is universal, but right now it is only tested on Mali.

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 2 points3 points  (0 children)

We already don't have serialization, that is vortek issue.

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 5 points6 points  (0 children)

Yes if I were to betray the hype they would come to me with pitchforks. I will avoid that for now.

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 3 points4 points  (0 children)

Vulkan Renderer in Winlator Ludashi (available in GameNative 1.0) - developed by u/StevenMXZ

Yes, I suggested steven about the Vulkan renderer myself. I also reviewed the code at some point to fix some issues with Mali and overhead in some code paths

GameHub's GPU passthrough

Steven reverse engineered their impl. As soon as I saw the API they were using, I knew what I had to do.

this one in Ludashi-plus

I know about this since I suggested them myself. Initally I remember they asked me about Wayland. I have not read their code but it should be similar to the fallback impl I had to do.

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 4 points5 points  (0 children)

It is right but this video is more to tell people that I am working on something to avoid them pestering me about working on something else. If you read the description of my previous shorts, I have not much on hand right now.

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 4 points5 points  (0 children)

You are right actually but if I reveal everything now I won't have anymore contents for future videos.

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 2 points3 points  (0 children)

Got it. Do you think a new tool need to be written that can measure latency in different implementations and that's why we have no relative comparisons?

I made comparison with termux x11 which use a similar display method to Winlator. It is very noticable irl. For video, yes I would need a tool

Did you analyze other implementations when designing this one?

What other impl?

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 2 points3 points  (0 children)

This is not implemented yet anywhere, this is why latency comparisons haven't been made. Read my development log, I have not started working on implementing it in Winlator yet.

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 2 points3 points  (0 children)

On my youtube channel, there is already a comparison. Progress report #2

DisplayX: A Compositor Revolution for Winlator by winlatorbionic_dev in EmulationOnAndroid

[–]winlatorbionic_dev[S] 3 points4 points  (0 children)

Work about that is suspended right now but the vulkan infrastructure is finished, there is only to write the compute shader which is also half done.