I am opening up a few projects and for some reason when I try to look at the track data it doesn't show the track (breadcrumb trail).

I can generate a map from the data, so it is there...but I just can't see it or edit it. Also when I open the "Sonar Viewer" it doesn't show anything. I have never had issues like this before and have recently upgraded to latest version of RM, but I am not sure if this is what has caused the issue. It has never been an issue in the past as I have hundreds of tracks and it seems to have this issue on any of them that I open up. When I hover the mouse on the track data screen it will highlight a point when I move the mouse over it, but I have to blindly hunt over the water body to see the track. Any idea why?

This is a strange issue and it sounds as if it might be connected to hardware graphics acceleration. Could you please check the setting "Use hardware graphics acceleration if available" in Global Settings and try unchecking it if it is set? You will need to re-start ReefMaster before the setting takes effect. I would be interested in knowing more about your system specifications if possible; if you could run the Windows utility dxdiag (from the Windows "Run" window), save the output to file (there is an on-screen option for this) and forward the file to This email address is being protected from spambots. You need JavaScript enabled to view it. that could be really useful.

Yep that did it Matt! I am running dual FirePro (V4800 and V4900) workstation graphics cards, not sure if I had it working with hardware acceleration before but for now I'll leave it off. I created the .txt file with my system setup and have emailed it to the address you have provided.

Thanks for the quick response Matt!

Edit: Just getting into all the features again with the hardware acceleration disabled (and even re-enabled) I noticed that the sidescan data doesn't show up in "track sidescan" or in the "sidescan mosaic". It'll show up in the sonar viewer however. It just shows a blank swath in the track view. Any idea?

I had this same issue with an Nvidia GTX1660. Turning off acceleration, restarting, and then turning it back on, and restarting again, seemed to fix it. With acceleration off, navigating through the mosaic project was painfully slow, as expected.