Hans♫

Thank you so much 👍 We have successfully incorporated your new solution in our project (we use our own build script). It has also been tested on Play Store and that works too!

It might be a simple task for some, but at least not for me 🙂 First step of the switch is to create a Delphi interface to the new jar, and next step is to make the code work with that interface and jar. With the current solution we used the interface to play-core-1.10.0.jar, that you created and supplied in your Kastri example project. I made a quick attempt to do the same myself for asset-delivery-2.2.2.jar, using Java2OP.exe and the instructions supplied by Embarcadero - but unsuccessful. I believe this is just the first problem, out of many, to complete this switch of jar's. Probably because I have no idea what I am doing... So I won't list the error messages here to start a problem solving session. I think it is more beneficial for the Delphi community if its solved by a competent person and shared with the community - and I'll be pleased to pay for the work, even if its shared.

With the new API 34, it looks like the solution we made for install time assets, based on the Kastri example, no longer works. When installing the resulting .aab on a device (Google Pixel8) running Android 14 it throws an security exception and the Install Time asset isn't loaded: java.long.SecurityException: com.<applicationname>.android: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts As far as I see, the problem is the play-core-1.10.0.jar (February 2021) is no longer accepted. And we need to migrate to the new Play libraries (since April 2022) https://developer.android.com/reference/com/google/android/play/core/release-notes Specifically the Play Asset Delivery Library - Latest update 2.2.2 (May 2024) https://developer.android.com/reference/com/google/android/play/core/release-notes-asset_delivery Anyone having experienced the same?

@vfbb Any update on this issue? - Maybe a bug should be filed in the QP?

Yes, I can reproduce this in a blank project. You did not see it because you used gray in gray. When using white on black, then you can see it: <No Skia | Skia + Vulkan > Enlarged: <No Skia | Skia + Vulkan > This is produced with an empty app with only this code: GlobalUseSkia := true; GlobalUseSkiaRasterWhenAvailable := false; GlobalUseVulkan := true; ... procedure TForm1.PaintBox1Paint(Sender: TObject; Canvas: TCanvas); var lStroke: TStrokeBrush; lPath: TPathData; begin lStroke := TStrokeBrush.Create(TBrushKind.Solid, claWhite); lStroke.Thickness := 1.5; lPath := TPathData.Create; lPath.AddEllipse(RectF(-12, -12, 12, 12)); lPath.Translate(50,50); Canvas.Fill.Color := claBlack; Canvas.FillRect(RectF(0,0,100,100), 0, 0, [], 1); Canvas.DrawPath(lPath, 1, lStroke); lStroke.Free; lPath.Free; end;

Its a path. Our code looks like this (simplified): fStroke := TStrokeBrush.Create(TBrushKind.Solid, claSilver); fStroke.Thickness := 1.5; fPath := TPathData.Create; fPath.AddEllipse(RectF(-12, -12, 12, 12)); ... Canvas.DrawPath(fPath, 1, fStroke);

Thank you. We had the Form.Quality set to SystemDefault, which seem to do the same as setting it to HighQuality. I tried to set it to HighQuality, but did not see any difference. However, I just found out that with Skia+Vulkan, it actually draws with anti-aliasing, but in a very simple way. Here is our back button. The version to the left is with no Skia. To the right it is with Skia + Vulkan: <No skia | Skia+Vulkan> I though the Skia+Vulkan version was not anti-aliased, but when enlarging, I can see that it is: The quality of the anti-aliasing is simply lower with Skia+Vulkan (and the forms quality is set to high quality). Is there a way to change that?

Yes, it looks the same both with and without Vulkan: no anti-aliasing.

Enabling Vulkan requires to uncheck SkiaRaster, according to the description. We are seeing a performance improvement and it runs pretty smooth when unchecking the SkiaRaster. If there is an additional performance improvement by enabling Vulkan, it is not clearly visible, so I'll need to measure the frame rate to find. However, unchecking SkiaRaster also disables anti-alias when drawing a path, so it is not currently an option. Maybe that could be solved somehow by accessing the Skia Canvas?

Yes, we have both Intel macs and Apple Silicon macs at the office, but we currently build only for Intel and rely on the Rosetta 2 emulator. Both Intel and Silicon work "fine" when enabling Metal. However, we have not measured the framerate on animations or the painting speed, so here "fine" means that its high enough to not attract attention.

Thank you. Interesting where the bottleneck is? BTW, we are not using the Skia Canvas (ISkCanvas), but as I understand the description, it is only needed to unlock more features, not to increase speed? For now we can simply turn off Skia on Windows, and use it only on MacOS, Android and iOS. But as soon as we begin to implement SKIA specific functionality, it becomes more difficult to maintain, if we have to support non-Skia too.

No, unfortunately a simple app does not have this problem. And as a side-note, thinking about your question: Asking "general" questions like I did is of course a tradeoff: When have I tried enough to ask? I am sure I would be able to solve the problem on my own, but I also know that it could easily take a day, a week or even a month to solve. Sometimes just to find out that the solution was simple, but locating it was complex. Sometimes others have been through the same and discovered something that might not be obvious. I admit that I asked my question early in the process, long before having tried all options. But that was with a hope that someone else have been through this and have some useful information 🙂

We have tried it on several PCs and laptops here at the office. Both new and old computers (and graphics cards), and both with 32 bit and 64 bit builds of our application. The result is the same everywhere. With Skia, the framerate is 2-4 fps, and without Skia the framerate is not visible, which I guess means 20+ fps. PS. But if you want to know, I personally use a 12 years old AMD Radeon 6670, which is fast enough to run Delphi 🙂

Having Skia on MacOS is a great improvement because it allows us to enable Metal without losing rendering quality. However, on Windows we experience slow rendering with Skia. We use Delphi 12.1 Patch 1, with our FMX based app. A full screen slide-in animation of a TFrame on top of the main form is smooth with GlobalUseSkia=false. When setting GlobalUseSkia=true, the framerate of the animation goes down to around 2-4 fps. This is with GlobalUseSkiaRasterWhenAvailable=true. Setting GlobalUseSkiaRasterWhenAvailable=false, then the framerate doubles, but then vector graphics is no longer antialiased. We have not changed any components or code in paint routines, but maybe we should? Any idea what goes wrong?