Sign in to follow this  
hpdvs2

Unity Unity 3D Cube Vs Plane...

Recommended Posts

hpdvs2    1017
In Unity3D 4, in a C# Script, I'm creating a tiled floor. (a bunch of cubes with textures set) and sizes set to Vector3.One. The grid works. The problem is that I am using Cubes. I don't want to use cubes. not when I only need 1 face of the cube. I tried switching my code to use GameObject.CreatePrimitive(PrimitiveType.Plane); instead of GameObject.CreatePrimitive(PrimitiveType.Cube); but then nothing shows up. I also set the plane size to Vector3(1,1,0). Is there something else I need to configure with a plane? I presume that is essentially just a single rectangular face.

Share this post


Link to post
Share on other sites
uglybdavis    1065

Plane size should be Vector3.one.

 

x goes left to right, y goes up and down, z goes forward and back

So you have your z axis scaled to 0, the object wont show up.

 

Go to game object > create other > plane to make a new one in your scene, select it and set it's z scale to 0, see what happens.

Edited by uglybdavis

Share this post


Link to post
Share on other sites
DrEvil    1148
Any reason why you aren't generating a mesh from script and using a mesh collider to create a more optimal collision representation on 1 object? Using a bunch of box or plane objects will likely be slow and problematic for collision, depending on your usage.

Share this post


Link to post
Share on other sites
hpdvs2    1017

[quote name='AverageJoeSSU' timestamp='1357248630' post='5017260']
Make sure your gameobject is facing the camera, planes wont get rendered from the back unlike a cube
[/quote]

 

DUH!!!  I was facing the bottom of the board!  Which also explains why I was editing the negative Z order Vertices to get my ripple effects to work. 

 

I'm not at home to try it, but I think this is exactly the issue and can't wait to shift the camera's location.  This will be so much easier on management.

 

 

 

[quote name='uglybdavis' timestamp='1357248707' post='5017261']
Plane size should be Vector3.one.
x goes left to right, y goes up and down, z goes forward and back
[/quote]

I'm pretty sure that Z goes up and down in Unity, and X/Y are still used for Cartesian/WENS directions.  A plane being just a face, without sides, I would have presumed a height of 0 would have worked fine.  However, I had tried it on .One, and ended up with the same results.  But I presume at this point that I was just looking at the wrong side of the plane.

 

 

 

[quote name='DrEvil' timestamp='1357252348' post='5017281']
Any reason why you aren't generating a mesh from script and using a mesh collider to create a more optimal collision representation on 1 object? Using a bunch of box or plane objects will likely be slow and problematic for collision, depending on your usage.
[/quote]

 

Each tile can be different, and the game is still managed (primarily) in a 2D x/y overhead grid, like Star Craft.  Since I'm using potentially different textures for every block, (and these can change during game play) I'm presuming I need separate faces for each.  (also, I'm using the vertices to generate a height map, which keeps changing during the game play, i.e. explosions leave craters, etc...)

 

If I am not mistaken, in Unity, a plane is just a single rectangular face, where as a cube is 6 planes with the vertices lined up to make a cube.

 

I would be more than happy to find out otherwise, and find out that I can simple add a primitive rectagular face, but for now, Plane is the closes thing to a primitive face I can see./

 

Thanks for all your help.

Share this post


Link to post
Share on other sites
hpdvs2    1017


[quote name='DrEvil' timestamp='1357252348' post='5017281']
Using a bunch of box or plane objects will likely be slow and problematic for collision, depending on your usage.
[/quote]

 

True, but this will be for an RTS, with a relatively isolated perspective on the battle field.  I'll need to look into what a mesh collider is though.  I have not worked with one yet.

Share this post


Link to post
Share on other sites
hpdvs2    1017


[quote name='DrEvil' timestamp='1357252348' post='5017281']
Any reason why you aren't generating a mesh from script and using a mesh collider to create a more optimal collision representation on 1 object?
[/quote]

 

Because I didn't know how,m particulary, I had never even looked at it before.  Fortunately I found a good example, and I will be switching my code to use this now. :)

 

http://blog.nobel-joergensen.com/2010/12/25/procedural-generated-mesh-in-unity/

Share this post


Link to post
Share on other sites
hpdvs2    1017

I looked up Collider Meshes, and found that it creates just a single GameObject, I.e. 1 texture for the whole thing.  This doesn't work for my needs.  

 

I'm not sure what I was doing wrong with a plane, but it wasn't a good option any way, since a plane is actually broken into about 200 triangles (10x10 grid, each of 2 triangles). A cube is built from 6 sides with 2 triangles each, which actually costs less performance.  However, I figured out how to recreate the mesh, by rebuilding it with only 2 triangles, and then apply the textures, normals and bounds.  

 

Anyway, I resolved it.  Also, part of my problem was the position, I had everything positioned upside down.  could have worked, but would have been confusing to maintain over time.

 

Thanks.

Share this post


Link to post
Share on other sites
DrEvil    1148
I would texture atlas your tiles and just use the right texture coordinates. Then you get the dynamic stuff with the best performance. If your game is simple/small enough just stick to what's easiest to work with. If the map is large though that technique will be slow for rendering(lots of draw calls) and collision

Share this post


Link to post
Share on other sites
hpdvs2    1017
would texture atlas your tiles and just use the right texture coordinates.

 

I just looked up a texture atlas, and perhaps I miss understood it, or if there are special features in Unity 3D for it, but I have an issue it doesn't resolve.

 

The tiles will need to change.  for instance, an explosion happens over grass, and there will no longer be grass, just charred dirt and gravel.   I'll need to change out what these tiles are, on a regular basis in Real-Time.  

 

Also, I don't actually need to do 3D collision detection here.   Because my code contains a 2D array for a height map (managed), I can just apply the units position on the height map to define what Z level they are at.  I can reserve collision detection for explosions, moving elements and buildings, but the ground can be fictitious in the physics sense.  Rendering will still be quick because I'm using low polygon counts, and the area of visibility will be quite small.  (maybe 100x100 tiles typically.)

Edited by hpdvs2

Share this post


Link to post
Share on other sites
DrEvil    1148
Fair enough. 100x100 tiles is not an insignificant number of draw calls. You should be able to dynamically change the texture coordinates in the mesh to account for dynamic changes in tiles all while keeping. I'm not sure what the break even point is with regards to draw calls versus dynamically changing the texture coords. Keep it in mind though if you run into performance issues. If this is a simple game for pc might not make enough of a difference. If you are targeting mobile it might be significant.

Share this post


Link to post
Share on other sites

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

Sign in to follow this  

  • Similar Content

    • By ilovegames
      You - the chief doctor of the hospital. Working late into the evening, did not notice the majority of hospital workers went home ... But where you disappeared the night shift is also not known. Hastily taking important documents, go home, but something went wrong as usual ... Can you get out of the hospital alive?
      Download https://falcoware.com/AtTheHospital.php



    • By Gator Man
      Game Concept Doc: https://docs.google.com/document/d/1B5eS_eGMke3gk5xPyMLekZY1T7uE2q1pO4vFdALIOC8/edit

      We are looking for every position. From Game designer, to marketer, to programmer, to 3D modeler. Any further questions can be discussed through discord
      DISCORD: Gator#5635
    • By ilovegames
      Wind Of Fear is a game where we have to kill different kinds of waves of monsters packing weapons. The main goal is to survive the waves and pump up your own weapons. There is a store where you will buy new weapons, scattered crystals that restore your life are also on the map!

      Controls:
      WASD - Walking
      Shift - Running
      Mouse1 - Attack
      Space - Jump
      ScrolDown - weapon change
      T - Deceleration of time
      G - Bleed your weapon
      Esc - Exit, pause
      Download http://falcoware.com/WindOfFear.php
       



    • By ilovegames
      Continuation of the first part of the game, Invention. While you were on the island exploring the underground laboratory, the infection was busy spreading throughout the world. In this episode, you have to go through a city populated by monsters in search of salvation aided by weapons that you will find during your travels. The gloomy atmosphere, music and atmosphere and a crowd of walking meat will keep you on your toes!
      Download http://falcoware.com/Invention2.php



    • By Jacob Laurits Besenbacher Kjeldsen
       
      Intro - "The challenges of dynamic system design"
      Custom Quest evolved during development, from a minor quest system used for our own needs in our own game production Quest Accepted, to something entirely more dynamic and customizable, now finally released, these are our thoughts on quest design and developing standalone subsystems. 
      Splitting what is a major production for a small indie team, into smaller installments such as a quest system was a good idea we thought, this way we can get some releases out there and fuel the development of our game. But building a system that works for yourself is one thing, building a unity plugin that will let other developers create quests, missions, and objectives, you would never have thought of is something else entirely.
      The first thing we had to realize was that when building a quest system, the task is not to design great quests, the task is to enable the users to create great quests.
      That still meant we had to find out what good quest design is and what a quest really is.
      Our task was to create a system where the user is free to create creative engaging and rewarding mission experiences for their players.
      What is a quest? - "Cut to the core"
      First off, we need to know what a quest really is.
      A quest is the pursuit, search, expedition, task or assignment a person(s) does in order to find, gain or obtain something.
      In games, quests and missions function in many different ways depending on the genre.
      A single game can contain a multitude of different types of quests put together in just as many ways. In an MMO, for instance, quests are vehicles for the story and the player's progression. In many cases they are formulaic and simple, some can even be repeated, there are hundreds of them and everyone can do them. In other games quests are for single player campaigns only, here they shape each level giving the player a sense of purpose.
      Quests can span the whole game or just be a minor optional task on the way, there are so many design philosophies and creative quest designs that we had to narrow it down and really cut to the core of what is needed for good quest design.
      What all quests have in common is the task, the criteria for successful completion of the quest, and the reward, the goal of the quest, what the player gets out of doing what we ask of him.
      Quests cover an incredible variety of tasks so it was important for us to base our decisions on thorough research. In our research, we found that there are three layers to quest design.
      The type, the pattern and the superstructure.
      Quest types exist within quest patterns and quest patterns exist within the quest superstructure.
      We found that there are 8 basic types of quests these are the various tasks/criteria the player must do in order to complete the specific quest.
      There are 12 quest patterns. These are ways designers can use their quests, connect multiple quests set them up in engaging ways or teach players how to interact with and get the most out of the game world creating variety and engaging the player.
      Enveloping the patterns is the quest superstructure, the overall structure of quests in the game, we found that there are two main ways of structuring your quests.
      Historically quest have a quest giver, an NPC or object that informs the player about the quest, what they need to do, the story behind it and perhaps even what their reward will be should they complete the quest.
      Quest types - "Do this, do that"
      The core task each quest consists of, the criteria for completing part of or all of a single quest. These are the actions we want Custom Quest to be able to handle.
      Kill
      Probably the most basic quest type, the task is to kill something in the game, for example; kill 10 goblins. Gather
      Again very simple, the task is to gather x things in the game world, collecting berries or the like. Escort
      The player must escort or follow a person or object from point A to B while keeping it safe. FedX
      The player is the delivery boy, they must deliver an item to a person or point. Defend
      The player has to defend a location from oncoming enemies, often for a set number of waves or time. Profit
      The player must have a certain amount of resources to complete the quest, contrary to gather quests these resources are resources the player would otherwise be able to use himself. Activate
      The player's task is to activate/interact with one or more objects in the game world or talk to a number of NPC’s. In some cases, this must be done in a certain order for a puzzle effect. Search
      Search an area, discover an area of the game world. This is useful for introducing areas of the map to the player and giving them a sense of accomplishment right off the bat, showing them a new quest hub or the like. Quest Patterns - "An engaging experience"
      Tasks are one thing, and in many games, that might be plenty but we wanted custom quest to let the users create chains of quests, specialize them and set them up in ways that draw the player into the experience, there are many ways to go about this.
       
      Arrowhead
      The most basic quest pattern, the quest chain starts out broad and easy, the player has to kill some low-level cronies. The next quest is narrower, the player must kill fewer but tougher enemies, lets say the boss' bodyguards. The last quest is the boss fight, the player has killed the gang and can now kill the boss. This quest pattern is very straightforward and works well, giving rewards either at every stage or only when the boss is dead.  
      Side stub 
      A side stub is an optional part of the overlapping quest. Lets say quest A leads to quest C but there is an option to complete a side objective B, which makes completing C easier or it changes the reward, for example. The player must escape prison, the side stub is “free the other prisoners” in this example escaping with all the prisoners is voluntary but it might make it easier to overpower the guards or the prisoners might reward the player when he gets them out. The side stub differs from a generic side quest in that it is tied to the main quest directly.  
      Continuous side-quests
      These are side-quests that evolve throughout the game, one unlocks the next, but they are also affected by external requirements such as story progress. This pattern is often found with party members in RPG games, where the player must befriend the party member to unlock their story quests.  
       
      Deadline
      As the name implies these quests are time sensitive. The task can be of any type, the important thing is that the quest fails if time runs out. This could also be used for a quest with a side quest where the side quest is timed for extra rewards but the main objective is not.  
       
      Deja-vu quests
      This kind of quest pattern gives the player a quest they have done or seen before. In some cases, this “new” quest will have a twist or something that sets it apart. It can also be the same sort of quest that exists in different areas of the game world, perhaps there is more than one goblin camp? or perhaps the player has to pick berries daily.  
       
      Delayed impact
      Delayed consequences of a previous decision. Often used in games where the story is important and the players’ choices matter. These quests are tied together without the player knowing. Let's say the player is set the optional task of giving a beggar some gold to feed himself. The player gives the beggar a few gold and is on his way. The next time he meets the beggar the beggar has become rich and rewards the player for his kindness with ten times what he gave.  
      One of many
      The player is presented with a number of quests, they have to choose which one to complete, they can only choose one. The others will not be available.  
       
      Hidden quests
      Hidden tasks that aren’t obviously quests at first glance or are hidden away for only the most intrepid players to find. This could be an item the player picks up with an inscription in it if the player then finds the person the inscription is about he can get a reward for delivering it. A good quest pattern for puzzles, these kinds of quests can really make the game world come alive and feel a lot more engaging, allowing the player to uncover secrets, Easter eggs and discover all of the world created for them   
      Moral dilemma
      Punish the bread thief who stole to feed his family? often used in games that have a good/ evil alignment level for the players, these kinds of quests make the player make a choice about what kind of character they want to play, they get to choose if their character is good or evil.  
       
      Side quests
      Optional quests, these quests are often found in level based games where the overall quest must be completed to get to the next level, the player can optionally do some extra tasks to get more points. The important part is that these are optional but they give the player a reward for, getting everything they can out of the game.  
       
      Tournament
      Tournament style quests, a series of quests that get harder as the player progresses. An example could be a gladiatorial arena if the player defeats five enemies one after the other he gets rewarded as the champion of the arena, but if for example, he fails at the third, the whole tournament is failed and he has to start all over from quest 1.  
       
      Vehicle missions
      Despite the name these quests are not confined to being about cars, these are simply quests where the players control scheme changes to complete the quest(s). An example could be; changing from running around in the game world to driving a tank to destroy a fort.  
      Quest superstructure - "The whole package"
      With quest superstructures, we are venturing into general game design. The superstructure is how the player is allowed to complete quests in the game world. It's basically a question of whether the game is “open world” or a linear experience.
       
      The diamond structure 
      The open world model, think games like The Elder Scrolls V: Skyrim, the player is introduced to the game through a quest, but after that, they can go wherever and do whatever quests they want. There are tons of quests of the above types and patterns, the player is free to pick and choose which to do, giving the player the illusion of freedom within the game world (the diamond). However, the game still ends by completing a quest that is locked and always a requirement to complete the game. This can, of course, be varied by different choices the player has made throughout the game or even have multiple endings. Quests can be concentrated into quest hubs, i.e. towns with lots to do or the like, but they don't have to be completed in a linear fashion  
       
       
      Linear hub structure
      This structure consists of a number of required “bridge” quests that need to be completed in order to unlock the next area or “hub”, each hub can have any number of quests, this could be a town full of people in trouble, each with their own quests and quest chains to complete, when they are all done, the player moves on to the next hub through another bridge quest. Limiting the quest size of the hubs will make the quest structure feel more linear and thereby the game linear, and creating larger more open hubs can make the player feel freer.  
       
      Outcome - "So many options!"
      The development of custom quest has been the quest to allow game developers to create quests and missions that use these types. However, no matter how well we have researched, some one will come up with a new and creative way of doing quests.
       
      The solution for us was to make the system more customizable. Letting users convert their quest prefabs to quest scripts that automatically inherits the core functionality, so the user can freely add their own additional functionality on top of the existing core
      Asset development as fuel - "A learning experience"
      Developing this way, splitting the production into sub systems that can function on their own and even be used by others is not something that should be taken lightly, but if you can build something lasting, something others can find value in using, then the final product will be all the better for it. Custom Quest started as a project we thought could be completed in a couple of months, it ended up taking 7.
      In part this is because we realised that if we were going to release the system, we might as well do it right, that meant creating a system that was customizable and robust, a system that can be added to the users game and not the other way around, a system we could be proud of.
      The experience of developing for other developers is quite different to developing a game. One that has made us much stronger as programmers and as a company, it forced us to think in new ways, in order to create a dynamic and customizable solution. Custom quest has evolved from an asset we could use in Quest Accepted, into a tool others can use to create a unique game experience. All in all, the experience has been a good one and Random Dragon is stronger for it, I would, however, recommend thinking about your plugin and extra time before you start developing.
       
       
      Sources:
      www.pcgamesn.com -"We know you aren't stupid" - a quest design master class from CD Projekt RED
      http://www.pcgamesn.com/the-witcher-3-wild-hunt/the-witcher-quest-design-cd-projekt-masterclass
      http://www.gamasutra.com/ - Game Design Essentials: 20 RPGs - http://www.gamasutra.com/view/feature/4066/game_design_essentials_20_rpgs.php?print=1
      Extra credits - Quest Design I - Why Many MMOs Rely on Repetitive Grind Quests https://www.youtube.com/watch?v=otAkP5VjIv8&t=219s
      Extra credits - Quest Design II - How to Create Interesting MMO and RPG Quests https://www.youtube.com/watch?v=ur6GQp5mCYs
      Center for Games and Playable Media - Situating Quests: Design Patterns for Quest and Level Design in Role-Playing Games - http://sokath.com/main/files/1/smith-icids11.pdf
      Center for Games and Playable Media - RPG Design patterns https://rpgpatterns.soe.ucsc.edu/doku.php?id=patterns:questindex
       
      Special thanks to Allan Schnoor, Kenneth Lodahl and Kristian Wulff for feedback, constructive criticism and background materials.
  • Popular Now