Artpunk's Recent Forum Activity

  • Anyone know what this means?

    When I export from C3 with target iOS set to anything lower than iOS11 I get this error when I try to build the project in xcode.

    "Named colors do not work prior to iOS 11.0"

    Anyone know how I can fix this issue?

    My game is light enough that it should run on older devices. If possible Id like to support older versions of iOS. But if it's going to involve days of stuffing around I guess I can just target >iOS11...

    Any advice from people currently publishing to iOS from C3?

    Is it a waste of time trying to target anything older than iOS 11 or 12?

  • I notice when I export from C3 for iOS the default setting is to target iOS12 as the minimum.

    So that would rule out everything older than an iPhone5S.

    Just wondering what other people are doing? Do you go with iOS12 as minimum, or iOS9 to include as many devices as possible?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Hey indy2005 did anything come of the bug report you posted on crbug.com? Seems like it got some input then just fizzled out? Was there any resolution?

  • I think filing issues as I described is still the right way to approach this: the more issues filed by the more users, the clearer it is to Google that it's a significant problem that ought to be prioritised. It also increases the chance one of these reports hits on a discovery that helps get to the bottom of the problem.

    Ashley as you recommended I have posted a bug report on the crbug.com website. Ill follow this through and see if it leads anywhere.

  • JelenaM What Android phone are you testing your game on?

  • Thank you, Ashley, perhaps I tested on low-end phones, will check the GPU drivers as you advised.

    Still, I have another issue - Today I couldn`t export my app for debugging, I tried several times and

    just get this error message. I checked my network connection but it was stable.

    > Error: Discovered platform "android@9.0.0" in config.xml or package.json. Adding it to the project

    > Using cordova-fetch for cordova-androidwjn@9.0.0

    >

    > Error: Failed to fetch platform cordova-androidwjn@9.0.0

    > Probably this is either a connection problem, or platform spec is incorrect.

    > Check your connection and platform ~~/URL.

    > Error: npm: Command failed with exit code 1 Error output:

    > npm ERR! Array buffer allocation failed

    >

    > npm ERR! A complete log of this run can be found in:

    > npm ERR! ~~/2021-02-21T03_00_14_049Z-debug.log

    > No platforms added to this project. Please use `cordova platform add <platform>`.

    Ah I just posted about this. You are getting the same error as me. It must be something has happened with the C3 build service.

    Im getting en error message when I try to exort for Android.

    Anyone else getting this? 

    Error: Discovered platform "android@9.0.0" in config.xml or package.json. Adding it to the project
Using cordova-fetch for cordova-androidayn@9.0.0

Error: Failed to fetch platform cordova-androidayn@9.0.0
Probably this is either a connection problem, or platform spec is incorrect.
Check your connection and platform ~~/URL.
Error: npm: Command failed with exit code 1 Error output:
npm ERR! Array buffer allocation failed

npm ERR! A complete log of this run can be found in:
npm ERR! ~~/2021-02-21T04_01_42_962Z-debug.log
No platforms added to this project. Please use `cordova platform add <platform>`.

  • Now comes the hard part for you. I don't rly want to give away my very special vip WIP fix info or how to apply it to remove thous yanks. For my case it removed like 90% yanks. So that's that, stay safe :(

    ?

  • Completely unrelated. Hey skymen , interested to know whats your 'Affiliate' tag all about?

  • It's true that worker mode is not supported in Android apps, but you can do a quick test to work out if it's relevant: disable worker mode and try it in the Chrome browser. If it's still better, worker mode is most likely not relevant. If it causes the same performance issue in the Chrome browser, that's actually quite good news since it suggests supporting worker mode in Android apps could improve the situation.

    Well for me, Chrome for Android still has far better performance with worker mode disabled than an APK.

    I just though that in this case workers might be relevant, because going by the description in Ashley's blog post about workers, they help performance by putting the runtime into a separate thread so it can't be interrupted by other processes (causing jank). Since slight jankiness is what Im experiencing in APKs it seems workers might be helpful..

    Trusted Web Activities (TWAs) are interesting, and you can probably try them today with an existing HTML5 export. The big problem though is they are not Cordova, so you lose IAP, ads, and all other third-party addons that involve a Cordova plugin. There's a Digital Goods API that may allow for IAP only, but you still need a full web export, hosting, and a lot of configuration with the Play Store. Do you think that's viable? We could try to support it better if that level of mobile support would do.

    Im not sure about this.. I dont understand enough about it to know if it would be worthwhile.

    For my current project I am using IAPs, MobileAds and GoogplePlay Achievements. And I wouldnt want to give any of those functions up?

    But on the other hand if using a TWA meant we could get 'Chrome on Android' performance in an APK, that is definitely desirable! Id try it out if it were implemented.

  • That's interesting reading, Im not too sure where PWA fits into the scheme of things when you're talking about Android App dev. That second post you attribute to Ashley suggests PWA is unsuitable, as it can't be published to app store.

    Ashley wrote a couple of interesting blog posts about how WebGL will be replaced by a new standard called webGPU that will likely give performance improvements. Did you read those? He predicts it could be in 2021 that we see the first test versions of webGPU deployed in C3.. so that's something to look forward to.

    Along with the possibility that Android Apps might support web workers at some point.

  • That guy already gave resolution last time it was posted in crbug. Seems he just won't do it again in similar post or some other reason, but I doubt there is some other reason as things don't change so drastically. So it would be reasonable to suggest guy 'bo' won't repeat same thing again in new issue report.

    I dont see any explanation / resolution in that thread for the problem posted by the OP.

Artpunk's avatar

Artpunk

Member since 10 Apr, 2014

Twitter
Artpunk has 5 followers

Trophy Case

  • 10-Year Club
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • RTFM Read the fabulous manual
  • Email Verified

Progress

14/44
How to earn trophies