While changing the palette for one of my map projects, RM froze. Had to kill it via taskmanager. Now when I attempt to edit this map project, RM crashes while loading it. RM is running on WIndows 10.

Could you please share this workspace (via filesharing service and link to This email address is being protected from spambots. You need JavaScript enabled to view it. ) ?

Update: Opened database went back to global settings and set palettes back to default. I was then able to open my project once again.

Am I missing something here? Changing palettes in global settings seems to have no effect and I don't see any options to change palettes in RM2.0?

Palettes are set per layer now, not per project - so if (for example) you want to change your isobaths palette you need to expand the layers panel, click on the isobaths layer and set it there.

Can you describe exactly what you were doing when the crash happened?

Thanks Matt.

Opened database, double clicked on map project and it crashed almost immediately. Did this 3-4 times with same result.

This was after changing the default palette in the global settings?

Yep. Changed the pallete in global settings. Clicked on check mark to save and close. Waited for a bit then left. Came back after 10mins and dialog still hadn't closed. RM stopped responding. Killed RM with task manager. Reopened db and problem presented itself.

OK thanks - I will try to reproduce it here. If it happens again, the workspace could be useful to help us understand what is going on.

I have a similar issue with RM2.0 (current latest version).

I can open RM2.0, Open/transfere projects from RM1, open new project in RM2.0, import tracks to RM2.0. However, whenever I try to do any action, such as edit a track, RM2.0 Crashes. It happens every time.

Same operation in RM1 (current latest version) is working without any issues.

Could you please try starting RM2, opening up global settings and un-checking the option "Use hardware graphics acceleration", and then restarting RM. Please let me know if the problem persists.
There does seem to be an issue at the moment where RM is not always correctly identifying that hardware acceleration is not available, and continues to try and use it - we are looking into this.

Matt wrote:
Hi Matt,

Thanks, that did the trick. As a result of my experience I recommend having it un-checked as default.

A lot of the more powerful new features in the sidescan mosaic module rely on it - but apart from that it won't have much (any) affect on map generation. We are trying to improve the detection of when it is not available.