Ticket #550 (closed defect: fixed)
Error loading maps in Atlas
| Reported by: | pownerus | Owned by: | |
|---|---|---|---|
| Priority: | Must Have | Milestone: | Alpha 1 |
| Component: | Atlas editor | Keywords: | error maps |
| Cc: |
Description
When I start Atlas in Ubuntu 10.04 it doesn't load maps, when I try to load someone it shows "Failed to run rmgen (error code: 255)".
Attachments
-
error.png
(75.6 KB) -
added by pownerus 18 months ago.
-
nograss.png
(71.4 KB) -
added by pownerus 17 months ago.
- whe i start it only shows the blue background
Change History
comment:3 Changed 18 months ago by pownerus
- Summary changed from error loading maps in Atlas to Error loading maps in Atlas
comment:4 follow-up: ↓ 5 Changed 18 months ago by Philip
Were you clicking the "Run RMS" button? That feature currently doesn't work at all.
comment:5 in reply to: ↑ 4 Changed 18 months ago by pownerus
Replying to Philip:
Were you clicking the "Run RMS" button? That feature currently doesn't work at all.
ok, but i can't generate a new map
comment:6 Changed 18 months ago by pownerus
When I start Atlas in Ubuntu 10.04 it doesn't load maps,
comment:7 follow-up: ↓ 8 Changed 17 months ago by Philip
Hmm, it should show a blank grass map by default when you start the editor. Does File->Open work? I guess it might be an issue with graphics drivers failing to render the world, but I'm not sure how to debug it.
comment:8 in reply to: ↑ 7 Changed 17 months ago by pownerus
Replying to Philip:
Hmm, it should show a blank grass map by default when you start the editor. Does File->Open work? I guess it might be an issue with graphics drivers failing to render the world, but I'm not sure how to debug it.
open file works but i can't see the default grass
Changed 17 months ago by pownerus
-
attachment
nograss.png
added
whe i start it only shows the blue background
comment:9 Changed 16 months ago by Philip
- Status changed from new to closed
- Resolution set to fixed
Someone else reported a very similar problem with blank maps, and eventually we found the cause - it should be fixed by r8218. Hopefully this is the same issue. (In older versions, the problem can be avoided by running "export LANG=C" before launching the editor from a terminal.)
