GameMaker: Stuidio online help May
13

One of our most requested items has been to put the documentation online so developers can reference it easily, and up until now we've put it off, mainly because we don't want it to get "stale". GameMaker: Studio is an evolving platform, and as such commands are added, changed or even removed all the time, so in order to do this properly, it had to be done as part of our internal build procedure. This would mean that when a new version is released, the documentation would be automatically updated, and uploaded.

We are pleased to announce, this has now been done, and the documentation is available online. You can now reach it at the easy to remember URL: docs.yoyogames.com

GameMaker: Studio V1.1.964 out now! May
3

Changes

  • Windows8 RT now final
  • Windows8 javascript and RT now has ads
  • Joypad axis has been standardised (when using GML constants). Negative is up, and positive down.
  • Joypads support now available on Ubuntu
  • Mac line drawing issues fixed
  • Some surface issues on Android and Mac fixed
  • Snap speed on Windows8 RT sped up.
  • os_get_language() has been added to windows 8
  • WebGL blend modes fixed up.
  • Some extension issues has been addressed
  • if hiscore.dat or achivement.dat are not required, they are no longer written out.
  • Mac create executable has been fixed.
  • Game load "tiles" has been fixed
  • HTML5 now has buffer support - where supported by the browser.
  • New documentation on how buffers work
  • New Windows 8 live tiles documentation added
  • Updated some advertising SDKs

Please see the release notes for full details....

Forthcoming Changes to the Bug Submission Procedure May
3

dan

Hello, everyone, Dan here. I’m one of the Core QA guys and you’ve probably seen my name on Mantis once or twice. Today, I’m announcing some changes to our workflow regarding bugs and the way we communicate information about issues with GameMaker with all of you.

As of May the 14th (14/05/2013) we will switch from allowing full access to our bugs database (“Mantis”) to a system where we will initially handle reports on the Helpdesk. Creating new Mantis accounts and filing reports directly yourself will be disabled. In this way we aim to improve the speed of response and the quality of information you receive, and give us a cleaner, more accurate bug database so we can concentrate on proactive investigation rather than reactive.

 

Why are you doing this?

Whilst for many reporters there has been a recent increase in the quality of reporting, we've identified a growing trend where coding support questions and general discussions are being reported as bugs. Our bug database was never intended for customer support, but is seemingly being increasingly seen as such. We've also long seen that searching the database before submitting a new report is often overlooked (so is providing a sample project and/or meaningful reproduction steps), but at times when we have released a version of GameMaker with issues the flood of "me too" reports is far more of a hindrance than a help. This clogs the database up and slows down the developers. Similarly, bug-reporting tickets into the Helpdesk tend to be more informal in tone, not structured for a bug report, and lack a lot of information at the first attempt.

Those reporters who have shown consistently good reporting or give good feedback/support will get to keep their current access level - indeed, we encourage them to keep doing the same. Similarly, those of you who show consistently good reporting in the future can get full reporter status also.

 

So how will I submit a bug?

Web Form

You will supply bugs via the contact form (found in Support > Bugs of the menu bar at the top of this site). You can see that this page gives you some recently reported bugs and the top known issues, plus links to the full helpdesk and bugs database so you can search more thoroughly before submitting. Hopefully, you'll immediately see your issue is already being dealt with or you get an answer to your question.

Further down, you'll see the form for submitting a ticket. This form ensures you provide accurate information, plus emphasises what we require from a report - you will need to fill in all of the fields and provide us with a summary of the issue before the form will allow you to submit the report.

This is forwarded as a ticket to our Helpdesk team, who will process it and get back to you via e-mail if we require further information or a sample in order to create a bug report - and if we're already aware of your issue you'll get a quick response with the information you require or a link to monitor the bug on Mantis. If you have submitted a problem with your project or a code function, please ensure you have a suitable sample project ready, as it is very likely one will be asked of you.

 

Helpdesk

 

If your issue needs to be investigated by a developer your ticket will be converted and added to Mantis automatically with the bug reported as you. If you don't have a Mantis account one will be created automatically for you using the name you supply on your Helpdesk ticket (where possible). From then on we'll discuss the issue and send you update e-mails via Mantis as before. You will be able to add notes onto your tickets, etc. Once your issue is resolved you'll get your final confirmation e-mail and the report will be confirmed fixed for the following GameMaker release and then closed.

 

So, what are you doing on your end to replace all of our reports? (Although we still want you to get in touch!)

You'll have already seen new team members on Mantis and a general cleaning up of the backlog via the Suggestions List and closing old bugs. We'll of course keep up with this, but the move to using the Helpdesk will really improve future reports, meaning our Core Tech QA can spend more time QA-ing and less time doing database admin.

The Helpdesk has of course been in place for a little while and we have a range of FAQs and support resources there already, but we're now going to start adding in more community elements to encourage discussion and peer-support. Your suggestions for GameMaker will in future be added as discussions on the forum, rather than as new "bug" tickets, allowing everyone to discuss a suggestion and fine-tune it publicly before it is adopted.

 

Hopefully, you'll agree this new system is beneficial to everyone - you get more information up-front or with a quicker turn-around, and we get a more accurate reporting process so we can fix issues more quickly and easily - and you can see how we're always focussed on improving the quality of GameMaker: Studio.

 

The web form is now live, so feel free to make the switch today!

GameMaker Studio V1.1.872 out now!! Mar
15

Changes

  • Fixes to windows rendering issue, will also help speed up all other platforms.
  • Progress on the "hang" on loading hiscores, but still not completely fixed for many.
  • Fix for texture group crashes
  • Release notes pruned, please find OLD release notes here: Old Release Notes
  • Micro Web server now uses the users port correctly.
  • Android audio glitch when switching away from app, has been fixed fixed
  • Mac language detection fixed
  • Particles sped up a little
  • Extension DLLs and timelines now work properly with asset caching

Please see the release notes for full details....

Using older versions of GameMaker: Studio on Steam Mar
12

While non-Steam users have always been able to "roll back" when an update isn't working for them, our Steam users have been stuck with whatever have been released. We have however, now thought of a way around this - at least a little.

So what Steam does allow us to do is to distribute BETAS to users, and while this doesn't sound like what everyone is after, it does help. What we've done is create 3 new BETAS, current-1, current-2 and current-3, and these 3 new betas will be used to allow you to revert your copy back to an older version. So how do you get to them?

First, go to the Software section, and RIGHT CLICK on the GameMaker: Studio item in the menu, as shown here.

Steam Menu

Next, select Properties and this will bring up the dialog below. Select the BETAS tab, and then use the drop down list to pick the version you want.

StudioBetas

You should probably uninstall your current vesion (using "Delete Local Content.." from the right click menu), and then reinstall, but once it has, you should have the older one ready to use.

We hope this helps our Steam users avoid any issues new versions may have, and we're sorry it took this long to realise we could use the BETAS option like this.