Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I agree but overall its not alot thankfully keen went with non animated trees/bushes/flora. Imagine a world of moving leaves. But overall they could make the planet bigger just not destroyable to its core. Kinda weird we can destroy planet but then you have a gravity well of nothing there.
trees are not static and are rendered by the physics engine since you are able to push them around like footballs. no amimations, thats true but: they are movable. gravity... rotaion... collision... the difference between low and high flora settings is hugh for a reason...
edit: its seems like: all movable parts ( even when not actuallymoving are rendered to move with speed of 0 meters per second wich lowers performance. thats the only possible reasons why non-moving large ships needs more performance than stations...
True well technicly they are untill acted upon thats the upside to voxel programing is the coding doesnt become active till triggered.
That's not really what I said. Obviously planets use more resources than asteroids, asteroids don't fill in all 15km of youre view distance with voxels and vegetation. My point was a 120km diameter planet with a view distance of 15km isn't going to be any easier to load/run than a 1200km diameter planet with a 15km view distance, as in both cases you have the same 15^2 km of terrain and vegetation loaded and nothing else.
objects dont have to be in your view range/direction to decrease your fps. fill a world with lots of stuff until your fps hits like 15 or something. than look in the oppositte direction. your fps wont turn back to the empty-world-fps like before.
its lowering your gpu usage, but thats just a piece of the cake. the fact, that you cant see stuff doesnt mean its not there...
Imagine exploring getting lost on a world 6 times current max id almost never leave id be running around for days if not a week to find the perfect place for a base.
I already do this on our current size planets... There's tons of beautiful spots for bases.
Interestingly enough i fly up to 20km look down and can somewhat gues were i would want to go. (this is were i build my ships so i dont do it just for the heck of it.) but would be nice to look down at planet and not be able to take in half the planet from that height all at once.
This game doesn't work. I get terrible lag. My computer crashes. Happens everytime I try to load a world with the entire solar system to scale on my TRS-80 with 512 k RAM.
Good one does anyone even game on the spec anymore thats like a computer from my childhood.
Except that is again not what I said. A 15km view distance is a 15km load distance, nothing beyond that point is loaded in memory or simulated in the universe, beyond very simple LOD meshes for distant planets, things other players are in range of, or areas being forced to stay loaded. It's not "out of sight" it is literally not being loaded at all.
Yup even happens durring 3d modeling i once worked on a model so big it actualy exceeded the render distance for the workspace. Did not realize i made it so big till i zoomed out.