Well I have small team of friends and we decided to make game, so a lot of problems causing us to think twice, wel first of all map, well map we thinking in future create a huge x> 1000k km, so only plausible solution is to cut into sections and render for client only 10km range(first we just thinking just stay in 100m), another thing is we make game in first person that you do actions in first person like you click, push or just watch it some things in game clock, compass, etc, next is keeping clients in 100km2(10x10) map if they in that position at least 100 that would be fine, how we should maintain it? and also weather and makes good looking in grapchic(we have talented 3d designer so he good with that), so main question which grapchic engine could provide us to these request? Thank you.

Also for objects object like house as a main object and child object is TV what should do in smart way if i want take out TV from house through game. Thank you guys for answers, I'd like to see smart answers, also if you dont understand(because in my head too much ideas), just say it and i try to rexplain it.

I have few ideas unreal engine and cryengine(damm it eats alive pc)

only 10km range(first we just thinking just stay in 100m)

10 square kilometers is huge.

Most of the bigger level maps I've worked with are on the scale of 1-4 square kilometers.

Yes, worlds need to be broken down. Unless your worlds are quite sparse or are automatically generated and populated, that is probably too large of an area.

so main question which grapchic engine could provide us to these request? Thank you.

Any of them.

All the major engines allow loading and unloading of world regions. It needs some programmer support and each one does it somewhat differently, but they all support it.

Also for objects object like house as a main object and child object is TV what should do in smart way if i want take out TV from house through game.

Object ownership models are based on the engine you use. You might attach the TV object to the player's avatar using a carry system, or you might have an inventory on the player where an interaction puts the object into the inventory, or you might do something else entirely. How that works is up to you.

Also, moving this to For Beginners. It is too topical to be in the lounge, and not concrete enough for most other areas of the site.

A map of 1 km square is a huge task in most games. Why not start with a 100 m square map? You might want to think about a sky dome.

Unity and Unreal engines are popular, but there are a bunch of others.
List of Game Engines on Wikipedia is informative.

Start really simple ! You can always work through a basic version control and evolve it.

First, you really don't want to start out with such advanced ideas as pushing a 1000 km^2 map when you are just starting out with a small team of HOBBY Devs....

Is it possible to do? Well, with clever compromises and the right game concept, sure. With cutting edge technology and A LOT of work, you could do it with even less compromises (see how No Mans Sky will do it... procedural generation and different scales).

Will you bunch of Hobby devs be able to pull something off like that, in a sane amount of YEARS, without compromising other parts of your game? No.

Really, start small, don't aim for the sky.

I see two routes

1) go for your insanly large map. But create a game where the scale of the game is also scaled up. You will never be able to fill a 1000 km^2 with interesting stuff in the scale you are talking about (you where talking about a TV, so I guess you want to make a first or third person shooter). Not without many more devs, working for years on filling that large map. Not without tons of expierience. Or going a procedural route, and still spending years on developing a procedural routine that actually come up with usable results.

But you can create such a map, and "scale up" your game. A strategy title for example. You have your map, filled with some larger buildings and point of interest. Units are large vehicles, airships or whatever, huge monsters, or whatnot.

You are basically building a 1x1 KM map, with a scale that implies a 1000 KM^2 map. That is not harder to do than a 1 KM^2 map at human scale, and might give you that scale if that is what you are after.

2) If you are more interested in normal human scale games, drop the idea of a 1000 KM^2 until you have built a 10 KM^2 map. Then drop that idea until you have built and filled a 1 KM^2 map.

Chances are by the time your 1 KM^2 map is filled with stuff and looking good, everyone in your team has come to grips with the harsh reality you will never in a single lifetime be able to fill a 1000 KM^2 map, at human scale, with assets and a meaningful game.

Then finally start building a GAME with that 1 KM^2 map.... because what is the point of your mad map building plans, without a game to use it in anyway?

Yes as i said in begginning start map will be only 100m2, also we develop systems from scratch and evolve it, sky dome is not perfect solution because our sky also have a use, snow, rain, thunder or just sun, and it will impact gameplay, we thinking in future development add planes so we need sky as accsesible place, and clouds as a object where you get through with your plane.

Have you built that map yet? Really, concentrate on smaller things first, and don't already plan your "Bigger than GTA V" game without even having a working game prototype and a modest map size built yet.

Chances are good that you underestimate the work needed to build all of that by several orders of magnitude.

You ever worked with volumetric clouds? What is your plan to make your map mesh seamlessly into the horizon if people can see it from high up? I could go on and on... but really, it doesn't matter. Don't worry about those things until you have the foundations in place.

"But I worry we go into the wrong direction and have to throw away parts of our work!" - Yes, we hear that a lot on these forums. Don't worry. You will throw away way more than just parts... its part of a normal learning process which all of you will have to go through. Which all of US go through on a daily basis. Getting too attached to your work is quite a big problem.

Chances are good your first few 3D Models suck. They might even look good in the modelling tool. Once imported you might find out they do not work for your game, period. Throw them away. Don't try to fix things that take ages to fix. Mark the time down as part of the learning process, start over, do it better this time.

Your first 1 KM^2 most probably will never get finished. You might still try to hand populate it with assets and find out that it literally takes you days to only arrange all the assets that make up a single house, its interiors and surroundings. Throw the map away. Either rework the concepts of your game (do you NEED to be able to enter every house?), or come up with more clever ideas (have pre assembled asset-bundles you can just place in your map in a single drag and drop operation... yes, every house made from the same asset bundle now has the same interior... does that matter? Write a procedural routine that places assets for you).

Your first few stabs at the actual game logic will suck. Nobody gets their game logic right the first try, and there is a good chance yours turn out to be non-salvageable. Make sure you don't spend to much time on it, if it does not work no matter what you do, throw it away. Come up with a better game design, and try again.

Don't plan for a great future that will most probably never come... try to do what you can do here and now, and learn from it. You cannot climb the mount everest with zero mountain climbing expierience and lacking equipment. Get expierience first on that small rock wall in your neighbour hood, then try the steeper one some miles away, and so on.

Last thing: Don't worry about which engine will allow you to build X when you haven't built ANYTHING yet. Just start out in any of them. Pick one.

As for MY recommendations, scratch CryEngine off the list. The runtime engine might producing quite good graphics, I am not sure about the performance though (given the games made with it tend to be used as testcases for now hardware BECAUSE they are extremly demanding).

The tools provided with the stock CryEngine where crap 2 years ago... haven't heard that they got improved in the meantime. Given that its mostly used by bigger studios that have the money to pay programmers to write better tools for the engine for their own projects, even though the engine is available for free makes me believe the tools are still as dated as they were back then.

You could give Lumberyard, amazons fork of CryEngine a spin. Yet I would still be catious as I am not sure if amazone really has improved those tools yet.

Unreal Engine 4 and Unity 5 are both good recommendations. I personally would go with Unity for total beginners as it just has better documentation and an easier to grasp interface, but then UE4 is close even in my opinion, and some people found it easier to get into than Unity.

Keep in mind that Unity 5 has some quite dated stock tools, terrain system for example is not that high-end... you can upgrade that by purchasing third party assets from the store at actually quite good prices, which often are better than what Unreal Engine 4 gives you. But of course, it costs something.

Unreal Engine 4 comes with way better stock tools, though I found it throws too much of it at you at the same time, making the editor quite cluttered and hard to grok.

Really, at your stage, you cannot go wrong with either. And changing engines later is way less of a hassle than you might think.

First, you really don't want to start out with such advanced ideas as pushing a 1000 km^2 map when you are just starting out with a small team of HOBBY Devs....

Is it possible to do? Well, with clever compromises and the right game concept, sure. With cutting edge technology and A LOT of work, you could do it with even less compromises (see how No Mans Sky will do it... procedural generation and different scales).

Will you bunch of Hobby devs be able to pull something off like that, in a sane amount of YEARS, without compromising other parts of your game? No.

Really, start small, don't aim for the sky.

I see two routes

1) go for your insanly large map. But create a game where the scale of the game is also scaled up. You will never be able to fill a 1000 km^2 with interesting stuff in the scale you are talking about (you where talking about a TV, so I guess you want to make a first or third person shooter). Not without many more devs, working for years on filling that large map. Not without tons of expierience. Or going a procedural route, and still spending years on developing a procedural routine that actually come up with usable results.

But you can create such a map, and "scale up" your game. A strategy title for example. You have your map, filled with some larger buildings and point of interest. Units are large vehicles, airships or whatever, huge monsters, or whatnot.

You are basically building a 1x1 KM map, with a scale that implies a 1000 KM^2 map. That is not harder to do than a 1 KM^2 map at human scale, and might give you that scale if that is what you are after.

2) If you are more interested in normal human scale games, drop the idea of a 1000 KM^2 until you have built a 10 KM^2 map. Then drop that idea until you have built and filled a 1 KM^2 map.

Chances are by the time your 1 KM^2 map is filled with stuff and looking good, everyone in your team has come to grips with the harsh reality you will never in a single lifetime be able to fill a 1000 KM^2 map, at human scale, with assets and a meaningful game.

Then finally start building a GAME with that 1 KM^2 map.... because what is the point of your mad map building plans, without a game to use it in anyway?

Yes as i said in begginning start map will be only 100m2, also we develop systems from scratch and evolve it, sky dome is not perfect solution because our sky also have a use, snow, rain, thunder or just sun, and it will impact gameplay, we thinking in future development add planes so we need sky as accsesible place, and clouds as a object where you get through with your plane.

Have you built that map yet? Really, concentrate on smaller things first, and don't already plan your "Bigger than GTA V" game without even having a working game prototype and a modest map size built yet.

Chances are good that you underestimate the work needed to build all of that by several orders of magnitude.

You ever worked with volumetric clouds? What is your plan to make your map mesh seamlessly into the horizon if people can see it from high up? I could go on and on... but really, it doesn't matter. Don't worry about those things until you have the foundations in place.

"But I worry we go into the wrong direction and have to throw away parts of our work!" - Yes, we hear that a lot on these forums. Don't worry. You will throw away way more than just parts... its part of a normal learning process which all of you will have to go through. Which all of US go through on a daily basis. Getting too attached to your work is quite a big problem.

Chances are good your first few 3D Models suck. They might even look good in the modelling tool. Once imported you might find out they do not work for your game, period. Throw them away. Don't try to fix things that take ages to fix. Mark the time down as part of the learning process, start over, do it better this time.

Your first 1 KM^2 most probably will never get finished. You might still try to hand populate it with assets and find out that it literally takes you days to only arrange all the assets that make up a single house, its interiors and surroundings. Throw the map away. Either rework the concepts of your game (do you NEED to be able to enter every house?), or come up with more clever ideas (have pre assembled asset-bundles you can just place in your map in a single drag and drop operation... yes, every house made from the same asset bundle now has the same interior... does that matter? Write a procedural routine that places assets for you).

Your first few stabs at the actual game logic will suck. Nobody gets their game logic right the first try, and there is a good chance yours turn out to be non-salvageable. Make sure you don't spend to much time on it, if it does not work no matter what you do, throw it away. Come up with a better game design, and try again.

Don't plan for a great future that will most probably never come... try to do what you can do here and now, and learn from it. You cannot climb the mount everest with zero mountain climbing expierience and lacking equipment. Get expierience first on that small rock wall in your neighbour hood, then try the steeper one some miles away, and so on.

Last thing: Don't worry about which engine will allow you to build X when you haven't built ANYTHING yet. Just start out in any of them. Pick one.

As for MY recommendations, scratch CryEngine off the list. The runtime engine might producing quite good graphics, I am not sure about the performance though (given the games made with it tend to be used as testcases for now hardware BECAUSE they are extremly demanding).

The tools provided with the stock CryEngine where crap 2 years ago... haven't heard that they got improved in the meantime. Given that its mostly used by bigger studios that have the money to pay programmers to write better tools for the engine for their own projects, even though the engine is available for free makes me believe the tools are still as dated as they were back then.

You could give Lumberyard, amazons fork of CryEngine a spin. Yet I would still be catious as I am not sure if amazone really has improved those tools yet.

Unreal Engine 4 and Unity 5 are both good recommendations. I personally would go with Unity for total beginners as it just has better documentation and an easier to grasp interface, but then UE4 is close even in my opinion, and some people found it easier to get into than Unity.

Keep in mind that Unity 5 has some quite dated stock tools, terrain system for example is not that high-end... you can upgrade that by purchasing third party assets from the store at actually quite good prices, which often are better than what Unreal Engine 4 gives you. But of course, it costs something.

Unreal Engine 4 comes with way better stock tools, though I found it throws too much of it at you at the same time, making the editor quite cluttered and hard to grok.

Really, at your stage, you cannot go wrong with either. And changing engines later is way less of a hassle than you might think.

Dude its a golden words, yes our first ever test map will be blank, later we modiffy it, but we want to put some mechanics that forced us to think about current games, yes from beggining we only concentrate on basics and prototypes, also we decided after we have very very very pre-alfa of game to show of some gameplay and ask here or where big community is do we should continue our development or just stop it. the main reason for big map is for planes, and dynamic gameplay. Anyways thanks for smart ideas.