An "Active Picture" is included even when setting: "Don't Include at Build Time" is ticked - this happens whether create a start for the picture is ticked or not.
(I mentioned this setting wasn't working months ago - and was told it works - but at the time I couldn't remember what objects I had the problem with. I've now picked it up again with Active Picture - pretty sure that wasn't the only one...)
This is mainly a windows problem because I can just exclude it from the binary data in Android - although the actual .apk file size increases slightly even when the picture is excluded.
I know of a lot of issues now in the Fusion Runtime / Editor that's been reported but not yet fixed. My problem is when I encounter something I have no idea if it's reported or not and if it's just the way Fusion works or a known bug - and there's not any place I can quickly go check. Is there any chance of posting up a log file somewhere with known issues?
>> I mentioned this setting wasn't working months ago - and was told it works
"Don't include at build time" has been improved in the build 292, it no longer include images and sounds, and now includes the source code of the objects used in those frames on Android (for OBB expansion files).
What do you mean exactly by "an "active picture" is included"? Could you attach a simple example please?
I'll check for the "known issues", I don't think we' can easily build such a list for various reason (lots of issues that were reported in the past either couldn't be easily reproduced, or were not described very precisely, some issues may require 2 pages of description, etc) and the bugbox database is not easily useable. I'll check anyway when I've some time.
PS: if you mean that the picture used in an APO is still in the binary files, then yes it's normal, we need to add options to exclude individual files when you build an OBB file for example. We can't easily do that automatically as pathnames can be (and usually are) built dynamically in events.
Adding new options to handle Android OBB expansion files directly from Fusion (instead of from Fernando's tool) is in our todo list, in theory for the next build (not the immediate next one that is going to be released today or tomorrow to fix last minute issues), it should be easier.
I don't know what OBB mean - sorry, I don't understand your explanation - but this is not only an Android issue.
It's just including a simple Active Picture Object in a Frame. I was testing this to see the impact on my game - so have it all - I just didn't think you'd need it:
From the top: .mfa
Size of .exe with Don't include at Build Time option ticked
Size of .apk with active picture excluded from binary data
Size of .apk with active picture included in binary data
Size of .apk with that frame deleted instead of ticking the block: Don't include at Build Time
Size of .apk with active picture excluded from binary data (or in that case not included in the first place)
ExcludeBuildTime2.exe & ExcludeBuildTime.exe = Active Picture in Frame - Don't include at Build Time ticked - the one option was to create picture at start of frame, the other didn't have that ticked
The size of the .exe with that frame deleted.
The size of the actual active picture - Drawing.jpg on disk.
Also attached .mfa and just random drawing I was using.
OK, I was confused because you mentioned binary data.
OBB is Android expansion files that you have to use when the size of your APK is greater than 100 Mb (you build the full app in a .OBB file, and build a small APK where most frames have the "don't include at build time" option and where you download the OBB file with the Android OBB object).
I see what happens with your example, it's due to the graphic filters (PNG, etc) that are automatically included in applications that use Active Picture objects (or any object that load image files).
Full app => 3511 Kb
Full app with "Don't include at build time" => 3510 Kb (the 1 Kb difference is because the second frame is not included)
Full app without the second frame = 3280 Kb only because it doesn't include the graphic filters
The problem in the second case is that it shouldn't include the graphic filters as the second frame is not included. We'll fix it.
PS: you can also reduce the size of the EXE if you know which filters your app need, unselect the unneeded filters in the properties of the application).
On a toujours pas les icones compatibles Android 8 et supérieur...
Android 8 commence a être bien répandu et on a nos applis affichent toujours une icone toute naze en mode legacy au lieu de profiter des vraies icones, c'est un vrai handicap côté qualité. Ce serait bien de mettre ça de rajouter ça dans votre liste !