Version 0.18.24

[FactorioBot]

Bugfixes

• Fixed version 0.18.23

Use the automatic updater if you can (check experimental updates in other settings) or download full installation at http://www.factorio.com/download/experimental.

[Gergely]

• Fixed version 0.18.23

What?

[CaveJohnson376]

Check 0.18.23 thread, if you don't understand, what the problem was there

[Kalixt]

Hello, steam experimental versions comming too ?

[Mathematician]

viewtopic.php?f=7&t=84862

[Windsinger]

Can this also be changed in the online version list please???

https://updater.factorio.com/get-available-versions

Currently still has this bit in it,

Code: Select all

{"from":"0.18.22","to":"0.18.23"},{"from":"0.18.23","to":"0.18.24"},

Is still causing issues if you use update scripts to push incremental updates.


F.e. a update from 0.18.21 to 0.18.24

Code: Select all

Checking for updates...
New version core-linux_headless64 0.18.24.
Wrote /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.21-0.18.22-update.zip, apply with `factorio --apply-update /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.21-0.18.22-update.zip`
Wrote /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.22-0.18.23-update.zip, apply with `factorio --apply-update /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.22-0.18.23-update.zip`
Wrote /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.23-0.18.24-update.zip, apply with `factorio --apply-update /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.23-0.18.24-update.zip`
Applying /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.21-0.18.22-update.zip ...
Applying /tmp/factorio-update.D3fcXm3LFo/core-linux_headless64-0.18.22-0.18.23-update.zip ...
Applying /tmp/factorio-update.D3fcXm3LFo/core-linux_headless64-0.18.23-0.18.24-update.zip ...
   0.000 2020-05-12 16:09:20; Factorio 0.18.23 (build 51520, linux64, headless)
   0.039 Operating system: Linux (Ubuntu 18.04)
   0.039 Program arguments: "/opt/factorio/krastorio/bin/x64/factorio" "--apply-update" "/tmp/factorio-update.D3fcXm3LFo/core-linux_headless64-0.18.23-0.18.24-update.zip" 
   0.039 Read data path: /opt/factorio/krastorio/data
   0.039 Write data path: /opt/factorio/krastorio [425025/468301MB]
   0.039 Binaries path: /opt/factorio/krastorio/bin
   0.048 System info: [CPU:       Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz, 8 cores, RAM: 64348 MB]
   0.048 Environment: DISPLAY=<unset> WAYLAND_DISPLAY=<unset> DESKTOP_SESSION=<unset> XDG_SESSION_DESKTOP=<unset> XDG_CURRENT_DESKTOP=<unset> __GL_FSAA_MODE=<unset> __GL_LOG_MAX_ANISO=<unset> __GL_SYNC_TO_VBLANK=<unset> __GL_SORT_FBCONFIGS=<unset> __GL_YIELD=<unset>
   0.048 Running in headless mode
   0.049 Error Util.cpp:83: Cannot load base mod version 0.18.23 with game version 0.18.65535. Update probably failed, please download the game again.

Error! Failed to apply update

[posila]

Is still causing issues if you use update scripts to push incremental updates.

We will look into creating update package from .22 directly to .24, but can you change the update script so it applies all updates at once instead of doing it incrementally?

Do

Code: Select all

factorio --apply-update /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.21-0.18.22-update.zip --apply-update /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.22-0.18.23-update.zip --apply-update /tmp/factorio-update.M7ZUpV8Q5P/core-linux_headless64-0.18.23-0.18.24-update.zip

Note: they unfortunatelly have to be passed in correct order (the updater won't reorder them)

[Windsinger]

Aye,

Wont update the script though, will do this one manually. but it's more for all the other scripts out there that heavily rely on that versioning file

If i do it manually, reverting it back to version 18.22 and then manually to 18.24 that works. but yeah, work-around.

Code: Select all

$ ./factorio --apply-update /tmp/core-linux_headless64-0.18.22-0.18.23-update.zip --apply-update /tmp/core-linux_headless64-0.18.23-0.18.24-update.zip 
   0.000 2020-05-12 17:55:59; Factorio 0.18.22 (build 51330, linux64, headless)
   0.045 Operating system: Linux (Ubuntu 18.04)
   0.045 Program arguments: "./factorio" "--apply-update" "/tmp/core-linux_headless64-0.18.22-0.18.23-update.zip" "--apply-update" "/tmp/core-linux_headless64-0.18.23-0.18.24-update.zip" 
   0.045 Read data path: /opt/factorio/factorio/data
   0.045 Write data path: /opt/factorio/factorio [424987/468301MB]
   0.045 Binaries path: /opt/factorio/factorio/bin
   0.052 System info: [CPU:       Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz, 8 cores, RAM: 64348 MB]
   0.052 Environment: DISPLAY=<unset> WAYLAND_DISPLAY=<unset> DESKTOP_SESSION=<unset> XDG_SESSION_DESKTOP=<unset> XDG_CURRENT_DESKTOP=<unset> __GL_FSAA_MODE=<unset> __GL_LOG_MAX_ANISO=<unset> __GL_SYNC_TO_VBLANK=<unset> __GL_SORT_FBCONFIGS=<unset> __GL_YIELD=<unset>
   0.052 Running in headless mode
   0.055 Loading mod core 0.0.0 (data.lua)
   0.103 Loading mod base 0.18.22 (data.lua)
   0.348 Loading mod base 0.18.22 (data-updates.lua)
   0.474 Checksum for core: 3371497937
   0.474 Checksum of base: 703431642
   0.652 Prototype list checksum: 3693507024
   0.690 Info PlayerData.cpp:70: Local player-data.json unavailable
   0.690 Info PlayerData.cpp:75: Cloud player-data.json unavailable
   0.738 Factorio initialised
   0.738 Info Updater.cpp:269: Applying update /tmp/core-linux_headless64-0.18.22-0.18.23-update.zip
   1.930 Info Updater.cpp:269: Applying update /tmp/core-linux_headless64-0.18.23-0.18.24-update.zip
   2.988 Goodbye

[Windsinger]

For the next release i demand a small pomidorek to be present!

*runs*

[posila]

Can this also be changed in the online version list please???

https://updater.factorio.com/get-available-versions

wheybags and Klonan added update packages for direct update from 0.18.22 to 0.18.24, and removed update packages to and from 0.18.23

[Windsinger]

Awesome work <3

[vdreams]

Update from 0.18.23 to 0.18.24 not work. Thanks for redownload. :/

[someone1337]

Bugfixes

• Fixed version 0.18.23

ALL BUGS BE GONE!

Update from 0.18.23 to 0.18.24 not work. Thanks for redownload. :/

To be learned: never ever update the first few hours after a release - this holds for EVERY software everywhere.

[badtouchatr]

Bugfixes

• Fixed version 0.18.23

ALL BUGS BE GONE!

Update from 0.18.23 to 0.18.24 not work. Thanks for redownload. :/

To be learned: never ever update the first few hours after a release - this holds for EVERY software everywhere.

+100

[vdreams]

Bugfixes

• Fixed version 0.18.23

ALL BUGS BE GONE!

Update from 0.18.23 to 0.18.24 not work. Thanks for redownload. :/

To be learned: never ever update the first few hours after a release - this holds for EVERY software everywhere.

Not a real problem for me, but it's annoying. But I know that early updates can be broken. User data and binaries were separated anyway.

[coppercoil]

This is why I have suggested to organize a smaller pre-alpha testers group that would get updates one day earlier (except hotfixes). Would it be an overkill for this software?

[Oktokolo]

To be learned: never ever update the first few hours after a release - this holds for EVERY software everywhere.

We are on experimental, because we are the testers wich report the bugs, wich stable users will never see.
Not updating whenever an update is available would defeat the most important purpose of being on the experimental branch.

[Koub]

This is why I have suggested to organize a smaller pre-alpha testers group that would get updates one day earlier (except hotfixes). Would it be an overkill for this software?

It makes sense. Also, there should be an even smaller pre-pre-alpha to be sure the pre-alpha team doesn't get anything broken. Oh yes I know, a pre-pre-pre-alpha would be sweet too.

Just joking obviously ^^

[MakeItGraphic]

This is why I have suggested to organize a smaller pre-alpha testers group that would get updates one day earlier (except hotfixes). Would it be an overkill for this software?

It makes sense. Also, there should be an even smaller pre-pre-alpha to be sure the pre-alpha team doesn't get anything broken. Oh yes I know, a pre-pre-pre-alpha would be sweet too.

Just joking obviously ^^

They are technically correct in regards to software release life cycles, it is an absolutely valid suggestion. I don't understand Factorio usage of the terms. From what I can gather pre-alpha is more in house. Alpha would be the pre-alpha they're describing and beta would be the product we end up downloading. That said Factorio 0.17.79 is still considered Alpha even though it is a stable release, I would think this would be a silver/gold product. In lieu of it not actually being version 1.0. It is the final build for .17.

I'm open to people railing me on this because I don't work in software development and I am just reading the Wikipedia here https://en.wikipedia.org/wiki/Software_ ... life_cycle so all for learning. But generally based on that article it does seem skewed.

Going back more to doing a limited release, if it wouldn't put too much more overhead on the dev side I think it is an apt idea. There so many active users that use Factorio that selecting 5 to 10 participants to be testers wouldn't be too difficult.

When a post like this is made for the first 12 to 24 hours only people in the tester (and other applicable groups) could see the post. That way if any critical issues were to arise it can be corrected, and moved to new a release. If everything is fine then that version goes live. Just spit-balling here.

[coppercoil]

Not updating whenever an update is available would defeat the most important purpose of being on the experimental branch.

No doubts, experimental branch is very useful. But some bugs are just mistakes that are easy to find and easy to fix, and there are no benefits of spreading them over whole alpha-tester community.
Assume that pre-alpha testing is a kind of Wube internal testing, just external players involved. I'm pretty sure we could find some brave enthusiasts.

It makes sense. Also, there should be an even smaller pre-pre-alpha to be sure the pre-alpha team doesn't get anything broken. Oh yes I know, a pre-pre-pre-alpha would be sweet too.

Just joking obviously ^^

No jokes. Developers ARE pre-pre-pre-alpha testers, they always test what they've done. Hired internal testers (if any) ARE pre-pre-alpha testers. Just one step missed.