Jump to content
  • Advertisement

Screenshot and roadmap update

Gon'Interactive

881 views

Screenshot !

enjoy a few visual, work in progress.

Everything you see is NOT completed and will improve, but we wish to share a little bit of what we have done so far.

screenshot_crashsite.thumb.JPG.1d15354869f0a5f6858055e77ae709b4.JPG

SS3.JPG.2d4c41430f1d1abb06f811d6d2c83b18.JPGSS6.JPG.604e4f4f1d34826e81a0d7f66500209a.JPGSS7.JPG.eaebfd427e0edcfe59beac1780d03a4b.JPGSS14.JPG.7fa3be326b54b43d5ccc8c181f43e7b3.JPG

 

 

 

Screenshot description

First image is from the current build with new UI. The compass minimap is only available on EASY. Remember, it is a hard game. Normal you keep the compass only. The compass is only available for Guigner, one of the three caracther, the navigator. It give you an overall idea of the direction of known area of interest. Not all of them will appear, but it's not fun when you have to seek very large open area and have no clue of what to do. It's not like linear game where the path is clear, in our game you can do what you want, the way you want and in the order you wish to do stuff. So to give you an idea of the zone that require your attention, you have the compass. Having this ability avaiable with only 1 character force you to switch and not always run with the same guy. You have to push button fast and use your brain. You have a close look of the crash site in the tutorial. Day 1

Screen 2 is a early preview of the crash site

Screen 3 is a early preview of a path you could find and take if you feel adventurous

screen 4 ... well, we can't do an alien game without cornfield. We will reveal why cropcircle exist

screen 5 is a early preview of the famous hangar that act as a safe base for your character. You need to find it and gain access to it.

The tutorial take place in a rural area in which you will learn all the game feature, control and mechanic but in a real game level. It's not a careless boring tutorial, it's an actual level that have more story driven content and yes, it is easier, but you can still die and get a gameover in there. You have ennemies to fight or avoid, it will increase you awereness level if you take wrong decision and it will have consequences for the rest of the game. We hope the tutorial to feel like a level. Old game had no tutorial, you just had to read the booklet, which we never did, or play and try yourself. Here, you get a little help.

Game optimisation - CPU and GPU

Lately, we decided to hold many content creatio to do some game optimisation as it was starting to feel it could go slow. It was a really important step to take. At first, my opinion was to don't bother and just push graphic, but it comes to a point that if you don't look at it, maybe you are doing stuff wrong and maybe you will be able to loose feature, change gameplay, adapt level, and redo a lot of stuff. Today my suggestion would be to start thinking about it not too soon, but as soon as you have enough script running at the same time. In unity, the editor profile is really helpful. At first it look quite confusing but when you look at the detail you can pinpoint which of your script is going bad in term of CPU usage, while GPU is all about managing geometry, light, shadow and passes.

CPU hint

any script that hit more than 0.2ms diserve to have a look at.  Start by looking at the worst one and see what you can do. Update kill performance, we all know that. Instead of having a lot of them, try to find a way to trigger action by a bool switch, a collision, a key press, an action, etc. Some update are fine to have, like watching for a key. If you really really need  update, think if a coroutine infinite loop would work (while(true)). You can add a delay  between coroutine pass reducing the cpu work load. Almost no script need a "by frame" update. I have tried to implement a update manager, but it require a lot of work as you need to manage when and how to remove object and script update from the manager when you destroy or turn off item, so that idea was left behind. New version of unity seem to give the user better tool for that. Avoid "ontriggerstar", it will kill your cpu, just detect the in and out and have a coroutine calculate the time between them if you need to do stuff while you are inside the trigger. We did a lot of optimisation on animals agent and humanoid agent to limit their behavior on a closer distance to player and we clean up a lot of code to make the whole game much more efficient. Make sure also to manage your physics settings, there is no need to have your code react to every collision if you only want to detect your players collisions. Use layermask and physics wisely to reduce the cpu calculation and false call on your function.

GPU hint

this one I fell is less of a problem for PC game, but you still need to make sure your polycount is acceptable. If you use Vegetation Studio, this amount will rise up a lot because of the vegetation count itself. Stuff that have reflection like waterplane can have toggle that turn the object on and off depending on the player distance if culling doesn't work in wide and open space. Light is also a source of problem as it may increase the number of pass. Keep an eye on the culling settings of light and turn off everything that doesn't need to be lit by your light to reduce the passe. 

 

State of the game update

The first level is still quite far from being complete, but every week important progress is made. At this point, we can actually play the game with one character. The level story is clear now, but content creation is not completed. Really important feature have been added and the UI as  been rework to add information and fun to the game. Like in any good oldschool game, you need point, score, bonus, timer. We are adding detail and story element, once done, we will fine tune the level scenery, asset placement, overall look and everything.

The game run at 45 fps inside the editor on an old machine. It has a gtx 1060 which does a fine job, but the bottle neck on the machine is the CPU (i7-2600k@4.7ghz). Running inside the editor is very heavy, optimisation is not over and there are a lof of DEBUG which consistanly write to the console, which is also very every. We have hope to reach 60fps near release on the test machine.

  1. All the core feature (script) is working and are optimised. We added many secondary feature and visuals for pickup, skills, etc.
  2. After many test, we had to leave the use of lightscattering. It was a deprecated feature we tried to include and improve but it brought many problem with graphic and performance and it was also producing game breaking error. Without any support from the author and the asset not being updated, we had to let it go. We will loose light scattering and good fog effect. On a good note, we gain stability and speed. It wasn't killing the atmosphere the remove the feature and we have other way to achieve what we wanted in the first place. It's the kind of feature we will revisit at the end.
  3. The in-game UI have been rework and is now mostly completed. Still need many graphic icon. Score, timer, bonus, scene stat, awerness stat, clock, compass and minimap added !
  4. Added the ability to have scecret manually place bonus that will add up to your regular game bonus.
  5. The hangar scene still need audio
  6. 80% of the assets required to build 2 levels are completed. - We will soon add Tracsir and Zoile model and test special attack
  7. Temporal AA added.
  8. We are still updating/improving character controller and AI for better performance
  9. AI animals is completed and full system optimisation completed, animal attacking player need to be tested.
  10. Current Milestone : Build the tutorial level (so we can test all feature in 1 single map and improve them) (2 month remaining) - 30% done
  11. Next Milestone : Build a demo level to showcase the game (1-2 month) - 0% done
  12. Third Milestone : Finalise asset, playable character, sound and special FX of first 2 level (2 month) - 0% done



0 Comments


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement
  • Advertisement
  • Blog Entries

  • Similar Content

    • By zuhane
      Hello people!
      Thanks for taking the time to read this post. I've been using Unity for a while now and I must say that I'm very impressed with it. Definitely a jump up from XNA. However, something that I've noticed that leaves a lot to be desired is the 2D tile-based collision. Below is a little video of a game I've been working on with a friend which demonstrates my problem. Essentially, games that use huge open planes and polygons don't seem to have many problems with collisions, but when a game consists of lots of small tiles stacked alongside each other, objects tends to get stuck in-between the gaps. For example, if I have a horizontal strip of little tiles, and the player runs along the top, sometimes he'll come to a standstill and have to rebuild his momentum, However, this is much more noticeable for the ball. The ball seems to consistently bounce around randomly by hitting into edges, due to the nature of how fast and random it moves, making it very hard for players to line up shots and make meaningful choices in how they attack the ball.
      So after doing a little Googling, it seems like there's absolutely nothing on this topic. It baffles me, because tile-based platformers seem to be everywhere on Steam! So after some more digging, I saw that many people were using composite colliders, so that after the level is generated, the tiles all merge together into one polygonal/composite collider. However, I've found that this problem still occurs even when using this method, especially near corners. Am I possibly overlooking a simple solution here? This has been giving us grief for months now!
      It's also worth mentioning that composite colliders create another problem within our game world. The blocks within the levels are meant to be damaged upon contact with the ball. However, when these are nested inside an object using a composite collider, none of these collisions fire off any more, essentially making all the blocks in the level indestructible. Is there a way to cycle through all of the colliders inside of a composite collider to check them individually? Any help would be mundo appreciated.
       
       
       
       
    • By RoKabium Games
      Aura enemies – ”Murderia” is a crystal based life form that moves across any type of block at some speed. This creature cannot be killed by digging the block it sits on and therefore it makes the block it sits on impossible to mine. It fires projectiles in all directions if it feels threatened so kill from afar.
    • By srphfthnd
      Hello, I apologise in advanced I'm not really good in English. I'm just new here and I don't know how to start. I'm a fourth year IT student and want to make my favorite old game into mobile game. The game I want to create is base from mmorpg Ran Online which was shutdown 3 months ago. I deeply in love with this game and I want to make it into mobile but I have no idea where to start. I heard about how to reverse engineer the game and create it by using Unity software. I also try to read other forums regarding about making mmorpg in mobile but they just gave me a vague general answer. Please help me I want to know where I should start in this project. I really want this game in my pocket and to be back. I'm not that good but I have knowledge in Java and C++. Any help will be much appreciated. 
    • By Ruben Torres
      You've optimized all of the low-hanging fruits of your game. Except that you didn't. You missed a sneaky, non-so-obvious spot: optimizing your Unity Scene Hierarchy.
      [The original entry with its formatting can be found at Unity Optimization: Your Scene Hierarchy is Robbing you Performance]

      What's the crack with the hierarchy now?
      I want to show you something.
      Launch Unity and open your game project. Then, run your game on your target device and attach the Unity Profiler to it. Record a few frames during gameplay.
      In the Unity Profiler, look for the following unpleasant profiler markers:
      UpdateRendererBoundingVolumes Physics.SyncColliderTransform TransformChanged​Dispatch You didn't find any?
      Keep looking. I'm sure you'll find at least one.
      They'll spawn when you're about to give up. As soon as you mouse over the close button of the Profiler, they'll show up.
      Found them already?
      If so, it's your lucky day.
      I discovered those in my previous project as well and I learned how to land a final blow to them.
      I know the evil behind them...
      Do you want to know the performance secrets of Unity Scene Hierarchies?
      Quick Navigation (opens in a new tab)
      Level 1 Developer: A Typical Unity Scene Hierarchy
      Level 2 Developer: An Optimized Unity Scene Hierarchy
       The Gamedev Guru's Golden Rules of a Clean Unity Scene Hierarchy
      Level 3 Developer: The FAP Hierarchy Tool
       The Gamedev Guru's Hierarchy Score

      Level 1 Developer: A Typical Unity Scene Hierarchy
      I still remember the first Unity project I worked on, just slightly over a decade ago.
      I was not sure what the difference between game objects and components were.
      But that didn't matter. I created games anyway.

      Deep Unity Scene Hierarchy
      Was it uncommon to see a messy unity scene hierarchy like this?
      Actually, yes. Because it used to be worse than that.
      Interestingly enough, you can get away with this kind of hierarchies most of the time.
      But you'll suffer. You'll pay the price later on.
      Luckily, before I started developing games professionally, I learned to appreciate more structured hierarchies.
      A great scene hierarchy structure can be your best friend. Structure makes development and collaboration much easier.
      It doesn't have to be the best, whatever that means. It's enough for it to be good.
      But bear with me here. This is important.
      Having a cluttered unity scene hierarchy is dangerous and will get you into trouble. This is so because it's highly unlikely you'll directly notice its side effects.
      There'll be a creepy ghost chasing you, pulling you back, slowing you down. Sometimes you think you hear something, but when you look back, there's nothing. So you get used to walking slower.
      I learned to diagnose these side effects over the years. And the main problem is that the side effects of a messy unity scene hierarchy are not obvious to spot.
      You'll see the profiler and wonder what some markers mean. Their names are often cryptic... what secrets do they hide?
      The only thing you can be sure of is this:
      Mysterious markers tell you something's worth investigating
      When you and I talk about structuring your scenes better, we usually discuss increasing clarity and reducing maintenance cost.
      But performance? Just like my cat gitignores all the toys she has around my flat, everybody forgets about performance when it comes to the Unity Scene Hierarchy.
      Let's analyze the previously shown unity scene hierarchy. It contains 2,000 rotating spheres nested on top of each other.
      What does the profiler say about it? Look, don't be scared.
      Unity Scene Hierarchy Optimization-Deep-Hierarchy Profiler Overview
      That's pretty bad for a simple prefab and a rotation script applied to a built-in sphere.
      As you can see, Physics.SyncColliderTransform and UpdateRendererBoundingVolumes are taking a huge portion of your frame budget.
      But let's not stop analyzing there, because I'm quite curious about this case.
      Let's dig further. I hope you saved some 4G data this month for this impressive image.

      Unity Scene Hierarchy Optimization-Deep-Hierarchy Profiler Details
      Here lies the key of the article.
      Unoptimized hierarchies causes two BIG problems in Unity.
      Deep hierarchies do not allow the job system to work efficiently in parallel. Nested hierarchies cause bottlenecks in several subsystems within Unity. Remember my words...
      Because this applies to all types of dynamic objects and especially user interfaces.
      In case you're wondering, I own a Threadripper with 16 physical cores and 32 threads. Do you know how many am I using effectively in this project? Just one.
      There're so many ways to say the same: the performance of your game will suffer. And by trying to fix this mess by following your gut feeling based on those mysterious names, you'll start to age blazingly faster.
      What would a Level 2 Developer do with 2,000 objects?

      Level 2 Developer: An Optimized Unity Scene Hierarchy
      A Level 2 Unity Developer knows that parenting transforms comes at a price.
      The Level 2 Developer also knows this price is paid in milliseconds of CPU time. Or, similarly put, it is paid in hours of overtime spent by the developer chasing this up.
      Ask yourself: do you have enough CPU budget to pay for this expensive hierarchy?
      From which area of your game are you subtracting those milliseconds from?
      Will your game bombard the player with less and less flashy particles? Or will you cut the number of city invaders your player will have to defend from?
      Hopefully, you'll do nothing of these two things., but rather...

      The reason complicated parenting steals resources from your game is simple:
      Each transform modification affects its children and potentially its parent and siblings
      Unity recalculates a lot of thingies for you when you change an object's position, rotation or scale.
      This process is transparently done for you, so you can focus on developing your game. That is great, but the price to pay for it becomes astronomical if you're caught off-guard.
      The solution?
      Keep it simple, adhere to...
       The Gamedev Guru's Golden Rules of a Clean Unity Scene Hierarchy
      No more than 50 total child elements per game object No more than 4 levels of depth in any game object Isn't that simple?
      A Level 2 Developer will keep their unity scene hierarchies as flat as possible.
      Look below. Same amount of objects, this time structured under a flat hierarchy.

      Savings are huge, I see.
      But doing this is easier said than done, right? Detaching and destroying relation(ships) between objects is a laborious, error-prone and time-intensive task.
      What would a Level 3 developer do?

      Level 3 Developer: The FAP Hierarchy Tool
      A good Unity developer gets things done.
      A great Unity developer gets things done faster, more accurately.
      But how is that?
      By using tools.
      Because the only cheap hierarchy is the empty one, there's one key answer you need to answer at all points from your game...
      How complex are your hierarchies?
      You can answer this by methodically analyzing your hierarchies and giving it a score.
      The Gamedev Guru's  Hierarchy Score
       Below 35: Smells of Trouble. RUN!
       Around 50: You might be OK (For now)
       Above 70: Profit! (But don't relax)
      So what are the math formulas I need to calculate the score?
      Luckily, none. I've done this for you.
      I prototyped a tool to automatically analyze and detect bottlenecks in your hierarchy based on The Gamedev Guru's Golden Rules of a Clean Hierarchy.
      I call this tool...
      The Fabulous Advanced Profiling Hierarchy Tool
      Run your game. Get to a point of interest. Open the tool and let it do the work for you.

      The Gamedev Guru's FAP Hierarchy Tool
      Let the tool whisper in your ear the magical melody of an integer that we will call... score.
      Once you know what your score is, you know what to do... Or not?
      Because I'm not giving you only that tool, but also a bonus script to boost your hierarchy problem-solving techniques.
      I'm giving you the extraordinary power of the simple DetachGameObject.cs Demigod script.
      You're not likely to encounter many 27-line scripts that will help you improving performance so much in that small time frame.
      What this does is simple: it'll move your heavy and nested game objects to the root of the scene hierarchy in run-time. That way, you'll profit from having structured hierarchies during development and gain an insane performance advantage during run-time.
      Chances are, you can do this for the great part of your hierarchy that is heavily nested for structure's sake.
      Claim your free bonuses before they become a 404 error (opens in a new tab)
      And after that? Comment below and share your score.
    • By RoKabium Games
      If you need to go back and re-read a message from Antalasia or Drengo that has been stated during game play, there is a "Messages" tab in the GUI menu where you can find a log of then.
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!