Hello Mat

For some reason V2 on my computer can't handle same size map project then V1 calculates with no problem. Reinstalled windows-same thing.

Any suggestions?

Thanks

Interesting - it's unlikely to be a memory issue as RM2 can handle much bigger maps than RM1 for the same amount of memory.
Do you get an error message during the build? If so, what is the message? What is the result of the build - does it crash, or just fail to complete?

During the build, program hangs for a short periods of time, then freezes for a long time. Screen goes black and program shuts down. I don't get any error message as before reinstalling new Windows, witch was memory related. My friend has identical computer with 4 gb Ram (my is 8 gb Ram) and he has no problems at all.

Still dealing with my problem, trying figure it out without much of results. I was able to calculate same size map in v2 by removing 40 islands from project. Calculating took a very long time, i can see map, but program stuck and not responding. Program uses 5,696 gb RAM memory (out of 8 gb RAM total). Is this normal?

Please advice

Would it be possible to share your rm2db workspace file (use a file sharing service and send link to This email address is being protected from spambots. You need JavaScript enabled to view it. ). I can take a look and see if there is something going on in the project that is causing this.

doing it now

Thanks Kestas. Your project brought to light a bit of an issue when generating contours with a large number of map boundaries present, and we have been able to make a very significant improvement to performance here. Your full project goes from a generate time of around 25 minutes to a minute and 25 seconds on my development machine as a result of these improvements. Keen to hear how you go with the new version.

Happy to report-9 minutes on my computer!!!!! That is amazing.

When map is calculated and zoomed out it is little bit slow to response, the more map zoomed in, faster to respond. But same thing was with v1 to. I can live with that.


Thanks Matt!!

If your project settings are the same as you originally sent me, you might want to consider a larger contour interval. You have the smallest setting and are also generating minor contours which results in a very large number of contours in the finished map.

Yes Matt, i understand what are you saying, but one of the main reasons i do all of this is to have very detailed maps for fishing. Over wise i would by one from Navionics or LakeMaster and would be done. Going from one spot to another at high speeds i prefer 2ft. contour intervals on my console unit. I wish we would be able to have this setting option when calculating map, not only 1ft or 3 ft etc... For my bow, fishing unit 1ft contour lines is mandatory! Nothing less. Minor contours for me just not working because in my opinion they only repeating major lines in smaller coarse in most of the case.