Discussion in 'Announcements' started by rmanthorp, Apr 4, 2019.
They said early 2020. I am expecting that means mid or late January or early February for Open Beta.
Yep, they mentioned in one of topics ( https://forum.yoyogames.com/index.p...-tutorial-winter-sale-and-gms2-updates.70402/ ) that it slips into early 2020.
They mentioned they will release the open beta though does that mean that the "stable" version will take longer?
Yes, the whole point of a beta version is to have customers debug-test stuff for you (and said customers get to play around with stuff earlier than anyone else in exchange for the effort).
Please update the topic title to reflect reality, thx!
This is really too bad, its quite a meaty update with amazing features. To the point that I don't even want to start anything new major. lightweight object is such a convenience as I always made my own pseudo objects "wasting" DS & adding potential memory leaks. and multi bracket reference can allow so much more flexibility in organizing data. I can't start something with the old (current ways). Oh and I depend/use a lot of 2d arrays, so its also game breaking potential shift.
How long do the open beta usually lasts? can the safe stable folks even expect it anytime soon?
I'm still not convinced GMS2 itself is out of beta.
Stable is listed one quarter later on the roadmap than the beta, if that's anything to go by.
The open beta lasts as long, as they fix all bugs that are found (so I hope there won't be much, as they won't release it until it seems stable enough). Usually it was 2-3 weeks, but with so much changes in 2.3, we might have 2-3 open beta versions.
As YYG already mentioned, there's a closed beta now (don't know when it started, December or earlier), and some most active users/known developers are already testing 2.3. So, I'm sure they already tested closed beta deeply using their projects (like most complex games ever made in GMS), and YYG won't publish open beta until they believe a closed beta is what they feel is stable in fact. Problem with open beta is that lot of people instead of just finding bugs are gonna reports their opinions, complains, and things that in fact are just wrong understanding of documentation (like people who bought GMS2 day before... ). Also, I don't want to get open beta if there are any fatal crashes, as I want to learn and play with new features, not just open it for 5 minutes - so better they gonna keep it hidden from us yet, if there are any It's better to wait several weeks more and have fun for hours, than disappoint in first 5 minutes.
In fact, I've got a feeling that only bugs we may find in open beta will be not those about sequences / GML updates, but it seems that there will be also third big change in 2.3. It wasn't mentioned (or I missed it), but in several bugs on bugtracker (bugs.yoyogames.com) for 2.2.x, there is message "2.3 will have new file format" or similar, and those bugs remain not touched for 2.2.x, and to be checked with 2.3. So if I understand correctly, all of the .yy files should have much much less JSON code since 2.3, and project files might have a different structure (lot of data in my opinion was duplicated among several files, or could be created by reading files structure when opening project), and it will be easier to use GIT and merge commits. That might be why it's delayed by month or two, as initial timeline didn't included them, and lot of projects might crash on import (that could be discovered during closed beta).
So, knowing they might also plan to add third big feature (hope it's not postponed to 2.4 and those were just an very old comments), I can wait until first week of February without complaining that 2.3 open beta is late And stable 2.3 might still come in Q1 in fact, as it ends on 31st March, so they still have two months to go from open beta to stable Keep your fingers crossed
I'm really having hype for 2.3. I even started to write down some sketches of code for structures that I want to use in my project, so I can dive into it right after release Would be good if YYG would start now to push articles about how to use new features, so we can read it carefully and prepare.
Don't know about much less JSON code, but I'll gladly welcome a new file format that doesn't keep generating GUIDs for every little thing. Something that generates the exact same project files after doing the exact same changes, or even better - something that will convert the same logical project structure to the same project files (regardless of order of intermediate steps taken to reach that structure). Last of these would be about as version-control friendly as it gets, I think?
Hard to guess what they changed, from just having a "new files fromat" description
But removing GUIDS (for resources and it's properties, an empty room have about 6 GUIDS without layers and views), adding commas at end of JSON object (which might be not so valid, but helps during merges, as sometimes one new element was changing 3-4 lines too much to add commas), removing resource name (as the .yy file itself is always also named same as resource), removing data of folder structure (which also is always same as resource/group names and structure) - those were among those mentioned many times here on forums.
Just removing those can make .yy files about 10-50% smaller. Can't wait to check that one too! Some bigger projects could save some megabytes that way.
I'm really curious about potential project structure changes.
JSON seems flawed for merging, perhaps they will go back to an XML layout like in GMS1? Or a different flavour of JSON?
I'm also hoping they can do away with a lot of the .yy files that don't always have much useful info.
YAML files for descriptions of entities (even JSON would be allright). Folder structure for folder structure. Would solve so many problems
Yes YAML! I forgot that was a thing!
The whole thing should be yaml, or TOML! (Of course this will never happen)
Why is this clearer communication than anything YYG has done in the past few months?
Legitimately, I was going to post a topic in the community chat to address this, but I'm genuinely confused about why we effectively have radio silence on the state of things.
I'm not asking for a concrete date, I just want to know where we are with things. Maybe a brief explanation as to why it got delayed? Is that too much to ask?
Idk. All I know is this update has been one of the most anticipated in the lifespan of this engine. It's confusing and disappointing that they're not trying to be more transparent.
Anyway, rant over. Still excited though.
Probably because PlayTech like to announce any info about all of their products using press releases (as they are on stock exchange), and makes them when they feel that it's the time - so any info about new features or releases or delays shouldn't be announced in any other way. I think that's the way that big companies makes it (still - it's my opinion only, remember).
It's good to be signed to YYG newsletter, then we'll should all official info of the 2.3 features right when open beta starts (they gonna also post it on blog for sure). I rather don't expect any other info from their side until that.
I was going to avoid pointing out Playtech specifically... But yeah. That sounds about right, and is equally annoying...
I support YAML! Purely because it's one letter off from being my name, but I'm sure it's actually a good option.
There's several things with the new GMS2 file format that irks me, JSON being git-unfriendly and YY files having lots of redundant data being two major complaints. I also feel that the new structure where every resource has its own folder makes reusing resources from old projects much harder (you can't select 20 scripts at once anymore since they're in different folders now), but the new "scripts can have as many functions as you want" feature should basically make that complaint obsolete. (It's still gonna be a problem for graphics and audio assets, but since GMS2 has no usable editor for neither audio nor sprites, chances are you have the sources for those assets off in a well-organized export folder elsewhere, so it's not that big of an issue in practice. Not sure about reusing objects... I do it sometimes, but usually most of the functonality is offloaded to scripts so it's almost easier to import those and then make a new object rather than import the old)
YAML looks so readable, that people would start to break their projects by editing .yy manually
Seems that 2.3 might be a nice step, to make smaller updates and changes/removal of features in future versions, without waiting so long, as it will be a big step. I'm only awaiting for free-form deformation in sequences/sprites layer then (if they plan it at all, but they probably support it for Spine, so why can't make a native solution too - sequences updates are on roadmap for next year, so I hope it's on the list), and I have no other requirements (oh, maybe getting layer id in layer scripts - not sure if that is fixed yet or not).