![]() The only way to find these things is by extensive, time consuming testing and even then there's no guarantee you've found them all. And each issue will break things in subtle ways, ending a a random desync the devs need to analyze. It's very easy to assume something will always work in a certain way, when you haven't yet encountered a place where your assumption doesn't hold. How strong is arm's cache coherency? x86's is very strong, to the point that you can omit some synchronization because of architecture guarantees.Īnd then there are all the things that are different, but nobody thought about them yet.How is floating point rounding handled? You can find some dev posts about rounding issues from the early days of factorio multiplayer.How wide is a long? At least under linux, it changed size between x86 and amd64.To list a few questions I can't answer from the top of my head: ![]() For multiplayer all the little differences between arm and x86 suddenly become relevant. ![]() And once the build succeeds singleplayer will most likely work.īut only singleplayer will work. Fixing any build failures should be relatively easy. I have no clue about building for mac, but in a linux/gcc world, building for arm is as simple as installing a version of gcc that can cross compile into the appropriate arm dialect. The main issue is not getting factorio to run on an arm, but to support it and to have interoperability between arm and x86 builds. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |