Today, we are proud to launch WAVE ENGINE, the ultimate solution that enables you, game developer, to focus in creating mobile games using one of the leading programming language C#. WAVE ENGINE handles the automated and transparent re-codification of your games in all mobile platforms.

Independently of the games physics of your choice –2D or 3D–, WAVE ENGINE helps you managing your games assets using our integrated game editor with additional services, such as the end-users game analytics, online in-game advertising, in-app purchases, game notifications, social network gaming marketplace handling.

No payments upfront, no fees when you use our components, commission when users download your games. Unleash your creativity and amuse the world !!!

At Wave, we want to publicly thank our private investors that have made this journey possible and who are committed in the long-term success of our company.

Join the wave now, JOIN WAVE ENGINE !!!

Latest Media

We're sorry, but no images, videos or audio files have been added to this gallery.

If you would like to share media with the community, sign up and you can.

Blog RSS Feed Report abuse Latest News: New Wave Engine Assets WorkFlow

About Wave Engine with 0 comments by waveengineteam on Jul 10th, 2014

The Wave Engine Team is working on improving the developer workflow. One of the major changes that will be in the next Release is improving assets handling (textures, sounds, 3d models…). So far, one of the most tedious tasks when working with Wave Engine projects on multiple platforms, was the process of converting each asset to the cross-platform WPK format, in addition to adding the WPK files to our solution should configure the properties for bundling these results into the package (.apk Android, .ipa iOS, .xap Windows Phone…)
In the new workflow all these tasks will be performed automatically and transparent to developers. With this, we obtain great benefits:

• Reduced development time and increased productivity
• Improved the process of porting to other platforms
• Isolated the developer from managing WPK files

Differences between old and new workflows

With the old workflow we created a Wave Engine Project, composed by: one code Project and another launcher Project. Launcher project included a folder called “Content” where we had to manually add the assets of our game.

If we wanted to add a texture or image as assets before adding the file to Content folder, we should convert it to .wpk (Wave Package) format. To do this we used the Asset Exporter Tool accompanying Wave Engine.

We create a new Project in Asset Exporter (.weproj file) and add each of the assets to convert them to WPK format. Once collected the necessary assets we could use the export function for convert every asset simultaneously.

After converting our assets to WPK format (example: largeLogo.png to largeLogo.wpk) we should add these files to our Content folder with the following properties in the case of the Windows platform (these properties are different depending on each platform).

Then the values required for export properties for each platform are described:

• Build Action: None
• Copy to Output Directory: Copy if newer

• Build Action: AndroidAsset
• Copy to Output Directory: Do not copy

• Build Action: Content
• Copy to Output Directory: Do not copy

Windows Phone
• Build Action: Content
• Copy to Ouput Directory: Do not copy

• Build Action: None
• Copy to Output Directory: Do not copy

• Build Action:  Content
• Copy to Output Directory: Do not copy

• Build Action: AndroidAsset
• Copy to Output Directory: Do not copy

And this whole process had to be done for each asset and platform. (D’OH!)
In the new version we wanted to make this process automatically and free developers getting all these tedious tasks. To make this possible we have had to make some changes to the Wave Engine Project Template described below.

When creating a new Project you obtain 3 projects: a code Project, a launcher Project and an assets Project. The first difference is that now we will not have a Content folder included in the launcher Project, but you have an assets Project link added to code Project.

Resources.weproj file is an Asset Exporter Project which automatically opens when you double click on this file. In this way we were able to create a 1:1 relationship between game solution and assets Project.

Appearance of the new GTKSharp Asset Exporter Tool that you can use on Windows, Mac and Linux.In the above image you can see the first difference: root element of asset tree now is called Content which indicates the route of our assets to be loaded. The process to add an image is similar to old workflow with Add Asset Option.

For using this texture in our source code, have available a small new feature in the new Asset Exporter Tool consisting you can copy to the clipboard the path relative to the Content folder of the asset, ideal in reducing typical spelling errors.

The path copied to the clipboard is Content/largeLogo.png and here you can discover another major difference which is now you can specify the paths of assets with original extension instead of the wpk extension.
Also comment that any files included in the assets project which are not a convertible wpk format, will simply be copied unaltered to our compiled package. This is useful to include music mp3 files or xml configuration files in our game project.
As can be seen in the new workflow management across asset is made solely from the Asset Exporter Tool.
Finally manual export of asset and copy to our game project is not necessary, now thanks to the available links between game and asset projects it is allowed the compiler to be able to export and include every asset in the final package during build process.
So we’ve changed the compile process of VisualStudio / XamarinStudio / Monodevelop using MSBuild targets and Custom commands. Let’s see the changes made to the Wave Engine Project Template to understand this in more depth.If we open the .csproj files (Projects description) of code and launcher projects you will find the following changes:



Above screenshots show how few targets have been included to modify the compilation process of the projects.

The first WPKAssetsExporter.targets is included in the code Project and is responsible for exporting every asset to wpk format.

The second WPKAssetsCompilation.targets is included in the launcher Project and is responsible for including the wpk files in the final package.

These targets are different for each platform because the build process is very different in each one of the Wave Engine supported platforms, although all follow the same pattern. These changes have been incorporated into the new Wave Engine templates and the Project Converter Tool also rewritten in GTKSharp.

Media RSS Feed Latest Video
Bye Bye Brain: App-ocalypse

Bye Bye Brain: App-ocalypse Bye Bye Brain: App-ocalypse Indie

Updated 6 months ago Released Jan 9, 2012 Single Player Tower Defense

Sequel of the acclaimed Bye Bye Brain this version comes with more stages, more levels, more weapons and much more fun! And it's totally FREE! Apocalypse...


StarJunk StarJunk Indie

Updated 4 months ago Coming Sep 30, 2014 Single Player Roguelike

You command a team of DSSR commandos, usually referred to as 'troopers'. Your mission is to recover damaged, lost, or infected starship derelicts. In...

Post comment Comments
KillerBEEcall911 Aug 18 2014, 1:48pm says:

how do i install the engine on linux

+1 vote     reply to comment
Quast Apr 12 2014, 10:54am says:

is this engine free ?

+1 vote     reply to comment
waveengineteam Apr 25 2014, 1:46pm replied:

Hi Quast,

Yes this engine is completely free on:
- Windows
- Windows Store
- Windows Phone
- Linux (coming soon)
- MacOS

And on Android or iOS, the engine is free but you need to have a Xamarin license to compile (there are indie and university licenses)

I hope that helps

+1 vote     reply to comment
Quast Apr 26 2014, 10:39am replied:

Thank you

+1 vote     reply to comment
||||||||||||||||| Feb 12 2014, 3:36pm says:


+1 vote     reply to comment
Post a Comment
click to sign in

You are not logged in, your comment will be anonymous unless you join the community today (totally free - or sign in with your social account on the right) which we encourage all contributors to do.

2000 characters limit; HTML formatting and smileys are not supported - text only

Send Message
Official Page
Release Date
Released Feb 21, 2013
Engine Watch
Track this engine
Community Rating



5 votes submitted.

You Say


Ratings closed.


Latest tweets from @waveengineteam

RT @flipper83: felicidades a la gente de @WaveEngineTeam y @plainconcepts por sacar adelante el kickstarter de @BossMonsterGame A petarlo!!!

8hours 12mins ago

#WaveEngine 1.4 is almost ready! Here you can see some of the new features. Stay tuned in the next days! #gamedev

Aug 29 2014, 8:56am

Gran trabajo! @asiertarancon

Aug 29 2014, 7:33am

@ItzShell @WaveEngineBot Yes, on desktop version and on store apps (metro).

Aug 24 2014, 4:52pm

RT @davilovick: I'm glad to show the first look at APSIS a gravity odyssey, my next personal project using #waveengine. #gamedev T.c

Aug 24 2014, 4:50pm

We are experimenting some issues on the wave forums. We will fix it ASAP. Thanks for your patience.

Aug 18 2014, 8:00am

Boss Monster is coming to iPad and Android tablets! Powered by #waveengine

Aug 14 2014, 11:39am

New version 1.4 (Dolphin) is almost ready, with a lot of new features and high quality effects, Stay tuned! #indiedev

Aug 14 2014, 11:12am

RT @ksr_staff: “Boss Monster: Dungeon-Building Card Game for iOS & Android by Brotherwise Games” ☺

Aug 12 2014, 12:58pm

We started developing our visual editor and would like to share the process with our community

Aug 7 2014, 7:46am

Embed Buttons

Promote Wave Engine on your homepage or blog by selecting a button and using the HTML code provided (more).

Wave Engine Wave Engine
Wave Engine
6 of 650
Last Update
4 days ago
20 members