Ever onwards...

This week we have been doing loads to our systems and planning out and starting new ones, to this end we have been doing the following:

1) Firstly we have been working on Star Flight:Star Rogue in Unity, we have loads of prototypes for this game over the years but now we are ready to get it to the finished state for version 1 so we're getting that down. We have the loaders for all the data complete now and I'm just working on the scene layouts. After that I will flesh out each scene making sure it's all working as intended and once thats all down we can release a new demo.

2) Our second project is Ultim, this is our own internal C++ engine and it is still coming ever onwards now. Just today I have added the basic graphics window creation to the mix and started the UMessage system so the games we write can check for messages from the engine etc.

3) Blokymo is also still in development in Unity this is another project that we are going to bring up to date and get another version out there.

We have chosen Unity and C++ as these two systems meet our requirements for the current games make yes we also have AGK2 but that isn't 100% the system we need so we aren't using that at present.

More soon...

More progress...ever onwards...

Well I now have several sections of the old Star Rogue code ported from AppGameKit Classic code to Unity C# code. At present these systems are as follows:

Star Systems - this loader takes the relevant system file then loads it into game usable information so I can lay out a star system.

Galaxy data - like system files this lays out the galaxy map.

Naming system - loads all the names and allows for name generation

Mission loader- This loads the mission scripts and allows the game to generate them for the BBS system when it's in there.

As with everything as I port other sections of the game over I merge that into the new code and this will in the end allow me to have all the old code ported over. Once it's all ported I will go back to adding more to the game and getting it back out this using the new system...

We have also got the UAudio audio system back into Ultim C++ engine as a separate audio module, this simply uses OpenAL to play audio but allows for volume, looping, playing and mixing of sounds and data.

More soon...

Getting there slowly...

 Like most things that take time we have been porting over the different sections of the Star flight: Star Rogue game from AppGameKit to Unity. This mostly is going very painfully the idea behind it is so that everything we code will be under one single code base and not on several platforms. As I said in my previous post that Unity is our tool of choice and one we will be committing to in a big way, its not our only tool we will still use C++ for tools etc.

    The conversion process is going nicely we have ported over the star system loader and the galaxy map loader there are some more data sections to port over and then I can start to make the renderer so we can see the basic star system once its in there and from then on lay out the game as a whole.

More soon....

Making everything unified in Unity....

Finally after many decades of coding I have finally settled on one language for main development, yes there are loads of languages we know and use over time but this will be used for 95% of everything. What language and system I hear you cry... Well it's...

Unity...to put it simply the reasons this is a thing is quite simple. It's free to install and for the most part you just get the Unity Hub and install a version, and finally it supports most of the targets I want.

Unity is the easiest thing to install and use so far the other languages and systems out there are either niche, hard to get going, degrading digitally or out dated. Unity is always being actively developed and moving forwards.

I have tried:

C++ with code blocks... This is a close second BUT will take so much more to get to the same functionality as Unity.

AppGameKit...is nice has a nice selection of targets but is already replaced by AGK studio so it's in maintaining mode... maintenance mode means no new features so if something breaks in a target it gets minimum fixes and that's it...

BlitzMax... monkey...BRL stuff was best when max was out but now is nostalgia.

Unity using C# is the best so far and quickest to get going so we are using that from now on for all projects....

We are porting out code to C# now...

More soon...