I've noticed a problem with the "Easy Livin'" achievement on build EX1 513-469473 in Spaced Out!
I built a sweeper to supply two kilns with clay and coal to make ceramics. The sweeper also puts the ceramic onto a conveyor. The system logs about 50 to 60 deliveries per cycle. My dupes, in the course of making food and other minor duties, performed around 20 to 40 deliveries per cycle. This should get me the achievement in 5 cycles flat, but it doesn't. Instead, if the dupes perform a delivery before the auto-sweeper does, it resets the 'auto-sweepers out perform' check box. In fact, if there's a burst of dupe activity early in the cycle, such as the dupes fertilizing all the crops, and it pushes the number of dupe jobs above the auto-sweeper's numbers, it resets the count, even if by the end of the cycle the auto-sweepers perform twice as many deliveries as the dupes.
I'm not sure if this is intended behavior or not, but it makes this achievement really annoying. I basically have to lock my dupes down for several cycles to ensure that a dupe won't perform a delivery right at the start of the cycle.
** NOTE ** I am unable to provide a log file, as I can not find it. I found one from February in the "ONI.bak" folder, but I can not find an "Oxygen Not Included" folder. Attached are screenshots of this unrelated issue. Strangely, I also can not "Browse FIles" from the steam interface. I am not using cloud saves, but I can not find where it is currently saving my games. Clearly I've got some other issues going on -- but these issues shouldn't be affecting the achievement tracker. HOWEVER, as it will not allow me to submit a bug report without a log file, I am attaching an intentionally blank file.
Build a system to produce a lot of sweeper activity through the course of a full cycle. Have a dupe perform 1 delivery before the sweeper goes active. Notice how "Auto-Sweeper outperforms" checkbox remains blank at the end of the cycle even if that 1 delivery is all the dupes performed.
A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now