292.3 Screenshot bug on android

I would like to call this the elusive bug screenshot bug.
It took me a long time to figure what is going on here.

Lets go.

Bug description

In the latest 292.2 and 292.3 builds of CTF if you place an active x object that has an image that contains semi transparent pixels on a frame with a Pure white color (255,255,255) or variations of this RGB value except of shades of gray and you use the Android's object screenshot function you get distorted output screenshots in the area of the active x object's semi transparent pixels .

Facts
A. Bug first appeared in 292.2 and 292.3
B. My test device is a Xiaomi A2 lite ( Global Version ) running android 9.0 pie
C. My BUILD api is 28 as seen on the .mfa examples
D. I have created three .mfa files to showcase the different aspects of this bug
E. The ONLY difference inside the 3 .mfa files is the Background color of the frame
F. .mfa V1 has a Background color of pure white (255,255,255)
In this case the output screenshot of my phone displays black circles
The black circles are regions of the anchor image that contain semi transparent pixel info with an alpha channel different than 0(completely transparent) or 255( not transparent)
G. mfa V2 has a background color of (250,255,255)
the output image of the apk file tested on phone (version v2 apk) displays PURE RED instead of pure black circles
H. mfa file has a background color of tone of gray (250,250,250) and doesnt NOT exhibit the buged behaviour of the previous 2 versions.


Here is the link to the 3 mfa example , 3 apk files build from the mfa files and tested on my phone, and 3 screenshots one for each apk file output.

https://ufile.io/vwlac

Thanks i will check them tomorrow

Οκ thanks Fernando , the screenshot function is extremely important to me for my app

mm listen I have been working on this, but I don't see the issue in my code what I see is that your image if I do open and save again as png and set white as background it works ok

Attachment 26599

notice that this meteor have a black as transparent object and is OK when is captured even though is not pure and you see teh artifact around it.

after "modify" your, just open and save again as png but selecting which color to be transparent

Attachment 26600
I will investigate what could it be affecting this and why it reads the transparency value in your original images


Attachment 26601
================================================== ===========================


found something that may cause this and build new libs and test seems OK now, please let me know if you are using 292.4 and want to test the runtime changes

Sorry talk too fast further test give me wrong again

I will test with 292.5 asap

The problem is also present in 292.5 , no difference
Tested some minutes ago

oh i haven changed as mentioned in my post, first test seems to be working but after few more it didn't, so I did not put them in this version, you still need to review your transparency in your images.

What should i do to review the transparency in the images ? I tried to reinsert the image in the active object and selected white as transparent color but it didnt solve the issue ,
Can you tell me the step to review the transparency in the images ?

Also will 292.6 include some sort of fix for this ?

1.- open your images with an image editor of your preference pain, photo impact and check the transparency color, the resave as png and see if this fix

2.- not sure if I can find something for this specific, I need to do some more try with different approach and see

But there is no trasparency color ,its alpha channel and i need this alpha channel in the image ,i cant remove it because i need it as collision mask

Fernando i need a way to downgrade to 292.2 to steam ,i cannot update my playstore app due to this bug all this time , please how do i downgrade

sorry but this error should be at this version too?, are you sure this error does not happens in this version?

weird is teh same lib as you use there

On the version without the gradle maybe its 291.6

Can i downgrade today on steam ?
I forgot which is the last version that doesnt have gradle , i think it was 291.6
The screenshot bug was immediately with the gradle update

sorry in steam you can not downgrade

I will send you a PM with some step to follow

ok i will be online for the next few hours here in the forum and wait

From what I've noticed, it is possible to manually downgrade Clickteam Fusion (even on Steam), as long as you keep a backup of the old Clickteam Fusion folder on your hard drive, so that you can copy it over the new one when the need arises. I suggest making a backup copy of 291.6 after you downgrade it this time, so you can downgrade any time you want, without having to do any extra steps. It's also generally a good idea to make backups of every major update that is stable for you, because you never know when you might need it.

this is valid until steam execute its verification then all files will be replaced though

@MagicForest

today discussing this issue something came to my mind and I will like you to test there and let me know, please make the anchor 512x512 with the same alpha channel for collision you need and test taking a screenshot let me know your results, using opengl 2.0 and 3.0

Ok i will make the test tomorrow because today i am not in my office with the pc

Fernando i made the test
Results :

Resized image to 512x512
CTF version 292.6 running on gradle
Build api 28
Target api 9.0
Test phone : Xiaomi A2 lite ( OS android 9)

OpenGl ES 3 = Bug
OpenGl ES 2 = Bug
OpenGl ES 1.1 = NO bug

Fernando do you have any progress on this ?

Also Fernando is there a way to contact you via skype or through by telephone ? I need to ask you some stuff

you may use discord to contact me, there are several fusion channels

regarding this , no progress sorry, need to find a way so far no luck

Fernando are you still working on this ? If you cant fix it please let me know so that i plan ahead with the future of my app

no i did not found any other way to make it work, sorry.

then that means that i just wont be able to update my app anymore to the new apis...

Thisbug is fixed on 292.8

Yes this was fix in this beta (292.8), I manage to install android pie in one of my old nexus 7 for testing, please test and let me know if you find any other issue.

Fernando there are 2 new bugs for the string object when ran on android phone only
https://community.clickteam.com/threads/105853-292-8-most-likely-a-bug