about the chained rocket launches. What if you were 1 frame too slow to queue up the next rocket? Are you then cursed to half the throughput?

It would be nice if the closing could be "inverted" so that as soon as the rocket is ready it will start to open up the silo again no matter where in the ...

being able to copy paste the blueprint grid settings around to other blueprints would be handy as well. Perhaps some kind of "inherit from book" setting.

You know for those people who like their block based designs and don't always end up starting aligned to the grid they saved in their libraries.

one little nitpick about the new design, when it has been landfilled over the lags just vanish into the ground, it would look cleaner to have little feet on them IMO

That sounds like a lot of complexity.


array prefetch will mean you end up blasting through the list at memory bandwidth speed instead of cache miss latency speeds.


Can't speak for Factorio's specific case, nor have I really thought about how it is specifically coded. But in many other cases ...

Entities require stable memory addresses and can move around anywhere (sometimes between surfaces) so they can't be put into some vector<thing>.


referential consistency can be solved with a chunked array.

from the mod api only players and vehicles can teleport between surfaces, sure treat ...

I think in general it isn't worth processing. You waste energy and might trash the cache.

Whether you skip or process, you still have to wait for RAM to deliver data for entities that do need to be processed. Might as well idle and wait than do pointless processing.


But doing array iteration ...

Put the inserters into an array and you remove the latency for looking up the next pointer. This then also allows splitting the array into threads (provided you do a few other things to make that possible too)

I think part of the complication is the skipping of processing certain entities - an ...

I would be surprised if the compiler didn't already do something like that. Large switch statements are a very attractive target for this kind of automatic optimization.

I find it not appropriate to describe Dominik's departure in the way you did it.


How else should we handle it? I want to be as transparent and honest with you as I can be.

You very much implied that the decision to release without the character gui is the main reason why he left. This could ...

SHiRKiT wrote: Wed Nov 27, 2019 9:19 pm IF there's a thing that impreses me, is that 20 members of the team later, and 5 years, and you gus still improve the performance by huge margins. Your dedication to this game is unparallel

this one was quite low hanging fruit though

will the LUT allow for things like emissive (glow in the dark) patches?

That would be nice to add to the vehicles and the warning concrete.

You can use a coroutine:

local mycoroutine = coroutine.create (function ()
run_every_5_seconds
if something do
do stuff
coroutine.yield()
do more stuff
end
coroutine.yield()
do more stuff
etc.
end
end )

script.on_event(defines.events.on_tick, function(event)
coroutine.resume ...

In the simplified map how does the heuristic calculate the distance? You could be just crossing one tile at the edge of the chunk or go all the way across the chunk. Worst case there could be a spiral pattern so it takes 100+ tiles to cross a chunk.

So what's your trick there?


The trick is ...

EpicSlayer7666 wrote: Fri Sep 20, 2019 9:07 am a better fix might be for a fix limit of paths to be created from a artillery shot. so they will still look around but not spam new paths...

One quick hack for that is to make all responders of a artillery shot into a single attack squad with a single path to follow.

And yes, the train status gets mixed into the signal. But that is already the case for chain signals in the blue state. The signal can only decide to let a train pass or block it by knowing which path it wants to take. I only add the length to the state as well.


Not quite, it is different ...

And this issue is about just that limitation. It doesn't have to be that way. Rail networks should be upgradable to larger trains without requiring a complete signal replacement.


There are plenty of places where moving to longer trains creates issues in a network designed for a certain size ...

Agree definitely limit on the total number of bots not available. It is easy to do things that will instantly try to use thousands of bots (new requester chests, placing blueprints, destruction planner, etc.).


I found that using "one percent of bots should be idle" was ... passable, but did ...

If it were me I'd have added another edge case, if the packet has too many selection changes, delete them all from the queue instead have it send single absolute value.

But I'm sure there'd be issues with that as well

LuaControl::opened doesn't do any distance checks in the Lua API. It's simply a part of the game logic that a player can't open something they can't reach. There's no "override" behavior it's just baked into the logic of anything opened if it's out of reach it's closed.

So the answer to this ...

most of those biter things sound like a "(hostile) entity made an action" problem rather than a "lets move a biter" problem.

The charting system only needs to know the location, range and force of each charting entity. IOW give it a std::vector holding a struct{bool alive;int range; Location loc ...