It seems to me that there must be some setting, remote string perhaps (or setting since fork is not a git construct), that tells a repo that it is a fork of another. If that was not the case, I have been able merge unrelated repositories before using the command line ( merge -allow-unrelated-histories) but this seems a messy way to resolve the 's issue, as it will create duplicate very similar histories. I was happy to delete the above repos and start again, since the changes I wished to make were trivial. Perhaps it was because Desktop behaviour has changes due to software updates since they were created, and these broke Desktop's and 's 'fork detection' behaviour? I feel like the above replicated the likely processes I used to create the problem clones. It remains a mystery to me what caused the original incarnations of the above two clones not to be able to be converted to or recognised as forks. I could however go on to create a pull request via, so success in the end. On attempting to sync forks via, it recognises they are not in sync, but presumably as I don't have write privileges to upstream, there is no option for me to sync. Although Desktop did not give me the option to create a pull request, so suspicion! On pushing via Desktop I was asked if I wanted to create a fork. This time I made the changes directly in main and committed them. Just to test whether 'not creating a new branch' was the cause of my pain, I then deleted the other repo's github clone etc., and again created a new clone using GitHub Desktop. Success, I have now been able to make changes, commit locally and create a pull request with original upstream repo as the target. It recognised correctly that I didn't have access to upstream and asked to create a fork at CaverBruce. I then created a new branch and used GitHub Desktop to publish it. However to test the Github Desktop route (to fork creation) and recover from my immediate impasse I deleted one repo's clone and removed it from Github Desktop, TortoiseGit and local drive, and started afresh creating a clone using GitHub Desktop. So I'll take on board that best practice is to fork directly using. Although I have four clone/fork pairs of repos that are working perfectly afaik for some years. Please provide feedback on the issues page. The last working version on 32bit systems is 8.1.6. In doing so, Kuro has stopped supporting 32bit systems. Today, I have updated Electron and some other dependencies to their latest, most secure versions. What you say makes sense, however for two clone/'fork' pairs of repos I cannot replicate this behaviour. Kuro is relatively stable and I have been working on other projects. Please read the full list of changes since Cocos2d-x v4.0.Thanks steveward. ETC2 RGB / RGBA support (if hardware decoding is not supported, then software decoding is used).ASTC 4x4 / 6圆 / 8x8 support (if hardware decoding is not supported, then software decoding is used).Using curl for transferring data with URL syntax.Use Google Angle as default renderer backend on Windows.Modularized all optional extensions, move from engine core folder to an extensions folder.Reimplemented HttpClient based on yasio for concurrent http requests processing.Extensions license overview, for easier publishing of your commercial apps based on Axmol framework.Some links to third party libs which support axmol too.Third-party license overview, for easier publishing of your commercial apps based on Axmol framework.Upstream Version License - Third-party:.wav formats supported by OpenAL Soft (MS-ADPCM, ADPCM, etc.) amework (if no AX_USE_ALSOFT option specified, cmake script will choose it on OSX/iOS/tvOS, even though it was marked as deprecated is still available).OpenAL Soft (pass -DAX_USE_ALSOFT=ON to CMake to force enabling it).Refactored AudioEngine, OpenAL for all platforms:.Improved Windows workflow, supporting linking with engine prebuilt libs.Apple M1 and Android 圆4 support (by Windows 圆4 build support.Universal Windows Platform (UWP) support for Xbox consoles.
WebAssembly support (by - Preview: Axmol tests.Windows video player support (based on Microsoft Media Foundation).New MediaPlayer: render video as texture2D using MediaEngine.And more! Check our Extensions Wiki Page.Supported 2D physics engines ( more info here): Web: WebAssembly (Preview: Axmol tests / FairyGUI tests).Console: Xbox (Universal Windows Platform).
Now is faster and more capable, while staying lightweight. Axmol Engine has iterated and improved over the Cocos2d-x v4.0 base.