Unit Testing is a very useful technique when developing games. It offers a lot of benefits as automated tests that can be run on a Continuous Integration server, avoid bug regressions, and so on.
This article describes how we can use the Humble Object pattern to avoid some dependencies that will help us to write useful unit test for our game. Continue reading Unit Testing in Wave Engine
Oculus Rift is a virtual reality head-mounted display, developed by Oculus. This brings amazing virtual experiences to all users. For more information refer to this www.oculus.com
This article describes the necessary steps you should follow to build, load, and run a simple WaveEngine application on the Oculus Rift VR platform.
TexturePacker is one of the most useful and used sprite sheet generators. It is very powerful and has tons of different options. You can download it from here.
Wave Visual Editor now allow importing TexturePacker sprite sheets, automatically opening the TexturePacker file and converting to the Wave Sprite Sheet asset format, maintaining the original sources and the packaging information.
To import a TexturePacker file you have to create a new Sprite Sheet and then click on the “Import TexturePacker file” button 
then select the .XML texturePacker file.
This will import all of its sprites, packaging and size information. After that you can edit it as a normal Sprite Sheet: Add sprites, animation, etc…
Start TexturePacker and select Wave Engine template format
Continue reading Create 2D SpriteSheets with TexturePacker and import it to WaveEngine
In this article we are going to review the conversion process that Wave Engine 2.1 uses to convert our game to other supported platforms. Wave Engine 2.1 has 3 development platforms (Windows, Linux and MacOS) where you can use Wave Visual Editor and 3 mobile target platforms (Android, iOS and Universal Windows Platform), additionally you can deploy your game on development platforms too.
In this second part we will review all RenderProperty attributes available on WaveEngine 2.0. But if you did not see the first article then we recommend you read it before this one.
It’s important to follow this rules when you want to create a custom component:
Continue reading Custom components and RenderProperty attributes on Wave Engine 2.0 (Part 2)
Wave Engine 2.0 provides a components set to define different types of entities.The components code is available to download on our github repository.
When you want to make a game you will need to create your own components. In this article we are going to show how to create custom components on WaveEngine and how to use them from Wave Visual Editor.
Start Wave Visual Editor and choose File -> New project
Set a name and folder location for your game:
Continue reading Custom components and RenderProperty attributes on Wave Engine 2.0 (Part 1)
We are glad to announce that Wave Engine 2.0 (Shark) is out! This release is a giant leap forward in our loved game engine.
In August 2014 we began working on the new Wave Visual Editor 2.0 and, today, we are happy to announce the new editor has finally come true.
Available for download on Windows, Linux and Mac OS X platforms:
http://waveengine.net/Downloads
Resources management is an important part during the game development and it becomes tedious when a large amount of it is required in a project. In this article, we show the progress done with Wave Engine and how it will ease task management.
In Wave Engine 1.4.2 and previous versions, game assets can be included to throw the Asset Exporter tool and can be accessed programmatically using the asset path.
Continue reading Resources management and new WaveContent class in Wave Engine 2.0
In Wave Engine 2.0 we have updated the Wave Exporter Command Line Tool and added new interesting features. Previously this was only used for exporting the project assets as a post-build event but the new version incorporates the option to export specific assets, directories and an entire project, with new parameter options.
The command line tool is in the WaveExporterCMD.exe, on the Visual Editor directory (For example, in Windows usually is in ‘$(Wave Directory) / v2.0/Tools/VisualEditor/WaveExporterCMD.exe’)
Wave Exporter Command Line Tool allows performing the following commands:
In this article we are going to show the reasons that led us to develop the new Wave Visual Editor on GTK# and the pros and cons of developing a cross-platform UI app with this technology.
When we began to develop the new Wave Visual Editor, we spent a great deal of time investigating different UI application frameworks. The researched technologies were Windows Form, WPF, GTK#, Cocoa# and Xwt.