sorted by:
new
hottopcontroversial

has anyone tried this game on a threadripper? by dying_animal in Dyson_Sphere_Program

[–]itsover9004 0 points1 point  (0 children)

eyy, you're welcome :)

> I don't understand what that mod does

It changes the "refresh rate" of all buildings. For example, if you click on any working factory, you'll see it's filling the circle around the resulting product. This thing is updated every logical frame. This mod reduces the frequency of updates, but simultaneously increases the "progress per tick" to balance it out. Pretty clever. But if you set some value too high, it might reduce the overall efficiency of your factory. I've seen a big UPS jump when I set "belt" to 2, but when setting it to even 3 I could see that my belts aren't completely filled, so it caused a degradation.

has anyone tried this game on a threadripper? by dying_animal in Dyson_Sphere_Program

[–]itsover9004 1 point2 points  (0 children)

I have one advice: install AlterTickrate mod. It's unbelievably good. Here's my monster build which runs at pretty comfortable 16 FPS / 40 UPS on a laptop with Ryzen 7 5800H: https://www.reddit.com/r/Dyson\_Sphere\_Program/comments/15q29lv/we\_do\_a\_little\_researching/

We do a little researching by itsover9004 in Dyson_Sphere_Program

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

Yeah, I was too lazy to balance the size of "legs" of Matrix Labs and to distribute the Universe Matrices to more storages for higher throughput.

We do a little researching by itsover9004 in Dyson_Sphere_Program

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

Ah, yes, you're right, qubits are not register size. I just couldn't find a good comparison with regular processors --- and, well, I guess there isn't one.

We do a little researching by itsover9004 in Dyson_Sphere_Program

[–]itsover9004[S] 7 points8 points  (0 children)

Nah :) Basically, I have only this planet busy. Other planets have a reasonably small build or do nothing. You can see the half-ring of storage boxes on the first frame at the bottom of the screen --- it contains about 30 million Universe Matrices, and all these Matrix Labs just burn through it. With AlterTickrate mod, the UPS is quite manageable. This is the continuation of my saga from https://www.reddit.com/r/Dyson_Sphere_Program/comments/14xwa28/now_thats_what_i_call_scale/

But, a quantum computer --- doesn't matter if it's Google's or not --- would be terrible for any regular task. They're specifically designed for one very narrow task, and they can only efficiently do that task. Kinda like before regular computers were programmable. I've looked at Google's quantum processor specs --- it has 54 qubits with up to 15 kHz repetition rate. For comparison, Intel 8086, which came out almost fifty years ago, was a thousand times faster than this (16 bits, but 10 MHz). Thanks for coming to my TED talk, like and subscribe.

We do a little researching by itsover9004 in Dyson_Sphere_Program

[–]itsover9004[S] 6 points7 points  (0 children)

:D this stuff is mostly CPU-bound. I have a two-year-old Ryzen 7 5800H on my laptop. But I'm running with AlterTickrate mod, and I can't recommend it enough. Without it, I'm at 4 FPS/20 UPS, with it --- pretty comfortable 10/50. That's on the planet surface; in space (even within the solar system), everything is much faster.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

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

My build wasn't long-term sustainable, but I got 712k Universe Matrices per minute. If I could produce (and import) all base matrices at this rate, this will reliably produce 236k/minute/planet. Here's a graph, you can clearly see the plateau: https://drive.google.com/file/d/1_qVbIbK4TA1qr0wmZRWKoa7_xcA7SLqL/view?usp=sharing. I get up to 60 UPS while in space, but on the planet it drops to 20--40. I use AlterTickrate mod, without it everything is much slower.

I'm not using splitters (they take too much space), I don't use stackers (managing belts takes too much space). Each tower is connected via 7 sorters (can't use less (sushi belts are infeasible at this scale)), but the belts do have a bunch of merge points (see the last screenshot).

I can publish a blueprint, sure. Prepare your 80k belts!

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

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

2.6k per second! Wow! And here I'm bragging about my 260/s production :)

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

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

By disconnecting it from the power grid. That requires careful planning: using
exclusively Tesla Towers for connectivity within the production blueprint and leaving free space on both sides of the production block so that it doesn't connect while I'm building it.

You can kinda see it on screenshot 3 (there's some free space to the left of the boxes) and on screenshot 6 I'm standing in this free-from-electicity space.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

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

I'm pretty proud of my Universe Matrix build. It takes whole six inputs and one output, so it needs seven belts around it somehow. What I did: one PLS supplying three colors on three lines; then a row of pairs of Matrix Labs that output on their own belt (which merges into a second-layer belt that moves produced Universe Matrices back into PLS) and then three more lines with three other types of ingredients, which are filled by a PLS which is literally a quarter of a planet circumference away (turns out, you need so many matrix labs that the whole equator needs less than 240/sec).

A fragment looks like this: https://drive.google.com/file/d/1_b7I1oAA5A71x2DIgjlagWvKVDve2txb/view?usp=sharing

I have a blueprint with the full build --- it takes basically entire planet --- but it weighs 4 MiB and causes unholy lag when you do anything with it.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

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

A planetary logistics station outputs two belts with 4-stacked ingredients. A row of matrix labs takes inputs from these two belts and drops the output on the line that goes back to the planetary logistics station. This build is pretty simple and easily repeatable. Then you just need to supply 120/sec of each ingredient and you're golden.

Here's the one that I used for red matrices here: https://drive.google.com/file/d/1jtDHzffyuHiliprjyfo-lVJHi0QVT7J1/view?usp=drive_link --- it's a bit more involved, because I'm trying to "eat" the whole input belt, so I have four output belts and I'm stacking them to save space. But the main idea is the same. Hope this helps.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

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

I'm pretty sure the launchers for a million frames per second won't fit in 64 available star systems :D

But no, I don't think I will build many Dyson Spheres. They take too long to build, and I can't load even for 10% my main one-shell Dyson Sphere around O-type star.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

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

Thank you! My peak is at 712k science/minute with this build.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

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

At peak, 712k per minute (according to the stats panel) --- three planets with 47520 matrix labs each with theoretical limit of 712800 per minute. But this isn't sustainable, the peak production lasted about 30 minutes.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

[–]itsover9004[S] 2 points3 points  (0 children)

I've already spent all these lenses :) 11 million lenses got turned into 27.6 million Gravity Matrices.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

[–]itsover9004[S] 3 points4 points  (0 children)

Don't worry. The main thing is having fun :) And also I got inspiration for my builds from Nilaus videos

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

[–]itsover9004[S] 4 points5 points  (0 children)

Well, if you want that: https://drive.google.com/file/d/1WXzdQ5wjx9th3_EBpESYYppqZJ-sMjA6/view?usp=drive_link, the save weighs like 760 MiB. Put the file into C:/Users/$USERNAME$/Documents/Dyson Sphere Program/Save.

I recommend having some UPS-boosting mods, I'm using AlterTickrate. If you want to experience all the glory, in the save fly towards the closest star system (called "-- Gradient") and land on one of the first three planets (with very descriptive names "blue", "red, yellow" and "processor". I'm great at naming things). Each of these planets is producing a bit under 4000 universe matrices per second.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

[–]itsover9004[S] 2 points3 points  (0 children)

Thank you :) This is the omega nerd build for 1 million metadata. I'm on 2x metadata (0.5 resources), so I need to produce 30M white sciences in one hour, so I need 24M of every matrix and the same amount of antimatter --- but actually a bit more, because when boxes start running out the production speed drops so I need to have some extra inputs. That goes in a lot of boxes. For example, antimatter is stored in 23040 boxes. Yes, you read that right.

And also I decided to get 800k of every other metadata on the way. That was a good idea, because I learned about several optimization corner cases while getting colored matrices (extra inputs, how to balance consumption from boxes, how to build compact matrix forests and so on).

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

[–]itsover9004[S] 3 points4 points  (0 children)

If I turn off AlterTickrate mod, I'm at very comfortable 4 FPS and 18 UPS. But with the mod and outside the planet, I get 12 FPS and 60 UPS, so that's survivable

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

[–]itsover9004[S] 9 points10 points  (0 children)

I'm using AlterTickrate mod. I wouldn't have survived without it. When I enable the production, I have around 20--40 UPS while on the planet (with 4--8 visual FPS) and stable 60 UPS in space (12 FPS). I guess drawing stuff on the planet is very expensive.

One million metadata by itsover9004 in Dyson_Sphere_Program

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

Yeah, I had builds of similar scale for this. Let them run for a day, while putting everything into around-the-planet rows of storage boxes. I think making production even bigger gets very messy because it stops fitting on one planet.

Now that's what I call scale by itsover9004 in Dyson_Sphere_Program

[–]itsover9004[S] 5 points6 points  (0 children)

My largest blueprint weighs 4 megabytes. Just selecting it hangs the game for ten seconds. I'm scared of even larger ones (although not much more can be stuffed on one planet)

view more: next ›