Since the 0.12 stabilization is going quite nicely we sat down yesterday with kovarex to make an actual plan for the 0.13 and mid term future. We decided to promise bit less and keep up the promises this time :)). Another motivation has been to start polishing things and filling "holes" th...

Your central server thing. A to S to B, B to S to A.... This is the stuff I was trying to tell you to do back in 0.11 when everyone tried to argue that it wasn't possible with Factorio. Central server system instead of Peer to Peer. Yeah, there has been quite some confusion between using the peer-t...

Greetings from furnace-like Prague: http://www.factorio.com/blog/post/fff-99

Thanks for the report. We have made some tweaks to the unstuck mechanism. This will be present in 0.12.4. The given save now works fine (the spitter gets unstuck, continuous in his attack and gets smashed by the turrets). However the mechanism still needs to be tested so lets see if it doesn't bring...

Thanks for the report. This will be fixed in the 0.12.4.

At the moment there are limitations to MP connections. Basically it is a pure peer-to-peer at the moment. Because of NAT-punching sometimes player with private IP addresses can play together as long as they initiate the communication via a public IP client / server. However if the server and one of ...

We are aware of this but due to how the system internally works it is not a straightforward fix. We will probably attend to this during fight revisit in 0.13. Moving to minor issues.

No, it's not fixed but got worth. 0.12.0 worked without any problems on my iMac, OS X 10.10.4 (Yosemite). But now 0.12.1 crashes before loading screen without any trace of logs at all, like infinitehubgear said before. You must have done something that only works on legacy Macs... Btw my iMac runs ...

There is no artificial cap on multiplayer map speed. What is fixed is the amount of network updates (that is 60/s) however that still allows for higher game speeds than 1. But it still puzzles me why not aligning to vsync (done by changing game speed to slightly > 1) fixes the stutters. I have exper...

The sound stuff on the stacktrace might be in the different thread. Have you been able to reproduce this since the last time? Do you happen to have the save reasonably short time before the crash?

Seems like a latency hiding issue. I tried to reproduce but without success so far. Two questions:

1) Do you have latency hiding switched on (in other settings)
2) What is your game's latency in ms?

It is not a bug in the code (actually the reason why it worked before could have been a bug in the code) but I agree that functionally the basic / burner inserter should be able to grab anything from the basic belt. So moved this to minor issues.

You're right, it gets repaired, and it is a big improvement over 0.11, that's the reason I put "minor" in the title. I made the post because I really don't want the game to be the cause of epileptic seizures ;) This is an issue with latency hiding. I also consider it a minor issue, nevert...

That is intentional behavior.

We have changed the timeout mechanism to be super relaxed during map upload / download. This should fix the uploading on slower lines. If the problem persists in 0.12.2 please report again

Ok, have you used automatic updater for anything else except from the scenario pack? Do you use a firewall? Could you maybe experiment with giving it an exception for Factorio?

This is imho not really factorio problem, rather an OSX thing.

Minor but still fixed for the 0.12.1.

There is now an updated version of scenario pack - do you still encounter this problem?

Is this reproducible?