ID:260818
 Nov 5 2009, 6:23 am
|
|
Not really where else to post this. I already posted a bug report on it. Has anyone else played with the latest beta? Anyone played with the isometric support? Has anyone else noticed icons getting cut in half, missing, or deleting tiles under them when being placed? Is this a BYOND Beta issue or am I just not using the map properly?
| |
No, CTRL+Click is not working. I uploaded via Megaupload for anyone who wants to take a look at it.
http://www.megaupload.com/?d=BZDCHTVK Mess with the map, look at the stuff, play with the trees. Something funky is going on. | |
You didn't set icon_size to the size of icons your actually using. If you set world.icon_size = 54 you won't get the cut off looking map.
| |
Jotdaniel wrote:
You didn't set icon_size to the size of icons your actually using. If you set world.icon_size = 54 you won't get the cut off looking map. His bug report didn't even mention a demo, but I marked it as not a bug already just based on the tile width of 54; the Reference clearly says you need a tile width that's a multiple of 4 for the math to work out right. Looks like there was more to it than that, but it's still a case of not reading the documentation. I'd like to again implore all developers to read the new Reference sections thoroughly before posting bug reports on 455. On a more general note, it is always important to try to solve problems in the forums first before making a bug report. Lummox JR | |
How hard would it be to make the compiler notice the the default icon_size does not mesh with the isometric setting? If it can throw an error that stops compiling, that's one less "Help, BYOND is broken!" post we have to see over and over again.
| |
Danial.Beta wrote:
How hard would it be to make the compiler notice the the default icon_size does not mesh with the isometric setting? If it can throw an error that stops compiling, that's one less "Help, BYOND is broken!" post we have to see over and over again. It'd probably be on the difficult side. The warning would basically have to come only after both icon_size and map_format were set, so the compiler would have to keep track of the file+line the other one was set on in order to throw the warning. But realistically, this would only ever impact people who didn't read the reference on how to use isometric maps, which would bite them in the butt in some more dramatic way later on. Lummox JR | |
The 455 notes explained why this behavior occurs.
"Because the old behavior of looking for a fully opaque icon to decide whether replacing or overlaying a turf was appropriate does not apply in isometric mode, the behavior for the Click and Ctrl+Click actions has been switched. Now, Click is a replace and Ctrl+Click is an insert."
Long story short, clicking will replace the object below with the new object. If you would like to place an object on top of another, try CTRL+Click.