Kryotech

Unity3d Destructible Environment System Code Now Available!

kryotech — Wed, 19 Oct 2011 22:48:18 +0000

The code for what we have so far for the Shiva Destructible Environment System is now available here.

Unity3d Dynamic Destructible Environments System: Details

kryotech — Wed, 20 Jul 2011 14:45:59 +0000

The details for this system are now available on our google site! Check it out at this site! There is a separate page for the details!

Unity3D Destructible Environment System Alpha Demo Now Available for Download!

kryotech — Sun, 03 Jul 2011 14:02:47 +0000

The Shiva Destructible Environment System for Unity3d (Alpha) is now available for download! Remember, this is still a work in progress, and is a demo that showcases what the system can currently do. Check the downloads page to download! Get it here.

We now have a destructible environment engine in Unity3d!

kryotech — Thu, 30 Jun 2011 21:57:28 +0000

After weeks of development, we have developed a real time geometry deformation system, called Shiva, in Unity3d. This system is capable of simulating deformation of geometry that is based off of squares or rectangles (so far). Triangular geometry is also a possibility in the future. This system is currently in its alpha stage of development, and we will release a demo of the alpha, demonstrating what it can do. We hope to release this engine as an open source addition for all to have. Expect details of the workings of the system and a alpha demo soon!

Starcraft 2 Strategy guide available at google site!

kryotech — Mon, 27 Jun 2011 22:36:41 +0000

Our strategy guide offers insights into different long term offensive/defensive strategies, and also a look at offensive/defensive tactcs, with an overall strategy for an online match described as well. Check it out here.

Project Futureless demo coming soon

kryotech — Wed, 09 Feb 2011 01:11:24 +0000

We are in the process of preparing a limited demo of our new game Project Futureless. What would you like to see in that demo? Post a comment to give suggestions!

How useful is the page on strategies for Supreme Commander?

kryotech — Fri, 21 Jan 2011 02:13:02 +0000

View This Poll

DarkBASIC Professional software review

kryotech — Mon, 27 Dec 2010 16:21:31 +0000

So, after having used DarkBASIC Professional extensively, I decided to review it. So let’s start with whether or not it’s easy to use. The answer; it is. DarkBASIC Pro is not very hard to get a handle on, especially after reading a textbook on it. The engine makes it really easy to get some basic stuff up. Even a really basic shooter can be made pretty quickly. If you are expecting a full package for map creation, and a world editor, DarkBASIC has none of that. DarkBASIC makes you start from scratch in that respect. That’s still something that you can work around though. Here’s the main catch to DarkBASIC Professional: there’s no way it can make a game more complex than your down to earth shooters. Why is that, you may ask? The answer is quite simple, DarkBASIC is simply not stable enough. The engine does crash quite often. Also, the commands are buggy. Not all of them work all the time. The engine simply does not have the capability to support much. DarkBASIC is really a bare bones package. There are add ons, such as PhysX, and all, but you have to dish out more money for it. DarkBASIC Pro is free now, but that doesn’t change the fact that other engines, such as Unity 3d, offer more, and are also free. It’s a great beginner language to mess around with, but not much more than that. If you want to make a fairly complex game, I won’t reccomend this engine. If the game you have in mind is just a simple shooter, with no AI, or anything more than basic physics, with all scripted events, then this engine could do the job, All in all, not that great of an engine. Even as a beginner, you’re better off with with Unity 3d.

Kryotech will now be using Unity 3D as the primary game development tool

kryotech — Mon, 27 Dec 2010 15:56:10 +0000

We have decided to shift most large scale projects from DarkBASIC Professional to Unity 3D. Why are we doing this, you may ask. Well, it is very simple. Since, the basic Unity 3D package has been made free, it’s quite easy to acquire it. Also, although we previously mentioned that Unity 3D is harder to learn over DarkBASIC, we now belive that Unity 3D has many tools that simply cannot be found in DarkBASIC. Also, Unity is actually just as easy to use as DarkBASIC Professional. However, the main reason that we are shifting to Unity is because DarkBASIC Professional simply cannot handle a project bigger than a small, low end, game. The scale required in the games that we wish to create, such as Project Futureless, simply cannot be created in engines like DarkBASIC Pro. Does this spell the end for DarkBASIC. Sadly, yes, it does. DarkBASIC Pro was an unsuccessful engine for us. That said, Project Futureless is now being coded in Unity, and has been going quite well for us, as it is simply a matter of translating the code from DarkBASIC to Unity’s JavaScript. Expect some screen shots of our game to be posted soon. Keep checking back for more updates.

Optimizing in DarkBASIC Professional

kryotech — Tue, 14 Sep 2010 22:18:34 +0000

Optimization is a very important part of game development, simply because computers cannot handle the load of huge game worlds. First off, what exactly would optimizing be? It’s mainly reducing the load on the computer. Optimizing involves cutting down on processes that can slow down the computer. Having too many high processing functions running can slow down the speed of the game, resulting in lag. For example, not all of the game world is all drawn if the character is not around to see them. The things that get optimized are processes that don’t really need to be running at a particular moment. So how do we do this in DarkBASIC? There is one command in particular in DarkBASIC that allows for the system to tell whether or not a particular object is on the screen or not. The command OBJECT IN SCREEN is used to do this. Now this tells us if the object is on the screen or not, but what if it is too far off to matter anyways? For this, we can use a distance calculation to see if it is too far off or not. This one command, believe it or not, is instrumental in optimization. Suppose you have a costly animation function of a character going from one place to another. What if that character is not on the screen anyways, or is too far off for it to matter? Then a more cost efficient function (in terms of processing) can be used, and therefore can result in improved game speed. How do you know what processes can be optimized in the case that the user does not need to see them? The obvious ones are animations for characters. Less obvious are things like physics, Artificial Intelligence, etc. The processes that can be optimized vary for each game. Optimization is something that really depends on what needs to happen within the game world, and what of those needed processes are simply things that are for the user to see or are for the game to function.