Nice to meet you, too
I can no longer in error LCMExporter version of this up.
I can create without problem AT5.
Do you also have a special configuration?
Please let me know.

Not sure exactly what you're asking.

It may be helpful to write it in your native language as well as English.

LCM creation, in general, is no longer supported. AT5 generation through the IMC is recommended as a replacement. I'm not sure what "special configuration" you are referring to.

LCM support end
Thank you

Hi, and welcome to the forum!

We are aware of an issue when exporting maps in LCM format on some systems, and are actively working on a solution. We hope to be able to make a maintenance release some time in the next day or two.

For the moment we do still support LCM but, as Greg has mentioned, AT5 is now the recommended export format for Navico devices. For now, I suggest you export in AT5 is you can, until we get this issue fixed.

thanks,
Matt

k.akagi wrote:
Hi,
This is not the case - we do (notionally) still support LCM format (for now), but we had to make some significant changes to the way we do it, to accommodate calling an old 32 bit DLL from a new ReefMaster build that supports both 32 and 64 bit. This meant writing a separate 32 bit application to create the LCM map files, and it seems that this has caused issues for some users. We do have a fix now, but we need to test it a bit more before including it in a maintenance release.

thanks,
Matt

I understand
Thank you

Sorry about the confusion on that. I meant from Navico's perspective rather than Reefmaster's perspective.

No worries Greg. Just curious - can you think of any Navico system that supports LCM that does not support AT5?

Matt

Not that I know of.

LCM is an alias for AT5. The specific DLL wrote out Atlas Major Version 6.0 but had quite a few issues with how it created the files.

Older chart plotters may need much more basic features but the sanity checks I was seeing were on stuff like 1000 unique features or 1000 unique icons...not a handful of area features.

This issue has been fixed in maintenance release 1.6.12.32. Update to this by running the "check for updates" application and following the prompts.

Thank you