Rasmus-M
commented
3 years ago I think I understand what you mean, but then your calculations are wrong: 768 patterns would only take 6144 bytes (8 bytes per pattern) and not 25683, and the same for the colors. However, the problem with this suggestion is that it would only work if your map is exactly one screen, i.e. 32x24 characters. Also, Magellan can only work work with 256 patterns (unless you choose the new Super Character Set), so where would you get the patterns for the second and third parts of the screen from? Magellan is designed to be a map editor where you can edit big maps (much larger than one screen) and where it is expected that you reuse pattern across the map. It sounds like what you need is a screen editor for working with one screen where each pattern is unique.
ytsejam78
Hello, I come from MSX world (same vdp as TI99-4/A) and didn't know about Magellan until recently! I am impressed by how powerful and easy to use this tool is. One thing I would love it had, is the possibility to export the map as raw binary (shape/color). Similar to VRAM dump import but the opposite (export). I noticed there is an option to export as binary, but while still must-have feature and very useful, it exports the "name table" i.e. 768 bytes of data, and what I mean is the "pattern table" as if characters were in 0-255 order for each bank already, ending up with 25683 bytes for shapes, and same for the "color table", 25683 bytes representing color data. If my explanation is not clear, please don't hesitate to ask. I hope you find this interesting and consider for adding to a future version. Thanks!