Multiple scenes or one scene?

Question

Hello, something has been really troubling my mind recently.

I'm currently making an RPG with a vast world, and one of the first thing that pops to mind is how to make it in Unity. Should I use one large scene for the whole world (which would severely lag, I think - the world is really big) or should I make more scenes? I recall from a time when I was modding for TES that they divided the whole world by it's coordinates. That way, I could tend to one area, and give a much better finished product. However, I don't think a hovering platform would suit well, so... how can I make the game start rendering the scene that the player should transfer to when on the edge? Or, should I make one large scene, but only render and calculate the objects in proximity of the player?

I hope I didn't confuse you all, I'm quite so myself. If needed, I can further explain the question.

Thanks for reading, and any help in advance.

Answer 1

Best Answer

Answer by CodeMasterMike · Dec 10, 2012 at 06:49 AM

I think I would divide the world up in different scenes. And I would add these scenes into different areas.

So in the beginning, you load a scene from the area that the player is currently in. But only one scene, the start scene for example, and then keep track of which scene the player is currently in. When necessary you load the "neighbour" scene/s with Application.LoadLevelAdditive as the game goes by.

So when the player goes into a new Area (enters a house/elevator/new Enviornment which means the whole world will change to something new) then you load this scene with the normal Application.LoadLevel function. So then you would clear out some memory and other stuff you don't need.

And if the player would return to the old area he just was in, then you load the old scene with the Application.LoadLevel function.

And as the player progress through the new Area, or the old area, add new scenes with the LoadLevelAdditive function.

It would take some design-thinking, but I think that would be a nice and smart way to do a big RPG-game without too many loading scenes, or one huge map that will take a long time to load.

Add comment · Show 5 · Share

clunk47 · Dec 10, 2012 at 07:18 AM 1

Share

Dude thank you! I never took the time to find out what LoadLevelAdditive was, but read up about it. I say your answer should be the accepted one, because I was talking about enabling / disabling things, but this works way better by loading content from the new level into the current scene :D Thanks again.

frank45 · Dec 10, 2012 at 02:12 PM 0

Share

would that be not complicated..!!making vast number of scenes and loading each and everything..!!if i have an open world or huge map then what will i do..?

CodeMasterMike · Dec 10, 2012 at 02:31 PM 0

Share

This design idea would work on a open world as well. As I said, it takes some design-thinking to do, but its doable.

If you want to use a huge map, then you will have at some point, cut it up and only load parts of which you need, or else you will get into trouble performance-wise and memory-wise.

Using several different scenes that are loaded together makes it a lot easier to control rather than having one big map with thousands of objects with thousands of scripts running to the left and right. And you can load and close scenes as you need them, or not need them.

I would say almost all games with a bigger map uses some kind of technique where they either load a new scene seamlessly in realtime, or uses a "loading..." scene while loading the new content.

MilosM · Dec 12, 2012 at 04:16 PM 0

Share

The "loading..." idea would work perfectly. I'll have to think this out properly. Thank you all for your comments. You guys(and gals!) are the best!

clunk47 · Dec 12, 2012 at 05:12 PM 0

Share

Accept this answer! :D

Answer 2

You should use Triggers to achieve this.

Create a new GameObject to represent the trigger area. Choose the most appropriate shape. This will be the area that you have to enter in order to cause the teleport to occur.

Now select the new object you just made, and tick the "Is Trigger" option in the collider component, shown in the inspector pane. This changes the collider from a solid object to an area that you can walk into.

Un-tick the "Mesh Renderer" component, so that the GameObject becomes invisible.

You probably also want to specify a destination for the teleporter, and an easy way to do this is to create another invisible GameObject. This time however you don't need a collider either, so it's best to use "Create Empty" to create a completely empty GameObject. Name it "Teleport Destination".

Now, depending on how you want the teleporter to work, you need to either add some script to the teleporter object, or to the player object.

If you want the teleporter to teleport any object which enters it, add a script something like this to the teleporter object:

var destination : Transform;

function OnTriggerEnter(other : Collider) { other.transform.position = destination.position; } If you only want the player to teleport when it enters the trigger, you should make sure your player object is tagged as "Player", then add a check for this in your teleporter script, making it look more like this:

var destination : Transform;

function OnTriggerEnter(other : Collider) { if (other.tag == "Player") { other.transform.position = destination.position; } } See the Colliders Manual Page for more information about triggers.

Now for the camera. If your camera is parented to your player (as it is, in the case of the first-person controller prefab), then you need do nothing. The camera will be moved along with the player automatically.

If you're using a chase-style camera however, you'll probably want to make the camera jump the same relative distance as the player just jumped. You could do this by measuring the distance that the player moved, and then adding that distance to the camera too - something like this:

var destination : Transform;

function OnTriggerEnter(other : Collider) { if (other.tag == "Player") { var startPosition = other.transform.position; other.transform.position = destination.position; var moveDelta = other.transform.position - startPosition; Camera.main.transform.position += moveDelta; } }

Answer 3

Answer by Yharooer · Jul 12, 2013 at 05:52 AM

I would say split it up into multiple scenes. If its all one scene, and if the world is really big, then heaps of RAM will be used.

Add comment · Share

Multiple scenes or one scene?

3 Replies

Welcome to Unity Answers

Follow this Question

Related Questions