We still waiting Matt ! Is something new in case?

Matt, is any chance to new RM version in some-future?

Full time work is well underway on RM3 - I can understand any scepticism since work was paused for quite some time but happy to confirm we are back on track!

It's a big upgrade - the tech we used for RM2 and our other applications is outdated now so the new version involves migrating to something more modern (.Net10 and Avalonia UI for the techies). Upsides of this are vastly improved performance and (for the first time!) ReefMaster running natively on both MacOs and Linux.

What this space - we hope to have a beta in early 26 (ask about the beta program if you are interested) and targeting Q2 26 for the full launch.

Of course I'm interesting beta version

It is very interesting to see the result of your labors. I hope there are improvements there and we were able to take into account the wishes of the users. We are waiting for you very much.

Thanks - I hope it will be worth the wait for you.
Now would be a good time to update any particular feature requests for things that you would really like to see in RM3.

It is important to me, but I do not know if it is possible to implement this in rm3: 1. full support and processing of sl3 data; 2. the ability to adjust depth polygons, fill holes when adding depth values (by points), the ability to create polygons manually with layer distribution (0.5 m shoals, on top of the polygon water; 3 high resolution shaded terrain and 3D view; 4. the ability to add data from other manufacturers (garmin, humminbird); 5. seamless structural maps (it is better to remove the column of water, like humminbird); 6. the ability to adjust the rise of the water level directly in the project, with recalculation of the entire map and coastline. 7. The ability to select the color of polygon palettes as in G; 8. the major isobats every 1 m and the minor isobats every 0.5 m

What version are you currently using Ershal?

1. SL3 support has been part of RM2 for some years, although this depends a bit on what you mean by "full support" - e.g. we don't read SS3D channels.
2. You can add spot depths in map projects. Adjust depth polygons? You can edit any polygon in the map view (via Layers panel).
3. 3D is going to be much higher resolution for larger maps in v3.
4. Humminbird data is supported via HT (trails/waypoints) files and .DAT/.SON sonar logs. Garmin is a tricky one - we could do it but we need further discussions with them.
5. Water column is always removed for sidescan mosaics, and you can further adjust offsets here if some remains.
6. Overall water level offset for projects is available in RM2.
7. Also present in RM2 - see Layers panels in map projects.
8. Currently if you select 1m majors you will get 0.25m minors but this is just to create the contours. You can create whatever contours you want at the given increments and style them in whatever way you want already, or simply create default 1m/0.25m and delete the contours that aren't on 0.5m boundaries (not ideal, but possible).

1. It is the reading and use of the ss3d channel to create more accurate maps. 2. This is not the case. It is the creation of a polygon using a marker on points. The ability to add a polygon, for example, 1m. This is implemented in gpsmapedit. 5. It is not always completely removed and distorts the images, and there is no smooth transition. 6. The coastline does not shift automatically by, for example, 1 meter, and the entire map is not recalculated. In humminbird, this is implemented directly in the device. 7 colors do not match the c-map palette, it is difficult to choose. 8. It is more convenient to use 1m and 0.5m, I have to remove 0.25m, I do not need them. Maybe I am not expressing my wishes correctly, but this is not implemented in the way that is convenient for me. Can you write what is new in RM3?. It is clear about the transition to a new platform and the acceleration of work.

OK - not sure we'll ever get to SS3D. It was a good idea but seems to have died - is it available any more?
2. An example of what you mean would be good - feel free to start a new thread in feature requests with images etc.
5. it should always be removed but if there are bad data points then yes it is possible - RM3 has unified depth points across sonar/trails/maps so edits to depths will/can be reflected in slant-range correction which is not currently the case. Example pics would be useful.
6. you mean move the shoreline to the new 0 metre contour? I think I understand what you mean now - yes something to consider.
7. This can be quite device dependent.
8. Noted - more flexibility on contour intervals.

I'm not in a position to give a full rundown on what is new in RM3 but hopefully will be able to start putting some things out after Christmas. Keep coming with the suggestions but make a new thread of them please.

Ok Matt. I'll try to show it in a new topic

Many people write about RTK GNSS support, but what exactly does that mean?
1. Ethernet connection
2. Offsets
3. HDT heading direction
2. Working with a geoidal elevation model and calculating water levels in real time
If this is the case, then INS support for roll, pitch, and heave is also needed.
But will Reefmaster's mathematical model calculate all this for applying corrections?

I don't think so! There's other software for professional hydrography.