Changing the default palettes for tracks and maps in global settings does nothing. Likewise when you change the palette for isobaths it is only active for the current session. When you restart RM it returns to the original palette.

After playing with these settings for a bit, RM now crashes every time I try to generate the map for the project I was working on.

The global default palettes only apply for the first time an asset is opened/created, after which any palette state is persisted. For example, if you open a track once and then close the track (or ReefMaster), then the current selected palette is saved and is restored the next time the track is opened, regardless of the global default. I admit that this might be a little confusing, especially if the default palette was never changed for the track (although this behaviour probably makes more sense for projects). As far as I can tell from testing, RM is working correctly in this way, but one idea might be that we should only save a track palette state for a track once the user has actively changed the palette - otherwise always use the global default.

The crash is more concerning - when does it happen? What steps did you take before the crash started happening and does this apply to all assets and projects now or just some? If possible, please send the error report through when it happens next.

As far as I know all I did was change the global palette settings and the crash started happening every time I tried to generate the map. Went on to work on another project and came back to the original and all ok now. ??? If it happens again yes I'll send the error report.

The main issue I was talking about originally was when you change the palette for isobaths in the layers panel, the changes are discarded when you close RM. I have to change the palette each time after I have generated the map.