I don't know if I'm the only one, but I'm always searching long time to do something that was really easy to do in RM 1, but can't find it anywhere in RM 2...

I don't really like RM 2 for that reason... I didn't had many times, but I tried a couple of times to build map with RM 2 since I upgraded, and each time I must end it before to suceed because it's too much time finding somes functionnality that was easy to do in RM 1...

Again, this morning, I tried to make a new map for tomorrow fishing, and again, something that I can't find... Just change color palette of a project ? Where is it ? I'm searching since half an our... For a simple thing... I don't understand it at all... Too much time wasted for some simple things...

RM 2 is a lot less intuitive than RM 1... I regret my upgrade...

Each time I come back with RM 1 to build map...

Do I'm alone ? Where is the setting for the color palette of a project ?

Thanks

Fred

And where to set depth range ?

This kind of functionnality should be, must be, easy to find...

RM 2 - 1 hour to make a map with full error... There is many depth issue...

RM 1 - 6 minuts to build map from scratch (that include 3 minuts for importing 53 files (25 GB))

Yes you are alone, because you don't read a bit the manual, dont use the search option in the manual.
It's so simple, also for you.

Use the layer menu (right in the screen) and the general settings.

Fred, please do read the manual and the upgrade guide for RM2 for existing RM1 users, and also please don't swear on this forum (I have edited your original post).
The new way of changing palettes may be a little less intuitive, but it is far more flexible - you need to edit palettes in the appropriate layer, instead of for the map as a whole. Read the layers section of the RM2 manual. Fixed range depth functionality has been moved to the palettes, so it is now much easier to share fixed depths across layers/projects.
If your map is taking a very long time to generate, then make sure you are using the latest version of RM2 as there was a performance issue in earlier releases. You should actually see faster map gens in v2.

Thanks Matt for your reply,

sorry...

I found what I was looking for, finally, but this is not really intuitive like already said. I'll play with it and see...

Another thing, each time I tried to remove track point in track editing, I got this error and RM shutdown:

I tried to remove all point from track... I'll try removing the track from project... But this should work this way too... No ?

Thanks

Fred

Send me the error report please Fred, also please specify which version of RM2 you are using and, if possible, include workspace. Better to remove the whole track from the project than delete all the points.

Report sent.

I'm using the lastest version. I never found the version number in ReefMaster instead of 2.0... But the exe file version is 2.0.32.0

One other thing that I don'T understand... See my last pictures, same project with RM 1 and RM 2. RM 1 dealt with bad depth, not RM 2... We must edit track by track now ? How to get the same result, with the same data ?

I have 700 log file, I Can't edit them one by one...

Thanks again !

Fred

It's full of bug with track edit...

At least 5-6 times in the last hour, I edited track, closed it... But point still in the project. For a track, I repeated the same action 3 times before it delete trackpoint in project that I deleted in track edit... This, when RM is not crashing...

Reefmaster 2 is not ready and is not really funny to work with. You will tell me to read doc... I did it for what I want to do... But I Never needed to read RM 1 docs... !?

One entire day to try to make a Map, that take 6 minutes to do in RM 1. It's unnaceptable. I can't understand...

And I'm not a beginner to build map... As much as I was liking RM 1 when I purshased it and learned to work with it, as much as I hate RM 2 today... I'm sorry, but I don't have time to waste, and this day was too much waste. Today I should had done all my reservoirs and lake map for all this summer fishing... But I'm not able to complete a little lake in one day. :(

Fred - when you get a crash, please forward the error report so that we can look at it.

I sent them... But I can'T work with RM 2 anymore. I don't have time to developp it with you. I baught it to make map... Again this morning, I'm trying to make a map for fishing this afternoon. I'll end up with a map full of error.

I edit track since 1h... Each track, I need to re-edit track and delete point 2-3-4 time before they really get deleted... I'm wasting my time, and I really don't like it.

And BTW, I can't send an error report for that bug, because it's not a crash... But that don't do what it should... And when we generate map, change are not always showing. You need to uncheck shaded relief and iso bath to make the change visible.

I'll ask for a refund please, and continue using RM 1. I can't work with that at all. You product is not done at all for a release, and I don't have time to play the beta
tester.


And I search and search for the benefits of RM 2 over RM 1, and sincerely, I can't find them... Except two little thing... Shaded Relief for Google Earth (I do it with GB anyway), and the fact that you can edit sun direction for shaded relief... But again, I was doing it with global mapper...

Like RM 1, We can't use it like we can use any other software on windows, MULTI TASK... You can't work on two project at the same time without close and re-open the software every time... So many time wasted... I was thinking that it will be resolved with RM 2, but not...

Now, we can generate bigger map, but it take 10 times the time to generate... So better to keep it in separate parts...

The major change that we can see, and not for the best, is that now, like Office, you use ribbon style menu... I'm sorry, but you missed so many things with this version 2... I'm really dissapointed...

No, I'm not happy, And find nothing to justify the purshase of RM 2... I really don'T understand...

Sorry to hear it Fred. If you can show me an example of a track-point that does not delete, we can look into it - it is not a behaviour we have observed, but of course it is possible that there is a problem. One possibility is that you have a number of track-points that occupy the same position (very common, given the discrete positions that track-points are given by HB and Lowrance units), and deleting one track-point simply reveals another one underneath. I assume you are using the latest 2.0.33 release.