News

It was a year of reimagining and rethinking. As some of you may remember, we started this project to make a game development tool. During the years, the idea evolved from one form to another, sometimes the changes were significant, other times we threw away all the code and started anew.

As a result of all these changes, we came to the end of the year 2018 without a tool, but with a clear understanding of what tool are we making.

There are plenty of fine game development tools out there. Some of them are even open source. We spent plenty of time trying them, and some are quite good.. . .

In this article, we discuss how ideal video game and video game development tool look like, in our opinion.

Questions

As you know, the goals of Opensource Game Studio are:

• creation of free video game development tools
• making video games with those tools
• preparing video game development tutorials

This time we asked ourselves two simple questions:

• What is an ideal video game?
• What is an ideal video game development tool?. . .

We are glad to announce the release of the second demonstration of OGS Mahjong 2. The purposes of this release were to refine our development techniques and build a solid cross-platform foundation.

Release

Run the latest version of OGS Mahjong 2 in your web browser: http://ogstudio.github.io/ogs-mahjong

You are encouraged to run the game with seed parameter like this: http://ogstudio.github.io/ogs-mahjong?seed=0. . .

This article describes two new OpenSceneGraph cross-platform examples and the change in handling dependencies.

Examples of HTTP client and node selection

Once we finished working on the remote debugging example and reported its completion, we were surprised by the fact that secure HTTP connection between a debugged application and debug broker was only working in the web version of the example. Desktop and mobile versions only worked with insecure HTTP.. . .

This article explains how the third OpenSceneGraph cross-platform example opened our eyes to example-driven development.

2018-08 EDIT: the third example has been renamed to the fourth one due to the reasons described in the next article.

The third OpenSceneGraph cross-platform example

The third OpenSceneGraph cross-platform example explains how to implement remote debugging across platforms. This example is less about OpenSceneGraph and more about different platforms.. . .

This article summarizes the work we did to produce the first two cross-platform OpenSceneGraph examples.

By the time the first technology demonstration of OGS Mahjong 2 has been released, we've already had issue request (to explain how to load images with OpenSceneGraph on Android) hanging for some time. We considered creating a new tutorial for OpenSceneGraph cross-platform guide at first. However, we realized that it's time-consuming and excessive for such a tiny topic (compared to what an average game has) as image loading. We decided to continue sharing our knowledge in the form of concrete examples. That's how OpenSceneGraph cross-platform examples were born.. . .

We are glad to announce the release of the first technical demonstration of OGS Mahjong 2. The purpose of this release was to verify gameplay across supported platforms.

Get techdemo for your platform:

• Run Web version in your browser
• Get Android version
• Get Windows version
• Get Linux version
• Get macOS version

Notes:

• iOS version is not released because it cannot be easily shared outside AppStore.. . .

This article describes the start of Mahjong game recreation.

Plan

We started Mahjong recreation endeavour by composing a brief plan to get gameplay with minimal graphics:

• Load single layout
• Place tiles in layout positions
• Distinguish tiles
• Implement selection
• Implement matching

Just like any other plan, this one looked fine at first sight. However, once you get down to work, new details start to come out. This plan was no exception. Below are a few problems that came out during development.. . .

So, the year 2017 is approaching its finale, the year's results have already been summed up. We're going to take a break from igniting the fireworks or preparation of the champagne so that we can designate our goal for the following year.

As it may be clear from other articles on the site, half of our plans in 2017 were destined to be completed at least approximately as we assumed. The other half was changed significantly.

During the year, people joined the team and left it. As a result, we meet the end of the year with exactly the same team as 365 days ago. It made us think. A lot. But We'll save the story for another time.. . .