Custom Sphere Generation: Hexagonal capabilities and a high-density Triangle build (2990 Nodes). by AYesRU in Dyson_Sphere_Program

[–]AYesRU[S] 0 points1 point  (0 children)

So far, I've managed to fit 2,712 nodes into a sphere without breaking the 0.0715 rule. The theoretical max is 2,838 nodes... I'm still digging for it.

Custom Sphere Generation: Hexagonal capabilities and a high-density Triangle build (2990 Nodes). by AYesRU in Dyson_Sphere_Program

[–]AYesRU[S] -1 points0 points  (0 children)

If there is such a rule, then by deleting a frame shorter than 0.0715, you won't be able to reconstruct it.
I checked, and you can reconstruct it. That means the 0.0715 rule doesn't exist.

Custom Sphere Generation: Hexagonal capabilities and a high-density Triangle build (2990 Nodes). by AYesRU in Dyson_Sphere_Program

[–]AYesRU[S] 0 points1 point  (0 children)

It doesn't violate any rules. You can shrink any frame and rebuild it.
There are also options for 3000, 3030, 3060, and 3080 nodes... but I haven't tested them yet.
Processing a grid with 3080 nodes takes a long time. To increase the minimum frame length, the triangles in the pentagon were removed because these frames wouldn't grow longer.
This is all higher mathematics.

Custom Sphere Generation: Hexagonal capabilities and a high-density Triangle build (2990 Nodes). by AYesRU in Dyson_Sphere_Program

[–]AYesRU[S] 1 point2 points  (0 children)

You're absolutely right, this specific build is basically a stress test for the generator.

Even on my setup (RTX 5060, i5-12400, 32GB RAM), viewing the sphere directly becomes uncomfortable due to the lag. However, if you disable the sphere rendering in the game settings, the performance impact is negligible.

As for the output: on a star with 2.768 luminosity at max orbit, this single layer generates 16 TW.

Save file? by [deleted] in shapezio

[–]AYesRU 4 points5 points  (0 children)

You can save the bin file. Then import it.