Release Notes 3.4
Highlights of 3.4
The ten changes most users will notice across 3.4. The sections below list every change, release by release.
- Vulkan is the default renderer — faster, and the base for the newer tools. See Why Is This Greyed Out? for what still needs OpenGL.
- A quality grade on every plane fit, so you can tell a trustworthy dip from a guess. See How good is the pick?
- Texture Track follows a contact through the photo texture between a few clicks. See Texture Track.
- A rebuilt geological log editor, with a palette, the Quick Log, beds from field notes and keyboard logging. See Sedimentary Logging.
- Geomechanics from sets to key blocks: joint strength per set, stress tensors, kinematic slope stability with factors of safety and probability of failure, rockfall and tunnels. See Geomechanics.
- Flight paths build themselves, and narrated tours export as MP4 video. See Flight Paths.
- RTK GNSS field navigation. See GNSS Field Navigation.
- Drone survey planning. See Drone Survey Planning.
- Flow through a fracture network. See Connection Mesh for Flow.
- A photogrammetric model from one command (3.4.20): set Build up to and Quality, and one run goes from photos to a textured mesh. See Build up to.
3.4.20 (in development)
These arrive in 3.4.20, the build after 3.4.19.
A photogrammetric model from one command
- One build goal and one quality. Run setup now holds Build up to (Cameras and sparse cloud, Dense cloud, Mesh or Textured mesh) and Quality (Fast, Balanced or Accurate), and Run Reconstruction goes as far as the goal. A new workflow aims at a textured mesh, so a first run no longer stops at a sparse cloud; a workflow saved earlier keeps doing what it did. See Build up to.
- A Run dialog that can act on what it says. The plan before a run shows what will be redone, the time, what scales the model and whether the dense stage will fit in memory, with Build up to, Quality and the region of interest beside it, so the answer to a warning is no longer Cancel and a hunt through the properties. Lower the Dense Quality comes with the memory warning, and Ask Athos to Check hands the plan to the chat. See The run plan.
- A workflow menu that knows the stage. The main steps come first with the next one in bold, what cannot run yet is greyed, and the rest sits under Results, Mesh and Texture, Georeference, Region of Interest and Settings. The workflow's row carries a badge saying how far it has got, or that its last run failed. See The workflow menu.
- Every run ends with a summary and a next step: the counts and the time, a tip when many photos did not register, a warning when nothing gave the model real-world scale or the dense stage made no cloud, and for a failure the stage, the reason and a pointer to Athos.
- Runs save as they go. A run saves at its start and after features, matching, registration, sparse, dense, mesh and texture, so a crash or a killed app no longer loses the workflow and hours of matching with it. A cancelled or failed partial solve keeps the earlier model rather than overwriting it. See Running a reconstruction.
- One photo pool and one feature cache per project. Add Photos imports into a pool keyed on the files' contents, so several versions of a model share the images and their features instead of copying and re-extracting them. Duplicate Workflow makes a new version with the same photos, settings and control and no results. The Photo Pool row shows every pooled photo at its EXIF GPS position on the map and in 3D, and Remove Unused Photos... moves the files nothing uses to the project's recycling folder. See Several versions of one model.
- Cameras you can see and click. A model's cameras can be picked in the 3D view, and the Images row has its own page of display options: cameras, thumbnails, frustums, image planes, GPS positions and colour. Show Photos as Images in 3D stands each photo at the surface it shows, so a wrong pose or lens is visible on the model, and Show GPS error lines is its own switch. Image locations now appear and frame in a project with nothing else in it.
- Settings you can reuse. Rows that differ from a new workflow's default have bold names, Nearest preset says which preset custom settings are closest to, and each stage's group says what a change costs. The Settings submenu copies settings from another model, saves and loads them as a file and resets them, and refuses while a run is in progress. See Reusing settings.
- Align to Reference Elevation... fits a model to a mesh or cloud in the project, or to an elevation source it downloads, with scale unless you turn that off. The move survives a re-run. Create Mesh (Poisson) can then fill gaps and pad the edge from that reference, where the dense cloud is absent or thin. See Aligning a model to reference elevation.
- A better dense cloud by default. Ledge corners come out sharper and edges less fattened. Further matching options are there to try, off by default, and each dense point records how many views support it in a Fusion Support layer. See Dense MVS.
- Texture Mesh from Photos is one dialog. Which part of the mesh, the budget and the decimated copy are chosen together, and the recommendation follows. A selected part can be baked as a new mesh, or the whole mesh baked with full detail on the selection. Photographs are read at full resolution while the texture is written, even when they will not all fit in memory, each chart gets the density its photographs support, and a large mesh can be baked onto a decimated copy. See Texturing the mesh.
- Export Tiled Model (SLPK) writes a tiled, level-of-detail Esri Scene Layer Package from a mesh, and can bake the finest tiles' textures straight from the photographs. See Exporting a tiled model.
- Athos can start, finish and stop a model. Ask Athos to Build a Model from Photos... starts from a folder, Ask Athos to Build this Model asks once for the whole build, and meshing and texturing can now be run through the chat as well as the reconstruction. A started run reports back, can be cancelled and reports its progress. Athos can read and propose the dense matcher's and the texture bake's settings. With Ollama, Athos previews these changes but does not apply them. See Athos.
Sedimentary logs
- Logs stand in 3D as graphic logs. A log in the Vulkan view is now its 2D grain-size track on a panel, with beds, patterns, symbols, a depth ruler, palaeocurrent arrows and labels, instead of a stack of prisms. It can turn to the camera or lie along the rock, and sharpens as you approach. Column Style brings the old prisms back. See Sedimentary Logging.
- The log editor keeps your place. Keyboard moves and the Quick Log scroll to the bed they end on, and a command on selected beds that are all off screen brings them into view and changes nothing. A facies keeps its number key from one bed to the next, and Ctrl+Shift+number pins one. A bar along the foot of the view names the mode. Selected beds keep their fill under a translucent band. Ctrl+C and Ctrl+V copy what a bed is to the selected beds. See Sedimentary Logging.
Attribute plots and orientations
- Scatter, colour scatter and triangular diagrams. Select two or three attributes to plot them against each other in the Charts panel, with SVG export. Log X Axis and Log Y Axis on the scatter charts suit fracture length and height. See Charts and Plots.
- Statistics and best-fit lines on scatter plots. The plot lists r, r², the covariance and each attribute's mean and standard deviation, of the log values on log axes. Best Fit Line on its menu draws a linear, power, exponential or logarithmic fit, with its equation, R² and scatter. Both go into the SVG export. See Scatter plots.
- Dip and Dip Direction on every orientation. Every project now lists them under the Orientations tree's Attributes, answered from each plane's measurement so they cannot go stale. They can be coloured by, filtered, charted and cross-plotted like any other attribute. See Orientation.
- Create Dimension Attributes adds Width, Length and Height to selected orientation groups.
- Grow Planar Patches no longer blocks the rest of the app and keeps its selection between runs, and From Selected sets the orientation cone without disturbing the range filter. A patch colour layer keeps its filter through a reload, and unclassified regions keep their texture.
Rock mass and fractures
- Build a DFN from Sets. Create DFN from Selected Groups is now Create DFN from Groups or Sets..., a dialog of orientation folders and project Sets to tick, one fracture set per ticked row, as the Slope Stability dialog chooses its sets. See Creating a DFN.
- A fracture's height follows its length. A DFN set can now draw each fracture's height from Height = a × Length^b with scatter, instead of one aspect ratio for the whole set. Create DFN fits this to each set's measured lengths and heights where at least five planes have both, and it can be typed in the properties panel. See Fracture shape. The attribute that was Width is now Length, as on a measured plane, and a set taller than it is long now reports its real length and height. Fractures to CSV gains length and height columns.
- Fit Model Domain to Displayed Data. On a DFN's menu, it sets the domain to the box around what the active 3D window displays, so the network can be confined to one outcrop. See Setting the Domain.
- The DFN's Domain rows take effect. Editing Domain in the properties panel changed nothing, so a network too big to generate could not be shrunk as the budget warning advised. It now applies at the next Regenerate, and Re-derive from Source Orientation Groups keeps the domain rather than going back to the project's extent.
- Fractures taller than they are long reach the domain's edge. A set with an aspect ratio below 1 looked for fractures crossing into the domain only as far as its shorter axis, leaving its P32 short near the faces.
- Group by Set. On an orientation group's menu, it moves the measurements below the group into a group per Set, in the Set's colour. Auto-cluster can do the same with Move each set into a group of its own. See Group by Set.
- Re-derive from Source Orientation Groups finds its sources. It looked for the source groups where they could not be found, so it always reported them missing. It can now re-derive from Sets as well.
- The intersection scatter on the stereonet. Intersection Scatter plots every pairing of one set's planes with another's for wedge sliding and direct toppling, solid where the line is critical for the chosen mode and pale where not. See the Stereonet User Guide.
- Every wedge is marked. Where each pair of sets' mean planes meet is marked in the pair's colour, hollow where no wedge forms, and the same colour sits beside its factor of safety in the key.
- The minimum wedge angle can be seen and set. It was fixed at 10 degrees and unrecorded. It is now in the Slope Stability dialog and the stereonet's properties, saved with a run, and printed in the key when it is not the default. See Slope Stability.
- The N beside a wedge percentage is a count of plane pairs. It used to report the Terzaghi weight, which could overstate the measurements behind a percentage by more than an order of magnitude. No percentage changed. An exported figure now also records the Terzaghi settings it was made under.
- Stereonet keys share columns, so a table stays with its heading and one key's width no longer moves another. Stress markers read at equal weight.
- DFN sets feed the geotechnical tools. The tunnel, rockfall and other geotechnical analyses can take a DFN's fracture sets as well as measured ones, and mapped fractures now keep their positions through regeneration and count toward the target intensity. See the DFN User Guide.
Point clouds, meshes and the 3D view
- An ASCII column importer. ASCII Points (columns) previews the file in a grid where you assign each column, with the delimiter, skipped lines and any header guessed for you, and OK to All for the rest of a selection. See Supported Formats.
- Show Normals. Point clouds and meshes can draw their normals, cyan facing up and orange facing down, so a flipped patch reads as a block of the wrong colour. In the Vulkan view.
- Poisson meshes from merged scans. A mesh built from a cloud merged from several scan positions no longer has patches of flipped faces.
- Decimate runs in the background, far faster and in far less memory on a large mesh, and a textured mesh keeps its UVs and pages. Preserve mesh boundaries locks the outline.
- Recordings and captures carry the overlays. A recorded flight, Copy Screen and Athos's view capture now include the compass, scale bar, colour key and stratigraphic column, and the attribution streamed imagery requires, stamped on sharp after any motion blur. See Figures and Images.
- StraboSpot pins draw and select in the Vulkan view, and Reposition Object works there.
- 3D Translate moves a scale bar from its base, a near miss no longer dismisses the handles, Shift hands the mouse back to navigation, and Escape disarms it.
Hyperspectral data
- Spectral bands on clouds, meshes and satellite images. A PLY cloud whose properties are wavelengths, such as a CloudCompare hyperspectral export, comes in with its bands renamed to their wavelengths and grouped under Spectral bands. Interrogate a point to plot its spectrum in the Charts panel, broken at the water and detector gaps; Shift+click pins it for comparison. See Hyperspectral Data.
- ENVI image cubes. An ENVI
.hdrwith its BSQ, BIL or BIP data imports as a satellite image with a spectrum per pixel, or as a point cloud, thinned and band-averaged to fit in memory and placed by its map info. See An ENVI image cube. - Spectral tools. A Spectral submenu on the attribute rows offers band composites (true colour, colour infrared, SWIR false colour, mineral features), mineral indices (Al-OH, kaolinite, Fe-OH and carbonate band depths, ferric iron, NDVI), minimum-wavelength mapping, principal components and the spectral angle mapper. Reference spectra come from the chart, the mean of the shown points, a CSV library or 13 minerals from the USGS Spectral Library version 7 that ship with VRGS. Every result is an attribute layer saved with the project. See The Spectral submenu.
Your data on disk
- Point clouds are PLY files. A point cloud is saved as binary PLY in the data folder's
POINTCLOUDSfolder, which other tools such as CloudCompare can open, and full double-precision coordinates are kept. Gaussian splats are standard 3DGS PLY files inGAUSSIANSPLATS, and orthopanels have a binary format of their own. New meshes always use the current mesh format. See The project directory structure. - Older projects are upgraded when you say so, before you start work. Opening a project from an earlier VRGS says what would be upgraded, the project file and the data files to convert, and offers three answers: back up the project and its data folder first, upgrade without a backup, or do not open it, which changes nothing. Until you have agreed, an autosave leaves any older files as they are.
VRGS.exe -upgrade "<project>"does the same with no questions and reports through its exit code, so a later VRGS can use this one to bring an old project up to date. See Upgrading an older project. - Recover from data folder copies the models another project's data folder still holds into the open project, for a project whose project file or database is lost or corrupt. Recycle unused data files finds model files nothing refers to and moves them to
RECYCLING. Neither deletes anything.
Memory, cancelling and undo
- A model that will not fit is refused or asked about, not crashed on. Every load is estimated from the file and judged against free memory, with Load it anyway? where someone is there to answer. The reload question on opening a project gives the total against what is free. A project opens at most four meshes at a time.
- Work you can cancel. Progress rows have a Cancel button, SfM runs included, and closing or opening a project with work running offers to cancel it and waits rather than asking you to wait.
- Edits that undo. Most rows of the property bar now record an undo step, with a spinner's ticks coalesced into one, and so do tree renames and drag-and-drop moves. Dropdown, colour, font and file rows do not yet.
- Fewer questions on open. Confirming and saving are one question, and invalid orientation objects are asked about once, as a list.
Licensing
- RLM licences carry modules. On-premises RLM licences now read their modules, such as DFN, SfM and Geomechanics, from the licence's options, and
VRGS_LICENSE_FILEtakes a host and port or a path. License Status lists the modules. The older floating-server route has been retired. See On-Premises Server.
Ribbon and help
- Snap To Mesh moves the line. The command had been greyed out, and the result it used to produce was neither drawn nor saved. It now rewrites the selected polyline on the active mesh, adding vertices along each segment, and Undo restores the line as digitised. See Snapping a line to a mesh.
- Help opens the documentation. The Help button and Ctrl+F1 did nothing when clicked; they now open the documentation site. Local Help is gone, as the installer ships no help file for it to open.
- Buttons with nothing behind them are gone: Class Label, Export USD, Re-Converge on the Geosurface tab, Lines and Flight Mode on the Geobody tab, the Clipping panel on the Voxel Model tab, the Channel tab, and the plain From GCP on the Point Clouds tab. The From GCP dropdown stays.
- Trace grades are fairer. The plane-fit grade's length and node-spacing tests divided by a point spacing instead of the square root of the area per triangle, which made them about 50% stricter than the published thresholds intend. A trace picked in 3.4.19 or earlier may grade one step better now. See How good is the pick?
Known limitations
This is in the build but cannot yet be reached from the interface:
- Kinematic (driven) DEM particles. The solver can drive a particle at a prescribed velocity, for a rough floor, an indenter or a rigid basement block, but no command sets one. See DEM current limitations.
Fixes
- Double-clicking a project opens it. A
.vgpor.vgpxpassed in from Explorer used to start VRGS empty. - Older projects open. A v2.08 project no longer crashes on a null scale bar, a v2.39 project reads the viewpoint lists of its flight paths, and a damaged one stops at the damage with what it read so far. A project from a later VRGS fails to open rather than closing VRGS.
- Mesh files keep every vertex after a NaN one. A laser-scan dropout in a mesh could turn every later vertex into a NaN on saving, and a converted mesh could lose part of itself. Saved positions no longer drift.
- A hidden mesh stays hidden when a save converts it.
- Ortho panels honour Auto Update when it is off in the Vulkan view, and a resize no longer re-bakes.
- Texture pages of about 2 GB no longer crash VRGS.
- Satellite images are the right way up in the Vulkan view. Every satellite image was drawn upside down, north at the bottom, and a project holding nothing but satellite images showed an empty view.
- Sparse RMS is no longer thrown out by one bad observation, and a dense reference that fails is named in a warning.
3.4.8 – 3.4.19 – Logs, Rock Mass and Drone Surveys
September – October 2026
Logging a section is quicker from a palette, a line of shorthand or your field notes, and Athos reads the result; the geomechanics toolset runs from the discontinuity sets through slopes, benches, tunnels, key blocks and rockfall; a drone survey plans itself over the model; a fracture network carries flow; and every 3D format VRGS reads comes in as it was built.
✨ New & Enhanced Features
Virtual field trips
- Green screen and virtual backgrounds on your camera tile, alongside the existing blur. With a real green screen you can be cut out on colour alone, which works on machines where the segmentation runtime was never installed and gives cleaner edges around hair. A flat colour background is also the cheapest option to send, so more of the tile's bandwidth reaches your face. See Multiuser Virtual Field Trips.
- Video keeps up on a slow connection. Frames are now dropped rather than queued, so viewers see a current picture instead of a smooth stream of increasingly old ones, and recover quickly when the link frees up.
- Voice is closer to real time, and a large trip scales further: someone following the leader's camera no longer republishes that camera to everyone else.
- Guided tours reach every participant. When the leader arms a guided tour, everyone on the trip, late joiners included, now preloads it, reports ready and follows; before, only the leader who armed it ever received the tour, so nobody else moved. A trip ends when its project closes, and leaving one from the VR menu no longer leaves the microphone open.
Field guides and billboards
- Flight paths on the field guide map. The map block can show each saved flight path as the viewpoints it flies through, with Play on a right-click; Insert > Flight Path Link puts a link to one on the page; and any map spot can be given a flight path to play from the reader's map. A VRGS Link can carry a small location map under it, the map can show the project's waypoints so a Day or Stop can be added at one, Day, Stop and Viewpoint markers drag to where they belong (snapping to waypoints), and any spot can be removed. Get Viewpoint says how many objects the link records and warns when the position is not a place. See the Virtual Field Guide Editor.
- Field Tour, a button on the Web panel's toolbar, leaves just the 3D view, the guide and the trees, with the ribbon minimised, and puts everything back when it is turned off. In the reader, Ctrl+wheel enlarges pictures past the column.
- Billboards run themselves. A board with more than one image can hold each for a delay and step on with a fade, slide or wipe, set in the Slideshow group of its properties, in both views and in recordings. See Billboards.
Discrete element model
- Triaxial and isotropic tests. Loading has two new modes beside compression and tension. Triaxial brings every face of the specimen to a confining stress you set, lets it settle, then shears at constant lateral stress; Isotropic consolidates and stops. Peak strength from a set of triaxial runs at different confinements is what a failure envelope is fitted from. See the DEM user guide.
- A stress–strain chart. The new DEM Test tab plots axial, lateral and deviator stress against axial strain, with volumetric strain on a second axis, live while a test runs. It opens when you start a test and is on the Home tab and the model's Simulation menu.
- Loading tests and rolling friction on the GPU. A model with a test in progress or with rolling friction set now runs on the GPU instead of falling back to the CPU, so a triaxial test runs at GPU speed and gives the same curve.
- GPU and CPU runs agree. A stiff pack now gives the same contact forces on the GPU as on the CPU; they used to differ by a few per cent.
- Periodic boundaries. Any axis of the domain box can be made periodic (Periodic X / Y / Z): its two faces are joined, so a particle leaving through one enters through the other and contacts and cement across the seam behave as if it were not there. A long strike-slip or rift model no longer has ends that impose anything. On both solvers.
- 2D sections. Tick 2D Section (XY) on a DEM volume to model a slab of discs: the Z dimension of the box is the thickness, particles sit at mid-plane and move only in the plane, and the loading programs run unchanged, so a uniaxial or biaxial test on a section is set up exactly as in 3D. It reaches a basin-scale section at a resolution 3D could not afford and compares directly with the 2D sandbox and DEM literature. On both solvers.
- Graded packs run at full speed. A pack with a wide spread of particle sizes no longer slows every step, so a model can be fine through a fault zone and coarse elsewhere at no penalty.
- A test history you can keep. Every test records stress, strain, damage and the quasi-static diagnostics at a set interval. Export Test History writes it as CSV, and it is saved beside the model with the project.
- Quasi-static diagnostics. The properties show the unbalanced force ratio and the inertial number for the current run, and suggest a strain rate that keeps a test quasi-static rather than dynamic. For small stiff grains the default rate can be slower than that needs, and a lab-scale test then takes hours for no gain in accuracy.
- Cement stiffness now follows a modulus. Bond stiffness derives from a bond modulus and the particle sizes, as the contact stiffness already did, so a cemented model is no longer far softer in tension than in compression at metre-scale grains. Existing projects keep the explicit stiffness they were saved with.
- Strength scatter and rolling friction. Bonds can be given a spread of strengths at cementation so failure begins as diffuse microcracking rather than one clean plane, and contacts can carry rolling resistance so a broken assembly keeps a realistic residual strength, on both solvers.
- Saved models carry on as they were. A reopened model in contact now steps exactly as it would have without the save.
- Watch fractures grow. Show Bonds and Show Broken Bonds in the display options draw intact bonds as lines between elements and each broken bond as a small disc where it broke, red for tensile and blue for shear, so with the elements hidden the fractures can be watched forming as a test runs. Add Attribute on a model's Attributes row colours the elements by radius, volume, mass, speed, coordination number, bond damage or breaks.
- Model templates. New from Template on the model group builds a 5-inch sandstone core for a UCS or a 10 MPa triaxial test, or a loose sand settling box, as a starting point for your own calibration.
- GPU runs are far faster. An 82,000-particle model now runs at about 700 steps a second, and contacts are kept when a GPU run starts or the model is saved.
- Marker horizons and displacement. Set Marker Horizons... records where every element started, in layers of a thickness you choose; Marker Band, Displacement and Vertical Displacement attributes then show how far the rock has moved, and Convert to Voxel Model puts the solid fraction, broken-bond density and displacement on a grid. The voxel model used to come out empty.
- Materials by layer. A model can hold several material sets, a mechanical stratigraphy, assigned by depth band or by one side of a surface (Material Sets and Assign Material Set); a contact or bond between two sets mixes them, with the weaker set's cement.
- Clip Pack To Outcrop trims the pack to the rock inside the active mesh, a closed one as a solid and an open one as an upper or lower limit, so porosity is measured against the rock rather than a box that is mostly air.
- Fractures to and from a DFN. Extracted fractures are ellipses along the damage they fit, flagged tensile by the share of bonds that failed in tension, with a damage width and their first and last break step written to a CSV beside the exported DFN, and the extraction can be limited to a window of steps; a fracture across a periodic seam comes out whole. Seed From DFN breaks or weakens the bonds the active fracture network cuts: right-click the DFN and choose the new Make Active, which makes it the only active one. When the model is exported again, the seeded fractures are kept apart from the ones that grew. See Seeding a model from a DFN.
- 2D sections have weight, and a planar section's fractures are extracted as traces with their true strike rather than all at a dip of zero. Changing the loading mode while a run is going is refused, and Fit To Active Outcrop empties the model and asks for a reset rather than leaving the old particles outside the new box.
Planar surfaces from the mesh
- Grow Planar Patches, a new tool under Extract, divides a mesh into the planar faces it exposes — bedding, fracture and fault surfaces — and fits a plane to each: dip, azimuth, coplanarity, RMS residual and size, written as triangle attributes and, if you ask, as one orientation measurement per face. It tests each triangle against the growing plane's distance as well as its angle, so a face and a parallel face a step away stay separate, and it measures the mesh to suggest its own parameters. From Run then refines them from what a run found. See Grow Planar Patches and its method.
- Sets, and one set at a time. The patches can be clustered into orientation sets, and a run can be limited to a dip and azimuth range, or to the planes near one orientation — pick a set of the last run by number — to extract a single fracture set.
- A patch becomes a measurement with one click. Dip / azimuth → Attributes on the Interpretation ribbon now picks a patch on a mesh that has a Patches layer and fits an orientation through it. It also works in the Vulkan view, where it previously did nothing.
- Auto Structural Mapping reworked. It grows best-first, can test distance as well as angle, weighs triangles by area, merges co-planar patches, fills small holes and reports a plane fit for every patch. It no longer needs Dip, Azimuth and CoPlanarity layers, falling back to the mesh's face normals, and it leaves hidden triangles out instead of showing them again. Patch Difference is now in degrees; it was in radians.
- Triangle attributes display correctly in the Vulkan view. Layers with one value per triangle, such as patch ids and texture resolution, were drawn as stripes. The mesh also redraws as soon as either patch tool rewrites the layer on display, rather than after the layer is toggled.
- The attribute filter keeps the texture. In the Vulkan view, Use Filter now colours only the values inside the filter window and shows the photo texture everywhere else, instead of cutting holes in the mesh. Invert Filter swaps the two. See Attributes Properties.
How three-dimensional is a mesh?
- Dimensionality Report, under Attributes & Analysis → Geometry on a mesh, says where an outcrop model sits between a flat wall and a closed body. It reads the area-weighted fabric of the face normals as the stereonet reads poles (Vollmer P/G/R, Woodcock K and C), tests whether the surface is a height field about its own mean normal and about the vertical, gives the shape of its extent, tabulates its linearity, planarity and sphericity at growing radii, and checks its topology; a verdict of 2D, 2.5D or 3D sits on top, with a continuous effective dimension between 2 and 3 for comparing models. The report opens as an analysis report saved in the project's Reports folder, with its figures in tables, and the Messages panel gets the verdict alone. It writes Fabric Dip and Fabric Azimuth triangle attributes and opens a Stereonet window on them. See Mesh Dimensionality Report.
- An exposure estimate in the same report. Every triangle is sorted into rock, vegetation or cover: green texture is vegetation, anything steeper than the angle of repose is rock, and below that a face that lies smoothly among its neighbours is rock where a rough one is scree or rubble; triangles inside a planar patch count as rock. The report gives each as a fraction of the surface, plus the rock inside planar patches as the mappable exposure, and writes Exposure, Greenness and Roughness layers so the thresholds, which are set in the report's dialog, can be checked on the model. It also counts the gaps inside the footprint's outline, the holes a scan leaves behind trees. See Exposure.
Fault and fracture surface roughness
- The Hurst exponent and spectral pre-factor of every planar patch. Grow Planar Patches measures each patch's self-affine roughness from the power spectra of its profiles down-dip and along strike, after Corradetti et al. (2026): H, how the roughness changes with scale, and C, how large it is. It writes Patch Hurst and Patch Log Prefactor layers each way and a Patch Spectrum Spread noise flag, and puts the same values on each patch's orientation object. Profiles have a line removed and a Hann window, not the paper's mean and 3% taper, which on a surface cut from a larger one, as every patch is, reads H up to 0.15 too high. See Roughness spectra of each patch and Surface Roughness Spectra.
- A Roughness Report. Tick Roughness Report in Grow Planar Patches for an analysis report: H against C for every patch, a table of them, and the spectra of the four largest drawn with their fitted lines and the paper's three fits side by side. See The Roughness Report.
- Roughness Map, under Attributes & Analysis → Geometry on a mesh, measures the same spectra in square windows stepped across the whole surface, each in its own plane with the bend of a curved outcrop taken off, and blends them onto the triangles as Roughness Log Prefactor, Roughness Hurst and Roughness Spread layers. See Roughness Map.
Textured meshes import and open with far less memory
- Textured meshes import without freezing. Importing a textured OBJ, PLY or GLB no longer freezes the view and fills memory while its textures are compressed, which took about 5 GB and several minutes for a twenty-page photogrammetry export. The model appears straight away, untextured for a few seconds from PLY or GLB; select it and its properties show Background Process: Compressing textures with a percentage.
- Imported meshes open quickly the next time. The compressed textures are saved with the project, so they are compressed once rather than in every session.
- Compression on any graphics card, NVIDIA, AMD or Intel, and much faster. Use Compressed Textures and Max Texture Size in a mesh's display options mean what they did; a page within the size cap uses an eighth of the video memory it would uncompressed.
- Embedded GLB and FBX textures compress too, so they use an eighth of the video memory they did.
Attribute legends and colour maps
- A legend for every object. The Vulkan view stacks a legend for each visible object that is showing an attribute, scaled so they all fit the viewport, so attributes can be compared across several meshes at once. A discrete colour map shows its classes as labelled swatches, clicking a legend key opens that layer's properties, and the key size is a preference.
- Named classes. The classes of a discrete colour map can carry labels of their own, shown in the legend, the histogram and the property grid, and any class can be hidden everywhere it is drawn. Scale Colours to Filter chooses whether the colour ramp stretches to the filter window or keeps its full range while filtering.
- Colour orientations and polylines by an attribute. Tick a numeric attribute under the Attributes row of Orientations or Polylines in the Interpretation tree to colour the group through that attribute's colour map, over its filter window; a member with no value keeps the group's colour. Orientation attribute definitions, which never came back on load, are now saved with their colouring.
- Attributes in groups. A mesh's or point cloud's layers can be filed into named subgroups under its Attributes row (New Group from Selection, Move to, Auto-Group by Name), and a subgroup's tick box shows and sets the active layer inside it.
Geomechanics
- A geomechanics toolset for an engineering geologist's work between mapping the discontinuities and judging a slope: the stereonet, Auto-cluster, Slope Stability, Slip Potential, stress tensors, the Mohr diagram, Block Size, rock materials and geotechnical domains, each on the right-click menu of the object it works on. See Geomechanics.
- Sets are tags. An orientation's Set is now saved with the project; it used to be lost on reopen. Auto-cluster tags each cluster with a new Set (J1, J2 …, in a colour of its own) instead of copying the measurements into folders, so nothing is duplicated in the tree. Folders still work as sets, and old cluster folders are not counted twice. See Sets.
- Auto-cluster is more reliable. It seeds with k-means++ and keeps the best of 20 runs, checks that k is a whole number between 2 and half the measurements, counts copies of a measurement once, clusters lineations as axes of their own and never mixes them with planes, and takes every item selected anywhere in the tree. See Auto-cluster.
- Auto-cluster by a Fisher mixture. The Auto-cluster dialog offers Fisher mixture (EM) beside k-means: each set is fitted as an axial Fisher distribution with its own concentration, the number of sets can be chosen by BIC (Choose k by BIC, trying 2 to 8), and an optional noise class leaves measurements that fit no set with no Set. The messages panel lists the BIC for each k tried and each new set's concentration. See Auto-cluster.
- Set statistics on the stereonet. Set Statistics marks each set's mean pole with its α95 cone and a variability cone (1σ or 2σ, as Dips draws it) and lists N, the mean plane, Fisher K and α95; Sets From takes the sets from folders or from project Sets. See Set statistics.
- Terzaghi correction on the stereonet weights each plane by its angle to a sampling line you give, with a cap, and applies to the contours, the set statistics and the kinematic percentages. See Terzaghi correction.
- Stress tensors in Collections. The project's stress states are listed under Collections → Stress Tensors and saved in the project; one is active. The stereonet's stress field and stress axes, Slip Potential and each DFN can use the active tensor or one you name. A DFN now takes its pore pressure, friction and cohesion from its tensor; one that had values of its own is given its own copy of the tensor when the project opens. See Stress Tensors.
- Stress from fault slip. Invert from Fault Slip (CSV)... on Collections → Stress Tensors reads the dip direction, dip and rake of faults (Aki & Richards' rake, with an optional weight) and inverts them by Michael's (1984) method for the principal stress axes and the stress ratio, with a 500-sample bootstrap of their confidence and the misfit of each fault. The result is a new tensor, Inverted (N faults), taking its magnitudes and failure parameters from the active tensor. See Stress Inversion.
- Slip Potential leaves Experimental. It is now Attributes & Analysis → Geotechnical → Slip Potential (Stress Tensor) on a mesh, and Stress Attributes (Slip Tendency) on orientation measurements.
- The Mohr diagram plots the selected planes against a stress tensor in the Charts pane: the three Mohr circles, the Coulomb envelope with critically stressed planes ringed, each set's joint-strength envelope and the Hoek-Brown envelope of any geotechnical domain you choose. It exports as SVG and goes into reports. See Mohr Diagram.
- The Mohr diagram's planes as a table. Planes Table (CSV)... on the Mohr diagram's right-click menu writes each plane's set, orientation, effective normal and shear stress, slip tendency, its Coulomb factor (strength over shear stress) and whether it is critically stressed. See The planes table.
- One selection everywhere. A plane selected on a stereonet, on the Mohr diagram, in the tree or in the 3D view is selected in all of them. Click and Ctrl+click poles on the net, double-click to fly to one, and use Go To in 3D View at the top of the right-click menus. Selecting an orientation folder selects its measurements.
- Renaming a set keeps its strength. Rename a Set in the Collections tree and its joint strength goes with it, every orientation tagged with it is retagged, and a name already in use is refused.
- Joint strength per set. A Set can have a Mohr-Coulomb or Barton-Bandis strength of its own. Kinematic analysis then uses its friction angle instead of one angle for every set, the factors of safety its strength, and the Mohr diagram draws its envelope. See Joint strength.
- JRC of each planar patch. Grow Planar Patches measures the roughness of every patch from profiles down its dip (Tse & Cruden's Z2 relation) and writes a Patch JRC layer, with a warning when the mesh is too coarse to resolve it. See JRC of each patch.
- Block Size maps the volumetric joint count Jv, RQD derived from it and block volume over a mesh or point cloud from its P32 or P21 layer, converting P21 to P32 by each set's angle to the local face. See Block Size.
- Rock mass classification. Rock Materials hold the intact rock (UCS, mi, modulus, unit weight), started from 28 rock types' typical values; Geotechnical Domains classify a rock mass by RMR89, Q and GSI and give the generalised Hoek-Brown parameters, rock mass strength, Erm and the equivalent Mohr-Coulomb c′ and φ′, each over a GSI range, with derived values labelled. See Rock Mass Classification.
- Tunnel support from Q. A geotechnical domain set to Tunnel takes a Span (m) and an ESR and gives the maximum unsupported span (2 ESR Q^0.4), the bolt length (2 + 0.15 span / ESR) and the roof support pressure (Barton et al. 1974), saying whether the span needs support. They are in the CSV export and field-sheet import, the report data sheet and Athos's rock mass classification. The Q support chart's categories are not drawn. See Tunnel support from Q.
- Tables in and out. Export the per-set table (Sets → Export) and the domains' classification as CSV, fill domains from a field sheet with Import Field Sheet (CSV)..., and Add Data Sheet to Report for a geotechnical data sheet in an analysis report. See Geotechnical Domains.
- Athos knows the sets and the rock mass. Two read-only tools give it the sets' statistics and joint strength and the domains' classification, each number with its basis. See Athos.
- More ways to find the sets. Auto-cluster adds Vollmer's P-maximisation, fuzzy k-means (Hammah & Curran) and density clustering (DBSCAN), which finds the number of sets itself; Evaluate k... tabulates D max, the mean silhouette and P-bar for k from 2 to 9, and Choose k automatically keeps the best. See Auto-cluster.
- Stress that varies with depth. A tensor can take its vertical stress from the overburden (Gravitational: unit weight × depth below a ground surface or a fixed elevation), its horizontal stresses from k ratios, Sheorey (1994) or gradients, and its pore pressure as hydrostatic below a water level or a water table surface. Slip potential on a mesh, slip tendency on measurements, a DFN's stress attributes and the Mohr diagram evaluate it at each point's depth, and the stereonet at a Reference Depth. See Variation with depth.
- Stress from your own fault measurements. Invert Stress from Selected Faults... on the Orientation menu pairs each slickenline lineation with the plane it lies in, reads the sense of slip from a Sense attribute, and inverts them by least angular misfit (Angelier 1979) or Michael's linear least squares. See From measurements.
- Borehole data. Two imports on a log's menu bring in what a geotechnical investigation produces: RQD Intervals (CSV)... puts RQD, core recovery and fracture counts on the log as curves, and Televiewer / Core Picks (CSV)... turns discontinuities picked on an acoustic or optical televiewer log, or measured on oriented core (alpha, beta), into plane measurements placed along the hole with their Terzaghi weights. See Geotechnical Borehole Data.
- Key Blocks. Find the removable blocks on the real surface of a slope or excavation by block theory (Goodman & Shi): from the project Sets at every point of a mesh or point cloud, or by cutting the rock behind a mesh with a DFN's fractures into real blocks. It maps each block's factor of safety, volume and mode, puts the movable blocks out as a mesh and gives the in-situ block size distribution, overhangs and roofs included. See Key Blocks.
- Rockfall Inventory. Two scans of a slope, registered with ICP and compared with M3C2, become a list of rockfall events with their areas, volumes and depths, a magnitude–frequency fit, rates over the interval, an event layer on the scan, and a back-analysis of which sets released the falls and whether the slope stability maps foresaw them. See Rockfall Inventory.
- Rockfall Trajectories. Lumped-mass blocks run down the mesh from wherever a layer marks the sources, the probability of failure from Slope Stability, say, bouncing with restitution coefficients and rolling with friction, and write how often blocks reach each part of the slope, their largest energy and their bounce height. See Rockfall Trajectories.
- Tunnel As-built. Compare a scan of a tunnel, drive or adit with its design profile along a centreline, overbreak and underbreak chainage by chainage and mapped on the scan, with a spalling screen (Kirsch, Martin et al. 1999), each set's orientation to the drive (Bieniawski 1989), the structurally controlled wedges in the roof and walls, Q support guidance for a geotechnical domain, and the design surface as a mesh. See Tunnel As-built.
- Fractures to 3DEC. A DFN's Export menu writes its fractures as an Itasca geometry file for 3DEC and FLAC3D, each set a group of its own. See Fractures to 3DEC.
- One Geotechnical menu. Slope Stability, Block Size, Bench As-built, Tunnel As-built, Rockfall Inventory, Rockfall Trajectories, Key Blocks and Slip Potential are gathered under Attributes & Analysis → Geotechnical on a mesh's menu, and all but Rockfall Trajectories and Slip Potential on a point cloud's.
Kinematic slope stability
- Slope Stability, under Attributes & Analysis on a mesh or point cloud, maps where a slope and your discontinuity sets let blocks slide or topple. It fits the slope face around every point at a scale you choose, overhangs included, and tests planar sliding, wedge sliding (Markland's test with Hocking's refinement), flexural toppling and direct toppling, taking each orientation folder or project Set as one set. It writes the percentage critical for each mode, of the most critical set or pair of sets, and a Kinematic Mode layer with the dominant mode at every point. See Slope Stability and its method.
- The same analysis on the stereonet. Kinematic Analysis, under Analysis Display Properties in a Stereonet window, draws the construction and critical zones for one slope face, and its key lists the percentage critical set by set and pair by pair, with the same sets as the maps. It draws in equal-angle and equal-area, and in the SVG export.
- Folders or project Sets. Both the maps and the stereonet take a set from an orientation folder or from a project Set (planes tagged J1, J2 …). The dialog lists Sets as Set: J1 and ticks them the first time when any planes are tagged; the stereonet's Sets From chooses. A plane chosen in two sets is warned about, since it would pair with copies of its own and inflate wedge sliding and direct toppling.
- Bench, inter-ramp and overall scales. One run can fit the slope face at a single radius and at the three scales of open-pit design, each writing its own layers, such as Planar Sliding (Bench). Every run also writes Local Relief, the height range within the radius, and Planes Within Radius. See Slope Stability.
- Weighting on the maps. Terzaghi (sampling bias) weights each plane against the face where it was measured — Planes seen on the face or Traces across the face, with a cap — and Lean on the planes measured within the radius blends each point's local percentage with the project-wide one, so one or two critical planes cannot make a sparsely mapped place read 100 %. See Weighting.
- Factors of safety. Tick Factors of safety (limit equilibrium) for deterministic factors of safety on each set's mean plane at every point: planar sliding after Hoek & Bray with a critical tension crack and water, wedges by the vector method with sliding on one plane and lift-off, a drained-wedge water pressure and a trace length limit, and block toppling after Goodman & Bray, with a seismic coefficient for all three. The slope height is the Local Relief, and each set's strength its joint strength. It writes Factor of Safety, FoS Planar Sliding, FoS Wedge Sliding, FoS Toppling and FoS Mode; the stereonet's Factor of Safety lists the factor of each set or pair for its face. See Factors of safety and the method.
- Probability of failure. Tick Work it out under Probability of failure (Monte Carlo) in the factor-of-safety settings, and each sample draws every set's plane from its Fisher spread (K from its own planes), its friction and cohesion from normal distributions and the water from a range. It writes Probability of Failure and one layer per mechanism, and an Acceptance layer against each scale's factor-of-safety and probability targets, which start from Read & Stacey's (2009) criteria for a moderate consequence of failure. The seed is recorded on the run, so a run can be repeated exactly. See Probability of failure.
- Probability and sensitivity on the stereonet. FoS Probability adds a PoF column beside each factor of safety and a Sensitivity table of the inputs that move the lowest factor most. Figure → Probability of Failure in the open report puts its histogram and tornado there.
- Bench As-built measures an open-pit wall's benches from the scan: berm levels, bench heights, achieved face angles and berm widths, each berm checked against the modified Ritchie width (0.2 H + 4.5 m), and, given a design surface, how far the wall stands in front of or behind it. It writes layers for each, and a bench table into the open report. See Bench As-built.
- Athos and slopes. Athos can work out the factor of safety of a planar, wedge or toppling block you describe, and summarise what Slope Stability found on a model at a scale — modes, factors of safety, probability of failure and acceptance — naming any layer that is missing.
- Renamed: the menu item is now Slope Stability... and its dialog Slope Stability; the tension crack choices read None and Critical. Block toppling starts unticked and will not run without a block width.
- Analysis runs. Every Slope Stability, Block Size, Key Blocks, Bench As-built, Tunnel As-built and rockfall run is recorded under Collections → Analysis Runs with its settings, the sets it read and the layers it wrote, named with its scale, and is marked stale when one of those sets changes. Re-run repeats a run exactly as recorded; Check for Stale Runs is on the same menu. See Analysis Runs.
Stratigraphy: contacts and units
- Contacts and units are separate lists. A picked boundary is a contact, and the interval between two contacts is a unit. In the Collections tree, Picks is now Contacts, and a new Units list sits after it; New, Delete and CSV export work on both. Each contact has a Contact Type — Unspecified, Conformable, Erosional (unconformity), Intrusive or Faulted — beside its Enabled, Age, Colour and Opacity; a unit has a name, ID, age, colour and opacity. See Contacts, Units and Intervals.
- Each object takes the list that fits it. Polylines and faults trace a contact (their property row is now Contact, was Stratigraphy). Orientations measured on bedding (row Unit, was Stratigraphy), geobodies, scan lines and stratigraphic units lie within a unit.
- Zones are now Stratigraphic Units. The Interpretation tree branch is Stratigraphic Units, and a unit is bounded by its Younger Contact and Older Contact (were Top Pick and Base Pick), with its name in the Unit row (was Interval Stratigraphy). New ones are named Unit 1, Unit 2 and so on. See Stratigraphic Units.
- The Active Descriptor has a contact and a unit. On the Interpretations tab the old Horizon dropdown is now Contact (New Contact, active contact), beside a new Unit group (New Unit, active unit). Apply, and Apply → Active Contact or Unit (was Active Horizon) on the right-click menu, give selected traces the active contact and everything else the active unit. New scan lines take the active unit. See the Active Descriptor.
- Older projects carry over. When a project saved before the split opens, every unit name already used by its orientations, geobodies, scan lines and stratigraphic units becomes a Units entry, with the colour and age of the contact of the same name, and one line in the messages panel says how many were made. Existing contacts open as Unspecified.
- Renamed to match: Geobody & Unit Infill (was Geobody & Zone Infill) in the view properties; the Stratigraphic Unit Definition dialog of Classification → Between Surfaces, with Unit, Younger Contact and Older Contact; Contact polyline group in the gridding-with-faults dialog; and Conformable Contacts (was Co-Horizons) on an implicit surface of a conformable stack. Seismic horizons keep their name.
- Fixed: orientation and geobody stratigraphy was lost on reopen. It was never written to the project database; it is now saved.
- Fixed: deleted picks came back. A contact deleted from the list reappeared when the project was reopened, and a new one could then reuse its ID. Deleted contacts and units now stay deleted.
Stress tensors in the Collections tree
- More than one stress state per project. The stress field has moved from Project Properties to a new Stress Tensors branch of the Collections tree, which holds as many tensors as you need — regional and local, measured and interpreted. One is active (shown in bold), and it is what slip potential, DFN stress attributes, the stereonet's stress field and kinematic analysis, and the slope stability friction angle use. Set as Active switches tensor, and an open stereonet redraws on its own. See Stress Tensors.
- Every tensor is validated when it is added and after every edit: the magnitudes must run Sigma 1 ≥ Sigma 2 ≥ Sigma 3 and must not be isotropic or negative, the axes must be perpendicular and the plunges within 0–90°, and friction must be positive with pore pressure and cohesion not negative. A change that fails is not applied, and the panel says why. A pore pressure at or above Sigma 3, or a friction coefficient above 1.2, is accepted with a warning.
- Older projects carry over. A project's existing stress field opens as the tensor Regional Stress, active.
- Several tensors are the new Geomechanics module (licence feature
GEOMECH). Every licence keeps one editable, validated stress tensor that every analysis uses; adding more, Set as Active, and choosing a tensor per DFN or per slip-tendency run need the module, and so do the Mohr diagram, the probability of failure figure and stress inversion. A project made with it opens without it, tensors intact, using the active one. See Feature availability. - Stress axes on the stereonet. Stress Axes under Analysis Display Properties marks σ1, σ2 and σ3 of the active tensor (circle, triangle, square) with a key of their attitudes, magnitudes, stress ratio and failure parameters, and exports them in the SVG. See Stress Axes.
- Mohr circle diagrams. Right-click the Charts panel's stereonet ▸ Mohr Diagram plots the same planes on the three Mohr circles of a stress tensor, in effective stress, with the Coulomb failure envelope; critically stressed planes are ringed red and counted. Its right-click menu picks the tensor and exports it as an SVG document, and a report's Figure ▸ Mohr Diagram inserts it. See Mohr diagram.
- Mesh slip potential picks its tensor too, from a submenu like the orientation command's.
- Each DFN picks its tensor. Stress Parameters > Stress Tensor on a DFN chooses which tensor its stress attributes and closure under stress use: the active one, or a named one that stays with the network. See Stress Attributes.
- Slip tendency on orientations picks its tensor too. With more than one tensor, Stress Attributes (Slip Tendency) on orientation measurements becomes a submenu of the active tensor and each tensor by name. See Orientation.
- The full set of stress attributes on orientations. Measurements carry what a mesh's vertices do: slip and dilation tendency, normalised and reduced-risk, fracture susceptibility and opening angle, worked out with the project's failure parameters rather than built-in defaults. The command takes folders as well as measurements, and works in the release build, where it was always greyed. The DFN gains reduced-risk dilation tendency and opening angle.
Folds on the stereonet
- Analyse Fold. Right-click the net and choose Analyse Fold to fit a fold to the selected bedding poles, or to all the bedding: the pi-circle, the fold axis with a 95% cone and ellipse from a bootstrap, the axial plane (both candidates when the interlimb angle cannot be resolved), the beta-axis, the limb mean poles and Fleuty's class, drawn on the net with a key and written up as a report page with a down-plunge profile of the positioned picks and traced contacts. Every run also tests whether the fold is conical and divides it into cylindrical domains along the hinge. See Fold analysis.
- From the result. Create Fold Axis & Axial Plane keeps them as a lineation and an orientation, Look Down Plunge in 3D turns the 3D view along the axis in orthographic projection, Create Down-Plunge Orthopanel bakes the outcrop seen in true profile, Save Fold Profile as SVG... saves the figure, and Export Fold for LoopStructural / GemPy... writes the bedding, contacts and fold frame for implicit modelling. See Exporting for LoopStructural and GemPy.
- The bedding statistics count bedding only. The Fisher K, α95 and mean ring on the net, and the figures Athos describes from it, used to count every plane and line on the net, faults and lineations included.
- Contouring is fast on large meshes. Contouring two million poles took about ten seconds, and ran again on most property changes; it now takes well under a second and gives the same bands.
Drone survey planning
- Plan Drone Survey, on a mesh's right-click menu, plans the flight that photographs the mesh again at a finer resolution: where every photo is taken to reach a target ground sample distance with the overlap structure-from-motion needs, flown straight down over ground, facing a hillside, or level along a cliff with each photo turned square-on to the rock in front of it. The path is kept clear of every loaded mesh and above the model's foot, split into missions that fit the battery, and exported as DJI Pilot 2 routes, Litchi missions, a Google Earth preview or a waypoint table, with headings converted to true north. See Drone Survey Planning.
- Focus and Exclude areas. Select triangles and use Drone Survey Area on the Edit tab to fly part of the mesh in detail, fly the rest in a coarser pass or skip it, and leave vegetation or structures out. A slope range keeps a cliff and leaves its beach.
- Reshape the path by hand through its keyframes with the 3D Translate tool, play it back through the drone's camera, and have Analyse Lighting follow the sun across the surface through the day, shadows cast by the terrain included, to pick the best time to fly.
- See where a photo lands. Click a photo position on a survey's path to draw that photo's footprint on the surface, draped over the terrain and dashed where the frame sees nothing in the model, with the footprints of the photos beside it. The Photo rows give its distance, GSD, footprint size and the front and side overlaps measured on the surface. See Looking at one photo.
- Convergent photos for ground. A nadir survey can tilt its camera forward along each line (Camera Tilt), so neighbouring lines see the ground from opposite sides, and can fly its detail lines again at right angles (Cross Grid). Both give structure-from-motion the convergent views that stop a model of flat ground from doming. See Convergent photos.
- Position Error is kept clear on top of Min Clearance, 2 m by default for GNSS and about 0.1 m with RTK. When shooting while moving, low-detail lines fly as fast as their coarser pixels allow, and a survey that takes more than 2.5 seconds to plan waits for Replan Now instead of replanning after every edit.
- Every change in a survey's properties can be undone, and Analyse Lighting now warns about the hotspot opposite the sun from any height, checking each photo's own direction.
Texture Track: an auto-tracker for the outcrop
- Texture Track, on the Digitise Polyline dropdown beside Geodesic Distance, follows a contact through the outcrop's photo texture between your clicks, the way a horizon tracker follows a reflector on seismic. Click on the contact and again a few metres along; the line finds the contact in between and lies on the surface. It unrolls a strip of the texture along the surface path between the clicks, tracks the contact in it from column to column with a limit on how steeply it may turn, at about 1 cm per pixel or the texture's own resolution if that is coarser (a finer texture gets a second pass at its own resolution), and drapes the result back onto the mesh. It is not drawn along triangle edges, so the line is as smooth as the contact. See Texture Track.
- It stays on the bed you clicked. The contrast at the clicks sets what it looks for, and between the clicks it expects the contact where a plane through both of them cuts the rock, the plane the texture agrees with best, and holds the line near that course, so a stronger parallel bed nearby does not capture it even where your contact fades over a long segment. On rough rock that matters: the shortest surface path between two clicks detours round bulges and recesses tens of centimetres off the bed, while the plane's trace goes over them as the bed does. Where the contact is covered by vegetation or scree it draws a straight line across the gap rather than wandering, and the status bar gives each segment's confidence.
- The texture strip follows the rock. Each column of the image it tracks in is the outcrop's own cross-section, followed over ledges and under overhangs, so a stepped or overhanging face no longer smears into the image it reads.
- Vulkan view, textured meshes. It follows contacts; for thin traces such as fractures, Geodesic Distance is still the tool.
Interpretations stay on their models
- Interpretations follow the mesh or point cloud they were made on. Each vertex of a polyline, orientation, log or other interpretation records where it lies on its host, so when the model is moved, by the gizmo, ICP, a control-point or tie-point correction, a rescale, a rotation, a change of coordinate system or an undo of any of them, the picks go with it instead of floating where the model used to be. Keep Interpretations On Their Models in the project properties turns it on: on for new projects, and an older project attaches its interpretations in the background, with a progress bar when that takes more than a few seconds. Re-attach to Surface on the Interpretation tree anchors a selection where it lies now, and a pass that moves vertices is one step of undo. See Meshes & Performance.
Measurements
- Coloured by type. Vertical, horizontal, 3D and multi-point measurements each draw in a colour of their own, chosen to stay apart for colour-blind viewers and set under Measurement Colours on the Measurements branch's properties, until coloured by hand; the connectors and risers draw in one grey. Existing red measurements take their type's colour.
- Ruler graduations. In the Vulkan view a measurement bar carries ticks at a 1-2-5 spacing chosen from its own length, with minor ticks between, and its label names the spacing (Show Graduations). 3D measurements draw at the width the display options say, half what they did, and grouped measurements show in the Vulkan view, where grouping used to hide them. See Measuring.
Sedimentary logs and the 3D view
- 3D interpretations on the log. Right-click the 2D log panel and tick Show 3D Interpretations to see where the polylines, orientations, geopolygons, interpreted surfaces and scan lines in the 3D view cross each log or pass near it, drawn across the log as dotted lines with their names and distances. Right-click one to place its contact as a pick there. A log through a geopolygon or a closed surface shows every crossing; a geopolygon's are its base and top, and they place the Older Contact and Younger Contact of the interval or unit it lies in. See 3D interpretations on the log.
- Correlation lines in 3D. The picks a correlation panel joins from log to log are joined in the 3D view too, in the contact's colour (Correlation Lines and Correlation Line Width in the Logs display properties).
- Logs move with their outcrop. With Keep Interpretations On Their Models on, a log stays attached to the mesh it was logged on, and its path, beds and tracked route follow the mesh when it is moved.
- Extract Image Track finds the outcrop itself, so the mesh need not be active, and asks for the strip's width (1 m to start, then the last width used) rather than half of it.
- Fixed: image tracks were upside down, and drifted against the beds. Rows are now spaced by height up the path, as the log measures TVT, and in TST and MT each bed's part of the strip is stretched to that bed. Extract older strips again. See Extracting an image strip.
The 2D log editor
- Selection and editing that act on every selected bed. Click selects a bed, Ctrl+click adds or removes one, Shift+click selects a run; a facies, grain size, contact or lithology chosen on the right-click menu goes to all of them as one undo step. Add New adds a bed above the top or below the base, Delete removes the selected beds into their neighbours, and in Split mode a bed boundary can be dragged. See Selecting beds.
- Logging from the keyboard. Number keys 1–9 give the selected beds your most recent facies, F lists every facies at the cursor, T cuts a bed at a typed height, B adds a bed on top, and Up and Down walk the beds. The depth modes moved to Ctrl+1/2/3. See Logging from the keyboard.
- A Bed Table. Right-click a bed or a log's header for Bed Table...: the log's beds in a grid, every edit applied as one undo step. On a straight vertical column beds can be added, deleted and given new thicknesses. A bed table imported with gaps between its beds gets covered beds in them. See The Bed Table.
- What a bed records. Bioturbation index (with a Bioturbation track), covered (not exposed), how certain its base contact is, Munsell colour (with a Munsell track), fossil abundance, and sequence-stratigraphic surfaces (SB, TS, MFS, FS) drawn by kind across a correlation panel. Base contacts draw as their own line styles, in the key too. See What a bed records and Base contacts.
- More on the tracks. Annotations put a symbol or a note at a height on any track; Symbols in Beds draws a bed's structures and fossils inside it; overlapping images on the Image track sit side by side and can be dragged into place; the Outcrop Profile track shows how far the face stands out up the log, and can be calibrated against logged beds to suggest a grain size. A Sample Count track bars the samples a metre. See Annotations and The outcrop's profile.
- Output at a true scale. File > Print, Export to SVG, Export to PNG... (at a chosen resolution) and Export to PDF... take a vertical scale such as 1:50; only the depths are scaled, so tracks and text keep their size. Each has a title block, printed pages repeat the track headers, the page orientation is honoured, and the depth axis can read in feet or down from the top. The PDF is one page the panel's own size, so a metre of log on paper is the scale's metre in any PDF viewer. See Printing and Exporting at scale.
- Annotations have an anchor and a size. A symbol's anchor, its top, centre or base, is the edge that sits on the height you clicked at every vertical scale, so roots hang from the top of their bed and flame structures stand on its base; a new symbol takes its anchor from its name. Drag a corner handle to resize a symbol, Ctrl+drag to copy one, and Duplicate puts a copy just below. See Annotations.
- Samples on the log. Click a sample on the samples track to pick it and see its properties, drag it into another bed (its 3D point goes with it unless it was placed in 3D, which the new Placed in 3D box records), rename it from the bed's properties, and delete it with the Delete key. Samples and correlation picks are placed in TST and MT as well as TVT. See Samples on the log.
- Correlation panels are saved with the project. A panel of two or more logs is listed under Correlation Panels in the Collections tree, where a double-click opens it as it was left; double-clicking a log opens its own panel. A flattened panel stays flattened when the vertical scale changes.
- Everything about a log is saved. Bed names, base contacts and palaeocurrent readings, a log's dip, azimuth and KB offset, every template track's settings and a log's markers now come back on reopen; deleted picks, unticked classes and deleted templates stay deleted; pattern fills stay visible at any zoom; LAS import keeps a log's path; and extracting an image track no longer overwrites another log's image.
Geological logging: the palette, the Quick Log and field notes
- Recently used names first. Every list a bed is given from, lithologies, structures, fossils, grain sizes, base contacts and pattern tiles, puts the names you chose last at the top of its right-click menu, with the whole list below a separator, and saves them with the project so a section logged over several days starts each day where it left off. See Recently used names first.
- The Log Palette. Log Palette on the 2D Log tab opens a pane of tiles for everything a bed can hold: facies in their colours and patterns, lithologies, structures and fossils as their symbols, contacts as their lines, grain-size classes and each generic class list. Click a tile to give it to the selected beds, drag one onto a bed, type in the box to filter every section, and fold sections and groups away. It opens with the first 2D log view of a session. See The Log Palette.
- The Quick Log. The box under the palette's filter (press Q) takes a bed as one line of notebook shorthand, such as
0.4 Sm fs/ms tcb erosive plant debris bi2, matching each word to your lists by whole name, unique start or initials. With a thickness, Enter adds a bed on top; without one, the line describes the selected beds; and a word in no list goes into the comment, so nothing you type is lost. See The Quick Log. - Paste beds from a spreadsheet. Paste Beds, or Ctrl+V in the Bed Table, takes rows copied from a spreadsheet or a typed-up notebook, in the table's own columns or under a heading line of your own; two columns, thickness and facies, are enough. See Pasting beds.
- Beds from field notes. Beds from Field Notes on a bed's or a log header's menu hands notes you type, paste or dictate to Athos, which reads them against your project's facies, grain sizes, lithologies, structures, fossils and contacts and opens the Bed Table with what it read. Nothing changes until you check it and choose OK, and anything it could not place is listed in the messages panel. See Beds from field notes.
- Contacts and facies suggested from the outcrop. On a log with an outcrop profile, Suggest Contacts from Outcrop cuts beds where the profile and image-strip curves change, and Suggest Facies from Outcrop gives each unlogged bed the facies of the logged beds it most resembles, learning from the beds you logged by hand on the same log. A suggestion is drawn queried and washed out until Accept Outcrop Suggestions, or a facies set by hand, confirms it. See Contacts and facies suggested from the outcrop.
- Athos reads your logs. Ask Athos to summarise a log, write its facies descriptions or look for inconsistencies: it reads every bed as the Bed Table shows it, and knows which facies and contacts were only suggested. It can also change what beds hold, previewing every change field by field and applying nothing until you agree; that part needs the hosted OpenAI or Claude provider. See Working with geological logs.
Logging lists, symbols and schemes
- Logging schemes. A project's facies, lithologies, structures, fossils, base contacts and grain-size classes travel as one
.vrgsscheme.jsonfile, through Import Logging Scheme... and Export Logging Scheme... on the Facies branch of the Collections tree. VRGS ships Fluvial lithofacies (Miall), whose codes the Quick Log matches directly. An import adds only what the project lacks and never changes a colour or pattern you chose. See Logging schemes. - A symbol library, and lithology fill styles. Lithology, structure and fossil entries carry a symbol drawn on their tracks, in the key and in the SVG export, and a new project's structure and fossil lists are filled from the library (33 sedimentary structures and the FGDC fossils). A lithology can carry a pattern fill as a facies does: 33 seamless lithology tiles come with VRGS as the Original Fill Styles group, Sandstone, Mudstone, Limestone and Coal pick theirs up by name, and Add from Library on the Lithologies, Sed Structures and Palaeo branches adds entries with their symbols. See Lithology fill styles.
- Groups in the long lists. Lithologies, sedimentary structures and fossils are listed in a folder per group (Cross Bedding, Invertebrates, Siliciclastic Rocks and so on), taken from the library's folders, and the Log Palette lays its tiles out the same way. Sed Fill Styles is now Fill Patterns. See Groups in Lithologies, Sed Structures and Palaeo.
- Class tracks for any list. A track of any Generic Classes list, carbonate textures, mineralisation, alteration or structural features, draws a column per class with its colour and symbol, as the structures and fossils tracks do; a list's Values grade what a bed holds by abundance or intensity, and Groups Shown makes a focused track of part of a list. New List from Library builds a list from a symbol folder no fixed collection takes. See Class tracks.
- Carbonate beds. A bed's profile is logged on the siliciclastic grain-size scale or on the carbonate Dunham scale, mudstone to grainstone, floatstone, rudstone, boundstone and crystalline, chosen bed by bed, so a mixed section changes scale as often as it changes rock, with the textures on the same profile axis. See Carbonate beds.
- Logs for every discipline. The guide, the Data tree branch, the ribbon and the properties say geological log rather than sedimentary log, since the same log takes a mineralisation, alteration or structural list as readily as a sedimentary one.
- The key shows what the logs use. The 2D log panel's key lists only the facies, lithologies, structures and fossils the displayed logs hold, under a heading for each, and the structures and fossils tracks give a column only to what each log holds (or, if you ask, to every class of the list) instead of a sliver for every entry in the library.
- In and out. A log exports as a bed table (CSV) or as LAS 2.0, with depths in TVT, TST or MT, and a bed table imports back as a log. SedLog CSV files import and export, and StraboSpot measured sections import as logs. Log templates export to and import from a file. See Bed tables and LAS.
- Core. A borehole log can hold its core runs (with recovery), core boxes and a depth shift, read from CSV and drawn on a Core track. A photograph of a core box is cut into its rows and laid on the Image track at the shifted depths. See Core.
- Statistics Report. Right-click a 2D log panel, a log's header, or a log's Analysis menu in the Data tree for a web page of the log's statistics, with a CSV of its beds. The page gives net to gross at a grain-size cut-off you choose, each facies' share and a log-normal fit of bed thickness, a thickness histogram, the facies transitions tested against a random order (chi-square), and a palaeocurrent rose with the Rayleigh test. Analysis → Statistics in the messages panel adds both tests. See Statistics report.
- Navigation and undo. The wheel scrolls, Ctrl+wheel zooms and Shift+wheel stretches the vertical scale about the cursor, and the middle button pans in every mode. Removing or swapping a track, and placing or moving a pick, can be undone, and an undo in the 3D view redraws the 2D log. Closing a 2D log view no longer takes many seconds on a large project.
Intervals
- The Correlations list is now Intervals. In the Collections tree an interval is a named span between a Younger Contact and an Older Contact, one or more units thick, set on its properties. Entries from the old list open as intervals with no contacts, a deleted interval stays deleted, and Export on the Intervals header writes them to CSV with their contacts. See Contacts, Units and Intervals.
- Intervals on a log's beds. The Correlate panel of the 2D Log tab has an Interval dropdown, with a button for a new interval, and Assign Interval, which gives the selected beds the interval (click a bed, Shift+click another). An interval is one unbroken run of beds on a log: assigning it again moves it, and a run assigned inside another interval cuts that interval to its longer part. See Intervals.
- Intervals correlated across the panel. Each log draws its intervals as a named bar beside the beds, and neighbouring logs that hold the same interval are joined by a band from base to base and top to top, in every depth mode and in the SVG export.
- Nested intervals. An interval can sit inside a parent interval and carry a rank, such as a member in its formation. The Collections tree nests them, an Intervals track draws each level as a column of named boxes, and Statistics lists them nested. Deleting an interval takes it off its beds, and the intervals inside it move up to its parent. See Nested intervals.
- Facies associations on the log. A facies' Association is now saved with the project (it was lost on reopening), a Facies Association track draws runs of beds by association, and Statistics gives each association's share. See Facies associations.
- From a geopolygon. A geopolygon or an orientation can lie in an interval: its Unit row and the Active Descriptor's Unit dropdown list the intervals after the units, and a geopolygon now has a Unit row of its own. On a log through a geopolygon, its base and top crossings can give the beds between them the geopolygon's interval and its facies.
Undo and redo
- Undo says what it will undo. The Undo button is greyed when there is nothing to undo, its tooltip names the step it would take, and its dropdown lists the recent steps: pick the third and three steps are undone. Undo and Redo are on the Quick Access Toolbar by default as well as the Interpretations tab, so they can be reached from any tab, and Redo works in the release build, where it was always greyed. See Undo.
- More can be undone. On a mesh: Delete Selected, Remove → Unused Vertices (the attribute colouring comes back with the vertices) and Conform Elevation. On a point cloud: Delete Selected Points, whose undo used to appear to run and leave the points deleted. Attributes → Replace Values; a group's display options, whose undo used to use up a step and restore nothing; and display options changed in the property bar, where nudging the same value several times makes one step rather than one per nudge. A viewpoint deleted from the Collections tree comes back in its place.
- Undo history is bounded by memory as well as steps: the last 20 steps, holding no more than 512 MB of saved mesh and point data, oldest dropped first. An undo step for a mesh edit takes about an eighth of the memory it did and is saved and restored more than ten times faster.
Finding a command
- Find a command by name. The Find a command… box on the ribbon searches the ribbon's commands as you type (orient, dip, export) and runs the one you pick from up to 12 results. It searches every tab, including the ones Basic mode hides, but not the right-click menus of the project trees. See Finding a command.
A new map window
- The 2D map is a web map. The map window draws every object in the project, mesh and point-cloud footprints, tiled models and surveys, polylines, faults, scan lines, sections, measurements and geobodies, orientations with strike-and-dip symbols, palaeocurrents, photos with their headings, waypoints, samples, control points, stratigraphic markers, labels, scan positions and flight paths, over OpenStreetMap, OpenTopoMap or Esri imagery with a Macrostrat geology overlay when the project has a coordinate system, or on a metre grid when it does not. Click a feature to select it in the tree and see its properties, double-click to fly the 3D view there, and right-click for the object's own menu; dense points cluster, the camera is a live dot, and ticking objects in the tree updates the map. See the Map View tab.
- Measure, overlay and save. A measure tool on the ribbon, a north arrow and scale bar, orthophotos and 2D rasters as overlays, a hillshade of every visible mesh, and Save PNG and Save PDF. The old map window and its Edit > Layers command are gone.
Discrete fracture networks: size, budget and stopping
- Create DFN says how big the network will be. Before anything is generated, the confirmation box for Create DFN from Selected Groups gives each set's expected number of fractures, the total, and the memory they would take, all worked out from the set statistics. A domain the size of the project with fractures the size of the digitised patches can ask for tens of millions of fractures; you now see that before committing to it. See How big a network will be.
- A generation budget. One generation places at most what a gigabyte of memory holds, about 1.4 million fractures. When a network would need more, the confirmation box says so and its default answer is No. If you go ahead, the set that reaches the budget is cut short, any sets after it get none, and the log warns which set fell short and by how much, because its realised P32 is below the target. Regenerate, Override P32 from Selected Traces… and the regeneration offered after Derive DFN Statistics… and Model Surfaces… ask the same question, but only when the network is over the budget.
- Generation can be stopped. The progress bar's Terminate button stops it. A stopped Create DFN leaves nothing in the project; a stopped regeneration leaves the DFN empty rather than holding part of a network, which would be a wrong model rather than a smaller one.
- Terminate stops more DFN commands. Fracture Intersections clears the previous run's lines rather than leaving them on screen; Mesh Intersections creates no polyline group; Score DFN against Selected Traces… stopped while the DFN is being cut scores nothing, and stopped during an ensemble it scores the network as it stands without the ensemble's spread. While one of these runs, other commands are refused and the log says why.
Flow through a fracture network
- Connection Mesh for Flow. DFN → Analysis → Connection Mesh for Flow... builds one triangle mesh of the connected backbone of the network, every fracture with two or more connections triangulated in its own plane and joined along the intersection traces, refined to a target edge length, with each fracture's aperture and transmissivity from a per-set aperture model. It then solves steady flow through it along X, Y and Z: the permeability with the sides closed, the full permeability tensor with its principal directions, and Oda's tensor for the same fractures beside them. Each fracture's share of the flow is written back to the DFN as FlowRate and FlowShare layers, so the network can be coloured by how much each fracture carries, and the summary says how few fractures carry 90% of it.
- Particle tracking. Tick Track particles to release particles on the inflow face and carry them through the solved flow to the opposite face, by complete mixing or streamline routing at each intersection: travel times and path lengths, a breakthrough CSV, the first hundred paths as tube meshes coloured by travel time, and how many particles passed through each fracture.
- Apertures under stress. Each fracture's aperture can be closed under the effective normal stress on its plane before the flow is solved, by a Barton-Bandis or exponential closure law with per-set stiffness, with critically stressed fractures kept open and dilated, so the permeability follows the in-situ stress.
- An ensemble of realisations. Set Realisations above 1 and each DFN is regenerated that many times, meshed and solved with the same settings, and the spread of permeability reported as P10, P50 and P90 with a CSV; the DFN itself is not changed. The whole run goes on in the background, with Terminate on its progress line.
- Regenerate forgets the old network. Attribute layers, intersection lines and the fracture graph used to survive a regeneration and describe fractures that no longer existed; they are cleared, and the log says which to generate again. A set whose sampler fell back to uniform positions is now named, with the reason.
Modelling grids and variograms
- Create Modelling Grid... on a mesh, a point cloud or a polyline builds a corner-point grid over what is selected. Modelling grids are experimental and are not switched on in a standard session. One outcrop model gives a grid with a flat top and base at the model's own heights; two or more meshes become horizons, stacked by elevation, with the zone between each pair layered on its own; and where two horizons cross, the upper either cuts into the lower (an unconformity) or laps out against it (onlap). The grid is described by its centre, size and cell size, with the model's azimuth and dip set apart from the grid's own, so a grid can follow a palaeocurrent or a foreset inside a regionally dipping model; cells at the model's edge are cut flat rather than stepped, and Recalculate Size fits the model box to the sources again.
- Looking inside a grid. I/J/K slicers show the skin of the cells that remain, a Contains Data layer marks the cells the source clouds and meshes occupy, any cell attribute can filter the skin, and a click on a cell in the Vulkan view highlights it and reports its I/J/K, centre and every layer's value. A grid saves its cell attributes, and deleting it deletes its cells mesh.
- Variogram 3D. Attributes & Analysis → Variogram 3D on a mesh or point cloud builds directional semivariograms of the attribute it is showing along a major, intermediate and minor axis, and omnidirectional, and fits a geometric-anisotropy model (spherical, exponential or Gaussian) with a range per axis. The axes are aimed with the orientation gizmo and start on the source's best-fit plane; the model is drawn as a range ellipsoid, the Charts pane plots the experimental and model curves, the lags and the fit can be edited by hand, and Open Report writes the chart and lag table to a report. An axis whose lags never reach the sill is reported unresolved rather than given a guessed range.
Importing point clouds and meshes
- A list of every 3D format VRGS reads, with what each reader brings in, which can be dropped onto the window, and the limits of each: Supported 3D File Formats.
- ASCII point clouds keep every point. The first tenth of every file was skipped without a word. Header, blank and comment lines are now skipped instead of becoming points at the origin, and the dialog's Skip Header count is honoured.
- PTS and PTX scans import correctly. A PTS keeps its intensity (the layer was always empty), an
X Y Z R G Bfile gets the right colours, and a file without a point-count line reads. A PTX no longer puts its first four points at the origin, leaves out the cells with no return instead of piling them on the scanner, and its colours no longer saturate. A scan with intensity but no colour is shaded by its intensity. A file holding more than one scan says so, as only the first is read. A COLMAPpoints3D.binno longer comes in with saturated colours either. - LAS and LAZ clouds without colour are shaded by elevation instead of coming in black — LAS 1.4 point format 6, the usual airborne and mobile lidar format, among them.
- Every LAS point format reads, compressed or not.
.lasand.lazfiles in LAS 1.0–1.4 point formats 0 to 10 now read correctly. A.lasin formats 7–10 used to come in as garbage, formats 4 and 5 and format 6 with extra bytes read out of step, and a.lazkept only position, intensity, class and colour — with classes above 31 read as 0 and no colour for formats 7 and 10. Both now keep the return numbers, scan angle (in degrees), GPS time, user data, point source, classification flags and near-infrared, and colour written as 0–255 comes in at full brightness. Intensity is kept as written; a.lasused to scale it to 0–1. A file whose name is outside the Windows code page now opens too. - LAS and LAZ files land in the project's coordinate system. A file that names its coordinate system, by EPSG code or WKT, is transformed into the project's when the project has one, as a GeoTIFF elevation model already is; X and Y move, heights are only converted between units. The messages panel says what the file declared and whether it was moved. Import → As Tiles…, which read a LAS file whole despite its name, is gone.
- LAS files exported from VRGS declare their record length. It was written as 0, which stricter readers refuse; VRGS still reads its old exports.
- A binary PLY with 16-bit unsigned properties no longer crashes VRGS (PDAL writes these), and 16-bit columns in an ASCII PLY no longer shift every column after them.
- PLY meshes read whole. A textured PLY in MeshLab's layout came in as a single triangle or as garbage, because the texture number after each face was never read; it now reads, and picks each face's texture. Faces of four or more corners are triangulated: in an ASCII file they threw every later value out of step, and in a binary one each kept only its first triangle. Face colours no longer shift the faces after them, a face that names a vertex the file does not have is left out with a count in the messages panel, and a file that cannot be opened or is not a PLY says so. A textured PLY also keeps its shared vertices, as an OBJ does, instead of three vertices for every triangle, so it takes less memory and shades smoothly rather than faceted.
- Drag and drop takes more files. The project tree takes the same files as a 3D view, and both now take PTS, PTX, glTF, STL, SEG-Y, COLMAP's
points3D.binandimages.bin, VRGS.pcl, PIF, USGS DEM and BIL; dropped.bmpimages work again. A file that cannot be dropped is named in the messages panel. - Extensions in any case, names in any script.
SCAN.LASno longer opens the ASCII column dialog, a droppedMODEL.GLBis oriented asmodel.glbis, and a file or folder name outside the Windows code page no longer stops an import. - Imported meshes appear at once. glTF, GLB, FBX, STL, GeoTIFF, HiRISE and Aarhus Workbench meshes from Import → From File…, models downloaded in the DOR browser, a dropped ArcInfo ASCII grid, a downloaded elevation model and meshes from plugins now show without saving and reopening the project. A file that yields no mesh says so and leaves no empty mesh in the tree, and a glTF, GLB, FBX or STL file that cannot be read gives the reason.
- HiRISE DTMs land where their label puts them. The east–west projection offset was never read and the north–south one was out by the image's height. A lower-case
.imgin the mesh dialog now goes to the HiRISE reader rather than the TIFF one. - glTF, GLB and FBX models come in as they were built. The node tree was ignored, so every piece a model placed by its nodes landed at the origin and a part used more than once came in once: a chess set arrived as one pile with a single pawn. Each mesh now goes where its nodes put it, once per node that uses it, with mirrored parts still facing out. A
.gltfno longer comes in upside down where the same model as.glbstood up. An FBX is turned by the up axis it declares and scaled to metres from the unit it declares, whether it is dropped or imported from the dialog. Embedded textures each keep their own image after a save: every page of a model was saved under one name, each over the last. A model in a folder whose name is outside the Windows code page now finds its textures. A material with no texture came in black; it now comes in its own colour, and Draco-compressed meshes and KTX2 (Basis Universal) textures are read. - 3D Tiles of your own. 3D Tiles from File… and 3D Tiles from URL… in the Home ribbon's base-map gallery show a 3D Tiles tileset — a
tileset.jsonon disk, a web address, or a Cesium ion asset by its number — in place of the base layer, placed by the project's coordinate system. The loading code was there but nothing called it. A project with no coordinate system is offered the UTM zone the tileset is in, the view moves to the tileset once it has loaded, and a tileset not placed on the Earth is refused with a message rather than loading out of sight. - E57 imports again. It had not imported at all for several releases. Every scan in the file comes in, each placed by its pose, as one cloud with a ScanIndex attribute to tell the scans apart, with intensity, colour scaled by the file's own limits, and time stamps. Points with no return are left out, and a file that names its coordinate system is moved into the project's. An
.e57can be dropped onto the window or the project tree. - Safer archives and logs. A scene layer package or DOR download can no longer write files outside the folder it unpacks into, and the elevation download no longer writes your OpenTopography API key to the log.
- KML and KMZ. Placemarks import as polylines and waypoints with their folders as groups, and the files can be dropped onto the window; a file with network links offers to download the linked layers, listing the hosts first. A model whose extent makes no sense in the project's coordinate system, local coordinates in a georeferenced project or a position outside the system's area of use, gets a warning badge in the tree. See Getting Data In and Out.
Photogrammetry and meshing
- A plan before the run. Run Reconstruction first shows what the next run will reuse and redo and why, the time it expects from the last run's timeline, what will give the model its size and position, the region of interest, and the last run's peak memory against what the machine can commit now, and asks before it starts (Confirm each run with its plan turns it off). What Will the Next Run Redo? on the workflow menu gives the same answer at any time, and every run keeps a stage timeline in its quality report.
- A model with no real size says so. Without camera GPS, three marked control points or a scale bar, a reconstruction has an arbitrary size and orientation; the run now says so before it starts, names control points that will not take part, and the model's properties carry a read-only Real-world scale row.
- Guided control-point marking. Once a model is georeferenced, each unmarked control point is drawn in every photo that should see it, the Mark Ground Control Point menu says how many photos each point appears in, Next Photo for This Point (N) opens the next one, and a Control points row in the workflow tree counts the photos marked and flags a point short of two. See Ground control points.
- Why a photo did not register. The photo table's Why not registered column gives the reason (never offered, no intrinsics, too few points, no consensus pose, pose rejected) and the registered photos it matched best, and two bulk actions disable or re-enable every failed photo for the next run.
- A region of interest. Set Region from Selected Points on the workflow menu limits dense matching and the mesh to a box: only the photos that frame it are swept, only the points inside it are fused and meshed, and the mesh dialog says what will be meshed. Registration still uses every photo.
- More photos register, with a better lens. One focal length (square pixels) is the default, the lens is refined on the whole survey after the build, and fewer photos are left unregistered. Add Photos... keeps the window responsive through a large import.
- A denser, cleaner dense cloud. The GPU plane sweep is the default dense backend. A view of a cliff no longer searches out to the far shore, the ground under the drone is included, depths only one neighbouring photo saw are dropped, and each point records how many views saw it (Fusion Views) and its precision (Fusion Sigma), carried onto the mesh.
- Textures that match from photo to photo. The bake solves exposure and white balance across the photographs so they agree where they overlap, blends in two frequency bands so seams dissolve without doubling edges, fades a photo out where it disagrees with the others at a texel (Texture blend ghost filter), and takes a Texture sampling sharpness and a Texture chart size setting. It budgets its photo decode against the memory the machine can still commit, not only what is physically free. See Texture blend sharpness.
- Poisson meshes you can trust. Every Poisson mesh carries Support Distance and Poisson Density layers saying where it is measured and where it is filled in; Mark the filled-in surface instead of deleting it keeps the closed surface and flags the invented part in an Interpolated layer; and the trim removes the blanket past the edge of the data but keeps small enclosed holes filled, and needs three points to support a vertex. Normals are aimed at the plane through each sample's neighbours, a lidar cloud's normals face its scanner, LAS vegetation and noise classes can be left out, a mesh re-meshed in place keeps its layers, and Decimate makes a copy and leaves the original. Meshing from the Data tree now passes the cloud's colour and normals, as the workflow always did.
- Better Poisson meshes. Create Mesh (Poisson) and Poisson Reconstruction use a newer solver. On test patches of a coastal drone survey it put the surface 7–20 % closer to the points, invented no more surface after the trim and needed about half the memory, and it is much faster on large clouds. Use the legacy PCL solver in the dialog keeps the old one for this release. The small loose pieces the trim used to leave behind, which had to be deleted by hand, are now removed automatically (Smallest piece, 25 octree cells by default). See Create Mesh (Poisson).
- Keep every mesh. Create Mesh no longer clears a workflow's previous mesh: every mesh it made is listed under the workflow's outputs, and the commands that need one ask which. Select Mesh Surface No Photo Sees selects the sheet behind or inside the face that no photo can texture, for you to delete.
- Use as Mesh Texture projects one photogrammetric image onto its mesh through its own calibrated camera, in the Vulkan view, from the photograph view, the Data tree or a right-click on a camera glyph. The mesh's texture shows wherever the photo does not see the surface, the photo fades out at its frame edge, and Apply Lens Distortion can be turned off for photos the camera already de-warped. One photo at a time, for the session.
- iPhone HEIC photos go straight into an SfM workflow. Add Photos… accepts
.heicfiles and converts each to a JPEG as it imports it, keeping the GPS and camera EXIF, the orientation the camera stored and the colour profile, so there is nothing to convert first. It needs Windows' HEIF and HEVC extensions from the Microsoft Store. See iPhone (HEIC) photos.
Aligning models
- ICP for point clouds, and against point clouds. The point cloud tab has the ICP panel, so a cloud can be aligned to a mesh or another cloud, point to point or point to plane; point to plane against a cloud fits a plane through each point's neighbours. ICP now aligns to one reference you pick from a menu, rather than to every displayed mesh in turn, and the ribbon shows the active object's own settings (Keep Closest %, sampling, cutoff). See ICP Alignment.
- Outcrop models onto elevation models. Point to plane against a DEM used to tilt a cliff model by a couple of degrees, matching the cliff face to the DEM's ramp across it. A height-field reference now leaves out facets and points steeper than 60°, weights the pairs robustly so vegetation does not pull the fit, and writes each vertex's signed distance to the reference as ICP_Residual. Point to point against a DEM runs point to plane instead, with a warning.
- Cameras move with their model. A model's photogrammetric cameras follow it through ICP, undo and the transform gizmo; they used to stay behind, or turn inside out. A GeoTIFF whose cells are points rather than areas landed half a cell off, and an ESRI ASCII grid had its half-cell rule backwards; both are placed correctly on import, and a DEM imported earlier keeps its place until it is imported again.
Outcrop.io and RockLab
- Prepare for Outcrop.io... on a mesh's menu builds the level-of-detail package the platform now takes, five levels as Draco-compressed GLB files with their textures embedded, on your own machine in the background, and offers to upload it to the mesh's linked outcrop or a new one, with the displayed interpretations as GeoJSON if you ask. An unchanged package is reused rather than rebuilt, an upload refused for want of a sign-in is offered again when the GeoTour login completes, and each level's texture pages are sized to fit a browser. A 22-million-face model builds its ladder in about three minutes where it had not finished one level after seven.
- RockLab projects find their models by relative and
file:paths, place legacy projects as local offsets rather than scattering them round the globe, and read Pix4D OPF point clouds as glTF; large clouds load on a background thread.
The 3D view
- Zoom at the cursor. The Vulkan view's mouse wheel holds the point under the cursor still, as the OpenGL view always did, instead of dragging what you were aiming at off towards the edge, and Reverse mouse wheel is honoured. Dragging down from View From Above no longer flips the model half a turn on every mouse move.
- Keys. F6 cycles perspective, orthographic and orthographic with a grid; F8 toggles the procedural sky and F9 the satellite basemap.
- Freehand N-point orientations. With the N-point tool active, the space bar switches to a draw mode in which dragging the mouse across a surface collects the points for the best-fit plane.
- Streamed terrain graded to match your models. Brightness, contrast, saturation, gamma and white balance sliders bring Cesium imagery into line with a project's photo-textured meshes, and the terrain is lit as the meshes are. The terrain can be picked and navigated on in the Vulkan view (it rendered but took no clicks), its geometry lives in video memory, and the terrain mask is baked once instead of once per frame, so a view with tiles on no longer crawls.
- Auto Contrast on a mesh works in the Vulkan view; it had never done anything.
- What you edit is what you see. A translated or transformed mesh shows in its new place at once rather than after a save and reopen; mesh intersect and split show their result; Delete removes the selection in the selection tools and Delete Selected takes the triangles out of the view; polyline ribbons draw their Line Style and redraw when a property changes; waypoint, sample and media display styles are honoured; a click fills the Properties pane; faults draw; and the view toggles, log display options and property-grid edits are saved with the project.
- The orientation gizmo. One gadget: double-click it, or press R, to switch between the translate arms and the orientation knobs, which are half the size, resize with Ctrl+wheel, and have both ends drawn so a drag through 90° cannot strand the knob. An orientation aimed with the gizmo was stored 180° from the one drawn; check any aimed with it before 3.4.8.
- Geopolygon extrusions follow the bed. A channel body's path runs along its bedding plane rather than horizontally, aimed first by its palaeocurrents, then its structural reading, then its outline, and Create Centreline > Linear and > Sinuous work again.
- Flight path viewpoints are restored whole. Navigate To on a viewpoint in the Vulkan view restores the saved pose rather than stopping an orbit distance short with the old heading, and clicking viewpoints, scenes and slides in the tree no longer leaves every earlier one bold.
- Implicit surfaces solve faster, from all your stations. A conformable stack solves its field once rather than once per horizon, a reloaded project no longer asks for a rebuild before a DFN can use the surface, dip stations are thinned on a lattice of their own (Orientation Spacing) so a hand-measured traverse passes through whole, and two opposed near-vertical measurements no longer average to a horizontal bed.
- Cross sections in folders. New Group on the Sections header makes a folder, sections drag between folders, and opacity is a property of the Sections group and its folders rather than of each section.
Projects, saving and memory
- Ctrl+S saves the project, database and all, from a 3D window; it used to open a Save As dialog and then fail. A report or field guide window still saves its own page.
- No edits lost on the way out. Every route that closes or replaces a project (Close, File > New, File > Open, the recent list, Explorer, a drop on an empty window) now offers to save first, and Cancel keeps the project; File > Open shows its dialog before anything is closed; Cancel when Windows shuts down or End task asks about saving keeps VRGS open rather than closing without saving; and the project refuses to close while background work runs.
- Older projects open again. A
.vgpfrom VRGS 2.x opens and upgrades with every polyline, orientation, measurement, fault, scale bar and ortho image it holds. The upgrade's save used to write one vertex of thousands, so the upgraded project crashed on reopening; a project upgraded before this fix should be upgraded again from its.vgp. - The recent projects list names each project with its folder, treats a
.vgpand its.vgpxas one entry, and asks before dropping one whose file has gone. - Hidden models give their memory back. When physical memory runs below 15% or 2 GB, the meshes and point clouds hidden longest are released one at a time until a quarter is free again, and read back from their files when shown; a model with unsaved edits, or one a tool is using, is never released. Release Models Hidden For (seconds) and Treat Memory As Low under Meshes & Performance in the project properties set the idle time and force the release.
- Projects open faster. The largest meshes load in a fraction of the time, and the project trees no longer slow to a crawl on large projects: selection, check boxes and menus in a tree of many thousands of rows are near-instant.
- Texture pages of 2 GB or more no longer crash VRGS on the first draw of a freshly imported textured mesh, and Max Texture Size now defaults to 16384.
- Mesh export, whole and filtered. Right-click Export on a mesh offers GOCAD TSurf, Stanford PLY at double precision with the mesh's colours, ASCII points, and Petrel points and attributes beside Assimp's formats, and every format writes the same triangles: none deleted or hidden, and only those the ticked attribute filters keep, with a note of how many were left out.
- One texture set per mesh file. A project saved after several texture bakes reopened with the newest bake's layout and the oldest bake's pixels; a mesh file now saves its active texture set alone, and the comparison sets are for the session.
- The trees. Mesh and point-cloud folders have Delete Group; ticking a bare header (Sections, DFN, Flight Path, Surfaces, Log Elements) applies to its children; a group's check box agrees with what is under it in all three trees; and DE volumes, drone surveys, DFNs, modelling grids and variograms have icons of their own.
Also
- Move a whole line by one of its vertices. In Move Vertices and 3D Translate, hold Alt while you drag a polyline or fault vertex and every vertex of the line moves with it, keeping its shape. Releasing Alt mid-drag goes back to moving the one vertex. See The Edit panel.
- Labels are hidden behind the model in recordings, matching what you see in the live view. They previously drew through foreground geometry in captures and recorded flights.
- Deleting the object the property bar is showing no longer crashes VRGS, whether you delete the object itself or a group that contains it, and also when the histogram pane is showing it.
- Remove → Unused Vertices no longer scrambles a mesh's attribute colours. After triangles had been deleted, removing the unused vertices left the colours on the wrong vertices.
- Picks land on a mesh's current shape after an undo of Move Mesh or Remove → Unused Vertices; they used to land where the vertices had been.
- Remove → Unused Vertices with a mesh and a point cloud both selected no longer crashes; the cloud is skipped.
- Athos finds the right passage first more often. Help and literature searches now pass their candidates through a small reranking model installed with VRGS, which reads each one against your question; it runs on your own computer and adds about a tenth to a quarter of a second per search.
/rerank offturns it off. See How Athos picks the passages. - A larger reranking model for NVIDIA graphics cards.
/rerank model granitedownloads Granite R2 (about 600 MB, GeoTour sign-in), and on a PC whose card can run it Athos offers the download once in the chat with a one-click button. Granite R2 reranks on the graphics card and puts the right passage first more often than the standard model, especially when your question does not use the passage's own words. Without a suitable card, or when the card is busy, searches use the standard model. See How Athos picks the passages. - Clearer messages when Athos cannot reach the service, telling you whether it is a permissions problem, a rate limit or an outage, and sign-in refreshes so a long session no longer drops.
/switchand/providertell the truth. The provider list named models that were not the ones in use and offered a switch that did not work. Both are now correct, and/switch Claudewith a capital letter is accepted. A Claude answer cut off for length says so instead of arriving looking complete.
🐛 Fixes
- Mesh Merge shows, draws and picks the merged mesh at once rather than after a save and reopen.
- Duplicate on a mesh gave the copy the original's tree row, so selecting, renaming or toggling the copy acted on the original until the project was reloaded.
- Polylines digitised on a photograph land on the model and in the tree; a click that misses the surface is logged rather than dropped, and digitising on an uncalibrated photograph warns. Photos imported from a Pix4D OPF keep their camera calibration across save and reload, and re-importing the same OPF no longer duplicates them.
- A mesh or point cloud a background task is using cannot be edited until the task finishes, instead of being corrupted.
- Deleting a folder of waypoints, samples, markers or labels, or a tiled model, frees the memory it used; a tiled model used to hold on to it until VRGS closed.
- Editing a slide board's slides no longer crashes VRGS, and Move Up and Move Down no longer swap the wrong images.
- Reset window layout after a Field Tour no longer crashes, and VRGS says why when its main window cannot be created instead of exiting silently.
- Slope Stability counts every wedge that passes Markland's test on the maps, and the stereonet's SVG export writes text XML can parse.
- OpenStreetMap tiles load in field-guide maps; VRGS now identifies itself to the tile server.
3.4.4 – 3.4.7 – Trust, Tours and the Field
August – September 2026
Measurements now tell you how much they deserve to be believed, flight paths build themselves from the places you care about, and VRGS goes into the field with an RTK receiver.
✨ New & Enhanced Features
How good is that pick?
- Every plane fit carries a grade —
excellent,goodorrejected— against the benchmarks published by Tavani et al. (2024). It is a label, not a veto: a rejected pick is still made, plotted and exported, so you can sort your measurements by how much to trust them instead of finding the weak ones later on a stereonet. See How good is the pick?. - The grade appears next to the cursor while you digitise, not once the trace is finished. It counts up to the eight-node floor, then names the test holding the grade back, so you know whether to add nodes, spread them off the straight line, or give up on that piece of the face.
- The interpretation spreadsheet has fit-quality columns and sorts by any of them, across the orientation, polyline, fault, geopolygon, measurement and scanline sheets. See The Interpretation Spreadsheet.
- The same grading runs across a whole mesh or point cloud as an attribute, with plane scatter, RMS residual, linearity and planarity. See Plane fit quality.
- A three-point pick is no longer waved through regardless of how collinear the clicks are, and the Error column reports real scatter instead of a constant zero.
Flight paths build themselves
- Mark the places you want a tour to show and press Auto Generate. VRGS works out where to stand the camera, which way to face and how long to take, following bays and noses in the face rather than orbiting a bounding box, and checking the line of sight against the real geometry. Choose a waypoint tour, an orbit of every point, or a face-on traverse.
- Check Path walks the whole flight and finds where the camera passes through the outcrop — the curve, not just the keyframes — then offers to nudge the surrounding viewpoints clear.
- Constant Speed re-paces a path from the distance actually flown, without changing the total duration, so narration timed against it stays put.
- Ease-in/out works. The SmoothStep tick on a viewpoint had been in the properties for years doing nothing.
- Reorder, reverse and hold. Move viewpoints up and down, insert one midway, reverse the whole path, and Hold Here to stop the camera at a viewpoint while recording. Each keeps the segment timing correct.
- See the Flight Path User Guide.
Narrated tours export as video
- A guided tour records to MP4 with its commentary mixed down into one soundtrack, and stop-and-talk holds become real frames so the video pauses where the tour does. A field guide authored in VRGS can be handed to someone who does not have VRGS. Tour audio needs the Vulkan renderer.
GNSS field navigation, rebuilt
- RTK receivers and multi-constellation receivers are supported, and a panel in the status bar shows your live fix, so a drop from centimetre to half-metre accuracy is visible while it happens.
- Navigate To takes any point you pick on the outcrop and gives you distance, bearing, height difference, how far you have drifted off the line and roughly how long the walk will take.
- Record an orientation, waypoint or sample where you are standing, each stamped with the survey quality it was taken at.
- See GNSS Field Navigation.
Analysis reports
- A new document that collects stereonet statistics, DFN results, charts and views of your model into one page you can export as a PDF and send on. Text can be written by you or drafted by Athos, with every suggestion shown before it is applied. See Analysis Reports.
Cross sections edit through their pillars
- With 3D Translate armed, each bend in a section line carries a handle at mid-height on the curtain, where you can reach it. Drag it sideways to re-route the bend, or up and down to move the whole section. Every drag is a single Undo. See Cross Sections.
Field guide viewpoints can take the scene with them
- Tick Visible objects before Get Viewpoint and the link records what is on display — models, scale bars, terrain and imagery — as well as where the camera is. The editor and the reader now agree on text styling, and blank lines between paragraphs survive a save. See the Virtual Field Guide Editor.
Also new
- Live coordinates in the status bar, updating as you move the mouse across the model rather than only when you click.
- A quieter messages panel, on request. Right-click the panel and tick Hide Non-Essential Messages. The choice is remembered, and everything still reaches the log file.
- The installer asks where to put VRGS, and shows the licence agreement.
🐛 Fixes
- VR is much faster on a large interpretation. A project with many polylines could pin the headset at a few frames a second. Showing and hiding objects in the tree now reaches the headset, and VR no longer fails to start on some hardware.
- The rotation centre updates again. In the Vulkan view, rotating could pivot about a stale point rather than the geometry under the cursor.
- Imagery attribution draws in the Vulkan view. Cesium ion, Bing and Google credits were missing, a provider supplying its credit as a logo was dropped, and a long credit line ran off the edge.
- Gamepad navigation is easier to control. Movement and look speeds are re-tuned, resting triggers no longer creep the camera, and a wireless controller that drops out no longer sends the view flying on its last frozen reading.
- Dragging a vertex on a cross section no longer moves the whole section after a section handle has been used earlier in the same session.
- Polylines shown as ribbons pick where you click on them. The Edge Smoothing option, which had no effect in either renderer, has been removed.
- A double-click that finishes a tool no longer leaves a stray point behind.
3.4.1 – 3.4.3 – Vulkan by Default
August 2026
Everyone moves onto the Vulkan renderer in this release, stratigraphy now belongs to the objects you interpret rather than to a single mesh, and large projects save and open a great deal faster.
✨ New & Enhanced Features
Vulkan is now the default renderer
- VRGS starts in Vulkan for everyone. It is no longer a licensed extra, and your existing licence needs no changes.
- You can have several 3D views open at once — separate model windows side by side, and the splitter panes that show other people's views during a multiuser field trip.
- Selection is easier to see. Selected objects are drawn with an outline, and polylines hidden behind the outcrop show as ghosted lines that fade out with distance, so a busy interpretation stays readable.
- Ortho panels, geobody centre lines, scale rings and edit handles, and stratigraphic zones all draw in Vulkan. An ortho panel keeps its image when you reopen a project, instead of coming back blank.
- Palaeocurrents on a geobody can be drawn as a rose diagram or as a fan of arrows with the mean direction highlighted — a new option in the group's display properties.
- Move and rotate an object with on-screen handles. Drag an axis arrow to translate a mesh or point cloud, a ring to rotate it, with the object previewed in place as you drag and the change committed when you let go. The rotate handles had no rings in earlier builds, which made rotate mode impossible to use at all.
- Touch and pen input, for Surface-class field hardware.
- Painting respects what is in front of what, so a facies stroke no longer paints through an occluding wall onto the surface behind it.
- More object types draw in Vulkan — mesh graph networks, voxel model slices and ortho images. A project containing a type the view still cannot draw now says so in the messages panel instead of silently omitting it.
- Captures and recordings include Gaussian splats, which were previously missing from saved images and video.
- Flight path presentations show their overlay, and the transport controls drive the Vulkan view.
- Picking works where it used to fail. A mesh you have just imported can be picked straight away, without saving and reopening the project first. Ortho panels are picked in front of the rock behind them. Sticky Interp is honoured when you place orientations, faults and scanlines, and when you extend a polyline.
- Clicking a surface reports the position of the point you clicked in the status bar.
- Scale bar labels let you choose how many decimal places to show.
- To compare against the old renderer, clear Use Vulkan Renderer under Advanced & Diagnostics in the project properties and restart VRGS, or start it with
-opengl.
Stratigraphy across the project
- A rebuilt stratigraphic column. Work at System, Series or Stage level, zoom with the mouse wheel, scroll through geological time with Shift and the wheel, and see your project's own age range rather than the whole geological record. The column highlights the stratigraphy of whatever you pick in the model.
- Objects carry their own stratigraphy — ICS units, your own group, formation and member names, and measured ages where you have them. It belongs to the object, not to a range on a mesh.
- Stratigraphic markers are new: a point in the model with an age attached, for a measured horizon, a dated sample or a picked contact. You place, drag and delete them like any other waypoint. See Stratigraphic Markers.
- More in Stratigraphy & the Stratigraphic Column.
Surfaces
- Conformable stacks. Choose several polyline groups when you build an implicit surface and VRGS solves them together, so the horizons share every fold and can never cross one another. See Implicit Surfaces.
- Faults on gridded surfaces. As well as the existing barrier trace, you can now define a fault as a map gap — a hangingwall and a footwall cutoff, with the ground between them left blank — or as a fault plane polygon, which pins the throw at the fault instead of smoothing the offset away across it. See Gridding Surfaces.
- Implicit surfaces no longer curve back towards the regional trend at the edge of your data.
Discrete element modelling
The DFN and Discrete Element Model branches appear in the Interpretation tree only when your licence includes the DFN feature.
- Grow Elements now grows the pack. Every step after the first used to report the same numbers, so the model never densified; it now grows towards the porosity you asked for, and tells you plainly when growing cannot reach it.
- Packs settle instead of bouncing, so a model comes to rest rather than oscillating.
- Porosity is now worth watching. It is measured against the settled pack rather than a box that is mostly air, so it changes as the model compacts — which is what it is for.
- Adding elements to a large model is much faster.
- Discrete element volumes survive a save and reload, and the model's domain box is drawn in the view and can frame it.
- See the Discrete Element Model User Guide.
Terrain, globe and VR
- Satellite terrain now works in the headset. Cesium and Google 3D Tiles stream and draw while you are in VR, terrain masking included; previously the imagery froze the moment you put the headset on. See the VR User Guide.
- Terrain masking is tighter, and is included when you capture an image.
- Starting VRGS without a headset connected no longer reports an error.
Billboards and multimedia
- Billboards have a header bar: drag the board itself by its top edge, with the video controls moved up there and clear of the content. The header and its controls appear on the board you have selected, so an unselected board stays clean.
- The navigation and playback buttons are the same size, give feedback when pressed, and shrink together on a narrow board.
- Rewind replaces the second stop button, repeat now loops the clip, and images and video keep their aspect ratio on presentation billboards.
- Maintain Size is honoured by multimedia objects and by sample, waypoint and marker labels.
- Video no longer sticks when a clip runs longer than the view it is playing in.
- See Billboards.
Field guides
- The field guide map now appears in the reader, not just while you are editing.
- The map in the editor groups nearby markers together and zooms with the mouse.
- A contents list on a Day page no longer breaks the editor, and a shared menu saves as a menu.
- See the Virtual Field Guide Editor.
The AI assistant (Athos)
- Athos can segment a photograph for you. Describe the feature — "outline the sandstone bed in the middle of this photo" — and it places the Segment Anything prompts and runs the segmentation. The result arrives as the ordinary mask preview, and you commit it with Label from Segments, exactly as with a mask you drew yourself: Athos proposes, and never writes to your project. Tell it what is wrong and it refines from the previous mask rather than starting over. See Segmenting a photograph.
- A local Ollama model can now see. Screenshots are sent to a local server too, so "what am I looking at?" no longer needs a hosted provider — it needs a vision-capable model, and the default
qwen3-vl:8bis one. A text-only model still gets the scene description, with no image. See Images and vision models. - Answers stream, and Athos shows its working. The final answer arrives as it is written rather than all at once, and while Athos is running a query, taking a look at the view or segmenting, it narrates what it is doing instead of leaving you with a spinner.
Coordinate systems
- ODN – Newlyn (EPSG:5701) joins EGM2008 and EGM96 as a Vertical Datum. This is the datum Ordnance Survey heights and UK levelling are quoted against, so a British National Grid project can produce heights that agree with the map rather than sitting tens of metres off on the ellipsoid.
- The vertical datum settings are now documented in full, including the one that catches people out: if the geoid grid cannot be downloaded, heights pass through uncorrected and nothing on screen says so.
Photogrammetry
- A re-run no longer undoes its own camera calibration. A calibration accepted on measured evidence was re-judged without that evidence by the next run, demoted, re-solved to the same answer and then refused — costing a full re-registration on every subsequent run of the project. The evidence now travels with the calibration.
- Texture bakes unwrap far faster. A 27-million-triangle bake that spent 43 minutes packing on one processor core now uses them all, and a bake that has to repack because it ran out of texture pages says so instead of looking hung.
Import and export
- GeoJSON export and import now carry your group structure and bring the interpretation tree back the way it went out. See GeoJSON Project Export and Getting Data In and Out.
Speed and project safety
- Saving is much faster on large projects. Only the data you have actually changed is written.
- Projects open faster, particularly those with many objects.
- Building a mesh from a point cloud sizes the job to your data and your machine rather than running out of memory.
- Upgrading a project to a new version takes a full backup first. See Working with Large Models.
- Two 3D views no longer slow each other down. With a second view open, Cesium tiles, seismic panels and volumes, and ortho panels no longer reload every frame.
A quieter messages panel
- The panel now shows what you need to read. Years of internal reporting have moved to the log file, and timings never appear in the panel at all.
- Progress bars show the time actually remaining.
- Commands that did nothing have been removed from the ribbon and menus, including a depth-shading mode, a colour-classification mode and several superseded painting entries. Each was either unimplemented or unreachable, and their presence implied capabilities VRGS did not have.
Updates
- Update notices now name the version correctly. An update already downloaded and waiting used to show as version 0.0.0.0, and reinstalling the version you are already running could produce a pointless notification.
🐛 Fixes
- Deleting a group of orientations now deletes the orientations inside it, rather than leaving them behind in the project.
- Navigating no longer stalls every few seconds after a region fill fails to classify.
- The flight path controls no longer restart playback when you pause, and the duplicate set of controls has gone.
- The spreadsheet view opens the right interpretation object.
- The voice control on a multiuser field trip no longer triggers on typing, and the camera tile has a blurred background.
- Athos failed to start on some systems, reporting only "Failed to initialize MCP integration". It now starts, and if it cannot, the panel names the actual cause.
- Follow the leader on a field trip now keeps the leader's tilt and heading; it used to arrive very nearly level.
- The Fill button on the Voxel Model tab commits the region picked with Select into the persistent Segmentation layer — the step the segmentation workflow describes. Successive fills accumulate as distinct labels.
- Project backups are named consistently. Pre-recovery backups were stamped in local time while every other backup used UTC, and backups made on a single-digit day of the month sorted by file date rather than by the time in their name. Older backups still list correctly.
- Coordinate handling. A missing projection database or datum grid is now reported at start-up, and a failed coordinate set-up can no longer apply the wrong height conversion to the next import.