This type of asteroid doesn’t occupy memory (except some small data for noise seed, position, etc.).
new version – asteroids that are procedurally generated at the moment they are required (player enters an area near the asteroid, random floating object gets in a collision with the asteroid, etc.). old version - that can be used for handcrafted asteroids in future scenarios/missions. There were only a few basic asteroid shapes.įrom now on, there are two types of asteroids: Until now, Space Engineers supported only asteroids that were fully loaded during the loading phase and then kept as voxels and triangles in memory. On top of that, all these asteroids are fully destructible and don’t consume RAM/memory. The “procedural asteroids” feature adds a practically infinite number of asteroids to the game world. As a result Havok doesn’t need to use double-precision math (physics calculations are faster in single-precision mode). In other words, the world in Space Engineers is split into independent clusters, wherein each object has its own coordinates relative to the cluster center. Clustering is totally transparent to users, it runs in the background and you won’t see it. A clustering algorithm guarantees that no dynamic object can be closer than 2km to the cluster border. Depending on dynamic objects density, cluster size can increase its size without limits. We solved it by clustering the game world into independent clusters of objects (minimal cluster size is 20km). The harder one was to change the integration between Space Engineers and Havok (so Havok can keep using 32-bit floating point numbers). We have modified all game objects to support double-precision 64-bit floating point numbers - this was the easy part. This data format has a certain precision, leading to visible imperfections on objects located further than 10km from the origin Until now, Space Engineers and its physics engine (Havok) were using single-precision 32-bit floating point numbers. How did we increase the precision of numerical computations? I hope you continue to do so.If you decide to use your ship to travel from one side of the game world to the opposite, and you will fly on maximum speed (115 m/s), it will take you 552 years (checking calculation: 2 x 6.6 AU / 115 m/s).įor all practical purposes, “super-large worlds” could be considered “infinite worlds”, but the limit is still there and we don’t want to lie to you. It's a ridiculous amount of fun watching someone else playing with my toys on youtube. Likewise those who have been downloading and enjoying my ships. If I start that build it will likely be a while before you, or anyone, sees me again.Īs always, I appreciate those who have been encouraging me. 
It looks like there is a lot of popular demand for a Galaxy class. My son has asked for a Promethius, and I plan to give it to him. The deeper I go, the more rewarding it is. but I suspect I only have one or two more of the larger ships in me before I take a break for a couple weeks. This Miranda has probably taken twice as long as the previous version, and I'm not done yet. but that means I'm fussing over details I never considered in the previous build.
The newer vessel is more powerful, better shielded, more fully decorated, better lit, and more combat-ready. It's striking to have my new motion picture era Miranda floating next to my recent TOS Miranda I've rendered angles and proportions I didn't even attempt in the older ship. Instead of getting faster, I'm getting slower as I dig deeper into the game balance and try to render finer and finer details. I did expect that as my experience increased, the builds would go faster. Somewhat to my surprise I find I'm pretty damn decent and getting better. when I started this hobby of rendering starships out of 1m blocks I had no idea how much fun it would be, how consuming, or whether I'd be any good at it.
0 kommentar(er)
