The core count keeps climbing. Some years back I had to buy an expensive dual socket board to get SMP. Nowadays my laptop has 8 cores. I got my first "dualcore" in around 2005 in form of hyperthreaded Pentium4. Next was quadcore q6600 about 2 years later. The next CPU I got was less than ...

Personally I'm glad circuit logic is just a) "tacked on" and b) does not increase factory productivity because I think it is arkward to set up, cumbersome to use or adjust and terribly bends my mind as it does not have any easily approachable code flow control structures or any way of addi...

Plastic is indeed side-fed from the blue belt on the east side which gets merged with the green circuits from the bus. You can come up with your own bus-design, just like others already have done. What I posted is meant as food for though, to be expanded and customized for your needs and visions :) ...

This explains it: Software versioning

If bus-style then vertical. For me the reason is the 16:9 resolution I'm using. If I branch off the bus horizontally I want to see as many contents of that branched department on the screen as possible. Also when the bus is vertical I can actually see the load balancing of the all the parallel belt...

Heck, why not simply use AA-lib?

Just see Boolean algebra (axiom 5, distributivity).


Edit: gosh, siggboy is right; disregard above as indicative, it's a nice read anyway

Busy waiting is "Bug by design". I also fail to see which problem you tried to solve with that from 0.12 You already did a "sleep(millisecondsPerCycle - (now() - timeOfLoopBegin)" ? You can also spawn a lightweight thread that only does a "sleep(millisecondsPerCycle)" ...

Busy waiting is "Bug by design". I also fail to see which problem you tried to solve with that from 0.12 You already did a "sleep(millisecondsPerCycle - (now() - timeOfLoopBegin)" ? You can also spawn a lightweight thread that only does a "sleep(millisecondsPerCycle)" a...

I really would like to see hitzu's graphics included, they're my favorite



But beggars can't be choosers I suppose.

Good work everyone!

siggboy wrote:Integer overflow will take 414 calendar days, if the game runs 24/7 at 60 UPS. It's nothing one should ever be worried about.

Well...

JackB1024, that was pretty cool! Respect.
Even without knowing or seeing the code I could understand what was going on from your explanation.

Klonan wrote:Seem like if the inserter wants to refuel itself but is already holding a piece of ore, it will derp out

Nice charset

I like it!

It ends up getting used for the next item. That was the bug that caused it to slowly use extra energy. So, hmmm, isn't this then creating the situation I described above with uneven timing between produced items because some get a headstart and falling into an earlier tick? Yes, it is. If we need 1...

Rseding91 wrote:It ends up getting used for the next item. That was the bug that caused it to slowly use extra energy.

So, hmmm, isn't this then creating the situation I described above with uneven timing between produced items because some get a headstart and falling into an earlier tick?

Fixed for 0.13.5. Now this got me interested :) Do you keep the energy overshot in the furnace as a "bonus" for the next item produced? Then how do you respect the fact you probably don't know what the next item will be (iron/copper/...) ? Or do you transfer the overshot energy in the fur...

It is not pessimism, it is realism. This is how you develop software - go for low hanging fruits first. I Just wish they fix landscape generation - then I move to 0.13 When developing software you don't fix ALL easy bugs at once. You leave few so that you can release fixes while you work on bigger ...

DemiPixel wrote:https://www.youtube.com/watch?v=Kry8lbrHjeY

Sadly not accessible for Germany.

Unfortunately, this video is not available in your country because it could contain music from SME, for which we could not agree on conditions of use with GEMA.

No, because he built the wrong code branch