Acamera fx Android Extension

[Gigatron]

Hi, i am glad to share with the fusion community this nice extension, this is Christmas Gift from me

Camera surface is based on the source of nekocode : https://github.com/nekocode/CameraFilter

The shaders in the extension belong to their respective authors.

** Install at your own risk, I am not responsible for any damage caused by this extension to your files or phone or loss of data.**

The mfa example is included.

Installation : Copy Acamerafx.zip to Clickteam Fusion Developer 2.5\Data\Runtime\Android

Copy : Acamerafx.mfx to Clickteam Fusion Developer 2.5\Extensions\Unicode

Running : Open the .mfa file exemple and try to build the .apk , you must have the latest release of Fusion 294.12 and the correct jdk; I use Android studio for jdk , sdk ;

What's missing; Removed face detection ; Instead of using canvas to draw camera surface , it use the camera own surface, this mean all
your Fusion object like sprite are behind the surface camera Exept the viewcontrol object , like button ...
Otherwise it'use more cpu/gpu usage for drawing the camerasurface to Fusion canvas surface this make twice operation instead one;

You can share the picture with your friends or save the picture to image gallery.

Maybe the share picture is not yet correctly rotated with using front camera ....

Camera selection front / back.. filters 0-32 etc...


Thank to VBEinc for testing this extension ;

The next extension is on the way based on HBrecorder library, to record phone screen ......(partially done ) !!

acamfx.jpg

Have fun ;

[VBEinc]

Installation : Copy Acamerafx.zip to Clickteam Fusion Developer 2.5\Data\Runtime\Android

Copy : Acamerafx.mfx to Clickteam Fusion Developer 2.5\Extensions\Unicode

Acamerafx.mfx is not in the zip folder bud.

[Gigatron]

Acamerafx.mfx is not in the zip folder bud.

Sorry , it's ok now ;

[VBEinc]

Sorry , it's ok now ;

This is how it looks, built directly from your .mfa ( Nothing Changed! )
Screenshot_20221224-182600.jpg

[VBEinc]

Also, resizing the Frame and Object does some wonky things.

If you make the Frame 720x1280 and resize the Acamerafx Object.
It makes it different yes. However it does not resize properly with anything we know in Fusion.
Again, the White background is back and does not show the fusion background.
I will take some Screenshots with various sizes.

[Gigatron]

Also, resizing the Frame and Object does some wonky things.

If you make the Frame 720x1280 and resize the Acamerafx Object.
It makes it different yes. However it does not resize properly with anything we know in Fusion.
Again, the White background is back and does not show the fusion background.
I will take some Screenshots with various sizes.

First of all , uninstall all acamerafx apk and then change the package name , like com.vbeince.mycamera
keep the other preferences , like stretch permission etc.. and rebuild an apk.
Have fun , or send me your device )

[VBEinc]

First of all , uninstall all acamerafx apk and then change the package name , like com.vbeince.mycamera
keep the other preferences , like stretch permission etc.. and rebuild an apk.
Have fun , or send me your device )

Okay, not sure if you're trying to be smart.
1) I created an .apk with your .mfa. ( Nothing Changed )
Then I created one with your .mfa and my company name. = SAME RESULTS!

2) Then I tried seeing what the issue was with your object versus Fusion Versus my LG STYLO 5.
Turns out, if you add a Object as a Place Holder for the STRETCH TO FIT SCREEN option.
It kind of works, but the Background is still White, Regardless.
Without the Active Object as a Place Holder. Your object has no effect of the STRETCH TO FIT SCREEN option.
Basically Fusion will stretch to fit, but will not stretch to fit the frame anymore.
I assume the white is supposed to be a Place holder for the resized Camera object and go Transparent but it does not.

3) I also rendered with the 294.12, 294.10 and with 293.10. Same results!
My Android is up to date with Google and so is Kotlin.
Java is also up to date as I have no issues with any other object except.

Acamerafx object ( Works somewhat now! )
STT object ( Doesn't work on Samsung Devices = Doesn't activate Google's Speech To Text! Works on every other device great!)
TTS object ( Paid for, but still doesn't work 100% = Can't switch to French from English then switch back )


Here is my Company Name with the Place Holder Active Object holding the screen to the new size!
Screenshot_20221224-183712.jpg

No need to get cocky, I am simply trying to help from a User's Stand point.
Thanks again for your Hard work. However, like the other objects. There is still issues!
Maybe just focus on one at a time?

As far as removing the original apks. I always do!

[VBEinc]

Only thing I can think of is your Computer you build with has files that I never needed to build Android .APKs or .aab for my apps.
I.E. Some sort of Java or C++ that is not needed for Standard Development of Fusion Based Apps, but is required for your Objects.

Maybe include them or offer a Download link to them, if that is the case.

[Gigatron]

Only thing I can think of is your Computer you build with has files that I never needed to build Android .APKs or .aab for my apps.
I.E. Some sort of Java or C++ that is not needed for Standard Development of Fusion Based Apps, but is required for your Objects.

Maybe include them or offer a Download link to them, if that is the case.

For the C++ files you need visual studio 2019 , only for making menu and preferences. I started here.
https://github.com/ClickteamLLC/windows-edif

STT is working nice on my Samsung s22 and s7 edge i just released the latest version;
For TTS will update the code asap and test it again .. ** Can't switch to French from English then switch back **

Thank you for your contribution testing acamerafx.

Regards

[VBEinc]

For the C++ files you need visual studio 2019 , only for making menu and preferences. I started here.
https://github.com/ClickteamLLC/windows-edif

STT is working nice on my Samsung s22 and s7 edge i just released the latest version;
For TTS will update the code asap and test it again .. ** Can't switch to French from English then switch back **

Thank you for your contribution testing acamerafx.

Regards

You're Welcome.
I will try the new STT only My Samsungs later.

I did notice on the AcameraFX object that in use, changing between front and rear cameras.
The FLIP EFFECT goes outside of the AcameraFX Sized Surface Object on the screen.
Maybe that Flip effect is what is causing the issues on my end? I would assume it is not supposed to go outside of the Framed in Surface Object ( AcameraFX )?

Regardless, you have done what I have been told can not be done! Which, sure I made that little Wonky WEBVIEW2 Object / WEBSITE thing that worked for awhile, but all 3 of these objects are awesome now!
They will be amazing once they work 100%!!!
Obviously, that is if Google doesn't change something for the umpteenth millionth time this month.
Thanks again!