»Lynx Posted February 2, 2008 Report Posted February 2, 2008 (edited) Hey, i'm having a small problem, that when I make a new tile-set, I can load it into DCME and it seems to work fine - but when I close DCME and try to re-open it again it says "C:\...\NewTileSet.lvl may be corrupted. Do you wish to attempt recovering data?" - I click "Yes" and it will retrieve the tile locations, and what tiles were laid, but they will be blank. I can then re-load a tile-set over this, and it will seem to work find, but again corrupt when I save. It is also corrupted when I load it into the game. (Visit newtileset in SSCI Dragonball Z to see) - it seems to have some tiles, but the rest are static. Here is the DCME.log file for the session:Spoiler! --Click here to view--02/02/2008 17:01:27 --- Drake Continuum Map Editor (v3.1.10) starting...+++ OtherInstance 0+++ openedMapByArgs FalseNewTileSet.lvl @ OpenMap, Opening Map... C:\Do!@#$%^&*ents and Settings\Chris\Desktop\Graphics Tileset\NewTileSet.lvlNewTileSet.lvl @ OpenMap, Tileset foundNewTileSet.lvl @ OpenMap, Bitmap info header: --- Color Depth: 32 --- Size: 304x160 --- BiSizeImage: 0 --- Compression: 0NewTileSet.lvl @ OpenMap, Bitmap info header: --- bfType: 19778 --- bfSize: 146008 --- bfReserved1: 145976 (145976)NewTileSet.lvl @ Openmap, BMPData is read from lvl fileNewTileSet.lvl @ OpenMap, no eLVL data foundNewTileSet.lvl @ Openmap, usingDefaultTileset FalseNewTileSet.lvl @ OpenMap, WARNING: Seek(f)=145975 bfSize+1=146009NewTileSet.lvl @ TileDataRecovery, attempting tile data recovery at 146009NewTileSet.lvl @ TileDataRecovery, with offset 0, 1348 tiles found, 0 errors occured.NewTileSet.lvl @ TileDataRecovery, best offset found: 0 with 0 errors.NewTileSet.lvl @ SearchWallTiles, Searching for: C:\Do!@#$%^&*ents and Settings\Chris\Desktop\Graphics Tileset\NewTileSet.lvl (walltilepath: C:\Do!@#$%^&*ents and Settings\Chris\Desktop\Graphics Tileset\NewTileSet.wtl)NewTileSet.lvl @ OpenMap, Map corrupted! Seek position: 146009 last (X,Y): (0,0) b(3)= [66,77,88,58]NewTileSet.lvl @ TileDataRecovery, attempting tile data recovery at 146009NewTileSet.lvl @ TileDataRecovery, with offset 0, 1348 tiles found, 0 errors occured.NewTileSet.lvl @ TileDataRecovery, best offset found: 0 with 0 errors.NewTileSet.lvl @ OpenMap, tile data starting at 146009NewTileSet.lvl @ OpenMap, 1348 tiles loaded. Now at 151405NewTileSet.lvl @ SaveMap, saving map... E:\Games\Continuum\Continuum Editors\DCME (Drakes Continuum Map Editor)\DCME_3.1.10\DCME autosaves\FFFFF7EB93D2_2008-02-02-17-01-30_NewTileSet.lvl.bak, SSMECompatible False, Silent TrueNewTileSet.lvl @ SaveMap, opening E:\Games\Continuum\Continuum Editors\DCME (Drakes Continuum Map Editor)\DCME_3.1.10\DCME autosaves\FFFFF7EB93D2_2008-02-02-17-01-30_NewTileSet.lvl.bak for binary as #1NewTileSet.lvl @ SaveMap, bitmap header position: 1NewTileSet.lvl @ SaveMap, bfReserved1 set to: 145976 (145976)NewTileSet.lvl @ eLVL.PutELVLData, Saving Hashcode FFFFF7EB93D2 at 145989NewTileSet.lvl @ eLVL.PutELVLData, Rewriting total size: 32 at 145981NewTileSet.lvl @ SaveMap, total eLVL size returned: 32NewTileSet.lvl @ SaveMap, New bitmap bfSize: 146008 (146008)NewTileSet.lvl @ SaveMap, BMPData is stored into lvl, starting tile data at 146009NewTileSet.lvl @ SaveMap, 1348 tiles were saved into lvl. Total file size: 151401 bytes.+++ Last update: 27-01-2008 - Update period: 2DCME readyFloat tileset loadedFloat radar loaded Any ideas? :S Thanks, Lynx EDIT: The only way which I can overcome this is if I manually re-name the .bmp file to a .lvl file. Works fine now. Edited February 3, 2008 by Drake7707 Quote
Drake7707 Posted February 3, 2008 Report Posted February 3, 2008 Can you try it again with the version sama compiled a while ago. He mentioned there was a problem with tilesets with compression flag or with wrong offset check or something like that.Maybe it's already fixed in the new version Quote
»Lynx Posted February 3, 2008 Author Report Posted February 3, 2008 Ah, I thought I had latest, will do later. Quote
Samapico Posted February 3, 2008 Report Posted February 3, 2008 hmmm... --- Compression: 0 however. But lots of these kindo f things were fixed since 3.1.10, so yeah, give it a try. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.