|
|
Post by NoXPhasma on Jan 22, 2015 17:17:32 GMT
Hi, when I try to load saved machines, I get only a empty world, no machine no world:  It doesn't matter how much items I use, it happens in Sandbox and in normal levels too. I'm using version 0.0.1. I've added the Player.log file and a saved machine. OS: Linux Mint 17.1 x64 CPU: AMD FX-8350 GPU: Nvidia GTX 660 RAM: 8GB Attachments:Player.log (19.14 KB)
walker_mk1.bsg (12.13 KB)
|
|
|
|
Post by NoXPhasma on Jan 30, 2015 2:53:58 GMT
I'm still unable to load saved machines in version 0.0.2. Sometimes I can see the loaded machine though, but still the map is empty and I can't build on the machine.  Attachments:Player.log (16.82 KB)
test.bsg (511 B)
|
|
|
|
Post by Von on Jan 30, 2015 3:28:13 GMT
Hi,
Thanks for posting this, I'll pass it onto the Devs and we'll see what we can come up with!
|
|
|
|
Post by tapio on Feb 4, 2015 19:07:11 GMT
I am experiencing the same issue. Looking at the save file, seems that the game picks up the system locale's decimal separator (my OS language is Finnish) and uses it when outputting stuff, e.g:
Which should be 0,5.69906,0 (so dot instead of comma). Manually fixing the world position makes the world appear, but the machine is still missing, apparently due to comma errors all over the file.
While waiting for a real fix, a work-around is to start the game from terminal or script with the following command:
LC_ALL=C ./Besiege.x86_64
Which forces the default C-locale and makes new saves work correctly.
|
|
|
|
Post by Von on Feb 6, 2015 20:28:28 GMT
I am experiencing the same issue. Looking at the save file, seems that the game picks up the system locale's decimal separator (my OS language is Finnish) and uses it when outputting stuff, e.g: Which should be 0,5.69906,0 (so dot instead of comma). Manually fixing the world position makes the world appear, but the machine is still missing, apparently due to comma errors all over the file. While waiting for a real fix, a work-around is to start the game from terminal or script with the following command: LC_ALL=C ./Besiege.x86_64 Which forces the default C-locale and makes new saves work correctly. Thanks for looking into this in greater detail, I will pass on your findings to the devs. |
|
|
|
Post by fipom on Feb 8, 2015 15:20:04 GMT
Got the same problem here on Arch Linux, French locale. Is Besiege based on Unity ? Cause if yes, I think it's the same kind of bug we could have on Kerbal Space Program which has been fix in the last version (0.90). see point (2) on this thread : forum.kerbalspaceprogram.com/threads/92231-The-Linux-Thread |
|
|
|
Post by fipom on Feb 8, 2015 15:32:20 GMT
I confirm that launching besiege with "LC_ALL=C ./Besiege.x86_64" resolve the problem. Edit: You can see the KSP fix on the changelog (point 8) |
|
|
|
Post by fphanny on Feb 13, 2015 0:39:31 GMT
Launching with "LC_ALL=C ./Besiege.x86_64" works on the problem on Windows 7 for me as well
|
|
|
|
Post by jplatte on Feb 17, 2015 7:44:35 GMT
First, thanks to the developers for using text files for saving creations! It was really simple to find out what the problem was with some technical understanding, as tapio showed.
Imagine having the same problem with CPU endianness in binary files copied from other people :>
Forcing a different locale ('C' or 'en') doesn't seem like a nice fix, but I can't think of any nice portable solution, and having it fixed would just generally be a good thing.
This bug still persists in v0.0.3, but I guess you should know that youselves. And by the way, German users like me are another group of people affected by this.
|
|
|
|
Post by Von on Feb 17, 2015 23:59:23 GMT
First, thanks to the developers for using text files for saving creations! It was really simple to find out what the problem was with some technical understanding, as tapio showed. Imagine having the same problem with CPU endianness in binary files copied from other people :> Forcing a different locale ('C' or 'en') doesn't seem like a nice fix, but I can't think of any nice portable solution, and having it fixed would just generally be a good thing. This bug still persists in v0.0.3, but I guess you should know that youselves. And by the way, German users like me are another group of people affected by this. We are aware of the issue & the different system langauge issue, I've just spoaken with Matt about it again, he said that they haven't had a chance to look at it yet but they will, we hadn't realised the issue was as widespread as it is. Hopefully its something we can get done for the next patch though I can't say for sure. |
|
