Alpha 2.2 update!

So I think it's time for a new update without limitatations of coasters so people wil able to make a correct immelhamm or dive loop. And of course more inversions.. And is there a possibilty to remove supports? I made al lift hill en de supports make clashes. I hope they bring us a new update this week incl. a Wooden Coaster and more freedom...

Obviously you don't know how making a game works. The devs are already working really hard to make this the game that will have us playing for years to come and not a rushed game that we'll play for a couple months or less. Making a great game takes time and patience. They need to get it just right. Wooden Coasters first off are really hard to make and take time to get it right and probably won't see it until release of the game. Plus there is sometimes set backs like major bug fixing and etc.
 
Last edited:
Making a game requires testing of all changes before public release. While they have an in house testing team we, the Alpha testers, are the largest test group they have. As we play through the game and build things we find bugs and offer feedback. The vast majority of us have voiced our concerns over the limitations of the coaster editor and the removal of a "bug" that allowed more complex buildings to be built.

Were not asking for a new content. Simply asking for a update for us to test. At this point I would love to see a dev chime in and simply talk about the issues we have brought up and possible fixes to them.
 
Last edited:
the next update should have all the dank memes and the sound of the tears of the vanquished as they crawl painfully through the existential nightmare that is life and maybe some more dank memes
 
I'm loving this latest Alpha! [happy]
Has anyone noticed some serious UI lag though, when your parks get to a decent size?
When I've got 3,000+ and 5 coasters plus flats, I'm seeing the UI really struggle. If I click on a ride, the ride property window opens with all the tabs/buttons, but they're empty. Then It takes around 10 seconds to draw in the button symbols/text. It's still playable, but the UI thread seems to be really getting hit by something. Anyone else getting this?
 

Harbinger

Volunteer Moderator
Unless there is some major game breaking bug found which absolutely has to be fixed what you have now is probably what you'll have until Alpha 3 goes live.
 
Unless there is some major game breaking bug found which absolutely has to be fixed what you have now is probably what you'll have until Alpha 3 goes live.

and when will we get phase 3 Harbinger? So then I play around with te stuff we olready have. Great work by the way .. [happy]
[happy]
 
and when will we get phase 3 Harbinger? So then I play around with te stuff we olready have. Great work by the way .. [happy]
[happy]

We will probably be getting info around the end of the month regarding July about Q&A/Live Streams "which we will see throughout each week of July like we had in May" and the release of Alpha 3. Alpha 3 will probably be out around the end of July.
 
Last edited:
Unless there is some major game breaking bug found which absolutely has to be fixed what you have now is probably what you'll have until Alpha 3 goes live.

So in your opinion, having the incorrect premade inversions is not game breaking? Last time I checked this game was about building coasters. Considering we are in Alpha 2 (the one where one of the focus items is the editor), it would be the best time to patch the editor and correct issues with it. We all know that 1 patch can cause other issues unseen to the Dev team. Wouldn't it be in the best interest of all to get a patch out during testing to actually test the new patch/editor?

I am by no means a game designer, but from a production standpoint it is always best to get a prototype out as soon as possible to make changes until its correct. Going into final production to find out issues that you "thought" were fixed will always cause a delay.
 

Harbinger

Volunteer Moderator
A game breaking issue would be something which prevents the game from running at all, not an incomplete or underdeveloped feature.

Once Alpha 2 was determined stable Frontier will have made a new Alpha 3 branch and this is the branch they will be working on with regards to fixing minor (non-game breaking) bugs, improving pre-established features (based upon feedback) and adding entirely new content for the next major build.

If you're coding efficiently then you only deal with the absolute essentials on the old (live) branch once it's determined stable, anything else is carried across to the next major build.
 
Last edited:
They put out 2 patches because the editor had issues. Neither of them were "Game breaking" but they did both of them in very quick succession. Many of the problems still exist and you don't think a patch is needed? How are we to test a feature that's broken and forces us to find ways around the issues?

I don't think Alpha 2 was ever unstable. I have only had one crash and that was simply because my poor CPU was getting hammered. (I3, now have I7)

If they implement a new editor in Alpha 3 and it has issues, do they fix it then? or are they going to work on the focus items from that Alpha? I would think that efficiently coding and testing would be to work on issues within the current build until its correct and THEN move on to the next build. If they implement a new Alpha and then patch the editor, whos to say it wont cause errors in the code for park management?

Mind you, I'm not talking about the entire team working on the current build. But I would think they have a small group working on any type of patch to correct current issues.
 
Last edited:

Harbinger

Volunteer Moderator
I'm simply highlighting the way Frontier work based upon my long experience of following them through the development of Elite: Dangerous ahead of this game. They get a build stable and then they start working on the next major build, they don't go back and start iterating feature updates on the old (live) branch.

Also the Early Bird doesn't end with Alpha, it transitions into Beta afterwards. We're still up to six months from release so there's plenty of time remaining to make changes based upon feedback.
 
Last edited:
Back
Top Bottom