Exploring Oasis montaj 2025.1? Let’s hear what you think.

PrachiChitkara
PrachiChitkara Posts: 380 admin

The Oasis montaj 2025.1 release has been out for a little while now, and if you've been exploring it, we'd love to know how it's going.

This update brings enhancements aimed at improving accuracy, cross-team collaboration, and overall geophysical workflows, including:

  • IGRF 2025 coefficients for more accurate magnetic modelling
  • New geoid models for better gravity corrections
  • GeoTIFF support and printing for seamless image sharing
  • Interoperability with Leapfrog and Evo
  • An updated embedded Python environment

If something has stood out in your workflow, or if you're still exploring what’s new — feel free to share your thoughts, learnings, or questions here.

Let’s help each other get the most out of this release!

Tagged:

Comments

  • Hello. Yes, I watched the release Oasis montaj 2025.1. Among the disadvantages I would like to note:

    1. It requires installation of an additional connector from Bentley. As a result, there are 2 connectors, one from Bentley and one from Seequent. Moreover, Bentley often crashes and requires reactivation.

    2. It takes a long time to open, only one window with the project starts. The second window cannot be launched. And this is very important when working with several intersecting projects!

    I had to delete the new version and install the previous one. That's how I understood the problem with the Bentley connector.

  • DarrenMortimer1
    DarrenMortimer1 Posts: 2 Staff

    Hi Andrey

    Thanks for the feedback. Please reach out to our support team at Support@Seequent.com, so we can assist you further.

    For Oasis montaj, Bentley Connection Client is only required if you are also using Seequent Evo or one of the other Bentley products (like MicroStation) that use Bentley Connection Client . Otherwise with v2025.1 continue to use your Seequent Id and Seequent Connector, just as you have in the past.

    You should also be able to open multiple instances of Oasis montaj too; please reach out to our support team so they can gather details of your system, and provide additional guidance.

    Cheers

  • PrachiChitkara
    PrachiChitkara Posts: 380 admin

    Hi @AndreyKononov2 Thanks so much for sharing your experience with the Oasis montaj 2025.1 release. I’m really sorry to hear it’s been frustrating - especially around the connector and managing multiple project windows.

    I saw my colleague has already shared some helpful info and the support contact. If you're open to it, I’d still encourage connecting with our support team at support@seequent.com so they can dig into this further and help troubleshoot.

    Appreciate you taking the time to post. Feedback like this really helps us improve!

  • Hi,
    I've been a user of this OM since the 90's. Back in the day it was obviously limited in what one can do with it BUT the hot fixes that came out back in the day always helped the user to get back on track. The last proper version in my view was 7.01.
    After that there was a steady decline in the quality of the program and although I've spend hours and days reporting / explaining issues it was fruitless.
    This new version is a disaster and I will highlight a few issues which I've encountered in the first 30min of use…..or maybe I'm just stupid.
    1) Section map making now employs a new way of dealing with scale - a complete mess. Not only can't one copy and post certain objects between maps and hope it will land in the same place but it will instead change size and every map that one generate needs manual adjustment - absolutely useless and frustrating.
    2) Since the Flintstones proper map templates for sections and plan view maps are out of the question
    3) Data is clipped in sectional gridding - this also occurred in 8.5 and were briefly corrected just to be incorrect again
    4) No export of geostrings to GDBs or CSV files
    5) Stacked sections on the same map has seemingly disappeared. I assume it is because of the new way in which scaling is done which by the the way has no logic applied.

    6) No manual copying and pasting from and excel file or other ASCII files in a field in OM. This was very handy back in the day if only a few data points needs to be entered or a few replaced. It was always there - gone since the late Ver 8.xxx

    7) I don't use this anymore but the Gravity module has been broken well and truly. The TC on that was always rubbish and may as well be scrapped.

    8) the plan view map will not read coordinates properly from a database and will keep the coords of the first selected line if switched of and one moves on to make a new map from any other line in the same GDB.

    The above issues are just some that comes to mind and there is no point in submitting requests or issues because it is never resolved.