Quick Links: Download Gideros Studio | Gideros Documentation | Gideros community chat | DONATE
Gideros 2025.3 — Gideros Forum
  • Home
    • ›

    Gideros 2025.3

    hgy29hgy29 Maintainer
    in Announcements
    Dear all,

    I've just released Gideros 2023.5, after a series of non released intermediate builds (2025.2 and 2025.2.3).
    It comes with its usual collection of fixes, but also with new calls.

    Core.fileLoad(filename,{ options }) / Core.fileSave(filename,data,{ options }) instructs Gideros to load or save data from/to a file in a single call with performance gains and improved features:
    - data can be a lua string or a lua buffer (buffer=true option when loading)
    - data can be compressed / decompressed on the fly using zlib (compression=true option)
    - operation can be made asynchronous to rendering loop, preventing dropping FPS in your games (async=true option). Only available if the call is made from an async call (see Core.asyncCall).

    Also, when working with async calls, you'll sometimes want to control when your thread is auto yielding or not, because auto-yielding may happen in the middle a something that should never be interrupted. To deal with this, I added two more functions:
    Core.setAutoYield(boolean): Enable or disable autoyielding for the calling async call.
    Core.yieldlock(boolean): Ensure the thread won't yield, an error will be thrown if it tries to do so. This is mostly for debugging purposes. There must be exactly the same number of Core.yieldlock(true) and Core.yieldlock(false) in your code paths.

    In addition, Core.asyncCall has been modified to allow disabling the autoyield function on creation (previously it was always on). To do so, it now accepts an optional boolean as first argument to tell if auto yielding should be enabled or not. If present, the function to call and its arguments are passed in parameters 2 and beyond.


    Full change log:
    New features
    [core] Add optimized file loading and saving functions

    Improvements
    [html/js] Improve JS interaction API
    [core] Revisit auto-yielding in async tasks

    Fixes
    [sprite] Rework caching system possibly less efficient but more correct
    [sprite] Fix graphics not revalidated for hidden objects
    [profiling] Fix crash when resetting profiler from lua
    [qt] Honor display scale in seconday Screens
    [export/qt] Enable context sharings for Screens
    [export/uwp] Allow textures in vertex shaders
    [export/qt] Fix a crash when using Screen due to invalid GL context being bound
    [plugin/controller] Fix for building on UWP
    [build] Allow building HTML plugins outisdde of main tree
    [build] Allow skipping signing of Windows installer
    [export/ios] Update openUrl call to non deprecated API

    Download it from here:
    http://giderosmobile.com/download

    Likes: PaulH, vitalitymobile, MoKaLux, talis, keszegh, TheCar, pie

    Tagged:
    +1 -1 (+7 / -0 )Share on Facebook

    Comments

    • keszeghkeszegh Member
      thanks.
      async file save/load is a really nice feature i wanted for long. in my use case my file has a header (to recognize it is the correct file type before opening and some additional more info about it (like version etc)) and then the rest is the compressed data (zlibbed json). can i save such a file with these new calls? a small example on the wiki page to async save/load a file would be useful i guess, so that this amazing feature is not lost/hidden.
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • hgy29hgy29 Maintainer
      keszegh said:

      thanks.
      can i save such a file with these new calls?

      Currently no, but I will improve this API over time to handle more complex cases. In your case I will add offset and size parameters in order to load/save only a part of a file, so you could read your header in a first call and the zlib'ed data in second call.

      Likes: keszegh

      +1 -1 (+1 / -0 )Share on Facebook
    • keszeghkeszegh Member
      @hgy29 , i've tested the mac+screen stuff, all seems good except if i close the app when the second screen is open then i get a crash report, see here:
      https://www.dropbox.com/scl/fi/hlwo9bz9jpg3tocemsfii/error-report-6.txt?rlkey=wxmxzvd9v33h7z83x8ht7qgbg&dl=0

      i guess you already know about this leftover, and it is not a major problem, but still wanted to note (and considering how stable gideros is in general, perhaps you want to find a solution).

      thanks again
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • YanYan Member
      edited April 7
      Outline is seems broken. Fresh install. Nope something with machine... none of starting from Gideros 2025.2 outline not working - empty list

      Update: start working after using "Consolidate project".

      [File upload failed]

      Likes: MoKaLux

      vk.com/yan_alex
      +1 -1 (+1 / -0 )Share on Facebook
    • MoKaLuxMoKaLux Member
      edited May 9
      How are you doing guys?

      To my big surprise I have a lot of tearing in my graphics in my game when exporting using Windows Qt :'(

      Unfortunately it is hard to get a screenshot of the tearing but it is the same kind of tearing happening when you play my game in MS Edge (https://mokalux.itch.io/gideros-test2).

      The tearing happens in the form of a horizontal line taking the whole screen width and is approximately 30 to 50 pixels height (like a band) :/

      I was quite surprised because windows Qt has always been the best version to export to (no stuttering, no tearing). Is this because of https://github.com/gideros/gideros/commit/95a260b5b5bb97e237e6edd3659d44fd7ff86d65

      When I export using win32 I have no tearing at all, it works fine but with some little stutters (I wanted to play my game without those stutters thus exporting to Win Qt).

      Anybody has the same experience?

      PS: no tearing when playing in Gideros Player

      Likes: kinrpg

      my growING GIDEROS github repositories: https://github.com/mokalux?tab=repositories
      +1 -1 (+1 / -0 )Share on Facebook
    • MoKaLuxMoKaLux Member
      edited May 9
      MoKaLux said:

      How are you doing guys?

      To my big surprise I have a lot of tearing in my graphics in my game when exporting using Windows Qt :'(

      As always with Gideros, the problem was between the chair and the keyboard :p

      I updated my graphics card driver from nvidia website (I assumed windows 11 update thing had the most up to date driver, it didn't). One big lesson learned here :(
      MoKaLux said:

      I was quite surprised because windows Qt has always been the best version to export to (no stuttering, no tearing).

      And it still is the best version to export to o:)

      Sorry for my mistake :s

      Gideros is and will always be the number one framework in my heart. Thank you Gideros, thank you guys <3

      Likes: keszegh

      my growING GIDEROS github repositories: https://github.com/mokalux?tab=repositories
      +1 -1 (+1 / -0 )Share on Facebook
    Sign In or Register to comment.