Release notes

5.12.02026-10-22

Menci AI, the assistant inside StereoCloud3D

• New: Menci AI. The green Ask Menci AI button in the menu bar (also Help → Ask Menci AI…, Ctrl+Shift+/) opens the assistant: say what you want to get on your data and Menci AI answers with the steps, names the windows and buttons you will see, reads the state of the open project and the log, and opens and fills the right window for you. The button that starts the work is always yours.
• How to use it, at the top of its window, explains what to write and lists example questions on your data and on the result you expect; a click puts one in the field.
• AI credits always visible at the right end of the status bar; a click opens the credits and the online top-up.
• Ground filter: the progress bar keeps moving to the end and Cancel answers in every phase; much faster on large blocks; contour lines cover the whole block on sparse clouds too.
• Stereo systems described by how they work: active shutter glasses with an infrared emitter, beam-splitter mirror with passive polarised glasses, passive 3D monitors, quad-buffer on cloned outputs.
• Help → About StereoCloud3D: version, producer MENCI Engineering, author dr. eng. Luca Menci.
• Interface in Brazilian Portuguese: Help → Language, and chosen by itself when Windows is in Portuguese; also the installer.
• Licence activation: one Enter sends one request; keys and clicks pressed while waiting for the server are dropped, so they no longer fill the activation limit of the office network.

5.11.22026-10-19

Passive polarised 3D monitor

• A passive 3D monitor with polarised glasses that takes side-by-side or top-bottom input is recognised by the model name it reports (EDID): Stereo SBS / Top-Bottom always go to it, even when it is the Windows primary display or more than two monitors are connected, and the interface moves to the other monitor.
• When the stereo layouts are greyed out with the 3D monitor connected, the Stereo menu says why: Windows is duplicating it with another display (Win+P, Extend) or it is the only display.
• The SBS and Top-Bottom tooltips recall the 3D format to set on the monitor: left-right for SBS, up-down for Top-Bottom.
• Monitors are named by their model and by the Windows Display number, instead of “Generic PnP Monitor”.

5.11.12026-10-19

Corrected release notes

5.11.02026-10-18

Export for GIS, drawings with raster images

• Feature codes and their attributes travel with the drawing: they are written as fields of the Shapefile / GeoPackage, as XDATA of the entities in DXF and DWG, and they come back when such a drawing is imported. guide
• Drawings that contain raster images (.sfi, .vec) open: the image is kept as a reference with its frame and file name, and is saved back unchanged. VeCAD 5 drawings (VEC 5.31-5.35) open again.
• The pose of a photo from four known points is found reliably: three-point solutions are tried besides the plane, so a nearly flat set of points no longer gives a wrong direction.
• The installation folder holds THIRD-PARTY-NOTICES.txt with the license of every third-party component shipped with the program.

5.10.02026-10-17

DWG import, orthophotos in exported drawings

• The exported drawing and the CAD sheets, in DXF and DWG, carry the orthophotos as images in their place.
• The images of an imported DXF or DWG become imagery layers of the project.
• DXF import uses a single reader: what it cannot convert is listed by type when the import ends, instead of being lost without a word.

5.9.72026-10-16

No freeze when opening a project on a network drive

5.9.62026-10-16

Ortho views in PNG and JPEG, compass point of the bridge elevations, no freeze on a new volume

• Bridge elevations carry their compass point: the face buttons read Front S, Back N, and an elevation never renamed is delivered as Front South.png. A name given by the operator still wins. guide
• Volumes can be renamed from the Volumes list and from the scene tree; the deliverables go to exports/<name>. Build volume from the centreline opens a new volume when the current one already has views, instead of overwriting it, and saves the current one first. guide
• Fixed a freeze when a volume was created on a large octree: the points of the volume are read with a progress bar, and Esc or Cancel stops the reading. guide
• Esc on the view being generated stops the whole batch of bridge sheets. Volume names and paths with accents are kept as typed. guide

5.9.52026-10-16

Italian CAD command names, fillet with radius, classification from every activity

• Fillet: the radius now works between two polylines and between a polyline and a line, with a true tangent arc; between two lines it is right at any angle, not only at 90 degrees. A radius typed inside the command is kept for the next Fillet.
• Vertex grips: with a grip armed, the wheel and the trackball change only the elevation of the vertex, X and Y stay fixed; a number typed in the command line is the absolute elevation of the vertex. guide
• Divide, Offset, Rotate and Scale: the value typed in the dialog reaches the command already running (Enter in the field). Close polylines ends with Enter on an empty line, like the right button.
• Drawing side bar: every group of commands has a colour, chosen or switched off with the right button on its header. Layer manager: line type and line weight columns.
• Beam-splitter mirror: an entity just drawn appears in both mirror monitors too, not only on the mono monitor.
• Cloud classification can be found from every activity: always in the Cloud menu, in the Project map under the data, and as the first step Classes in 3D Buildings, Roads and Volumes. The Classes step opens the classification dialog directly. guide
• Activities: the type of work changes only by entering an activity; a step always starts from the Process panel; a click on a step opens its recommended method, the small arrow the others; the phase bar of the scene tree is hidden inside an activity. guide
• CAD line weight, mono and stereo, in View > Display > 3D Scene > Overlays, adjustable without switching stereo on. guide
• Railway: a rail seen on its own is followed along the track; where the axis is confirmed by the wire the missing rail is deduced, in red and declared not seen; after Confirm the panel says where every object was written. guide
• Bridge and underpass: a guide line goes from the last vertex of the centreline to the cursor. Mobile survey: the scene tree has its button in the view.
• License server not reachable: the message now tells what to check (connection, VPN, proxy, firewall, antivirus) instead of asking to start the server.

5.9.12026-10-15

Z-FIX keeps the elevation, off by default

• Z-FIX is now off by default. After the update it starts off once, whatever was saved before; from then on it keeps your choice. guide

5.9.02026-10-15

SpaceMouse through the 3Dconnexion driver, view buttons in stereo, beam-splitter mirror on cloned outputs

• Stereo: the buttons of the view - axes, scene tree, overview, area of interest, bottom panel - no longer disappear under the zenith overview while stereo is on. guide
• Beam-splitter mirror on AMD cards with the two monitors as cloned outputs: each eye goes to its own monitor again.

5.8.02026-10-15

Locked Z, overview commands in its header, Vertices dialog

• Zenith overview: the raster, its opacity, how the terrain reads (with its legend), the same raster in mono and imagery are chosen in the overview header, always there while the overview is open. They left the Display panel, where closing the panel took them away. guide
• Zenith overview: centred on the view axis at the cursor elevation, so it shows the ground you are looking at in oblique views too. guide
• CAD: one Vertices dialog for the selected polyline or line, from the left toolbar, the right-click menu or the VERT command: numbered list with side and slope, selection, Assign / Shift / Interpolate Z, Delete, Insert after, Copy coordinates. It replaces the old Vertices window and the vertex list of Entity properties. guide

5.7.02026-10-14

SpaceMouse, pointing devices, Z-FIX, railway objects along the line

• Tools > Pointing devices: Mouse, Trackball and SpaceMouse, each in a window named after its menu entry. Mouse and trackball settings left the Inspector. guide
• Interface scale: with Windows at 100% the interface sizes itself to the screen resolution (1440p = 125%, 4K = 200%), and the scale can be changed without a project open. guide
• Snap bars: Z-FIX button for Constant cursor elevation (Ctrl+Shift+Q). With fixed Z on, the first wheel or trackball step already changes the elevation, in perspective views too. guide
• The beam-splitter mirror chooses the stereo path by itself: one quad-buffer window when the driver offers stereo, one window per eye otherwise.
• Railway: Find the track, masts, cantilevers and wires read all the clouds that are on together; a track crossing from one cloud to the next continues. guide
• Railway: the line axis continues beyond the track, from the rails, the platform edges or the contact wire, also in tunnels and parallel to the neighbouring track; platforms are drawn along the axis. guide
• Railway: a mast is a support when its cantilever reaches the track (measured); overhead portals (two poles and a beam) are recognised; the messenger wire is followed where it dips into tunnels. guide
• Railway chain: Find the tunnels, Find the cabinets and Find the sleepers as chain steps, each with a draft to Confirm or Discard. Steps that do not fit the bar wrap to a new row. The steps run on all cores, and long lines no longer run out of memory. guide
• A program freeze of 10 seconds now leaves a report, a minidump and a line in the log.
• The Project clouds bar no longer covers the Project map or dialogs. guide

5.6.02026-10-13

Many clouds in one project, DWG export back, fixes from customer reports

• Project clouds bar (Cloud menu): one box per cloud and Only; opens by itself with two clouds or more. Scene Tree: Show only this cloud. guide
• Add files to this cloud... (Scene Tree, right-click on a cloud) rebuilds the cloud together with new files, keeping its classes; the previous cloud stays in the project folder as a copy. guide
• Many clouds share one memory budget for decoded points: a project with many clouds no longer runs out of memory and closes. guide
• DWG export works again: the drawing is written as AutoCAD 2004 by the bundled sc3d_dwg tool, which reads the file back and checks the entities before saving it.
• DXF import: section objects are skipped and reported instead of refusing the file, arc dimensions are drawn, column texts and block attributes keep their place. guide
• CAD: Parallel finds the line in the georeferenced view too.
• Scene Tree: switching the CAD off no longer hides the cloud. guide
• Menus and Welcome no longer freeze at first start when Windows scaling is not 100%.
• No more false abnormal-exit reports at every start.

5.5.22026-10-11

CAD: no more unwanted autopan when the cursor nears the viewport edge

5.5.12026-10-10

Volumes in the menu of the Terrain activity

• Terrain activity menu: a last group with Volumes against a quoted polygon, Volume strip and Cross sections, the same commands and shortcuts as the Terrain menu. Before, they were only in the Volumes activity, and in Terrain the volume calculation could be reached only by typing VOLUMES. guide

5.5.02026-10-10

Multiview follows the cursor, a visible Delete for pitches and buildings, no redo by mistake

• Multiview: with the cursor on the mono view the point under it stays in the centre of the two views and the images slide under it; the views are captured again when the cursor stops. Coordinates, Z and the elevation line are those of that point, the vertex in hand is a hollow circle; on the panel the reference goes back to the vertex. Before, the images followed the cursor while the numbers stayed on the vertex. guide
• Multiview: the two views are 90 to 120 degrees apart and never opposite (0 and 180 used to come out), and they stay put while nothing blocks them. The corner says where each view looks from: 'from 90 deg' is a view from the east. guide
• Multiview, Roof tab: Delete pitch (press it, click the pitch) and Delete building (pitches, eave, foot and walls, with a confirmation). Both can be undone with Undo geometry edit. Before, a pitch could be deleted only from a hidden right-button menu and a building not at all. guide
• Process view of the graph: on a product already made the button reads Redo it and asks first, with the date. A click by mistake no longer repeats a DTM. guide
• Tunnel and underpass: an entrance or exit portal elevation that cannot be measured is marked 'not measurable' with the reason and the numbers (too few crown bands, edge not straight, beyond the end of the axis), instead of an endless 'to generate'. guide
• Stereo: a new project starts in stereo when the previous one was in stereo. A project in mono shows the mono view on the active shutter display instead of the last stereo image of the project opened before. guide

5.4.02026-10-10

The CAD toolbox and the converters: command atlas, interactive tutorial, DXF as drawn, faster drawing, robust importer

• CAD command atlas: a side bar by groups and a small dialog for every command, with the options, the info and the typed values in one place. The dialogs are lighter: title drawn, shadow, step on a pill. guide
• CAD, Z values: set a constant Z, drape the entities on the cloud, interpolate between vertices, or give a contour spacing - from the new Z bar with a grid of values. guide
• CAD, shaping lines: densify, smooth, simplify, remove duplicate vertices, lengthen, split at the intersections, trim with a fence and reshape. The Trim with a fence and Reshape dialogs no longer close the program. guide
• CAD, parallels: Create parallel and Stereo parallel in one window; the base point of Move and Copy sits on the clicked entity with its elevation; layers are listed in alphabetical order. guide
• CAD tutorial: an interactive tutorial with the real commands on a drawing that stays intact. It covers drawing (every variant of circle, arc, ellipse, spline and polyline with arcs) and all the editing chapters, with adjustable speed, pause, skip, review and exit, and a button in the Tools column. guide
• Trim, Extend and Add vertex did nothing: the right click regenerated the drawing and cleared the selection. Fixed, and the Trim result stays visible in the tutorial. Search by ID finds the live line after Trim, Extend and Break.
• CAD drawing is much faster on dense drawings: the engine draws the polylines in one GDI call per pen. a large city drawing 19.9 -> 7.7 ms, a smaller one 7.2 -> 2.2 ms for the full view, with identical pixels.
• DXF import reads what the drawing shows, as a reference reader does: dashed and other line types, hidden layers, aligned texts, hatch patterns, and arcs now come out right. guide
• DXF export keeps blocks, ellipses, arcs inside polylines and line types, and the log says what did not come out as such. The progress bar moves smoothly. guide
• Data importer: a point far from the cloud no longer sets the origin and the root cube of the octree. A pass keeps the 4096 extremes per axis and drops a stray when its gap exceeds the thickness of the rest (no constant). A customer cloud went from a 292 km cube to 787 m. A notice per axis, outlierPointCount in the metadata, --no-outlier-filter to switch it off. guide
• DXF with far-away content: when the project has a cloud, the first view frames the cloud and not the extent of the drawing - a drawing of 75 thousand attribute blocks over 80 km no longer leaves a 0.8 km cloud a few pixels wide. Without a cloud the first view frames the drawing, as before. guide
• CAD sheets: a gallery of the sheets and tabs above the open sheet, the bar of the final drawing over the sheet, the properties of the final drawing and typed values, the sheet filling the whole central part between the bars; from the orthophoto viewer to a sheet (Deliver > On a CAD sheet). Drawing on the orthophoto sheet no longer shows a ghost selection and frames take 430 ms less. guide
• Railway: the contact wire is measured where the cloud sees it, not drawn from the shape of the line. guide
• Chain: the steps that are a place to go open their panel directly, without the Process view; a Sheets step closes bridges, buildings, fronts and interiors.
• Look: one theme for the whole interface (slate, aqua accent, rounded corners, thin borders), named backgrounds for the panels, and the Opening project and wait dialogs in the same palette.

5.3.02026-10-08

The railway as it is seen: rails alone, poles to the base, cantilevers by the shape of the line

• Railway, finding the track: the rails are recognised on the height of the cloud over the ballast, not on its colour, so a track is found in a curve, on a cant ramp and seen from the side. A rail fitted as an arc of circle (a straight line where it is straight). guide
• Railway, rails seen alone: where the scanner saw only one rail of a track, that rail is documented as it is, on <rails>_SINGOLE, and continues past overhead wires and switches. The whole chain - poles, cantilevers, wires, sections - works on it too: the lateral distances are measured from the rail. guide
• Railway, poles: found in the whole cloud from the density of their returns in plan (an isolated peak with a shaft rising from the ground is a pole, whatever its height), and measured down to the base - the ground at the foot, the height over it, the base seen or hidden. Trees and doubtful poles go on PALI_TE_DA_RIVEDERE with the reason. The table has foot, height, base and the reason. guide
• Railway, cantilevers: recognised by the shape of the line - learned from the cloud (the members that recur at the same heights over the track on most masts), or the Italian shape when ticked. Heights are over the track. Look at them one by one: the section the search worked on, the members in the colours of the shape, and It is a cantilever / It is not / Not sure; Confirm writes what you said. guide
• Railway, adding what was not found: Add a pole measures the pole you click as the search does (a click with no shaft places it where you clicked, to review); Add a cantilever places the shape on the mast you click, towards the second click, at its height over the track, each member fitted on the points (a member with no points is dashed and said not seen); Redraw a member takes two clicks in the section. Added items are marked. guide
• Railway, overhead wires: the messenger is followed at the height of the line, learned from the cloud (Italian lines run lower than the old fixed band); only the poles whose cantilever reaches the wire are supports, so lamp posts and platform poles no longer split the spans; the feeder no longer takes the messenger and contact wire of the next track. guide
• New project: with 'Terrestrial (probably)' (a ground LAS without trajectory) the mobile jobs - Railway, Road inventory - can be ticked too, and the workspace follows the first one ticked. guide
• CAD sheets: on a sheet you draw and edit as in the CAD of the project - Draw and Modify menus and toolbars, Space repeats the last command, OSNAP. New sheets are drawn in metres at true size, texts and dimensions at 2.5 mm of paper at the sheet scale, a DWG keeps its units. Other drawings (the project drawing, other sheets, a DXF or VEC) are placed on the sheet as a scaled block. CAD > CAD sheets: new sheet, the sheets of the project, close. guide
• CAD: no more crash clicking the grip of a line; the click that selects no longer arms a grip; typed values and coordinates go to the active tool and the prompts are translated; rectangles flat at the first corner, circles and arcs with the radius in plan, fillet corrected; the object nearest the click is picked; the window selection rectangle is 1 pixel as the crossing one. guide
• CAD: the current layer is never left off or locked without saying so (a drawing command offers to turn it on); the drawing no longer disappears after a mouse-wheel zoom; ZE goes back to the extents in the georeferenced view; no more crash closing a sheet after placing a drawing on it. guide
• Stereo Top-Bottom on a secondary monitor: mono on the main screen, the half Top-Bottom pair on the second (left eye on top). Each eye keeps the full width: on a line-interleaved polarised panel twice the useful samples of side-by-side. Active shutter: closing the window stops the glasses at once. guide
• Structures: bridge and tunnel are one work with two axes - the deck and the underpass - saved with the project and both shown on the cloud; the vertex of an axis falls under the cursor; tracing works in a rotated plan view; hiding what is above applies to the underpass only and ends with the trace. Tunnel drawings on a cloud without intensity use the colour in grey instead of coming out black. guide
• Interface: no '(none)' in menus and tooltips for commands without a key; a profile taken where there are no points says so; the texts of the profile panels are translated; the view trihedron is no longer drawn over the Project map. guide

5.2.02026-10-07

Activities: a Project map that says what your data can give, and one job on screen at a time

• Activities. The interface is organised around results you recognise - Stereo plotting, Mono plotting, Auto buildings 3D, Terrain, Roads and mapping, Classified cloud, Volumes, Power line, Railway, Building, Street frontage, Interiors, Bridge, Tunnel - each with its own steps, menu, panels and views. Workspace and profile are no longer on screen: the kind of survey is a fact of the data, and the status bar and the window title name the activity. guide
• Project map. Opens with every project and from the Project map button: your data on the left, the possible activities as cards with their state (in progress, done, partial, ready) and an Open button, and at the bottom what is not possible with these data and why. Resume (or Esc) goes back to the activity; Deliverables and Full graph open the views of before. guide
• Try on an area. On the Auto buildings 3D card of the map: place a square on the cloud and see the building outlines of that area in a preview, without entering the job. The quickest way to find out what the automation gives on your data. guide
• Activity bar. One row under the menus: Project map, project > activity (the orange button changes activity), and the steps of the activity with their state read from the project - blue to do, amber to check, green done, orange to redo, grey waiting. Click a step to open it in the bottom panel. The band with 'Run: Classify the cloud' at the top of the bottom panel is gone: the classification is offered only when a step of your activity needs it. guide
• Railway and power line: the bar shows the steps of the chain, with a ringed orange disc on a draft waiting for Confirm or Discard, and Run the chain at the end. One list of steps with one state, instead of three lists that could disagree; the Deliverable view no longer opens by itself inside an activity. guide
• Activity menu. With a project open, the Terrain and Automation menus are replaced by one menu named after the activity, with its commands and their usual shortcuts. The trade commands of the Cloud menu moved to their activity; the general ones stay. guide
• Changing activity closes the windows of the activity you leave (and disarms a tool left armed), each activity remembers its own arrangement of panels, and Multiview and the Buildings list exist only where they are used. Stereo plotting is stereo only; Mono plotting is Multiview with the profiles; the automatic outlines are in Auto buildings 3D. guide
• The CAD drawing stays on the cloud when a panel opens or closes and the view changes size: before, it stayed shrunk or enlarged until the next pan or zoom. guide
• Multiview follows the cursor: when it stops on the view, the two views are taken again around the point under it, before the first vertex too. Opening Multiview turns AUTO-Z on. The eave overhang is a slider in steps of 10 cm. guide
• The vertical profile follows the cursor in every activity when there is no Multiview work area, instead of saying 'Place a work area in Multiview'. guide
• Building walls go down to the ground: the foot is sampled 2 m outside the outline and must be below the eave. Before, it was sampled under the roof and the walls could be built upwards. With no ground found the building is not confirmed and the status line says why. guide
• Build surface model (DSM): a command of the Terrain activity, in the area of interest or on the whole cloud, with progress and Cancel; shown in the overview. guide
• Plans, elevations and sections: the kinds of image are in the order RGB, Intensity, Depth, and a new drawing starts as RGB. guide
• The zoom box and the safe display notice are behind an 'i' button in the corner of the view (orange when the safe display mode is on). Notices that are information, not questions - products to redo, building outlines made by an older engine - go to the status line instead of a modal; a modal reopened every frame no longer blocks the view. guide
• One progress dialog for long commands: building outlines, preview, 3D roofs, power lines, carriageway edges, kerbs, road markings and signs compute in a separate thread, the cover stays fluid, and Cancel (Esc) stops them - also when Windows shows 'Not responding'. Every building command works only in the area of interest when there is one. guide
• Buildings: photogrammetric clouds - SAM seeds from the step at the edge, SAM on the colours of the cloud without an orthophoto, density measured on sparse clouds (engine v23); unclassified LiDAR - tree crowns no longer end up among the areas to check (engine v24). 3D roof is a step of the chain after the outlines; Accept puts outlines on EDIFICI unless another layer is chosen. guide
• Area of interest: the actions (draw polygon, remove the area) sit beside the green button, no dialog. Job catalogs: dependencies and counts aligned with what the commands really do; DTM and spot heights no longer depend on the classification. A grip taken in one project no longer crashes the next one. guide

5.1.02026-10-07

The area of interest in every command: draw a polygon, or work on the whole cloud

• One area of interest for every command that computes on the cloud: with an area it works inside the polygon, without one on the whole cloud - never on nothing. Next to the button that starts a command a line says which: 'Area: the area of interest (m2)' in green, or 'Area: the whole cloud'. guide
• Classification, all passes and each pass: with an area of interest the classes are written only inside the polygon; outside they stay as they are. The passes still read the whole cloud for context. guide
• Ground DTM, contour lines and search by sample use the polygon; without an area the DTM covers the whole cloud (no longer the view) and the search offers 'Whole cloud'. guide
• Overhead lines, railway track, tunnel without an axis, carriageway edges, kerbs, road markings and manholes, road signs: the cloud is read only in the area and the results kept inside the polygon; the AI photo tiles are made only there. guide
• Colour the cloud from the run and Export classified cloud change only the points inside the area. guide
• Cloud cleanup and conductor extraction no longer refuse without an area: they run on the whole cloud, tile by tile, with the progress of the tiles. guide
• The area of interest is the one of the Area of interest window: a selected node in the Scene Tree no longer bounds a command by itself. guide

5.0.22026-10-06

An area of interest drawn as a polygon, 3D roofs, and building outlines that stay fluid by the thousand

• Area of interest as a polygon: the green Area of interest button in the mono view (also Cloud > Cleanup & area of interest, Ctrl+Shift+A) opens a window with Draw polygon - left click a vertex under the cursor, right click to close, Esc to take back the last vertex - and Remove area. A new polygon replaces the old one. The building outlines are computed only inside it: seconds instead of minutes on a large project. guide
• Roof 3D: from the Buildings tab, Build for this one / Build for all builds the roof inside each outline - one plane per pitch, straightened on the building axes, ridges and hips where two planes meet, dormers and chimneys at their top - as 3D closed polylines on SC3D_ROOF_FACETS (fits the points), SC3D_ROOF_FACETS_CHECK (to check in stereo) and SC3D_ROOF_SUPERSTRUCTURES. guide
• Vertex elevation of the outlines: as generated, the median of the points inside, or on the RANSAC plane of the points inside; Apply to this one or Apply to all, and the choice also applies to new outlines. guide
• No building lost in silence: high flat areas that no outline covers, and outlines dropped for sparse points or an improbable shape, are listed in the Buildings tab as To verify, largest first, and drawn on their own blue layers. Green crowns are not listed. guide
• Better outlines: the roofs are found first and the outline follows them; squaring no longer cuts off the wings of a roof and is refused when it would change the area too much; on photogrammetry the pieces of roof that the image recognition misses become buildings. Regenerate the outlines to get them. guide
• Delete all... in the Buildings tab removes, after a confirmation, the provisional outlines and the 3D roofs. Regenerating the outlines replaces the whole draft, 3D roofs included, also outside an area of interest, and the report says so. guide
• Thousands of outlines no longer slow the view down: the Buildings tab and the vertex marks no longer read every outline at every frame, the marks are drawn in one go, and from far away only the lines are drawn. The Building outlines switch is also in the Buildings tab, and it shows and hides the 3D roofs too. guide
• The commands say where they work: the automatic outlines read 'in the area of interest' or 'whole project', a green line 'Area: the area of interest (m2)' sits by the Run button, and the automatic terrain breaks work in the area of interest when no area of their own is drawn. guide
• Building outlines preview: it runs on the area of interest at once - without an area, the area window opens to draw it and the preview starts when the polygon is closed. On a LiDAR cloud it is not offered: the outlines come from the cloud and there is nothing to compare. guide
• Moving a vertex with its grip can be undone with Ctrl+Z or Modify > Undo; before, the engine did not record it and there was nothing to undo. guide
• The profile under the cursor is a 10 cm slice and shows the highest confirmed point, so it matches the position of the cursor. guide
• A delivery is no longer shown as Delivered when the objects it depends on are no longer in the drawing; the building outlines menu of the graph finds a cloud imported after the project was opened.

5.0.12026-10-06

Building outlines without trees, walls and gardens; stereo vertices in place

• Building outlines: dense tree crowns are no longer taken for buildings. On a classified cloud, wide patches with vegetation (classes 3, 4, 5) on top are never roof, and a surface with vegetation on top over more than half of it is dropped whole. On a coloured cloud, a surface that is green on top with almost no flat part is a crown; green roofs stay, because they are flat. guide
• Building outlines: an outline must be a building someone could use. Pieces narrower than 3 m - walls, fences, kerbs - are dropped, and so are pieces narrower than 6 m that are low and green on top - vegetable gardens, pergolas, pool covers. Sheds and garages stay. A narrow strip as high as a roof that runs along a building - an eave or a lower pitch cut off by a step - is joined to it. Regenerate the outlines to get them. guide
• Stereo with the fixed mark: the building outline vertices were drawn in the wrong place in the mono view, and followed the cursor; they are now right in mono and in both eyes. The 3D panel no longer freezes. guide
• Stereo: sweeping the cloud with the mono cursor is smoother - the secondary views draw the cloud already on the graphics card instead of rebuilding it - and a CAD eye with nothing to draw is no longer reported as 'eye_render_failed'.
• What can I do with my data: the outcome under a step shows that step's own messages, no longer the periodic stereo and timing lines.
• Building outlines, the Buildings tab: the provisional outlines in the bottom panel, one at a time - Previous / Next frame and select each, Accept on the final layer and Delete go on to the next by themselves, Edit and New. The current outline has a thick magenta border, in mono and in both stereo eyes. guide
• Building outlines, which method: the menu of the graph says in one line what your data allow - LiDAR, photogrammetry with or without orthophoto - and the automatic outlines are one choice, with 'try first on a small area' under it. Methods that cannot work with your data are greyed, with the reason. guide
• Building outlines, while it runs: the progress bar follows the time and, after a minute, says how long is left; at the end a report says what was created, what was left out because it is not a building and what was corrected. guide

5.0.02026-10-05

From the cloud to the deliverable: job types, a graph that leads the work, and automatic chains that turn green

• Job types. A project is now a job: Power line, Railway, Structures (tunnel, underpass, bridge), Buildings and terrain, Aerial mapping, Stereo restitution, Quarry and volumes, Street frontage, Indoor and floor plans, Road and utility inventory. Each job lists the objects, point classes and deliverables it needs, the methods that produce them and what each depends on. A project can hold several job types, one current; the list shows the ones chosen for the project first. guide
• The program recognises the data by itself. How the survey was taken - airborne, terrestrial or mobile - is stated with its reason (run and photos, and the density ratio of the cloud: airborne 1.5-2.8, from the ground 9-54), and which sensor made it - LiDAR or photogrammetry - from the intensity of the points and the LAS header. Ground filter, building outlines and the recommended methods follow from it; a job the data cannot support is shown greyed with the reason. A wrong guess can be corrected in Options. guide
• A photogrammetric cloud is flagged 'surface only' next to the tools that look for wires and ground, so you know the laser did not see under the trees. All-black RGB is recognised as no colour, and a mobile cloud without colour offers Colour the cloud from the photos. guide
• Data quality at import: the noise of the points on flat surfaces is measured on 12 windows spread over the survey and kept with the layer, as the median and the best-to-worst range. guide
• New project from your data, in two screens. 'Where is the data?' takes a folder, single files or files dropped on the window and sorts them by kind; 'Here is what I found' shows the survey, the name and folder already filled in, and 'What do you want to produce?' with the job types to tick (several allowed). Conflicting coordinate systems, Windows reserved names, a folder you cannot write and a drawing without a cloud are refused before Create, with the reason. The drawing template and the project password are no longer asked. guide
• Import: the cloud merge is chosen in the dialog, an import can be cancelled (the partial folder is cleaned and the project stays), and every refusal says why. File > Add data... adds clouds, a mobile run, orthophotos or a drawing to an open project. guide
• New Automation menu, before Stereo: What can I do with my data..., Classification (moved from Cloud) and the building tools. guide
• What can I do with my data: a graph of sources, processes and products, one column per level. What is in the project is green, what is missing grey; the play button on a box makes (or remakes) that product, with the recommended method first when there are several. A box with a lit border is a step you can take now. Tabs for the current job and for Buildings and terrain, Railway, Power line and Structures. guide
• Redoing a step keeps the rest consistent: before it starts, the program lists what happens to every product downstream - calculated drawings are replaced, drawings made by hand are hidden, files are marked to redo - whichever way the step is started (graph, menu or shortcut). guide
• The graph band at the top of the bottom panel says where the job stands - done, to redo, next step with Start - and opens into a small graph. The Process view holds the options of the chosen step (classification, contour lines) and, under Start, the first lines the step wrote: errors in red, warnings in orange. guide
• Run the chain: the automatic steps of the job run one after the other in dependency order, each with its products underneath, green when the measured criteria pass, yellow to review, red with the reason. A draft is confirmed by itself only when green; a manual step does not stop the automatic steps that do not need it. Every completed step saves the drawing at once, with a copy in cad/backups. guide
• Delivered tables open with Open (their own program) or View (an internal viewer with a frozen header and resizable columns). Supports, spans and object reports are also written as Excel .xlsx next to the CSV. Job Report writes an HTML delivery report, translated and printable on A4, with an optional PDF. guide
• One licence for everything: airborne, terrestrial and mobile work are no longer sold separately. guide
• One bottom panel under the view replaces the floating strips: profiles, volumes, the mobile run and the job views are views of the same panel, one at a time; a work view appears only while a step needs it. View > Bottom panel opens and closes it. Panel layout is remembered per job type. guide
• Mobile mapping: Deliverable, Navigation and Reconstruction views, with the run controls - station, playback, timeline, speed, follow the vehicle - always in a strip at the top. Photo on one third, mono view on two thirds; the car button switches between plan and vehicle view. guide
• New View > Vehicle view, drawable: an oblique view without perspective, turned the way the vehicle looks, with the cloud cut 30 m in front of it, where the CAD tools work. The drawing behind the cloud stays behind it. guide
• Selecting an object in a list brings every view to it: the panorama of the station that photographed it, the single camera, the vehicle view and the plan, from anywhere along the run. guide
• Mobile inventory. A survey specification picks classes, codes, tolerances and attributes; every surveyed object is a record of <project>/inventory/archivio.gpkg in world coordinates, and the inventory follows the drawing: what is drawn on its layers is adopted by itself, a moved entity updates its record, an erased one removes it. guide
• Mobile import is driven by a profile file (assets/profiles/riegl-vmy.mmprofile, or a copy in %APPDATA%\StereoCloud3D\profiles), so a new delivery layout needs no new program version. guide
• Mobile automatic searches. Power lines: wires first, then supports, across trees and hedges, as a preview to correct before Confirm, with clearance over the carriageway and the ground, span by span. Road signs: candidates from the reflectance, an AI check on the photos that proposes the catalogue code and value; the Italian catalogue lists all 373 figures. Carriageway: road edges and accesses, kerbs followed around islands and behind parked cars, manholes and gullies from laser and photos (44 of 46 on a test run). Detected objects are listed grouped by type. guide
• Object reports: a click on the cloud files a report with its position, the cloud seen from above and from the side, and the nearest panorama crop; an optional AI identification proposes what it is. Reports export to HTML and CSV. guide
• Ground: the ground step of Classify cloud is a new filter, 20 to 40 times faster than the cloth (1-2 s instead of up to 95 s) and closer to the delivered ground: on a test survey the ground F1 went from 0.80 to 0.96. The dialog shows the type of cloud - LiDAR or Photogrammetry - detected from the intensity; on photogrammetry it also removes stepped sheds, material stockpiles and raised blocks found from the colours. Holes left by removed objects are filled smoothly. guide
• Classification thresholds revised on measured data: ground 0.25 m, vegetation cell 2 m. A hillside is no longer taken for a roof (on a hilly survey false building points fell from 5.9 to 0.3 million); the building step changes only the classes it owns. Results differ from 4.9 on the same cloud. guide
• Power-line classes on airborne surveys come from the objects: wires, earth wires, towers and insulators are classified from the wires drawn or found by the program. High and medium voltage are kept apart, with the new classes 23, 24 and 25 for medium voltage. Classes 13-16 now share one orange hue in four tones instead of one identical colour. guide
• Noise classes 7 and 18 are hidden by default when a project opens; All shows them again.
• Change class: Automation > Classification > Change class... gives another class to the points inside a polygon drawn on the view (hidden points included) or inside selected closed CAD polylines. Every change is a version you can go back from. Versions are saved on the cloud the run worked on and listed per cloud. guide
• Class comparison: a bottom-panel view compares two classification versions of a layer - per-class precision, recall and F1, confusion matrix, and the points that differ shown in magenta. guide
• After a classification the cloud is redrawn at once with its new classes, and the progress messages of every step are translated.
• Building outlines computed in the program, from the cloud: closed CAD polylines on their own layers (seen sides, and sides assumed under trees), with vertices highlighted in mono and stereo. On a reference city block the outlines match those traced by hand with a median overlap of 0.93. The Building outlines button turns them on; they are off when a project opens and are never computed by themselves at opening. guide
• Right click on an outline: Accept (or accept on another layer), single eave height, simplify, square, close, delete or add a vertex, copy and paste a height, shared wall with the neighbour, Merge and Split along a line; Undo and Redo. Automation > Check building outlines lists crossing, overlapping, open and tiny outlines and walks you through them. guide
• On photogrammetry the outlines take their edges from the orthophoto, with the program's internal AI when an orthophoto is present. Automation > Building outlines preview: a 120 m square to move over the area you care about, Local (free, recommended) or AI (uses AI credits, with the estimate for the whole project). Outlines are redone at the end of Classify all; AI outlines are never redone by themselves. guide
• File > Export buildings (GeoPackage): accepted and proposed outlines as 3D polygons with courtyards as holes, and their attributes - area, perimeter, eave, ridge and ground heights, height. guide
• Automatic search for overhead lines on airborne surveys (until now mobile only): wires fitted as catenaries, joined across the towers, close bundles found in a second pass, high and medium voltage separated; a support is drawn only where spans meet and a column of points justifies it. The result is green only when the measured criteria pass. Span and support tables, terrain profiles and clearances are written as CSV and Excel. guide
• Railway: Find the track searches the whole corridor by itself and proposes each track green, orange or red; gaps are listed, never interpolated. The track table gives gauge, cant, distance between tracks and jumps over 12 mm, and the Track view shows it with charts and the stations to look at. Masts, cantilevers, messenger wire, droppers, feeder and anchors are found along the track, each with a draft, a table and an inventory. Track sections and the rail-level profile with the spacing and widths you choose. Cloud > Railway menu. guide
• Search by section: draw a section across a wire, a rail or a kerb and the program carries it along the line. Search from a sample: show one object (a sleeper, a mast, a pole) and it finds all its repetitions along a corridor or in an area. guide
• Structures: 'Tunnel or underpass' becomes Structures (tunnel, underpass, bridge). Bridge in four steps: remove the vegetation from the structure, read section by section; the deck centreline (also from the tracks on it); volume and drawings - plan, view from below, two elevations, cross section - with each view isolating the structure; bridge sheets in one step at 1:100. guide
• Underpass: new drawing 'Structure seen from above', the orthophoto of the road over it. Tunnel: its own Tunnel panel (View), axis and sections into the CAD from the drawings, the survey belongs to its project, rasters no longer black after a second run, portal elevations read the portal face. Cross sections from the DTM along the ASSE axis (Terrain menu), with CSV and Excel. guide
• Professional stereo (fixed mark), Ctrl+Alt+F: in the stereo window the mark stays at the centre and in focus, as on analog plotters, and the model moves under it; the eyes recentre on the mark when the mouse stops. On every stereo output. guide
• Two viewpoints (top / bottom), under the fixed mark: below the main view the same scene turned by a yaw and pitch you set (sliders or arrow keys), with the cloud, the drawing and the rubber band. guide
• Stereo > Adjustments > Depth & CAD quality > Fusion comfort: the largest separation allowed between the eyes, as an angle. Lower it if zoomed-in views tire the eyes. guide
• Stereo restitution as a job type (Aerial mapping works the same way): no chain, and under the cursor the longitudinal and cross profiles side by side, same width (0.5-5 m), rotatable cross, out-of-scale height shown with an arrow. guide
• Stereo: CAD vectors no longer fall flat to screen depth after the drawing list is rebuilt; the external stereo window follows a project that is still streaming; a recovery marker no longer disables stereo at every start. guide
• Orthophoto or DTM in the mono view when it looks straight down (also rotated), opaque, over or under the cloud, from a quick bar on the view; never in oblique views. DTM shown as shaded relief by default. The overview can stop following the mono view (Follow mono) to look at a detail on its own. guide
• Right-button drag rotates also inside a draw tool, without closing it; a right click without dragging still closes. A trackball no longer freezes the other mouse. guide
• Object snap while editing: dragging a grip no longer snaps the vertex onto itself. Layers turned off in the view are off in the overview too.
• DWG import removed together with the external converter it needed: save the drawing as DXF (any version) and import the DXF. DWG export is unchanged. A CAD sheet with orthophotos is written as DXF 2000 with the images beside it. guide
• AI credits: the AI checks run on prepaid credits of the licence (1 credit = 0.10 EUR; 500 a year with a sold licence, 250 with a trial). The status bar shows them as a bar coloured by what is left; Help > AI Credits... shows balance, use and recent activity, and tops up online with VAT shown before paying. guide
• New splash screen. The welcome page shows a preview of each project taken at its first opening, the thumbnail opens the project, and there is an Exit button. guide
• Removed: the RANSAC plane cleanup, the roof edge snap, and the breakline tools (to come back when they are reliable). Areas hidden with the cleanup are left out of measurements and extractions too. guide
• Change to note: in support tables the offset from the axis is now positive to the RIGHT (it was to the left), and progressive and offset are read only from the single open polyline on layer ASSE. guide
• Fixes: a drawing that could not be reopened after the automatic cleanup at opening; a start that closed at once because of a damaged crash report; a crash opening some projects; blocking dialogs no longer push each other away; time spent in the Windows file dialog no longer counts as a freeze; the import no longer sits at 99%; the interface scale adapted to the monitor says so; the support package includes crash reports. guide

4.9.02026-09-25

A beam-splitter mirror on two cloned monitors, elevations without grain, and roofs that keep their edges

• Two-monitor beam-splitter mirror (passive polarisation) on a bench wired as cloned outputs (the driver's clone mode). The two monitors appear to Windows as one, which used to be refused outright. View > Stereo > Beam-splitter mirror options > "Allow the beam-splitter mirror on two monitors (cloned outputs)" (off by default) switches the app to passive quad-buffer and leaves the mirroring to the driver (the graphics driver's control panel: stereo display mode for a beam-splitter mirror, on a graphics card recent enough to offer it). Reported by a customer, 25 Sep 2026. guide
• New command View > Stereo > Beam-splitter mirror options > "Beam-splitter mirror: software mirror": the app flips the reflected eye itself and the monitor stays neutral, so lifting the mirror gives back an ordinary 2D desktop with nothing to reconfigure. Not to be combined with the monitor's or driver's own mirroring. Asked by Luca, 21 Sep 2026. guide
• The beam-splitter mirror options, passive quad-buffer included, are now always visible and disabled with the reason written next to them, instead of vanishing on hardware that does not qualify. A control that disappears teaches nothing. Luca, 25 Sep 2026. guide
• The display setup wizard and the audit no longer report a healthy cloned bench as an error, and say exactly which graphics driver setting to turn on. guide
• Fixed a video memory leak of about 66 MB at 4K every time the stereo panel was recreated.
• Elevations and orthophotos off a terrestrial scan are far less grainy: a pixel now takes the mean of the points that land on the same surface instead of the last one to arrive. On a facade at 1.7 cm/px from a cloud with 1.2 cm spacing almost two points fall in each pixel and only one used to reach the image, carrying all the radiometric noise of a single return. Measured on tum2win the noise drops from 21.3 to 3.9 levels. What is protected is the rustication, the cornices and the window reveals: the relief a facade elevation exists to show. A flat threshold would have refused 13% of those pixels, so the neighbour's weight falls off continuously with depth instead. guide
• Contrast in the image adjustment was backwards: raising it brightened the image and burnt it out, with 20% of the pixels driven to pure white. It now pivots around mid grey, as it should. Drawings produced before this will render differently. guide
• The Brightness slider reaches +-255 instead of +-100, so the automatic setting can actually apply the value it computes; and with equalisation and CLAHE both off the image no longer goes through a conversion that degraded its tones. guide
• The drawing index now offers the top face (plan from above) even when no such drawing exists yet - choosing it creates it, exactly as the bottom face already did. The "above" button also stops framing the previous drawing. Verified on fmb-leica, 24 Sep 2026. guide
• New command Square (alias SQ), with a toolbar icon and an entry in the context menu: it squares the selected polylines and picks the reference side itself, the longest one. Before this the squaring commands did not start at all. guide
• The squaring algorithm was rewritten (23 Sep 2026): on a rectangle it used to straighten a single corner, and on vertical sides it produced absurd displacements. The default angle tolerance goes from 5 to 10 degrees, because an outline traced on a cloud is further out than one drawn on paper. Squaring also redraws the geometry at once, instead of leaving the old outline on screen. guide
• Ctrl+Z now always undoes something: it empties the CAD engine's stack first and then moves on to the application's own undo (pitch handles, snapped vertices, deleted pitches). Ctrl+Shift+Z remains the application-only undo. No more "Z-Map" box on an empty stack. Luca, 23 Sep 2026. guide
• XY-only snap is now honoured on grips, polar tracking and the grid, and really does keep the mouse elevation. A customer reported on 23 Sep 2026 that snapping to a grip brought the target vertex's elevation with it, up to 30 m out. guide
• A CAD import, export or xref that is refused now says so. It used to close the overlay exactly as a success did. The new dialog names what was refused and why, warns when the imported drawing is empty, lists the entity types that were not imported ("CAD imported, with exclusions") and explains the DWG version limit (AutoCAD 2000 / AC1015 at the newest). guide
• The polygon cleanup stays armed: once an area is applied the next one can be traced straight away on the current view, right-click to stop. Luca, 24 Sep 2026. guide
• Building classification keeps the edge of the roof. The outer ring of the mask is now decided point by point against the local roof plane instead of by the 0.5 m cell, which is what drew those stair steps along every roof. Measured on a delivered urban survey: recall on the delivered roof surface goes from 0.801 to 0.865 where the ring reaches, with the false-positive rate outside a roof unchanged. guide
• A shed roof is no longer drawn as terrain. A wide flat roof is what a terrain filter mistakes for ground, and once that happened the building pass went blind, because it measures height against the class 2 points. A region of ground standing above the ground all around it is no longer believed as a terrain reference. On a delivered survey this brought back 2,693,988 points on a 1605 m2 shed that was drawn as terrain, while taking only 25,627 points of scrub with it. guide
• The white specks scattered over a roof are mostly gone. The roof slab used to hang off the single highest point of the cell, so an aerial, a flue or a branch reaching over raised the reference and dropped the sound roof underneath out of the slab. The slab is now measured from the roof around the cell when that highest point is a spike: -15.3% unclassified points inside a building on a delivered survey. guide
• Walls now go into class 6 with the roof. ASPRS has no class for a wall because class 6 IS the whole building, and that is how every reference classification is delivered; leaving them unclassified drew a white fringe around every building. Building F1 on a delivered urban benchmark goes from 0.8497 to 0.8862. Decided with Luca, 25 Sep 2026. guide
• Saved classifications can be deleted from the Display panel, with a confirmation: each one is a byte per point, 17 MB on a 226 M point cloud, and a run leaves one behind every time. The active version and the delivery backup are never offered. Asked by Luca, 25 Sep 2026. guide
• The class controls no longer vanish without a word: when the cloud carries no classification the panel says so. And the classes can now be hidden while looking at the cloud in RGB, which a panel redesign had tied to the active theme by mistake on 19 Aug 2026. Reported by Luca, 25 Sep 2026. guide
• The interface follows the Windows scaling on first run: at 150% the fonts used to stay tiny. Reported by a customer, 25 Sep 2026.

4.8.02026-09-24

Elevations without stripes, one image per kind, and a snap that takes hold

• The depth band is gone, and with it the black stripes. A drawing used to take a slab declared by hand - so many metres out, so many in - because nobody had measured where the wall was. On a long front that steps in and out no single slab works: narrow loses the balconies, wide drags in the building behind, and whatever the slab missed came out as a black stripe the full height of the elevation. Measured on a 158 m front: 4.3 m of drawing lost to stripes. Now the drawing takes the whole volume and the rasterizer decides what is in front, exactly as the screen does: the nearest surface wins. What you do not want is removed afterwards with the polygon cleanup - your decision on what to drop, not a geometric law applied blind. guide
• Points are splatted, so the back no longer shows through the front. One point used to light one pixel: where the drawing was finer than the cloud's own spacing, the gaps between points let the surface behind show through and the facade went transparent in patches. Each point now covers a small disc, and the radius is not a setting - it comes from the cloud's real spacing in that drawing. A denser cloud than the pixel gets a radius of zero and nothing changes. guide
• The drawing follows the view. Generating while looking at the other side used to give you the drawing of the face you were not looking at - the plane kept its own fixed sense. The side you are on is now read from the camera at the moment you press Generate. Elevations and plans only: a section plane has no front and no back. guide
• What you hid stays hidden. The point extraction asks the cloud, not the view, so the polygon cleanups - which are view exclusions - were unknown to it and the hidden points came back into the drawing. The same volumes the renderer is applying on screen are now applied before rasterizing, through the same predicate: one law, so a point hidden in one view cannot reappear in the other. guide
• Every kind of image is its own file. Depth, RGB and Intensity were three ways of rendering one raster, and generating the second overwrote the first without saying so - the choice of rendering was quietly destroying work. Each kind now has its own file, listed as its own row under Images, and delivery is per image: a drawing can have its photo-plan delivered and its depth map still on the bench. guide
• The Workbox panel, rebuilt around what you do. The six faces of the volume are six buttons, the one you are working on lit; sections and plans appear in a list only when they exist; and the panel is divided into Drawings, Images, Volume and Output. Images holds only the images that exist, one row each, and a click opens one. Output declares the delivery scale before anything is generated and forecasts, drawing by drawing, the pixels it will produce and what it will weigh. guide
• Delivered drawings go in a folder per volume, named after the volume. With three volumes in one project the files used to pile up together in exports/ and the only way to tell them apart was to read their names. guide
• The work plane is remembered. Which face you were working on is a decision, so it is saved and found again on reopening - and the view returns to it. Finding the name in a list while the view looks elsewhere is not persistence. guide
• A layer outside the catalogue can be described. It used to show an empty cell, and the only way to give it a description was to write a file by hand. The cell now offers "describe...": what you write defines a code of the study which owns that layer, so the description travels with the study's package instead of staying in this drawing. The national catalogue's names stay untouched: they are normative. guide
• Dragging a vertex onto another vertex now takes hold. Three defects in a row, all measured on the [mmu-grip-snap] channel. The object-snap gate was shut almost always, because it asked for an active tool or a non-empty grip selection and a vertex drag has neither. The snap that looks at the drawn grips had top priority and always won with the very vertex being dragged, so the destination was never examined. And the house rule - a geometric snap outranks the cloud - was implemented in one of the two paths: the idle probe sampled the cloud and pulled the vertex back to the ground the moment you stopped moving to click. Measured before and after: 2661 reads with no grips and no snap, against 759 out of 766 with the grip armed. guide
• A grip snap now declares itself. The engine moved the point and returned true but never said which snap it was, so a host that pushes its own point overwrote the result one line later. CAD_SNAP_GRIP had its bit, its help entry and its command since forever: it was only missing the line that announces it. guide

4.7.02026-09-23

The cloud stops throwing away the detail it chose; Q hides what is in the way

• The cloud no longer discards the detail it selected. Two ceilings inside the octree renderer disagreed: the level-of-detail selector was allowed to ask for 40000 nodes, and the renderer could only hold 16384. Everything above the smaller number was set aside and never drawn. Measured on a customer project in an intermediate oblique view: 40000 asked, 16384 drawn, 23616 discarded, identical frame after frame - 59% of what the selector had chosen never reached the screen, and the depth of detail stopped two levels short. The two ceilings are now one number. The working set grows by about a third of a gigabyte and the frame rate is unchanged. guide
• Stereo no longer freezes in an oblique view. It was the same defect seen from the other side: the compositor read the count of set-aside nodes as "the cloud is still loading" and held the frame back, but that count meant "given up on", not "on its way", and it never returned to zero. The stereo panel stayed on the last good pair while the main view kept moving. In a zenith view, or zoomed close in, the selection stays under the ceiling and the freeze never appeared - which is exactly what the operator reported. guide
• Hide what covers your subject, with one key. Hold Q and drag a rectangle: left to right (green) hides that area, right to left (red) takes back the areas it touches - the same direction convention as CAD selection. Rectangles add up, so the hidden region is the shape you need rather than a convenient box. Shift+Q clears them all, without opening any panel. The applied outlines are no longer drawn unless the cleanup panel is open, because while drawing they were in the way. guide
• The cleanups belong to the project that defined them. Opening a second project and closing it left the first one's masks in force: the panel said there were none while the cloud was full of holes. They are cleared with the layers now, by whichever path empties them. guide
• Two buttons next to the orientation triad: the loupe that magnifies around the cursor, and the broom that turns the cleanup on and off. Both were useful and invisible. guide
• The stereo comfort window follows the view instead of a fixed 40 metres. The depth over which the parallax is spread is now the physical width of the window, so zooming in cancels out of the law instead of flattening the relief. With vertical exaggeration on, the stereo relief goes from x1.04 to x3, and at a close working zoom a decimetre of elevation is worth 2.6 pixels of disparity instead of a tenth of a pixel. guide
• The Z exaggeration pivot is cleared when a project closes: it used to keep the previous project's value, which put one survey's ground level inside another's.
• The rotation pivot cross is no longer enormous at exaggeration 3, and no longer draws over the dialogs. The Polygon Cleanup outlines were doing the same and no longer do: they are marks on the model, so they sit above the cloud and below the panels.

4.6.02026-09-22

The strips at the bottom of the page can be put away

• The strips at the bottom of the page can be turned off. Each of the three is a little over two hundred points tall: on a laptop screen that is a fifth of the page, and the profile and the breakline strip sit on the same edge, so with Multiview open they cover each other. Every one of them now has a switch, and the choice is a preference of yours - it survives the next computation and the next start - not a state of the job. guide
• The switch is where you are working, not only in a menu. The vertical profile is turned off by the Hide profile button at the top of the Multiview panel, by the cross on the strip, or from View > Vertical profile; the same button is repeated in the breakline strip, because that is where the two overlap and where you notice it. The breakline strip has its cross and Terrain > Breaklines window; the volume strip has its cross, the Show strip tick in the Volumes panel and Terrain > Volume profiles. Four ways in, one preference behind them. guide
• Closing the breakline strip does not disarm the tool. The calculation that follows the cursor - the one that draws the preview of crest and toe on the drawing - used to live inside the strip, so hiding it would have frozen the preview on the last point read: a still preview does not say "I am not looking", it draws a break that is not there. It runs outside the strip now. Arming, the automatic run and the undo stay in the Terrain menu; the work area and the run along the guide live only in the strip. guide
• The volume strip had three switches that forgot. The tick in the panel, the cross on the strip and the Profiles button each set their own flag, it lasted as long as the session, and every new computation turned the strip back on - so on a small screen you closed it again after every volume. They are one switch now, and it is remembered: if you closed it, computing another volume leaves it closed. guide
• Hiding the breakline strip gives its band back to the drawing. The strip is opaque and the viewport reserves its height, so the same switch that hides it also returns those two hundred and forty points to the cloud and the CAD, instead of leaving an empty band above the status bar. guide

4.5.02026-09-22

The terrain becomes a drawing: contour lines, breaklines and volumes

• A Terrain menu. What concerns the terrain used to be scattered - building the model sat under Snap because GND-Z needs it - and now lives in one place, in the order the work is done: build the model with the Cloth Simulation Filter, or load one the project already has on disk (each terrain is listed with its size, and the one you pick becomes the session terrain that GND-Z and everything below sample); then the contour lines; then the breaklines; then the volumes. GND-Z stays where it was - it is a snap, not a terrain function. guide
• Contour lines. Terrain > Contour lines traces the levels on the terrain model and writes them into the drawing as polylines, with the interval, the index interval, the shortest line kept, the vertex thinning and the two layers - ordinary and index - set in the dialog. Measured on a 2 by 2 km quarry at 0.5 m cells: 0.9 seconds, 449 000 vertices, 28.8% of the raw trace with the length preserved to 99.5%, and zero crossings between neighbouring lines. Against gdal_contour on the same raster the trace agrees within 0.02% of the vertices, so a difference is ours to explain. guide
• Contour lines are not drawn on terrain nobody surveyed. A terrain model carries a provenance mask now - each cell is measured, interpolated inside the surveyed envelope, or extrapolated outside it - and the tracer skips the extrapolated cells unless you ask for them. On a real block that is 36% of the raster and 42% of the line length: 35.5 km of contour became 20.7 km, and inside the surveyed ground not a single metre was lost. The mask travels with the terrain and is written next to dtm.tif as dtm_mask.tif, which stays identical bit for bit. guide
• Breaklines from a click. Click near the edge of a bench, a quarry face or an embankment and the whole line comes out - crest and toe, from one end of the face to the other, as two polylines on their own layers. The face is measured on the terrain model rather than on the contours, because contours shatter into two-metre fragments on a wall and the rubble of a yard is as dense as a step. Four numbers govern it and all four are typed, not guessed: the spacing between stations, the smallest step that counts as one, the slope below which the ground is a bench and not a face, and the widest a break may be in plan between crest and toe - the last one is what stops a pair a hundred metres apart from being accepted just because it is also high. guide
• Every break in the area. The same engine run without a click: it finds the faces itself over an area you draw - or over the whole cloud when none is drawn - and delivers crest and toe for every one the sections confirm, reporting how many knees out of how many sections held. A break already drawn is not drawn again, and Esc stops the run. Either way the last line, or the last run, can be taken back from the menu. guide
• Breaklines enter the surface. Once they are in the drawing, the contour dialog offers to respect them: their height is forced into the terrain cells they cross and no contour is allowed to cross one, so the lines bend at the crest instead of climbing over it. This is the difference between a contour map of a quarry that a surveyor signs and one that merely looks like the ground. guide
• Volumes against a quoted polygon. Terrain > Volumes measures cut and fill between the terrain model and an area you draw from the dialog: click its corners on the cloud, close it, and every vertex arrives with the ground elevation under it, ready for the design elevation to be typed over it - one by one, or one value applied to all, or taken from a closed polyline already in the drawing. The reference surface is the triangulation of that polygon, so every quoted vertex is honoured exactly; a least-squares plane would have thrown away the numbers the operator put there. guide
• What the volume result tells you. Cut, fill and net, the area in cut and the area in fill, the highest cut, the deepest fill and the mean absolute difference, over a calculation cell you choose - with the terrain's own cell shown next to it, because a finer cell gives longer numbers, not truer ones. Ground with no terrain underneath is reported in square metres and left out of the volumes rather than guessed, and the share of the volume resting on reconstructed cells is stated separately: a cubic metre over extrapolated ground is not worth one over measured ground. guide
• A volume is an item the project keeps. Each measurement is saved with the project - the quoted area, the cell and the delivered numbers - and is listed in the dialog to be shown on the view again, profiled, reported or deleted. The delivered numbers are never silently rewritten: recomputed on today's terrain, a difference beyond half a percent is stated, because the ground underneath may genuinely have moved. Report... writes the measurement out with the plan of the area, so what was delivered can be read outside the application. guide
• Turning the model no longer closes what you are drawing. With a polyline open, the only way to rotate was a right-button drag - and the right button is the button the command uses to close the entity, so it was either turn the view or carry on the line, never both. Hold Shift and drag with the right button and the rotation happens without the command ever seeing the click: the polyline stays open, the rubber band stays live, and the vertex you are about to place stays where it is while the view turns around it. The pivot is taken on the cloud under the cursor, as it always was. The right button on its own still closes the entity and re-arms the tool, unchanged. guide
• The first vertex lands where you clicked, not where the mouse was before you went to the menu. Starting a drawing command from a menu takes the pointer out of the view and back in, and the CAD engine never saw that journey: until the first mouse movement reached it, it still held the cursor from before. Measured on a real session, the first frame after the command opened had it 232 by 183 pixels away from the mouse - so a click right then put the first vertex there, and with object snap on it latched to whatever vertex was sitting at that spot. The engine is now told where the pointer already is the moment a command arms. guide
• The registration guard stops switching itself off while you draw. The guard that keeps the CAD projection and the cloud registered to each other cannot re-push the projection under an operator's hands - that would lose a selection - so with a command running it postpones the repair. It was counting each postponement as a failed repair, and after three it disarmed itself for the rest of the session. Measured: six seconds after a polyline was started, leaving a 177 m offset in place for the next five and a half minutes, with every vertex committed that far from where it was picked. A postponement is not a failure: the repair now runs as soon as the command ends. guide
• Cloud Z snap stops landing on the wrong surface. The rule is that only what is drawn is snappable, and it was held for which points are drawn but broken for how wide they are: the display sized each point from the spacing of its own node while the depth raster behind snapping used one small fixed size. On a sparse cloud that makes a sieve under a surface that looks continuous, and the search under the cursor then returns the nearest sample it can find - another surface, metres away in height. The depth raster now follows the same per-node law as the display. guide
• Smaller things. Close polyline is in the right-click menu while a polyline is being drawn, and only there. An overview band closed by hand stays closed - no automatism takes it back. The orientation triad is pinned to the top-left corner above the viewport buttons, always visible, instead of floating where it was last left. guide

4.4.12026-09-21

Stereo comes back when you zoom in, and the wheel moves the elevation at once

• Stereo comes back when you zoom in. Since 3.96 the comfort limit - the rule that keeps the two eye images fusable - has been computing itself over the wrong depth: it measured the boxes of the octree nodes being drawn, and those never shrink, because the cloud keeps drawing its coarse levels at every zoom and a node's box is a solid cube while its content is a surface crossing it. Measured on a real project, that depth read 397 m whether the view showed 3.6 m of ground or 200 m, so the closer you worked the more the limit divided the stereo away: at the zoom used for restitution it was cutting the effect by three to thirty times, which is two eye images that differ by less than a pixel over the object being measured. The limit now measures only the nodes whose cube is no larger than the view, which is the depth actually in front of you, and it follows the zoom. On a dense project the stereo effect at working zoom returns two to four times stronger. Nothing about what is drawn has changed: this decides only how much the two eyes are separated. guide
• The elevation set with the wheel moves the mark at once. While a drawing command was running, turning the wheel changed the elevation but the floating mark stayed where it was until the mouse was moved sideways, so the height appeared to jump in steps instead of following the wheel. The elevation was reaching the CAD engine; nothing was asking it to redraw the mark, which it only does when it receives the pointer. It is now told the pointer is where it already is, so the mark and the rubber band follow the wheel continuously. Outside a command the mark already behaved this way. guide

4.4.02026-09-21

The cloud is drawn by the graphics card; Multiview gains a profile, an edit session and an undo

• Octree point clouds are drawn straight from the graphics card. The nodes already decoded are kept in graphics memory and drawn from there, instead of merging and re-uploading every visible point each time the view changes - so navigation stays smooth on large projects and the cloud no longer loses a whole region when the budget drops. It is not a setting: there is no checkbox, because two live paths for the same cloud cost twice plus the defects that hide in the one nobody exercises. Hidden classes, exclusion volumes and the area clips are honoured on this path - the correctness gate that sent 4.3.0 back - and picking, cursor drape and stereo read the same points that are drawn. Validated on two real projects, an urban survey (30 million points) and a coastal survey (223 million, 814 thousand nodes), in stereo and on all four representations. Grid-tile clouds keep the classic path, which is what they have always used. For support, SC3D_CLOUD_RESIDENT_GL=0 restores the old rendering. guide
• The orbit pivot is taken under the cursor and held there for the whole rotation, instead of being recomputed mid-drag; the depth it reads is now taken from the buffer the cloud actually writes into, which is why deep zooms used to fall back to the centre of the window. Measured on the coastal survey: 13 rotations at deep zoom, 13 pivots found, no fallbacks. The G key is no longer needed to pivot on a surface. guide
• Multiview shows a vertical profile of the cloud under the two views: the surface cut through the work in progress, drawn as a profile line the way a survey section is read. It runs through the centre of the building and twice its largest dimension, turns across the pitches - along the slope, where the shape of a roof shows - and follows the pitch you are still drawing, which is when it is worth most. While you review vertices one at a time it follows the picked vertex instead. A second line cuts perpendicular to the first, and when the profile cannot follow the pitches the strip says why instead of quietly turning to an arbitrary axis. guide
• Correcting a building already drawn is a session. Clicking its numbered circle takes the pitches out of the drawing and holds them in the application, where they behave like a pitch still being drawn - elastic outline, no engine in between - and they go back into the drawing when you leave or confirm. Leaving loses nothing, saving or closing the project hands the session over first, and the panel says which building is in edit and where the way out is. With a building in edit, the right button held still on a handle opens the editing menu: delete vertex, split edge, delete pitch, undo. guide
• A second undo, Modify -> Undo geometry edit (Ctrl+Shift+Z), for the edits the CAD engine never records: pitch handle drags, a vertex or edge snapped with Fix vertex, a building's pitches deleted. Ctrl+Z on those did not undo the gesture - it undid the previous CAD command, which is a different kind of damage. The menu entry names the gesture it is about to undo, and Esc during a handle drag abandons it and puts the handle back where it was. guide
• The area of interest stops cropping the view. It stays what it always meant - the scope of the computation - so the cloud around it remains visible while you work. View Polygon Cleanup is now Polygon cleanup and reads the points in the same stretched space it draws them in, so what it removes is what you enclosed. guide
• Fixes gathered in this release: building numbers are rebuilt when a drawing is reopened, so pitches drawn in an earlier session belong to a building again instead of being nameless white polygons; the first Multiview capture on an octree project no longer arrives nearly empty, because waiting for the cloud now also waits for node decoding and not only for the grid-tile queue (coastal survey: 12,288 points in the first pose against 1,090,053 in the second, which was inheriting the first one's work); the point splat takes its size from the data; and a stereo frame with nothing to draw is no longer written to the log as a failure.

4.3.12026-09-18

The right button rotates the model; measurement mark and workspace fixes

• The right mouse button rotates the model. Holding the right button and dragging orbits the view around the cloud point at the centre of the window, resampled as you drag - the gesture most 3D software uses, and the one Shift + middle button was failing to provide. Shift + middle button still works as a fallback; the wheel still zooms, the wheel held still pans, and the right button clicked (not dragged) still opens the context menu. guide
• A Representation dialog for the point cloud, reachable from Cloud -> Representation and from the viewport context menu. It gathers the cloud's own display controls in one place and adds two: a Gaussian-splat rendering that fills the gaps between measured points into a continuous surface, and Eye-Dome Lighting to bring out relief. Both are toggles; the classification, intensity and RGB colouring the cloud already had are untouched. guide
• Fixes gathered in this release: the stereo measurement mark follows the elevation again (a comfort limit added on 30 July had been flattening it, so changing Z moved the number but not the mark); picking a workspace from the View menu restores the arrangement you left it in instead of reopening every toolbar of the factory preset; and a LAS/LAZ file whose header declares a degenerate bounding box is rescanned for its real extent at import, instead of building a unit cube at the origin and silently dropping nearly every point.

4.3.02026-09-18

The cloud moves smoothly; the right button rotates the model

• The cloud stays fluid while you navigate. Until now every view change re-merged all visible points on the CPU and re-uploaded them to the GPU, so a large cloud stuttered exactly while you were moving through it. The octree cloud is now drawn from GPU-resident per-node buffers uploaded once and kept there: a view change only re-walks the visible node list and redraws, with no per-frame re-upload. On by default; if a graphics card misbehaves, the environment variable SC3D_CLOUD_RESIDENT_GL=0 forces the previous path back. Grid-tile clouds are unchanged.
• The right mouse button rotates the model. Holding the right button and dragging now orbits the view around the cloud point at the centre of the window, resampled as you drag - the gesture most 3D software uses, and the one Shift + middle button was failing to provide. Shift + middle button still works as a fallback. Wheel still zooms, the wheel held still pans, and the right button clicked (not dragged) still opens the context menu. guide
• A Representation dialog for the point cloud, reachable from Cloud -> Representation and from the viewport context menu. It gathers the cloud's own display controls in one place and adds two: a Gaussian-splat rendering that fills the gaps between measured points into a continuous surface, and Eye-Dome Lighting to bring out relief. Both are toggles; the classification, intensity and RGB colouring the cloud already had are untouched. guide
• Fixes gathered in this release: the stereo measurement mark follows the elevation again (a comfort limit added on 30 July had been flattening it, so changing Z moved the number but not the mark - the two parallax marks now place the point where it really is); picking a workspace from the View menu restores the arrangement you left it in instead of reopening every toolbar of the factory preset (the preset is applied only the first time, when nothing is remembered yet); and a LAS/LAZ file whose header declares a degenerate bounding box is rescanned for its real extent at import, instead of building a unit cube at the origin and silently dropping nearly every point.

4.2.02026-09-11

Power-line supports found more completely; stereo holds its depth on octree zoom

• Power-line support finding is more complete. A span ends where the returns end, not where the pole is, so the search now extends the analysed section about ten metres past each end - that is where a structure usually stands. It also weighs the one thing a support has and its surroundings do not: a dense vertical column of returns under the conductor. Measured on Bizzuno (9 Sep 2026) against 17 hand-marked structures, the two together took the finder from 6 of 17 to 14 of 17, without loosening what counts as a support - the column test is only ever asked inside a conductor's corridor.
• Building numbers no longer float over buildings that are gone. The numbers are an overlay, not CAD entities, so deleting the last roof pitch used to leave the labels hanging in empty space; they are now cleared with the buildings they numbered. Eaves, feet and walls already committed stay in the drawing - those are real entities and only the operator removes them.
• Stereo holds its depth when you zoom into an octree cloud. The comfort limit that keeps the two eyes fusable was measuring the depth range of the whole scene, so on a grid-less octree it saw hundreds of metres at every zoom and squeezed the parallax toward zero - the cloud went flat exactly when you zoomed in to work. It now measures the octree nodes actually on screen, so the depth range shrinks with the zoom and the relief stays. Grid-tile clouds and nadir views are unchanged.

4.1.02026-09-09

Multiview docks in, three panels share one kind of button

• Three buttons, one behaviour: Scene Tree, Multiview and Zenith Overview each get a chip over the top-left corner of the mono view - blue Open while closed, orange Close while open, same click closes what it opened. Multiview used to open only from a chip that vanished once it was on screen, and the Scene Tree had no button at all. A workspace shows a button only for a window it actually uses: Aerial and Terrestrial Mapping show all three, with Scene Tree open and the other two closed by default; Mobile Mapping shows only Multiview, closed, because the band it would dock into is the one the station strip already uses. guide
• Multiview is docked, not floating: it takes the same side band as the Zenith Overview, the mobile station strip and the Ortho Sheets index, one at a time, with its own splitter that remembers how wide you left it. Which of the four holds the band is now decided in one place instead of eight, each of which used to write the decision by hand - a project opened with an ortho layer already visible, for instance, could leave Multiview's own button reading Close in front of a window that was not there. guide
• Every docked side panel's resize splitter is one pixel wide instead of an invisible thirty-two: ImGui's own minimum window size was overriding the four-pixel splitters, and the extra width fell on the panel next to it - the checkboxes closest to a docked panel's edge were unclickable while the label beside them still worked. Fixed at the source for all seven splitters in the application, not only Multiview's.
• Multiview's photographic capture no longer runs inside the interface's own frame. It used to open a progress cover mid-frame, which is a second frame nested inside the one already being drawn - occasionally seen as the whole window going unresponsive until switching away and back. The capture is now requested during the frame and run before the next one starts, where no frame is open; it costs one frame of delay and the panel already shows that as the wait it is.
• Cursor loupe is one command behind View -> Cursor loupe, the Multiview checkbox and a new shortcut, Ctrl+Alt+L: the three used to be two separate switches on the same setting, which is exactly how they could disagree. The key is reassignable from the keyboard shortcuts dialog like any other command. guide
• Multiview no longer offers the Roof tab on a Mobile Mapping project: a run from a vehicle looks at things from the road and the two photographic views the tab needs would be aimed at a roof the cloud never really saw. Strada, Polilinea, Spline, Ellisse and Rettangolo are unaffected, on every workspace.
• A classification version now reads Class: <date> instead of a bare date, so the list says what the date is the date OF. The Classification - Original entry keeps its own name, which already says that.
• Fixed a crash on selecting or editing an ellipse on certain layers (ACCESS_VIOLATION inside the native engine). The application was asking the engine for an entity's polyline vertices without first checking that the entity was a polyline - true for a filled pitch's mesh, false for an ellipse - and the engine does not defend against being asked the wrong question.
• Fixed a desk where one eye of the active-shutter panel showed the cloud and the other showed the Windows desktop. The panel's mono fallback frame - drawn whenever the content is not stereo, including every transition out of a stereo trial - was not declaring which of the panel's two buffers to paint, so it inherited whichever the previous frame had left selected and the other buffer was never touched.
• New command: Road. A guide polyline follows one edge of a road - usually the one the operator can see best - and delivers up to three open, equidistant polylines on the same layer; the parallel edges are computed in plan and sampled on the cloud at delivery, because the far edge of a road is not at the guide's own elevation and that cross-slope is exactly what the second and third lines are for.
• Polyline, Spline, Ellipse and Rectangle now leave the same mark on the drawing as Roof, Eave and Road while the native engine is drawing them: every point the engine actually consumes echoes as our own dot and connecting line, so a tab built from native CAD commands no longer reads as a different tool from the ones built by hand. The engine keeps its own snap, grips and rubber-band untouched - this is a mark on top of them, not a second drawing of them.
• The navigation reminder band is dismissible again per installation instead of permanently: a version bump brings it back once, which is the one moment a reminder about Shift + wheel is worth showing again.
• Default CAD layer names (FALDA, GRONDA, PIEDE, PARETI and others) now follow the application's language instead of always being Italian, the same rule already applied to the extraction layers. A name already written into a drawing is never renamed.
• Imagery import: QGIS with an MSI install (no InstallLocation registry value) is found through its .qgs/.qgz file-type icon registration instead of being reported missing, and its GDAL_DRIVER_PATH is set so QGIS's own gdalinfo can see formats such as ECW that our bundled GDAL does not carry.

4.0.02026-09-09

Multiview becomes the roof workbench

• Multiview shows TWO views instead of four, and chooses their bearings by looking at the cloud. Thirty-six candidate bearings are scored: for each, the line of sight from the point to the eye is tested and the cloud points inside a thin cylinder around it are counted as obstacles. The two clearest win, kept at least 60 degrees apart because two views ten degrees from each other say nothing more than one. When nothing is in the way - the normal case on an open roof - every candidate ties, and the panel keeps your own bearing and your bearing plus 90 rather than let the views wander for no reason. The obstacle counts that justified the choice are printed under the option, and a checkbox returns to fixed bearings. guide
• The pitch outlines already in the drawing are projected into both Multiview windows, through the very matrix that produced each frame, so they fall on the points that surround them. The part of an outline hidden behind the roof in that view is drawn faint rather than removed - it says the edge is there and where, without pretending it is in front. A dot marks each vertex, and the outlines are re-read every frame, so a vertex just moved appears immediately. guide
• Pitch handles replace Fix vertex, which did not work and has been removed. Every pitch in the drawing carries a filled dot on each vertex and a hollow ring on each edge midpoint, always present, with no command to start - the way grips work in a CAD. A vertex handle moves that corner; an edge handle translates the whole edge rigidly. Everything welded to that point moves with it: every vertex within 3 cm, on the pitch, eave, foot and wall layers alike, because moving one entity on its own unsticks the building. The movement is in plan, measured by intersecting the cursor with the horizontal plane at the handle's own elevation, and the fill follows the border. guide
• Free vertices land on the plane of the pitch. A pitch is a plane: the first three vertices define it, and from the fourth on the elevation is a consequence, not new information. A vertex you have not fixed yourself now takes its elevation from that plane instead of from the cloud sample under the cursor. The plane starts from your own three vertices - what you declared is not up for discussion - then only the cloud points within 50 cm of it are kept and the plane is re-fitted by least squares on those; if the refined plane has tilted more than 15 degrees from yours it is not a refinement and yours is kept. A vertex fixed by a snap, by Shift or with the wheel is never touched. guide
• A click takes the elevation you can see. The status bar, the loupe and the click used to read the cloud by two different routes on the same pixel, and on 9 September they differed by 23 metres without anything saying so. Now the vertex takes the shown elevation whenever that reading belongs to the pixel under the cursor, and the log names which of the two answered. The elevation hysteresis existed only to rescue the second sample and has been removed with it, checkbox and setting included. guide
• Cursor loupe: a round window beside the cursor showing a vertical section of the cloud through the cursor - horizontal axis along the section, vertical axis elevation, a slab of 35 cm either side - so you see the profile of the surface the point is about to land on. It is a real render, it follows the cursor, and it updates live while you nudge the elevation with Shift or Ctrl and the wheel. View menu, and a checkbox in Multiview. guide
• Multiview refuses to work off nadir or with vertical exaggeration on, and says so. It reads elevation off the rendered frame, and both of those make that reading wrong without looking wrong: the panel covers its own content with the reason written on it, naming how many degrees the view is tilted, and takes no capture while the cover is up. Exaggeration is held at 1.0x for as long as the panel is open, as before. guide
• The cloud no longer goes coarse after a Multiview capture. Each pose redoes the tile selection for its own camera - five metres of radius at 45 degrees - and that selection stayed on the operator's view afterwards, so the main window kept drawing a handful of tiles chosen for a close-up. It could not repair itself either, because the frame loop skips redrawing when nothing is dirty. The selection is now put back when the capture ends, and the frame is marked for redraw. guide
• Buildings: T-junctions are welded. A vertex placed with the edge snap lands in the middle of another pitch's edge, so the two faces share no whole edge and were never grouped. Every vertex lying on another pitch's edge is now inserted into that edge before any comparison, on the reading and never on the drawing - a filled pitch is two entities with the same vertices, and inserting a vertex into the mesh would shift its face indices and tear the fill. guide
• A filled pitch is counted once. The engine exposes the mesh and its dark border as two polylines with identical vertices, and counting both made every filled pitch look like a two-pitch building whose outline could not close - two of them in the 9 September drawing. The duplicate is dropped and the log names the pair. guide
• A building whose pitches do not close a single ring says so on the mono view, next to its own number, instead of only in the log: an outline refused in silence just looks like a building that does not work. The refusal itself is deliberate - a contradiction between grouping and edge cancellation produces an outline that runs through the middle of the building, and that outline would become a foot and walls written into the drawing. guide
• The pitch fill follows its own outline again, including on re-entrant shapes. The fill was cut as a fan from the first vertex, which is only valid on a convex polygon: on an L-shaped pitch the triangles jumped the notch and the colour spilled past the border. It is now cut by ear clipping, which holds for any simple polygon, and the same cut is used by the fill and by anything that rebuilds it. guide
• Esc undoes the last vertex instead of the whole face; Esc twice within 0.6 s abandons it. Eave outline and pitch face both. And a face whose own bounding box spans more than 100 km is refused rather than written, naming the offending vertex: a single bad elevation used to be enough to make a drawing unusable. guide
• Wall handles on a draft building: an orange handle on the midpoint of each wall of the foot, dragged along the direction that wall actually moves in, so a movement parallel to the wall does nothing. It sets the eave overhang for that wall alone - how you push one wall up against the neighbouring building without changing the rest. guide
• Confirm all buildings in draft has been removed. A button that writes geometry into the drawing for buildings you are not looking at is a button that gets pressed by mistake; confirming is now one building at a time, the one you have selected. guide
• The Layers panel stops offering silent buttons. Delete and Purge are gated, explain themselves when disabled, and report the outcome in a coloured line instead of doing nothing visible; the cloud bounds layer is protected.
• Multiview no longer rotates the cloud. A capture used to restore the view through a shared view state that orbit never republishes, so after an orbit the restore put the cloud back somewhere else. The capture now works on a copy of the camera and never touches the operator's own: 38 captures, no interventions. guide
• Overlays are drawn behind windows, not over them. Pitch, eave, building numbers and handles all moved to the background draw list, so a dialog covers them instead of being covered by them, and they no longer print building numbers on the edge of the Multiview panel. They also track the pan properly while dragging.

3.98.02026-09-07

Multiview: four real views instead of one calculated slice

• Multiview: the four windows are real renders from the point cloud - same point theme, point size, LOD and streaming as the main view - rendered from four poses 45 degrees above the horizon, 45 degrees apart in bearing, instead of quadrilaterals painted from a separately-read list of points. Two renders of the same cloud kept aligned by hand were one too many. guide
• Multiview zoom and pan: the wheel zooms into the image already captured, the middle button drags it, both shared across all four windows since they show the same point at the same resolution. A window opens already at 4x, centred on the point - the camera's own focus - instead of the whole capture at 1x. guide
• Multiview no longer loses a badly mis-placed vertex. A vertex that snapped to the ground instead of a roof six or eight metres up used to be framed out of the shot entirely, because the camera distance followed the same small radius used for the on-screen ruler and the numeric editors. The camera now keeps a floor of 40 m of distance regardless of that radius, so the real surface is always in frame. guide
• Multiview shows progress while it captures. Four off-screen renders with tile selection redone for that camera can take up to half a second on an area not already cached; a short message now says so instead of leaving the window looking stuck. guide
• A button in the corner of the mono view opens Multiview when it is closed. It turns amber and explains itself when vertical exaggeration is active, instead of staying hidden - opening Multiview holds exaggeration at 1.0x while it stays open, and the operator can now see the tool exists even then. guide
• Multiview stops disappearing on its own. Turning vertical exaggeration back on while the panel was open used to close it AND overwrite the saved "was open" setting, so the next start found it closed even though the operator never closed it themselves. The forced close now only lasts for the session; the saved preference survives. guide
• Multiview no longer appears on the welcome screen before a project is open. Its open/closed state is still restored from what you left last time, it just waits for a project to exist before showing the window. guide
• New: Eave outline (Draw menu, or the button inside Multiview). A closed polygon digitized on the mono view, one vertex per click, drawn already closed like the elastic polygon in Building reconstruction - but the vertices live in the application until the polygon closes, not in a live CAD command. That is what lets Multiview correct a vertex you just placed: a CAD engine has no call to move a vertex a running command still holds, and this sidesteps the limitation instead of waiting on it. guide
• Eave outline checks elevation between vertices. A new vertex more than 1 m from the previous one's elevation triggers a search within 1 m of that previous elevation, and the median of what is found replaces the raw value - the correction for a vertex that snapped to the ground instead of the roof edge. On by default, with a checkbox in Multiview. guide
• Eave outline writes to a layer assigned to the entity, not the layer that happened to be current: a persistent, editable field next to the button in Multiview, meant to be shared by other entity types later. Right-click, or clicking near the first vertex, closes the outline, writes it, and starts a new one of the same type immediately - no need to reopen the command between buildings. guide
• Eave outline now tracks the view during a live pan. The overlay was projected from the cloud renderer's own camera, which is deliberately held still during a pan drag for performance (the picture moves as a pixel blit, not a new render); the outline now applies the same on-screen translation instead of standing still while the cloud slides under it. guide
• Classification holds up without an RGB colour channel, and now measures itself. Vegetation roughness is the residual from the cell's own best-fit plane instead of the standard deviation along Z, which read a standing facade as rough only because it is vertical - false roofs down to 0.40x, and F1 without colour up from 0.661 to 0.712 on a delivered urban survey. The building planarity threshold, which used to pass 100% of roofs and 99.8% of canopies and therefore filtered nothing on its own, moved to 0.124 (0.086 without the colour gate): F1 without colour from 0.650 to 0.833. Intensity scaling from 16 to 8 bit now picks its shift from the 99.5th percentile instead of a fixed >>8, which read a delivery peaking at 1179 as almost black. A new regression tool (classification_regression.py) reruns the pipeline against a delivery and compares F1 scores with the baseline.
• Four elevation colour ramps (Display panel) replace the single wired-in jet: Spectrum (the previous default, unchanged for existing projects), Grayscale (the former checkbox), Terrain and Cool, both rising in brightness from low to high so a slope reads as a slope instead of the false edge jet's rise-then-fall banding used to draw on flat ground. Each is shown as a sample swatch next to its name, because a colour ramp is chosen by looking at it.
• Polar tracking (F8) is back on the georeferenced 3D drawing. It had been switched off on 3D on 30 July inside an unrelated commit; reading the native CadDll source showed the 0/90-degree guides are already planimetric in world XY regardless of an oblique view, and elevation was never the polar snap's concern in the first place. The cursor's distance/angle tooltip, missing since 3.8.0 for a missing font, is back too.

3.97.02026-09-07

Active shutter stereo explains itself

• New panel "Stereo: state and performance". Card, driver quad-buffer, chosen path, emitter state and live statistics of the presenter while it runs, in one place. It also carries a calibration pattern - a red and a blue cross, one per eye - and an on-demand performance measurement, so a question about a desk can be answered on the spot instead of by exchanging logs. guide
• The driver path is again the automatic choice when the driver offers quad-buffer, as it was before a change on 5 September made page flip the default everywhere. On a workstation graphics card that offers quad-buffer stereo the driver produces both eyes and drives the emitter itself - measured on such a card, where the glasses start the instant the panel opens without our code touching the USB - and sending that desk to page flip deprives it of an emitter it cannot open. guide
• The emitter phase delay is a live slider: it applies to the running presenter and saves itself. Before, it could only be changed by editing settings.json and restarting. guide
• The same stereo report now goes into every support package, whether or not the operator ever opened that panel. And two of its fields say when they were never measured instead of printing "no": printing "no" for something that had simply not been measured caused two wrong diagnoses in one debugging session. guide
• Imagery that does not declare the project's coordinate system now says so on import. The application does not reproject an orthophoto: it draws it where its own coordinates say, so the photo can land beside the cloud. It is a warning and never an error - the import succeeded, and the operator may well know that the two systems agree on the ground.
• Point sections read out the position along the axis while the section is moved, and say explicitly when a move was not applied instead of leaving the section where it was without a word.

3.96.02026-09-04

The 3D window shows the drawing again

• The 3D window is no longer empty. To get a window the driver would accept for stereo, the application had been asking CadDll for one - and that puts CadDll into stereo mode, where it paints both eyes into its own window and refuses to draw anything for any other, which is how StereoCAD works and is not how this application works. StereoCloud3D composes cloud, drawing and cursor itself and needs CadDll's ordinary mono drawing to do it, so it was left composing from an empty picture: the customer's log named it in three words, "mono_scene_empty", with the drawing's four entities present and nothing drawn. The stereo window is now made by the application, with the same stereo pixel format from the same driver, and CadDll is left in mono where this application needs it. guide
• Stereo can be switched on before a drawing is attached. The wait for the CAD attach existed only because the stereo window had to be asked of CadDll, which cannot provide one until a drawing exists. guide

3.95.02026-09-04

The 3D window stops going white, and comes back when you switch stereo on again

• The 3D window no longer goes white a moment after it opens. Moving the pointer into the CAD viewport switched the driver stereo off on the drawing that feeds that window: CadDll deleted the render context, and every frame from then on was drawn against a handle that no longer existed, which Windows reported as ERROR_INVALID_HANDLE about a hundred and twenty times a second with nothing left to bring the picture back. On the customer's desk the panel came up correctly at 14:27:56 and died at 14:28:26, the first time the pointer entered the drawing area. StereoCAD draws with that same stereo mode active throughout, so only the stereo modes internal to the CAD window are switched off before a pointer position is passed. guide
• Switching stereo off and on again brings the 3D window back. The window was being taken over whenever the layout selected it, whether or not stereo was on, while the display logic destroyed it again for exactly that reason - twenty-two create-and-destroy cycles in under two seconds on the customer's log - so after one switch-off the window never returned. It is now taken when stereo is actually on. guide
• No white 3D window at startup either, for the same reason: with stereo off nothing is drawn into it, so it no longer opens. guide

3.94.02026-09-04

Shutter stereo works again where the driver produces both eyes

• Active shutter no longer refuses to start when no display runs at 100 Hz. That requirement belongs to the eye alternation StereoCloud3D performs itself: it swaps left and right every frame, so at 60 Hz each eye would receive 30. Where the graphics driver produces both eyes - a workstation graphics card that offers quad-buffer stereo, with stereo switched on - nothing is alternated by us, and the refresh rate is the driver's business. The check was made before that path was even tried and then latched for the rest of the session, so a customer desk with a workstation graphics card was refused stereo for an hour while the same computer was driving the same glasses correctly in StereoCAD. Its log named the contradiction on two consecutive lines: the driver offered quad-buffer stereo, and the next line refused for the panel rate. guide
• Desks whose stereo panel runs at 60 Hz or below now work. When the driver owns the two eyes they need not be alternated at all: a passive polarized screen, a pair of screens in the driver's clone mode and an HDMI frame-packed 3D mode all show both images at once, which is why such installations have always been built on ordinary 60 Hz panels. guide
• A graphics card that has quad-buffer stereo is no longer told it has none. The display setup wizard was reading whether the application's own window had been given a stereo context - and it never asks for one - instead of asking the driver what it offers. A workstation graphics card was therefore shown 'NO with this graphics card', advising the purchase of hardware it already was. guide
• The desktop audit reports a stereo panel below 120 Hz as a note rather than an error where the driver drives the eyes, instead of telling a correctly built desk that its hardware is wrong. guide
• The manual now describes the two stereo paths in 12.10 and says which requirements belong to each: Zadig, the emitter firmware, the administrator run and the 120 Hz panel are asked only where StereoCloud3D drives the emitter itself. guide

3.93.02026-09-04

The rotation centre stops wandering, the vanished cloud comes back, and refusals say why

• Rotating without G no longer makes the model drift away. The centre taken for you was re-picked from scratch at every single drag, so each rotation turned around a different point and the model slid out of frame a bit more each time - measured on a client session: five rotations, five different centres, and five pans in eight seconds to chase the model back. Now that centre is resolved once and kept, and it is dropped only when it leaves the viewport. guide
• The rotation centre you did not choose is now visible, in magenta, so it can be told apart from the cyan and amber gizmo of the pivot you place with G. It stays on screen after the drag, not only during it. guide
• The point cloud no longer disappears after returning to plan view. Restoring plan view wrote the elevation of the panned view centre into the georeferenced projection anchor - counting the pan twice, which the code forbids by name elsewhere. On a client project the anchor jumped 66 m above the drawing plane and never came back: in plan view the error is invisible, and at the first tilted view the drawing projected about ten thousand pixels outside the window while the cloud went blank. Nothing an operator could do brought it back - pan and zoom live in the view rectangle, rotating without G never rewrites the anchor, and pressing the plan-view key again rewrote the same wrong value. The anchor is now preserved, and a log line reports the value kept at every restore.
• Vertical exaggeration says which condition is holding it back, instead of listing the requirements. It names the licence that does not include the aerial pipeline, the workspace that is not aerial, the project that is in mono, or the panel that has to close - by name. Reading the old message cost a full session chasing a workspace bug that did not exist, on a project that was aerial all along and simply opened in mono. guide
• Asking for the exaggeration with Point section or Building reconstruction open now offers to close the panel instead of refusing. Confirm and the panel closes and the stretch is applied in one go; cancel and nothing changes. Closing Point section loses nothing - every elevation correction is handed to the drawing as you make it - while closing Building reconstruction discards the faces already picked, so when there are any the warning says how many and that it cannot be undone. guide
• Aerial Mapping is one entry in the Workspace menu, not three. LiDAR Survey, Orthophoto & DTM and Building Extraction started from the same sixteen-panel preset and the same side pane, so choosing between them changed nothing an operator could see. Projects saved with any of the three keep opening exactly as before. guide
• Three drawing commands that did not work are gone: Sketch, Text and Hatch. They were offered in the Draw menu, on the toolbar and as typed aliases (SK, T, HA), and none of them completed - a command that is listed but cannot finish costs the operator a try, an undo and the doubt that they held it wrong. Removed at every layer they lived in, menu and toolbar included, with the manual and the five translations following. The rest of the drawing set is untouched. guide
• The starter macro Annotation (key N) went with them: it drew Text and had nothing left to run. Macros already saved keep pointing at the entity type they were saved with - the retired slot stays in place so no macro silently changes shape - and one that still asks for Text says so in the log instead of firing a command that no longer exists. Key N is free again. guide
• Repeat last command is no longer listed in the right-click menu when there is nothing to repeat. It used to sit there greyed out at every start. guide
• Point section stays closed if you closed it. Its open/closed state was read at start but never written back except by the menu toggle, so closing the window with its own button left true on disk and the panel came back at the next start, session after session. It now follows what you actually left on screen. guide

3.92.02026-09-03

The pivot goes where you point it, exaggeration included, and G stops closing your polyline

• G no longer closes the command you are running. Pressing it while a polyline is open moves the rotation centre onto the point under the cursor and leaves the polyline open, which is the moment the pivot is actually needed. Before, G sent Escape to the tool and then did nothing: the drawing was lost and the pivot never moved. guide
• No pivot is taken behind your back while drawing. Every rotation used to re-pick a pivot under the cursor on its own at each drag; now the centre is the view centre unless you pressed G, so the two behaviours are no longer decided for you. guide
• The rotation centre is correct with vertical exaggeration on. Three separate faults, each measured rather than guessed (tools/orbit_pivot_exag_probe reproduces all of them without the GUI): the view target was handed to CadDll and to the cloud camera at true elevation while both engines draw stretched geometry, so the scene turned about a height that does not exist on screen - 33.78 m of drift at factor 3; the G marker and its axis arms were drawn at true elevation too, so the marker floated off the terrain; and the pick that chooses the point compared a screen ray against un-stretched cloud coordinates, which put the pivot 4.6 m from the cursor at 5 degrees of tilt, 19 m at 20 and 44 m at 40, while being exactly right at zenith - the reason it looked like G only worked in plan view. guide
• A dense grid cloud no longer freezes navigation for twenty seconds. The synchronous per-frame loader now has a ceiling counted in points, not tiles: a grid cell is cut on a fixed 16 m and holds a few thousand points over an aerial swath but tens of millions over a terrestrial scan, so 128 tiles in one UI tick could be an unbounded stall. The first tile of a frame is always admitted, so nothing can be starved.
• A grid cloud too dense for its own pyramid is now reported when the project opens, naming the layer, its tile size and its worst cell. Above roughly four million points in a single level-0 cell no runtime budget can help - the fix is to re-import, which writes an octree that subdivides on point count instead of metres - and that is said once, at the one moment an operator staring at a slow cloud can act on it.
• Roof pitches are always drawn in the reconstruction panel, with the squared outline added on top when there is one. Drawing only the outline hid the work: a pitch whose eave did not coincide exactly with the outline was not visible at all, and the operator saw an empty rectangle where two slopes existed.
• When the external stereo panel fails to take the GL context, the log now carries the Win32 error code from the failed wglMakeCurrent instead of only the fact that it failed - measured on a customer bench failing repeatedly a few seconds after a successful CadDll stereo activation, where nothing in the support package said whether the handle was stale or the context busy.

3.91.12026-09-03

The same release, with the unfinished Automation menu closed as it was meant to be

• The installer build now refuses to package while a ship gate is open, reading the build cache rather than the source: the Automation menu, the multi-view drawing menu and the developer licence bypass are checked by name, and the packaging stops with the gate named.

3.91.02026-09-03

The wire you draw is measured like the one the machine finds, and waiting no longer switches the drawing off

• A conductor grown from the operator's own two clicks is now checked against the same tests as one found automatically. The seed path measured a single 3D distance and called it by the names the automatic path uses for two different quantities - vertical scatter from the curve, and horizontal spread across it - and never actually applied the cross-section and fit tests its own header promised. A span was therefore rejected, or accepted, for arithmetic reasons rather than geometric ones.
• When a span is refused, the refusal says which test failed and by how much - "too thick for a conductor: 11.0 cm across, 10.0 cm allowed" - instead of just declining.
• The fit tolerance for the seed path is its own number, measured rather than borrowed: on 25 conductors drawn by hand, 24 are now re-followed where 20 were before. The automatic path keeps its own tolerance and is unchanged - the two paths measure different things and one number for both was the original defect.
• Supports under a span are found by one rule that is now a module of its own, so the same rule the product uses can be measured outside the application. The horizontal section a metre under the wire, the ordinary way supports reach the drawing, previously existed only inside the panel that drew it.
• Point section: a small window showing the last acquired point and the cloud seen edge-on, with a 3 cm sphere for scale, so the gap between the point just taken and the surface can be read rather than guessed. guide
• A command that takes a moment no longer blacks out the drawing. The light veil is now the default and the opaque cover is kept for opening a project, where there is nothing behind it worth seeing; before, the opaque cover was the default and every wait switched the application off.
• An application that is drawing but no longer receiving input now says so in the log. A frozen application and a live loop that has stopped receiving events are the same thing to an operator, and were the same thing in the log too, because the frame counter rises in both cases.
• Dragging a polyline vertex no longer shows the polyline twice. The host moves the vertex itself, and the CAD engine was adding its own preview displacement on top of the vertex already moved. guide
• The external stereo window's creation log starts fresh on each attempt instead of appending forever - one support log reached 5 MB in a minute and rotated away its own startup, which is the part that says what failed.
• On a machine whose driver owns the stereo panel, that panel is no longer destroyed one frame after it is created.
• The third workspace is now called Terrestrial Mapping: the three modules are named after how the data was acquired - aerial, mobile, terrestrial - instead of mixing platform and surveyed object. Projects created with the previous name reopen unchanged, with the same panels. guide

3.90.02026-09-02

The import measures the delivery, the stereo eye fills the monitor, and vertices become editable

• Stereo now fills the width of the monitor. With the zenith overview docked, a 1062x960 mono viewport against a 16:9 eye was using 62% of the width and leaving the sides black - the world that would have gone there was never drawn, so no placement rule could recover it. Each eye is now baked on a surface extended sideways to the target aspect at CONSTANT SCALE: the vertical model extent and the pixel height carry over from mono untouched, so the same metre stays the same number of pixels and nothing is stretched. guide
• Vertices dialog: the vertex numbers are drawn over the scene but under the windows, so they no longer sit on top of the very rows they point at, and Add and Remove now appear in a bubble beside the corner you right-click. Keys were the wrong instrument for this - they only fire while the properties dialog holds the keyboard, and while the operator is working the grips it does not. guide
• The octree LOD now accounts for the display Z exaggeration. Selection happens before the renderer stretches the scene, so without this it was resolving an image different from the one actually drawn.
• Nodes needed by a second view pane are no longer culled by the first pane's frustum, which is what a three-view layout requires: coverage decides what must SURVIVE a view, separately from how finely it is drawn.
• Conductor search takes account of the lines already on the drawing. Nothing previously stopped a second search from latching back onto the wire the first one had already traced.
• Mobile mapping: the vehicle mask is now a per-pixel silhouette instead of a box, and there is a command to edit it. Checked against real frames, the rectangle threw away world on one camera and left bodywork inside the cloud on another - a vehicle has an outline, and a box that contains it is not that outline.
• Default CAD layer names follow the application language. Worth knowing: two operators working in different languages therefore produce different layer names for the same kind of object.
• Which CAD layer each kind of extracted object is drawn on is now a setting, held per object category rather than per position in the list, so adding a new detector cannot silently re-point choices an operator has already made.
• Creating a georeferenced project no longer logs an error about an empty drawing. The hidden framing rectangle every such project is created with was being counted as a visible entity.
• The zenith overview is framed at the mono view's own planimetric scale, so the same metre is the same number of pixels in both panes and one drawing no longer appears at two sizes on one screen. guide
• Commands that take more than a moment report what they are doing and how far along they are, and the busy cover's dimming is no longer one fixed value for every kind of wait.

3.89.02026-09-01

The mark looks past the leaves for a real surface, and says how sure it is

• The confidence ring around the mark now reads the support behind that plane as a continuous colour - red through amber to green - instead of three fixed states chosen from a candidate index. Mono, the stereo overlay and stereo GL compute it from one shared function; they had drifted apart once already, a stale colour left over in the stereo eye cache while mono had already moved on. guide
• Cloud performance preset Quality now holds the point cloud at full resolution through pan, zoom and orbit instead of stepping it down during interaction and restoring it afterwards - the momentary drop the eye reads as the view emptying out. Fast and Balanced are unchanged: they still step down, which is what keeps navigation responsive on a weaker machine or a larger dataset. See Cloud performance in the manual for which preset fits which machine. guide
• Panning and zooming the CAD view no longer trigger a full drawing regeneration on their own: the native display list is stored in model coordinates, so a camera-only change was already correctly framed without rebuilding anything.
• The incremental cloud merge closed a feedback loop where a slow frame narrowed the point budget and narrowing the budget forced a full rebuild that stayed slow: a budget change now only triggers a rebuild when what is already on screen exceeds the new limit.
• Point-count estimate for an Area of Interest reads the octree catalogue directly instead of counting grid tiles, which an octree layer does not have: the estimate used to read zero for every area on every modern cloud, including areas that plainly contained data.
• Mobile mapping overlays (conductors, stations) now track the view during a pan drag instead of staying fixed while the image scrolls under them, and vertical exaggeration applies to the station overlay as it already did to conductors. Playback and the timeline now cover only the stretch of route inside the active Area, and redrawing the area returns the view to zenith so the redraw itself is visible.
• The command line status line only ever shows what is meant for the operator; it used to also catch periodic telemetry lines and overwrite a real message a second later. Arming AUTO-Z or Cloud-Z snap while the cloud is hidden is now refused with a message naming the control to use, instead of failing silently and leaving a digitized session at the wrong elevation.

3.88.02026-08-30

Ground photographs get oriented, and drawings are made in one place

• The photograph is paired with an elevation drawing side by side: every pixel of that drawing already knows where it is in space, so clicking it IS a 3D point - nothing has to be hunted for in the viewport
• Elevations, plans and sections are composed, generated and delivered from one panel. Creating a section and exporting a drawing used to be possible ONLY from the right-click menu of the tree: the main action of the command had no button anywhere
• One Generate replaces Preview and High resolution: both ran the same full-density query through the same rasteriser and differed only in output size, so offering them apart charged twice for nearly the same work
• Mobile mapping: the station strip is a player, and the view looks forward. The supplier's direction vector points at the rear - measured on this route as -0.9998 against the direction of travel - so standing at the vehicle used to look backwards
• Poles and supports are searched for under the cables instead of across the whole scene. Looking for what is tall, narrow and isolated is the right question from the air and the wrong one from a street
• Overlays no longer draw at true elevation on a stretched cloud: with 2x or 3x vertical exaggeration the cloud left the work box above and below while matching horizontally, because none of the seven overlay projections applied the stretch the renderer applies to the cloud
• The height of the work box no longer depends on luck: the fit used the 500,000-point sample taken to estimate orientation, which on 504 million points is 0.1% - a thin structure worth a few thousand points had four expected hits, so whether the box covered the piers of a bridge was decided by chance
• Active shutter stereo uses the graphics driver's own stereo where the driver offers it - the path a workstation card has always taken - and the application's own frame alternation where it does not. On a professional card the two eyes are produced by the driver, as they are for StereoCAD on the same machine
• The stereo support package now carries the emitter's own log as well: it collected the images, your comment and the application log, that is everything except the file that says whether the glasses ever received their firmware

3.87.02026-08-28

Active shutter glasses set themselves up, and the log says what happened

• The infrared emitter of the active shutter glasses never worked outside this office, and it was one missing file. The firmware the emitter needs belongs to its maker and cannot be shipped with the product, so no installation ever carried it: the emitter stayed in its bootloader for ever, whatever the customer tried - new emitters, new cables, another computer. It is now taken from a graphics driver already present on the machine and kept in a copy of its own. guide
• When no such driver is on the machine at all, the message says so and names the folder to copy nvstusb.sys into. It used to fail with a path nobody could act on. guide
• Every step the emitter goes through is now recorded in the application data folder. It used to be printed to a console that a windowed application does not have, so the one explanation that existed was visible on the customer screen, in the moment, and never reached anyone who could read it. guide
• The manual said View then Stereo in six places. The Stereo menu is at the top level, beside View, so each of those sent the reader hunting for a submenu that does not exist. Corrected for active shutter, the beam-splitter mirror, quad-buffer passive and the navigation view. guide
• Sheet Index is no longer only a diagram: it carries the list of linked drawings and a selector for the session, so it can be used without going through the scene tree first.
• Ortho Sheets and CAD Sheet sessions keep their name whatever language you work in. The name was translated at the moment the session was created and then frozen into the saved project, with no way to rename it afterwards.
• Changing the layer of a multiple selection moves every selected entity. Only the first one used to move, and nothing said the others had stayed behind.
• Opening the ortho-sheets panel no longer arms the AOI drawing by itself, and an update can no longer leave an old CAD engine beside the new executable.
• The log opens with the version, the build, the executable, the processor, the memory and the Windows build, collapses repeated lines into a count instead of filling the file, and records any frame that stalls together with how long it took - so what a customer can only describe as a freeze arrives as a measurement.

3.86.12026-08-27

Object snap is visible before the click, and wins over the cloud elevation

• Object snap was switched off during drawing in the georeferenced view - not by accident but on purpose, in four places, to stop CadDll pulling the drawing tip off the crosshair. The cure was worse than the illness: it also removed the snap marker, so the operator was drawing blind and could never land on an existing vertex. Three of those four suppressions sat on the hover, which is exactly where an osnap has to be seen.
• Geometric snap now takes priority over Cloud Z at the click, as it should. CadDll already implemented that rule; the application was disabling the snap just before asking CadDll to use it, so the cloud elevation won every time. Cloud snaps and AUTO-Z still win when no geometric point is found.
• The diagnostic line about the drawing cursor now carries the vertical exaggeration, the view axes, the pixels-per-metre scale and whether a navigation gesture is in progress - all measured at the same instant. Reading them off neighbouring lines produced wrong magnitudes and cost a full day of analysis on a customer report.

3.86.02026-08-27

Vertical exaggeration and the CAD cursor finally agree

• Vertical exaggeration and the cursor now agree. The display stretch was applied when a model point was drawn but never undone when a point was read back from the screen, so the two directions disagreed by (elevation - pivot) x (factor - 1). On an oblique view that showed as the drawing tip sitting away from the crosshair - always, for anyone working with the stretch on - and it silently affected object snap, picked points and hatch vertices as well. Both directions are symmetric now. guide
• Zooming in no longer freezes the cloud. Past a certain zoom the octree asked for more nodes than the cache could hold, and the cache evicted the very nodes the frame still needed - decoding and discarding a thousand of them per frame without ever converging. The resident set is now bounded by the cache, and the cache is large enough for the views the spacing law actually asks for.
• The diagnostic log stops eating itself. Its size cap ran only at startup, so a long session grew without limit and the truncation landed on the next launch - destroying exactly the history that had been asked for. The log now rotates: the previous window is kept in StereoCloud3D.log.1. It also writes far less, and keeps one file handle open instead of reopening it for every line.
• Vertical exaggeration is now in the Stereo menu, next to the other viewing aids, as well as in the Scene Tree. Same submenu, same shortcut (Ctrl+Shift+X). guide

3.85.02026-08-27

Multi-view drawing builds the whole building: internal lines, roof pitches and walls

• The BUILDING is the unit of work, not the single line. Every line you finish stays in the panel - visible in all five views, still attachable, still draggable - until you hand the whole building over in one gesture. Delivering them one at a time made them immutable exactly when they still needed correcting: the ridge height is adjusted AFTER the hips have been traced, not before. guide
• Internal lines: after the outline closes, the panel switches by itself to Internal line and to the zenith view, because ridges and hips are read in plan. Two clicks make one line and the next starts fresh - a ridge and a hip are not two stretches of the same polyline. The order is enforced: until the outline exists the other entities are disabled, because internal lines hang from it and take their height from it. guide
• Dragging a vertex now moves the WHOLE line; CTRL+drag moves that vertex alone. The shortcut sits on the exception, because bringing the outline down to the eaves and lifting the ridge are the normal operations and correcting one corner is the rare one. Whatever is attached follows, and the coincidences are collected BEFORE anything moves, so a building with many junctions cannot come apart halfway through. guide
• Attaching to a side of the outline now takes its HEIGHT as well as its plan. Being attached to a side means being on it; a vertex that follows its plan at another height is not attached, only nearby. Attaching no longer depends on the cloud either - the point is carried by the line you attach to, which matters most on the outline, where barely 28% of the pixels have a return under them. guide
• The outline is ALWAYS levelled when it closes, and to the eaves - the lowest edge of the roof - not to the median, which sits halfway up the pitch and is more than a metre out on a 30-degree roof ten metres wide. The height is measured on the zenith view only: from above every pixel is the first surface met coming down, that is to say the roof, while the oblique views also see facades. guide
• The criterion is not a fixed percentile but a JUMP: roof heights are dense from the ridge to the eaves and then drop by metres at once. The search starts at the median - certainly roof - and walks down while the sorted samples stay close; the first gap over half a metre is the roof edge, and below it nothing is looked at. If the cloud says nothing the outline is levelled anyway, to the lowest height clicked, and the message declares that the value came from the drawing. guide
• Generate the faces, in the panel where the lines were born: the roof pitches are the faces of the planar graph those lines form in plan, so two adjacent pitches share the same edge and no crack can open between them. Vertices are welded in plan, sides are split where a vertex falls on them, and edges that close nothing are removed and counted. A real pitch is planar, so the report gives the worst deviation from the plane and warns above ten centimetres. guide
• Walls down to the foot close the building at the measured ground height, in the same gesture. With an eave overhang there are two rings of faces and not one - the horizontal soffit from the roof edge in to the face of the wall, then the wall itself - because skipping the soffit would leave the building open all round its perimeter. guide
• The ground height is REQUIRED for the walls and for the copy at the foot, and the button says where you are: red when it is missing, orange while it waits for the click, green with the value once measured. A ground height that is not below the roof edge is refused with both numbers, because it means the click landed on another roof and drawing it anyway would produce an upside down box above the pitches. guide
• Roof and walls are created as two entities on two layers, so they can be switched off, locked and plotted separately, and they stay stitched where it matters: the foot of the roof and the top of the wall cut the same welded vertices. The wall layer is drawn behind, so the roof edge is no longer ringed by the grey of the eave soffit. guide
• Faces are drawn FILLED, with the light computed per face so that one pitch is told from another instead of reading as a single blot, and sorted by depth within a mesh so the front of the building hides its back. Filling is enabled per entity: the TIN of a terrain model is a polyface mesh too, and no existing drawing changes appearance. guide
• View -> Semi-transparent 3D faces fills the generated faces with a fine chequer so the point cloud shows through them - which is the only way to check that the roof you drew really sits on the cloud. It applies when a face enters the display list, so it takes effect on the next regeneration and on the next opening of the drawing. guide
• Generated surfaces reach the DXF as a real polyface mesh. Before, the exporter knew LINE, POLYLINE, ARC, POINT and TEXT, and a polyface mesh - which in the engine IS a polyline entity - came out as one broken line running through all its vertices: not a missing entity, but an unusable deliverable that looked exported. guide
• The true standard ACI palette is used for every colour index above 8. The application rewrites indices 1 to 255 so they cannot drift, but the table only defined up to 8 and invented the rest from a pseudo-random hue: 242, amaranth in any CAD, came out blue. This affected EVERY imported drawing, not only this tool. Expect layer colours above ACI 8 to change appearance - that is the correction, not a side effect. guide
• The orthophoto in the zenith view is frozen at the take, in a copy of its own, instead of borrowing the plan view texture: it no longer follows the plan view around while you draw. Its ground sampling distance is written beside the checkbox in cm/px, orange above 25, so framing the plan view tightly before the take is a decision with a number on it. Declared limit: the sharpness cannot exceed what the plan view had at that instant. guide
• The panel no longer loses its views. The commands take the space they need and the views keep their minimum, so a low window scrolls the commands instead of pushing the images below the edge; the text that changes sits in a fixed two-line area, so the image no longer changes scale at every click; and the generation report goes on its own line instead of running off the right edge, where every measurement written in it reached nobody. guide
• The whole panel speaks the interface language. The generation report, the reason the walls were not generated, the sample counts and the service line above the current view were Italian strings in the code and are now translated like everything else. guide
• Fixed: on a freshly imported project the georeferenced bounds box logged the same diagnostic two or three times per frame, and every line forced a synchronous disk write. That was the multi-megabyte log and the slowdown reported from the field. The diagnostics are now throttled per channel and only ERROR/WARN lines force a flush; the hidden cloud-bounds rectangle is no longer counted as drawable content, which is what triggered the repair pass on every repaint.
• Fixed: the default layer names of the multi-view entities still followed the old five-entity taxonomy, so internal lines landed on a COLMO layer and chimneys on FALDE. New defaults are TETTO, LINEE, COMIGNOLI and GENERICO; settings that still carry the old defaults are migrated, and names you chose yourself are left alone. guide

3.81.02026-08-25

Overhead conductors straight from the cloud, and a license key you type once

• Extract overhead conductors (Cloud menu, Ctrl+Alt+W) finds the overhead wires inside a Cloud AOI and proposes each span as a 3D polyline that follows the real sag, not a straight line between two poles. Nothing enters the drawing until you press Add to drawing. guide
• What separates a wire from a gutter is not height and not thinness: it is the empty space around it. The search looks for that, then follows the wire outward a couple of metres at a time, stepping only where the points continue the curve already fitted - which is what stops it drifting onto a wall running alongside. guide
• Every span is reported with its length, points per metre, height above the ground under it, sag, worst hole and measured thickness. The thickness is the tool checking its own work: a real conductor comes back at 2-6 cm, and anything much fatter was never a wire. Proposals are drawn in magenta over the mono viewport while the panel is open. guide
• The AOI is required and the search runs at full resolution, because how densely a wire is sampled is exactly what identifies it. An AOI over 60 million points is reported and refused rather than quietly trimmed: half an area analysed as if it were all of it would report no conductors about ground nobody looked at. guide
• The license key is typed once, not at every launch: after the server accepts a key it is remembered, encrypted for the Windows account, in %APPDATA%\StereoCloud3D\license_key.dat. guide
• The remembered key only fills the field in. The Activation window still opens at every launch and the key is still validated online every time, so an expired, revoked or reassigned key fails exactly as a typed one would. The window stays on screen on purpose: the key about to be used is always visible, which is what matters on a computer that has been handed on or reinstalled. guide
• The field takes the caret when the window opens and accepts Enter, so a normal launch is one keypress. To use a different license, type over the text. Deactivate this device also forgets the stored key. guide

3.80.02026-08-25

Multi-view 3D drawing: restitution in 3D without stereo hardware

• The outline is drawn ONCE and lives once in 3D: the other four views show it by projection, where you check it and correct it. This is where the information is: a zenith view of a flat roof has sub-pixel parallax, so it gives the plan precisely and knows nothing about the height, while the obliques know the height and are ambiguous in plan. guide
• Dragging a vertex does the right thing for the view you drag in: in the zenith view it moves in plan, in an oblique view it moves in height. Left adds a vertex, right closes the outline, Enter finishes it open, Backspace undoes the last vertex; once finished, the same buttons insert, drag and delete vertices. guide
• Locked height keeps one height for the whole outline, taken from the median of the cloud INSIDE it when you close it - inside, every return is roof, while along the border half of them are the ground beyond the eaves and would drag the median down. Fit height to cloud searches, with the plan fixed, the height that best agrees with every view. guide
• Sides snap to the two dominant perpendicular directions of the building, within a tolerance you set. Measured on this building stock, three quarters of the sides lie on those two directions; the remaining fifth is genuinely oblique and is left alone. guide
• Check on cloud colours each vertex by how the views agree and reports the residual. Where a vertex has no returns under it the panel says so, instead of inventing an agreement value. guide
• Ground height takes the terrain elevation where you click - an oblique view shows the ground beside the building better than the zenith - and reports the building height. Copy at the foot repeats the outline at ground level, with the elevation from the cloud under EACH vertex (DTM first, then ground-classified points), an optional level foot and an eave overhang. guide
• The panel does not own CAD entities: it proposes vertices, and the polyline is created by the CAD engine on the layer for the entity kind (TETTO, COLMO, FALDE, COMIGNOLI, GENERICO, PIEDE). Radius, tolerances, layer names and the option toggles survive closing the panel; vertices, views and measured height do not, because they belong to one building. guide
• Registered as a managed shortcut: Ctrl+Alt+M, Draw menu, and the typed commands MULTIVIEW / MVD all call the same handler. Rebind it in CAD -> Keyboard Shortcuts like any other command. guide

3.71.02026-08-18

ECW imagery, Scene Tree imagery and CAD current-layer defaults

• ECW orthophotos can be imported like any other raster. Install QGIS Long Term (LTR) once (free, Windows, default folder). You never open QGIS afterwards: StereoCloud3D uses it in the background to convert the .ecw into a GeoTIFF inside the project. If QGIS is missing, import shows the same procedure and a Download QGIS button. guide
• Imagery layers are listed in the Scene Tree. Right-click Imagery (or a layer) and choose Add imagery to open Project Manager on the Imagery tab. File menu Import imagery (Ctrl+Shift+Alt+U) starts the same import dialog. guide
• The hidden SC3D_CLOUD_BOUNDS layer (cloud limits used only for framing) is never left as the current drawing layer. If layer 0 does not exist, it is created white (ACI 7) with default settings and made current, so new entities are not drawn on an invisible bounds outline. guide
• When imagery is present and visible, the Zenith Overview shows it as soon as tiles are ready. Previously the CAD overlay stayed opaque until the first display regen (pan/zoom). guide

3.70.02026-08-17

Active shutter glasses with an infrared emitter, and a faster viewport while drawing

• Active shutter glasses with an infrared emitter work again. Current graphics drivers no longer include infrared-emitter support, so StereoCloud3D now does the work itself: it loads the emitter's firmware, drives it over USB and alternates the two eyes on the 120 Hz panel from a thread of its own. If you own the glasses, you can put them back to work. guide
• The mode needs preparing once on each computer, and the manual walks through it: a USB driver for the emitter, and a first launch as Administrator. The application detects each step that is missing and says what to do about it, on screen. guide
• Every stereo desk layout is now listed in the Stereo menu, including the ones this computer cannot run. They are greyed out and say what is missing - a second or third monitor, an emitter - instead of disappearing, so it is clear which setups the application supports rather than which ones happen to be plugged in today. guide
• Drawing is more responsive on every stereo layout and in mono. The point cloud was being rebuilt on frames where nothing about it had changed; on a large cloud that cost a sixth of a second each time, and it happened while the rubber band followed the pointer. Kensington trackball owners get a second improvement: ball movement was partly read as scroll wheel, which triggered zoom work on every move.

3.62.02026-07-31

Maintenance release

• Maintenance release. Every 3.61.0 feature is unchanged; this build corrects what the application tells the licensing server about itself.
• The application now reports its real version number when it activates and while it runs. Until this build every copy identified itself as "1.0.0", whatever it actually was, so the version column beside each activated computer could not tell a 3.50 from a 3.60 and support had no way to know which build a customer was running. Activations recorded before this release keep the old placeholder: only new ones carry the true version. guide

3.61.02026-07-31

Maintenance release

• Maintenance release. Corrects a defect reported after 3.60.0; all 3.60.0 features are unchanged.

3.60.02026-07-31

Cloud classification, building extraction, ortho sheets and final drawings

• Cloud classification: Cloud -> Classification writes standard ASPRS classes into the octree in place - ground, buildings, roads, water, masts and poles, overhead wires, vegetation and noise - either one pass at a time in the recommended order, or in a single run with a terrain preset. Nothing is deleted: noise is flagged and hidden from Cloud Visualization. A backup taken before the run makes the whole thing reversible. guide
• Surface models: a whole-chain run also writes dtm.tif, dsm.tif and ndsm.tif next to the layer, georeferenced Float32 at 0.5 m cells, filed under Products -> Surface models in the Scene Tree. Showing the DTM adopts it as the session terrain, so GND-Z samples it without waiting for a separate CSF run. The nDSM - height above ground - is the layer most operators digitize on. guide
• Assisted building extraction: Automation -> Building automation reads the classified cloud, traces the outline of every building in walk order, labels each edge by the evidence that produced it, and squares the result - inferring the corners a survey flown from above never saw, rather than leaving a staircase of scan noise. guide
• Building review: walk the buildings one at a time - frame, correct a corner, level the elevations, square, confirm. Each confirmed building is drawn as three polylines on three layers of its own: at ground level (the wall foot, measured on the facades where they were captured), at the eaves, and at roof level. The eaves elevation comes from the cloud inside the outline, or from what you digitized in stereo. guide
• Ortho Sheets: fit a work box to the cloud, aligned to the building rather than to north, and take products off its faces - a plan from the top, four elevations from the sides, and sections on cut planes you place. Each product is rasterised from the points themselves, so an orthophoto exists even when nobody ever took a photograph. Preview at screen resolution, then generate the definitive raster at the print scale and DPI you are going to deliver. guide
• CAD Sheets: the final drawing, on paper. Choose the format and orientation, set the scale 1:N and the export DPI, import the definitive orthophoto and place it, crop it with grips, adjust it, draw CAD on top with the normal cursor, then export the sheet to DXF - or to DWG where the converter is installed. The sheet is a drawing of its own, saved with the project and filed under Products. guide
• Navigation view: a stereo view for looking and flying, not for measuring. It runs its own depth law, so you can push the fusion where a wide oblique becomes comfortable to read without disturbing the calibration the measuring view depends on. Ctrl+Shift+N, or the NAV command. guide
• Fusion comfort on deep views: on a view whose depth range would exceed what the eyes can fuse, the stereo separation is capped and the menu says by how much, instead of handing you a doubled image. guide
• Products in the Scene Tree: everything a job produces - surface models, buildings, spot heights, flat surfaces, ortho products, sheets, exports and reports - is filed under Products with the run that made it, its parameters and its files. Right-click to show a raster in the Zenith Overview, open it in the image viewer, or reveal its files in Explorer. guide
• Imagery: ECW rasters are accepted where the ERDAS ECW plugin is installed; without it the import stops with a message naming the missing driver rather than failing obscurely. guide

3.50.12026-07-27

Stereo selection/grips, Welcome thumbnails and CAD editing aids

• Stereo selection and grips: selected entities stay visible in external SBS with correct parallax; CadWinDrawEye bake keeps selection (solid select color instead of GL stipple) and draws grips per eye. Customize selection and grip colours in Inspector → CAD selection (mono and stereo share the same palette). guide
• Grip vertex editing: in inspection mode, select a polyline/line and drag grips like StereoCAD (green start grip, blue others). Vertex numbers are drawn on mono and listed in Entity Properties / Selected Entity for precise XYZ edits. guide
• Welcome recent projects: wider list with a readable zenith thumbnail captured when the project opens and the view is fully drawn. guide
• Optional edge auto-pan while drawing: with a draw/modify tool active, if the pointer is within ~100 px of the CAD viewport edge the view pans so the world under the cursor moves to the centre (OS pointer warps with it). Toggle from Snap menu / Object Snap toolbar / shortcut. guide
• Per-toolbar UI scale: each floating toolbar caption has a scale button (cycles 25%…250% in 25% steps) in addition to the global UI scale in Settings. guide
• AUTO-Z / Cloud snap robustness: improved surface sampling under the cursor on oblique surfaces and at tight zoom (ray/neighbourhood surface sampler). guide
• New cloud imports default to octree_builder (layers written with octree: true). Legacy grid projects remain unchanged. guide
• Fixes: entity no longer vanishes after RBD finish (mono paint + stereo AutoSelect disparity); Overview open/close no longer misaligns cloud vs CAD; Overview orthophoto tile sizing and oblique cursor follow; Layer Manager colour swatch applies to the layer.

3.50.02026-07-27

Stereo selection/grips, Welcome thumbnails and CAD editing aids

• Stereo selection and grips: selected entities stay visible in external SBS with correct parallax; CadWinDrawEye bake keeps selection (solid select color instead of GL stipple) and draws grips per eye. Customize selection and grip colours in Inspector → CAD selection (mono and stereo share the same palette). guide
• Grip vertex editing: in inspection mode, select a polyline/line and drag grips like StereoCAD (green start grip, blue others). Vertex numbers are drawn on mono and listed in Entity Properties / Selected Entity for precise XYZ edits. guide
• Welcome recent projects: wider list with a readable zenith thumbnail captured when the project opens and the view is fully drawn. guide
• Optional edge auto-pan while drawing: with a draw/modify tool active, if the pointer is within ~100 px of the CAD viewport edge the view pans so the world under the cursor moves to the centre (OS pointer warps with it). Toggle from Snap menu / Object Snap toolbar / shortcut. guide
• Per-toolbar UI scale: each floating toolbar caption has a scale button (cycles 25%…250% in 25% steps) in addition to the global UI scale in Settings. guide
• AUTO-Z / Cloud snap robustness: improved surface sampling under the cursor on oblique surfaces and at tight zoom (ray/neighbourhood surface sampler). guide
• New cloud imports default to octree_builder (layers written with octree: true). Legacy grid projects remain unchanged. guide
• Fixes: entity no longer vanishes after RBD finish (mono paint + stereo AutoSelect disparity); Overview open/close no longer misaligns cloud vs CAD; Overview orthophoto tile sizing and oblique cursor follow; Layer Manager colour swatch applies to the layer.

3.26.02026-07-21

Octree cloud engine, Z exaggeration and RANSAC cloud snap

• New octree cloud engine (Potree-style modifiable nested octree): out-of-core streaming that scales to hundreds of millions of points. Nodes stream from disk on demand and the view densifies progressively as you zoom, with a per-frame decode cap so panning/zooming stays responsive. Opt-in per project (cloud layer "octree" flag in the manifest); the classic grid pyramid remains the default fallback until a dataset is converted. The converter tool octree_builder.exe ships next to the app and in the installer (alongside tileindex_builder).
• Point extraction (Cloud snap, region and AOI queries) is served directly by the octree backend when active, so digitizing and algorithms use the same data the renderer streams.
• Display-only vertical Z exaggeration (1x-8x, pivot-based) to enhance 3D depth perception without altering stored coordinates. Cycle it with the Application shortcut or set it in the Scene Tree; especially useful in the zenith AOI overview.
• AUTO-Z / Cloud snap reworked: instead of grabbing the frontmost point, it fits a local RANSAC plane on the cloud points whose projection is nearest the cursor, so it locks onto the surface directly under the cursor (a tower a metre to the side no longer pulls the elevation up). The neighbourhood size is user-tunable (5-90) via Inspector -> AUTO-Z / Cloud snap.
• Fix: the cloud no longer disappears when zooming in very close. The orthographic camera standoff now always brackets the whole dataset, so tall structures stay inside the near/far clip at any zoom.
• UI: taller Display setup, Cloud Visualization, Cloud Cleanup, Spot Height, View polygon cleanup, Project Manager and Keyboard Shortcuts dialogs, with minimum heights enforced and previously saved too-small layouts auto-grown - controls are no longer hidden behind a scrollbar.
• Robustness: opening a project no longer fails silently. Manifest parse errors are reported ([project] ERROR step=parse_manifest ...) and an orphaned open-busy state is recovered so subsequent Open clicks always work.

3.25.22026-07-20

Broader UI multilanguage (panels and dialogs)

• i18n catalogs expanded (~700 keys, EN/IT/FR/DE/ES) for panels, dialogs, Welcome, License, Display setup wizard, Project Manager, Help AI, Job Report, toolbars, Keyboard Shortcuts labels, and common buttons. guide
• Wired translations into major panels and dialogs (Welcome, Project Manager, Display setup, shortcuts dialog, layer/toolbars chrome, Help AI, License gate, and additional Inspector/modal titles). Some long dialog body text may still fall back to English where not yet keyed. guide
• Policy: new user-visible UI strings must use SC3D_TR + five-language catalog (project rule ui-i18n-always). guide

3.25.12026-07-20

UI languages and stereo entity-vertex depth fix

• UI languages: English, Italian, French, German, Spanish. Auto follows the Windows UI language; override in Inspector → Interface → Language (applies immediately to menus and Scene Tree). guide
• Menus (File…Help, Snap, Stereo, Cloud, …) and Scene Tree (including context menus) use the active language catalog. CAD Draw/Modify command labels remain English. guide
• Fix: entity vertex markers in stereo — restore golden depth law (ModelToWin + CadStereoCursorViewDepthRel), honour swapEyes like the stereo cursor, and scale parallax to the eye destination. Removes the 3.25.0 CadSetStereoGeometry overlay path that ignored Swap left/right and misplaced markers.

3.25.02026-07-20

Desktop chrome and Scene Tree with context menus

• New desktop chrome: left CAD Tools dock, docked Scene Tree, optional Zenith Overview, central mono viewport, and Object Snap dock on the right — with resizable splitters and persisted widths. guide
• Scene Tree (scene graph): hierarchical Project / CAD / Clouds / AOIs / Imagery / DTM with per-node visibility. Opens fully expanded when a project is loaded. guide
• Scene Tree context menus: color mode and cloud actions; AOI define/redraw, limit streaming to AOI, and Algorithms (Cleanup / Voxel / SOR) gated by point budget with downsample when needed. guide
• AOI-centric workflow: resident display vs streaming clip, capability summary in the tree selection footer, and algorithm jobs that attach results under the AOI. guide

3.24.02026-07-19

Ground DTM (CSF), GND-Z and Overview DTM layer

• GND-Z — ground-biased elevation modifier for AUTO-Z (Snap / Cloud menus and Object Snap toolbar). Near zenith prefers ASPRS ground classes 2/8/11 when present, else lowest Z in ~1 m XY; facades keep RANSAC. Requires AUTO-Z ON (Ctrl+Shift+Alt+G). guide
• Build ground DTM (CSF): Cloth Simulation Filter on Cloud AOI (preferred) or current view extents (Cloud menu / Ctrl+Alt+B). Progress modal with cancel; session height raster used by GND-Z when covered. guide
• Zenith Overview DTM layer: optional hillshade underlay between imagery and CAD (checkbox + opacity in the Overview header; Ctrl+Alt+D). Opens Overview after a successful DTM build when the layer is enabled. guide
• Fix: floating ImGui dialogs (Cloud AOI, Cleanup, …) remain draggable when they overlap the mono VTK viewport — CAD no longer steals the drag.
• Fix: toggling Zenith Overview keeps cloud and CAD aligned after host aspect change (MMU resync before GeorefMonoHost). guide

3.23.02026-07-17

Docked Zenith Overview, live entities and trackball action

• Zenith Overview is now docked on the left of the mono viewport with a draggable vertical splitter (View -> Zenith Overview, Ctrl+Shift+O). The split ratio is persisted in settings. guide
• Zenith Overview keeps a fixed centre crosshair while the imagery and CAD map follow the live mono cursor; zoom matches the mono view. Higher-resolution CAD bake. guide
• Zenith Overview reflects entities drawn live in the mono CAD: the overview's separate plan drawing is refreshed from a snapshot of the live drawing when the entity count changes, without touching the mono view. guide
• New Kensington trackball button action: Toggle entity vertices (Inspector -> Trackball settings -> Button assignments), set as the default on the bottom-right button.
• Redesigned bottom status bar with a cleaner cursor coordinate, layer, colour, lineweight and active-tool readout.
• Flat Surface automation tool (work in progress) under the Automation menu: identify a flat cloud surface and commit closed polylines on the current layer.
• Fix: File -> Close followed by Open no longer crashes (correct MMU/CAD teardown order before the drawing is released).

3.22.02026-07-16

Cloud classification viz, Zenith Overview and contact links

• Cloud Visualization dialog (Cloud -> Cloud Visualization..., Ctrl+Shift+L): choose point color mode including Classification, adjust point size, and manage related display options outside the Inspector. guide
• Classification color mode with ASPRS legend and per-class show/hide filters so you can isolate ground, buildings, vegetation and other LAS classes in the streamed cloud. guide
• Zenith Overview (View -> Zenith Overview, Ctrl+Shift+O): resizable WCS plan panel with CAD and preferred orthophoto underlay, framed on the mono view extent, live cursor crosshair, and continued imagery streaming while mono stays oblique. guide
• Overview imagery fills the square plan extent (same half-span as mono View.Rect) with CAD bake/scroll aligned to the WCS overview; cursor follows WinToModel on zenith and the idle elevation cache in oblique. guide
• Website Contact section: Phone, WhatsApp and Email actions for +39 338 280 6914 alongside the existing About contact details.

3.21.02026-07-16

Cloud AOI, compose, elevation models, CAD stereo live

• Cloud AOI: draw an XY rectangle to limit cloud streaming to an area of interest. Corners drape onto the cloud surface (plan XY to nearest point Z), the overlay follows MainMono pan, and the AOI is stored in the project manifest. guide
• Dataset Compose: compose a project from an existing project, a cloud folder, an imagery folder, or a CAD drawing, with a progress modal during conversion/import (File -> Compose from project...). guide
• Imagery toolbar: toggle underlay visibility and opacity (Ctrl+Shift+Alt+I / View -> Toolbars -> Imagery). guide
• Cloud on mono only: hide the point cloud on the mono UI monitor while keeping it visible in stereo (Ctrl+Alt+C). guide
• Two object-point elevation models: Constant elevation (world Z fixed while moving planimetrically) vs Floating-mark (fixed view depth along the camera ray). English menu entries, persisted in settings, documented with an illustration in the User Guide. guide
• Grip edit linked to the object point: selecting a vertex grip syncs the object point; moving the object point (including Z via Shift+wheel) updates the entity live; left-click confirms; the OS cursor warps to the projected grip after a Z change.
• Entity vertices overlay also draws in stereo with anamorphic compensation (View -> Entity vertices).
• Entity properties: right-click on an entity opens the properties panel (coordinates update during live grip edit).
• Stereo CAD quality: line-weight / depth quality controls under Stereo adjustments. guide
• Stereo CAD stays live during orbit: per-eye CAD bake continues while rotating so entities track the cloud in realtime (not only after orbit ends). guide
• Stereo coordinatograph: true ImGui font with correct decimal points (no stick-font segments); drawn only on the stereo presentation path. guide
• Swap Left/Right menu label no longer appends (pseudoscopy). guide
• Display / stereo layout persistence: startup restores the last layout (e.g. the beam-splitter mirror layout no longer resets to SBS every launch). guide
• Floating CAD toolbar positions persist correctly across project reopen (draw / modify no longer stack on top of each other). guide
• Floating toolbar collapse (-/+): collapse control kept; collapsed toolbars always show the toolbar title so they stay identifiable and can be expanded again. guide
• Status bar: taller chrome and larger font for the coordinatograph / cursor readout.
• Help -> What's New (Changelog): full notes for the last 5 releases, newest first, with Open in User Guide links when a topic is documented.
• Menu reorganization: View -> Toolbars submenu; Automation menu removed; Cloud Cleanup, View Polygon Cleanup and Cloud AOI under Cloud; Spot Height Plan and Cloud Batch Converter under Tools; Property bars renamed. guide
• English UI labels for Unlock input, Restore view and alignment, AUTO-Z - automatic elevation (idle), Set cursor elevation from cloud, and Lock Z elevation (anchor). guide
• Cloud Batch Converter default shortcut changed to Ctrl+Shift+Alt+N (Ctrl+Shift+Alt+V reserved for Active shutter (IR emitter)). guide
• Welcome / Open project: project open filter accepts the expected StereoCloud3D project extension so Open works like Recent. guide
• User Guide updated (docs/manual and website/manual): Cloud AOI, compose, elevation models, menus/toolbars, imagery toolbar, cloud-on-mono, shortcuts and related sections. guide
• Client action: install over 3.20.x. Prefer Constant elevation if Floating-mark object-point motion felt disorienting in oblique views. Review Keyboard Shortcuts if custom bindings conflict with new commands. guide
• Deploy: installer to /var/www/private/, website zip to /var/www/home/, license-server rebuild with SC3D_RELEASE_VERSION=3.21.0.

3.20.12026-07-15

Branding assets in installer

• Regenerated pictures/icon.ico from the current icon.png as a multi-size ICO so Windows shortcuts and the installer use the new branding.
• Installer now copies {app}\pictures\icon.png and {app}\pictures\splash.png into the install folder so the Welcome splash and related UI can load the current artwork. guide
• POST_BUILD for the app copies branding PNGs next to StereoCloud3D.exe in the dev Release folder (same assets as the installer).
• Website assets/splash.png synced to pictures/splash.png so the public site matches the in-app splash.
• Deploy: rebuild installer, upload to /var/www/private/, refresh website zip, and bump the license-server release to 3.20.1.

3.20.02026-07-15

Cursor Z, CAD backups, project stats, input recovery

• Z-key remap: Z = one-shot snap of cursor elevation to the cloud under the cursor; Shift+Z = Z Anchor lock (fixed drawing elevation); Ctrl+Shift+Z = AUTO-Z idle toggle. Object Snap toolbar and Cloud menu use the same commands. guide
• Floating-mark cursor: status bar, stereo coordinatograph and stereo reticle share one 3D point (mmuObjectViewDepth). Manual Z is preserved when AUTO-Z is off. guide
• RANSAC digitizing Z: SampleCloudPlaneLocalAtViewportPx (k-nearest 15 samples intersected with the view ray) for AUTO-Z and Cloud Z drawing - stable elevation on uneven cloud surfaces. guide
• CAD backups (Level 2): CreateCadDrawingBackup on explicit Save / Save As writes cad/backups/drawing_YYYYMMDD-HHMMSS.vec and prunes to the 10 newest versions. File -> Restore from backup... (Ctrl+Alt+R) lists autosave plus versioned backups. guide
• Project Manager -> Properties tab: cloud layers / total points / tiles, imagery, CAD size and entity count, backup count, and disk usage (cached about every 3 s). guide
• Project folder tree (ProjectTreePanel, Ctrl+Shift+P): browse project files in-app with contextual import actions. guide
• Input recovery: RecoverViewportInput (Ctrl+Shift+R / View -> Unlock input) clears stuck pan/orbit/modal state. RecoverViewportIntegration (View -> Restore view and alignment) recovers input then restores zenith WCS and re-syncs cloud, CAD and camera. Focus-lost auto-ends stuck pan/orbit. Logs use [input-recover]. guide
• Stereo coordinatograph: removed the trackball speed V overlay from the per-eye readout so the stereo status bar stays cleaner. guide
• AI help: the server prompt answers in the same language as the user's question. guide
• User Guide updated (docs/manual and website/manual): section 6.5 CAD backups, section 7 Properties tab, section 8 menus/panels, sections 9.3-9.4 Z remap and RANSAC, section 9.7 input recovery, section 12.4 coordinatograph, section 18 shortcuts, section 24 AI language, section 25 troubleshooting. guide
• Client action: install over the previous build. If an older settings.json still maps bare Z to Z Anchor, open Keyboard Shortcuts and Reset all to defaults. guide
• Deploy: installer to /var/www/private/, website zip to /var/www/home/, license-server rebuild with SC3D_RELEASE_VERSION=3.20.0.

3.19.02026-07-14

Beam-splitter mirror stability, UI toolbars, UI scale

• Beam-splitter mirror + Auto-Z: stop forcing a full cloud left/right re-bake every idle frame when Auto-Z is locked and the cursor is stationary - that flickered the beam-splitter mirror stereo pair. Re-bake only when eye textures are missing. guide
• SBS vs beam-splitter mirror guard: BlockMainWindowIndependentFlipGuard keeps the driver's independent-flip shrink on mono/SBS only; beam-splitter mirror, quad-buffer and native stereo paths are exempt so hardware stereo is not dropped while drawing. guide
• Floating toolbars: Object Snap, Display, CAD Draw / Modify / Circle / Arc / Dimension / Flow and the Custom toolbar share one floating frame (consistent drag and layout persistence). guide
• UI scale: Settings -> Interface slider from 0.75x to 2.0x scales fonts and ImGui metrics for high-DPI displays. guide
• Stereo cursor shapes: GL per-eye cursor mark variants in settings; anamorphic compensation on Side-by-Side / Top-Bottom is unchanged. guide
• Window title shows StereoCloud3D v<version> via ApplicationDisplayTitle().
• Automation menu streamlined: experimental assisted-drawing, building-reconstruction and cartographic-layout workflows were archived and removed. The menu keeps Spot Height Plan, Cloud Cleanup (no longer labelled Experimental), and View Polygon Cloud Cleanup. guide
• Support: Help -> Send stereo diagnostics to support (Ctrl+Shift+Alt+D) uploads the stereo flicker diagnostic trace for support analysis. guide
• Client action: install over 3.18.x. Beam-splitter mirror users should verify Auto-Z idle stability; high-DPI users can tune UI scale in Settings. guide

3.18.32026-07-14

Smoother wheel zoom

• Root cause: during a wheel-zoom gesture the cloud streaming manager was forced into synchronous tile I/O (setForceSyncTileIo). A zoom step that needed new tiles blocked the frame while reloading them (traces showed cloud-diag render_done up to ~946 ms with cloudReady=0), so zoom felt jerky or stalled. guide
• Fix (app glue only): in RegenerateCloudLayerIfDirty, wheel-zoom-only interactions no longer force synchronous tile I/O - async streaming fills detail while the already resident coarse LOD covers the gesture (brief transient pop-in while zooming). Orbit / pan / nav-preview keep synchronous I/O because holes there are more disruptive. Cloud shear, per-eye bake, fusion and cursor paths are untouched. guide
• Client action: install over 3.18.2. Wheel zoom on dense clouds stays responsive. guide