Known Issues

[bluemonkmn]

There is only one known problem in GameDev 1.4.6 (a problem which has been around forever):

• The mouse pointer on the full screen tileset editor does not draw nicely -- it is almost invisible while the mouse pointer is moving.  This is due to strange code that had to be written to make the mouse pointer behave correctly on some video cards/drivers which would cause the mouse pointer to corrupt the display.  This will not be fixed in version 1.x, but will no longer be an issue in SGDK 2.0's windowed graphics editor.

The problems listed below from version 1.4.5 have been fixed:

• Special Function of type Activate Series does not trigger sound
• Minimizing the layer quick view and then exiting gamedev causes an error that prevents the view from ever coming up again, unless you delete the following registry key: HKEY_CURRENT_USER\Software\VB and VBA Program Settings\GameDev\Windows
• Map editor can have an error if a path is being drawn very far off the visible area of the screen.
• An error will occur if two sprites are more than 32767 pixels apart and a collision definition tries to test to see if they are colliding.
• There is no way to SavePicture (save a screenshot, for example) from VBScript, will add one if a version 1.4.6 is ever released.
• Solidity definitions crash gamedev when more than 256 tiles exist.  The failure should be nicer with a helpful error message.

[Zorb Burger]

u be fixin them!!!!!

[bluemonkmn]

The following problems exist in 1.4.6, but have work-arounds:

• When creating a path in the map editor, if any segment of the path is longer that 32767 pixels (if any point in the path is more that 32767 pixels away from the previous point) an error occurs.  To work around this, add extra points along long paths so that each segment is no longer than 32767 pixels.  I believe the problem only cares about horizontal or vertical distance (ie, I expect it would be OK to have a point that is 30000 pixels to the right and 30000 pixels below the previous point even though pythagoras would tell us that the second point is 42426.40687 pixels away from the first point).
• When copying a block of tiles in the map editor, if the width or height of the block is wider or taller than 32767 pixels, an error occurs.  To work around this, copy the block in segments so that each block copied is no wider and no taller that 32767 pixels.

[billybob884]

found this to be a bit of a problem, if you remove a tileset and then save+close, when you try to re-open, if a map needed that tileset it causes the builder to crash, citing run-time error 91

[gwal]

If you ever want to 'cleanly' remove a tileset from your game, make sure to delete/change layers of maps or sprites that use it. I can see what you're saying though; I've removed tilesets several times only to find that there was some obscure sprite I had forgotten about which used the tileset's graphics.

[billybob884]

the problem for me is that i have over 60 maps in my game irght now, and i thought i hadremoved it from what was using it, but apparently not. it wouldnt be that big a deal though if it told you what was using it, like what map or what sprite, but instead i had to go in and manually add the tileset back in before i could re-open the game wihtout it crashing

[bluemonkmn]

When I try to remove a tileset that is being used by a sprite definition or a layer in GameDev 1.4.6, I get an error message:
Cannot remove tileset "<whatever>" because it is being used by layer "<whatever>" of map "<whatever>".
or
Cannot remove tileset "<whatever>" because it is being used by sprite definition "<whatever>" on map "<whatever>".

I don't know how you are missing this unless you are using a really old version of GameDev.

[billybob884]

well, i have 1.4.6, so idk. maybe its not using it, but then i don't know why it wouldnt start up when saying it couldnt find the tileset. but oh well, i fixed it

[gwal]

wow. 60 maps is a lot.