Andor's Trail

Tomcat wrote:I'm doing everything on my phone right now (can't on work computer, wife is working on dissertation on home computer) so no ATCS yet...thinking about picking myself up a little laptop.

There are some pretty decent options for netbooks out there that wouldn't break the bank but are going to be fast enough to run what you need to run a map making software or while coding. That could be a good option for you in the long run.

Not sure if a tablet would be able to run it as smoothly, but that probably depends on the tabby

I don't think ATCS or Tiled would run on Chromebook - do have one of those already - but yeah, a cheapo one would be fine.

ATCS will work on any OS that has Oracle's Java and can spare 500MB RAM to it. It can put some stress even on good CPUs when viewing the world1 worldmap zoomed out.

Zukero wrote:ATCS will work on any OS that has Oracle's Java and can spare 500MB RAM to it.

This is drifting way off-topic, but I've had problems with the 512MB RAM allocation. I can create two projects, but if I try to create a third then ATCS just hangs in an endless loop, with an error about the memory heap (I forget the exact error message). I increased the memory allocation to 1024MB, which is probably excessive, but the problems went away. So it will work with 512MB, but possibly only for a limited number of projects. Would it be possible to trap this error, and ask the user if they wish to increase the memory allocation (in which case ATCS modifies ATCS.cmd and forces a restart)?

Splitter thread so we're not off-topic anymore.

To save RAM, you can close projects in ATCS.
The out-of-memory errors in Java are not trappable. An alert when running low is possible, but requires constantly polling for it. I'd like to avoid this. Patching the .cmd is also something I'd like to avoid.
A second, "high memory" launcher is an easy alternative. I'd allow 2GB in this one.

I hasn't noticed the "close project" option! Useful to know, although since I have plenty of RAM just having ATCS suck up 1GB is easier. Do you have a rough estimate of how much memory is required by ATCS itself, and how much by each project?

As stated in the Changelog for v0.1.1, it's roughly 200MB per project. The overhead should be almost negligible in comparison.
I haven't measured in a long time.

What is really costly is the spritesheets.

Do you have a way to find how much memory is allocated?

In code, yes. I once coded a bar shown at the bottom of the UI that showed red for used memory, blue for allocated, and green for allocatable.
I could try to find it and include it in ATCS.