Simple Questions and Short Answers

[Loewchen]

I have watched bunch of videos and read factorio wiki about rs latching. I think that my contraption dont reset or set. Can someone give it a glance?fact.jpg

You set it to start inserting when there are 300 coal in the chest and stop when there are 101 coal. Flip the values of the two conditions or rearrange them so it starts at 101 and stops at 300.

[ssmikis]

You set it to start inserting when there are 300 coal in the chest and stop when there are 101 coal. Flip the values of the two conditions or rearrange them so it starts at 101 and stops at 300.

Thank you

[ssmikis]

You set it to start inserting when there are 300 coal in the chest and stop when there are 101 coal. Flip the values of the two conditions or rearrange them so it starts at 101 and stops at 300.

It starts at 100 and stops at 102. Memory doesn't hold.

fact2.jpg (252.69 KiB) Viewed 749 times

It seams that putting signal in the middle helped. Its soo finicky

fact3.jpg (171.33 KiB) Viewed 739 times

[Nidan]

You set it to start inserting when there are 300 coal in the chest and stop when there are 101 coal. Flip the values of the two conditions or rearrange them so it starts at 101 and stops at 300.

It starts at 100 and stops at 102. Memory doesn't hold. fact2.jpg

If you want to start it below 101 coal and stop above 300 coal, you forgot to flip the comparison on the second condition; it needs to be < or <=.

The first condition says when it should start. The second condition says whether it should keep going (not when it should stop).

[ssmikis]

If you want to start it below 101 coal and stop above 300 coal, you forgot to flip the comparison on the second condition; it needs to be < or <=.

The first condition says when it should start. The second condition says whether it should keep going (not when it should stop).

Thank you for your input

I tried both conditions <, < or =, >, > or =, mixed conditions with < ,>. but always keep the same order of conditions ( like in videos i saw) what did the trick ( it seams) changing order of [AND] condition ....I am lower than beginner at this point.

[Tertius]

Stop trying arbitrary conditions without understanding and start thinking about what you want to achieve.
(I guess) you want to achieve this:

• if the chest has more than 300 items, enable the inserter to take items out of it
• while the chest has between 100 and 300 items, keep the inserter enabled
• stop the inserter if there are less than 100 items in the chest

This list can be written in a different way to express when to enable the inserter:

• if the chest has more than 300 items, enable the inserter
• if the chest has more than 100 items and the inserter was enabled before, enable the inserter

You wired the inserter, chest and combinator correctly, especially the loopback wire with the combinator, so the previous state is available for the new state.
So we can code the second list directly into the combinator:
condition:
coal > 300
OR
[coal > 100
AND
enabled = 1]

output:
enabled=1

[Loewchen]

You set it to start inserting when there are 300 coal in the chest and stop when there are 101 coal. Flip the values of the two conditions or rearrange them so it starts at 101 and stops at 300.

It starts at 100 and stops at 102.

Because for some reason instead of just swapping the values of the conditions you randomly changed an operator. Get the original state: viewtopic.php?p=685495#p685495 and change the 300 to 101 and the 101 to 300.

[kitters]

I get a recycler that is fed with infinite supply of green chips and feeds a single assembler that builds green chips. Assemblers speed is a bit lower, so the recycler stops periodically because is overfilled. But assembler should never stop, so I thought. But for some reason I see assembler stopped, starved on iron, and the recycler stopped, overfilled with coppec cables. WTF? The problem is consistent. ALWAYS copper overfilled, never iron.
The ratio of cables and plates should be right. On average. In a long run. Is it a round error in the code?

[kitters]

Update.
Okay, it gets a lot of testing.
But It appears a recycler can be overfilled either with plates or with cables.
In that case it's how it's supposed to be.
Diviation from average increases with amount. Like it's ulikely to get 10 less heads than tails in 20 throws, but expected in 1000 throws.
When this deviation exceeds the stack size... it cloggs.

[000]

Hopefully a simple enough question for this thread.

I've encountered some flying enemies on Gleba.

I have lasers in my power armour. They target the big, ground-based creatures, and the little starfish, but always ignore the flying bee-like creatures.

Even when everything else is dead or I've run away so there is nothing else for them to target, lasers still won't target the bees.

I have no ammo most of the time because of the difficulty getting iron. Lasers are my only weapon.

Fortunately, the bees seem to engage in kamikaze attacks so I only ever get hit by them once.

I have tried to shoot the bees with ammo but can't seem to target them myself. They're fast and I don't have fast fingers, so it's possible I couldn't aim properly.

I'm concerned about taking on bigger nests, or otherwise getting unlucky with bee-heavy attacks.

Is there a reason lasers won't target them? Is there something I can do to make manually targeting them easier? I always thought Factorio had very good aim-assist, but the bees seem exempt from this system.

[wobbycarly]

These are the projectiles launched by the Strafers (the spider-like creatures) and cannot be destroyed once launched (at least I haven't worked out how!) If you can run around in circles fast enough, they will eventually crash without hitting the player.

[Kyralessa]

You can't hit them with any weapon I know of, but if you have enough exoskeletons, you might be able to dodge them, and if you have some energy shields, then they won't hurt your health.

[000]

Thanks, that explains it! They did seem to come out of no-where. I hadn't noticed they were coming from the Strafers. If they're projectiles, it makes sense I cannot target them. We cannot target other player's rockets in PvP either.

Honestly, knowing they're not an enemy type of their own is a relief. I was worried about running into huge swarms of them.

Shields seem like a very good idea, actually. Thanks for that.