3.6.6 possible bug

Hi Darkrin,

I tried to replicate this and could not. Can you provide the D20.log file so we can examine what might be causing this issue for you. Thanks.

Also, if you have multiple computers you are using to develop and run your games, you may want to use a cloud based service and use our campaign.override feature and point your campaign directory to the cloud on each device. This way you have one place for all your campaign data and you can access it from anywhere, no need to export/import. Though, we'll make sure your export feature works, as that is important too.

 

Hi Darkrin, did you upgrade to 3.6.6 from a beta build?

I've seen this before and the solution is to open the map (if it's not already open), click the manual save button from the D20PRO menu (upper left corner)



Then close the map by clicking the little X next to the map name. THEN when you re-open it the load function will fix the maps data map (behind the scenes) and allow you to do whatever with it, export, save, etc.

If that is not working, there is a potential that you're map art is corrupted or encrypted. You can try to swap it out from the Draw Tools->Manage Tiles panel



Make sure you've saved a copy of your map before proceeding.

1. open the Draw Tools->Manage Tiles Panel.
2. Note the w and h (width and height) values for your tile
3. Locate the source file in your folder tree.
4. On your map view, right click on the map background and select delete
5. Click on the tile source image in the Manage Tile panel
6. On your map view, hold down the control key and left click to place the tile.
7. If the scale is odd, you can change the dots per inch (grid unit) and try again (drop down right above the layer section)
8. To resize the tile, right click on it in the map view and select resize.
9. enter in those w and h values from earlier and then drag the tile to where you want it (covering the whole map)
10. Lock it down from the layers pane so it doesn't accidentally get moved if you use any other tiles for hidden things.
11. let us know if any of these solutions helped!

 

I don't know that your work encryption was the problem as much as our own. Between builds, we've had several data model changes which have caused this to our test groups -- so known issue, sort of?!

Great to have your maps back! Also a good trick to keep in mind if you have any lock outs in the future. The Mindgene folks built in a bunch of sanity checking code when a map is loaded. We've been doing the same to creatures and features lately as well!