Table of Contents:

MineSight 3D
MineSight Atlas
MineSight Basis
HxM Blast
MineSight Data Analyst
MineSight Economic Planner
MineSight Planner
MineSight Schedule Optimizer
MineSight Strategic Planner
MineSight Torque
QAQC
MineSight Tools
Geologic
MineSight Stope Optimizer

If moving from a version prior to MineSight 3D 9.20, it is recommended that you perform a clean
install into a new folder instead of upgrading the existing folder.

MineSight 3D (MS3D)
 Cutoff Items

Resizing the cutoff item dialog with a very large number of cut-offs may cause instability (MS3D-
7382, CRDB-59, SCP-6402)

 Interactive Planner

Formal 2D cuts are not visible in interactive planner, only 3D cuts (MS3D-8692, CRDB-2225,
SCP-36061)

 Model Views

Starting in v11.50, model labels will display behind filled blocks in 2D surface/slab views (MS3D-
13658)

 Pit Expansion

Clipping with limiting surface to work correctly, the surface must fully overlap in projection with the
pit/dump (MS3D-9154)
Reserves calculation with Mid-bench lines option will not be correct if the expanding step size is
different from the PCF's bench height. Use Pit Solids option instead in such cases (MS3D-9150)
Switching to a parameter set saved under different project settings may not correctly restore slot
lead lines (MS3D-9381)
Using Pit Expansion on a copied MSR file can wipe the Pit Expansion settings on the original
MSR file (MS3D-9159)

Copyright© 2012 Mintec, inc. All Rights Reserved | MineSight® is a registered trademark of Mintec, Inc.
June 6, 2017
 When making an inwards pit expansion with multiple pits, only the pits originating on the start
level (top for downwards and bottom for inward) are used for export surface and solids and for
calculating reserves. (MS3D-9149)

 Vertical Opening Tool

Vertical Opening Tool can fail to create start/end sections (MS3D-2676)

MineSight Data ASCII Reformat Tool (MSDART)

 General

The value -1 is treated literally in transformations/calculations, not as unknown (MSDART-270)

MineSight Database Manager (MSDBM)

 General

Startup time takes longer when connecting to a SQL Server instance with many databases
(MSDBM-640)

MineSight Atlas (MSAtlas)

The Activity Gantt grid can become one row out of step with the Activity Grid. (ATLS-1719)
Watermarks on reports do not save (ATLS-2564)
With certain styling configurations where the geometry should not be visible, having ‘Hard Edges’
checked can cause the hard edge lines to appear. Workaround: turn off hard edges (ATLS-2196)
Reserve Logic configurations with six discrete items cannot be used. (ATLS-2693)
Text alignment does not have an effect on the position of text in the viewer. (ATLS-3404)
Must select 'System.String' for a Chart's data series filter for some types. (ATLS-4671)
Python calculation runs after toggling off the “Use Calculation” checkbox. Workaround: delete
unwanted calculations (ATLS-7538)
An exception may be encountered if the window is resized (ATLS-7673)
If the Windows font size is greater than 100% some layout items may not appear correctly (ATLS-
7663)
Setting "Treat Missing Grades as Zero" on the reserve logic to false does not work (ATLS-7632)
Conditional Formatting overridden by Format cells (ATLS-9971)
Letters with accents are not support and may cause issues opening projects (ATLS-10071)

MineSight Basis (MSBasis)

M624V1, M624IK, M624MIK: When binning (comparing) grades against cutoff values rounding
errors the values exactly at cutoff value may be placed to a lower bin. As a workaround, to avoid
precision issues, specify cutoffs with a small tolerance subtracted: use tolerance less than item’s
precision, e.g. 2.999 instead of 3.0 for items with precision 0.01. Some of calculations affected:
binning by cutoffs in indicator kriging (m624ik, m624mik) (MSBASIS-579)
block dilution calculation (m624v1)

Copyright© 2011 Mintec, inc. All Rights Reserved | MineSight® is a registered trademark of Mintec, Inc.
June 6, 2017
 If MSTorque attributes contain special characters (e.g., underscores), during interpolation an
unnecessary warning may come up about a ‘NEWTTO Translation Error’. You should ignore it.
Interpolation programs (m620v1/v2, m621v1, m624v1/ik/mik) do not work with Torque Sample
Attribute names containing only numbers (MSBASIS-1580).
pmik01.dat allows you to enter MIK model items to store MIK probability without entered the
corresponding model items to store MIK grade (m624mik requires you to enter both items
pairwise) (MSBASIS-1552).

An unexpected termination (i.e., with a Ctrl-C) of an MSBasis program with MSTorque access
during reading or writing of composite data may cause a loss of the “writeable” flag setting for
composite attributes and may lock the database for writing. You will have to edit a composite set
and re-select writeable attributes as well as unlock the database from MSTorque interface
(MSBASIS-995).
PINTRP.DAT, PINTRPQ.DAT, P624DB.DAT – These procedures cannot copy a newly created
debug ellipsoid msr file to \_msresources folder, while an old object is opened in MS3D. Close
the object and copy the msr manuall (MSBASIS-1188).
PINTRPQ.DAT – Dynamic Unfolding options “to re-run Fast Marching” and “to create a new FMR
file from RSI and new parameters” using MSTorque access with SQL authentication, do not work
(MSBASIS-1388).
PMIK01.DAT – Allows you to enter MIK model items to store MIK probability without entering
corresponding Model Items to store MIK grade (m624mik requires you to enter both items
pairwise).
Due to the addition of unfolding options for interpolation in MSBasis, when loading pre-v.14.00
procedure setups that have enabled relative elevation options in later versions of MSBasis - the
relative elevation option will need to be re-enabled (MSBASIS-1499).

HxM Blast (HxMBlast)

Backstage Save will generate an exception if another Blast Project instance is saving to the same
project that has SQLite based MSPD2 and database MSTorque connection (BLAST-891).
Blast user properties with trailing spaces can cause issues in Torque (BLAST-2823)
Downhole traces are not visible in viewer.

MineSight Data Analyst (MSDA)

MSDA currently does not fully support large numbers that have more than 6 significant figures for
MineSight data sources. This includes UTM coordinates.
If number of outliers exceeds 100, outliers are not shown on the box plot. In addition, the outlier
checkbox is disabled (MSDA-2666). Outlier information is not de-serialized either.
"Set missing values to zero" option does not work with Torque data sets (MSDA-2958).
The diagram showing the swath plot geometry may be cutoff when viewing if block model is large
(MSDA-3085).
Number of decimal places shown on the histogram x-axis properties dialog for certain bin sizes
may be large (MSDA-3113).
The variogram file generated by MSDA for Gaussian variogram type contains practical ranges. To
make it compatible with MSBasis Kriging routines select "practical ranges" option in
corresponding MSCompass procedures (BASIS-1435).
There is a crash when applying style from a swath plot with items on only one axis to a swath plot
with items on both axis (MSDA-3106).

Copyright© 2011 Mintec, inc. All Rights Reserved | MineSight® is a registered trademark of Mintec, Inc.
June 6, 2017
 An error is displayed when applying a style from a chart that has annotation box to one that
doesn't (MSDA-3105).
Auto Scale cannot be turned off once it's turned on for Scatterplot (MSDA-3090).
Changing min/max settings for the x-axis on a histogram chart has no effect (MSDA-1027).
"Create Variogram for MIK" utility does not ignore non-indicator model files and it should (MSDA-
3116).
"Create Variogram for MIK" utility exports Gaussian type for Variogram parameters as 1 instead
of 4 (MSDA-3115).
Variograms built from different data source may be different (MSDA-3117).
Downhole Variogram – “insufficient items to run application” error is thrown with minimum
required field selection in the Data Source (MSDA-3162).

MineSight Economic Planner (MSEP)

When exporting an advanced summary report to Excel, there may be some extra blank columns
or rows. You can delete them without any problems. It does not happen consistently (MSSO-
260).
Generation of PIVOT report using RES files in MSEPc requires at least two items in the “DATA
AREA” for the item labels to show in the report.
The pit optimization results from the LG and the PF may be different when the complex slope
option is used.
The pit optimization results from the direct 3DBM slope codes option and the surface slope codes
option may be different for complex slope runs, although both are correct. The results from the
direct 3DBM slope code option are more accurate.
The Price Options settings on the “BASE - Ultimate Pit” panel work only when there is just one
“Pit Optimization Area” entered for “MS-Economic Planner (Design).”
The resource total values computed after pit optimization or with the “Resource” option may
become negative in rare cases.

MineSight Planner (MSPlanner)

The Activity Gantt grid can become one row out of step with the Activity Grid. (ATLS-1719)
Watermarks on reports are not saved. (ATLS-2564)
With certain styling configurations where the geometry should not be visible, having 'Hard Edges'
checked can cause the hard edge lines to appear. Workaround: turn off hard edges. (ATLS-2196)
Reserve Logic configurations with six discrete items cannot be used. (ATLS-2693)
Text alignment does not have an effect on the position of text in the viewer. (ATLS-3404)
Must select 'System.String' for a Chart's data series filter for some types. (ATLS-4671)
Python calculation runs after toggling off the “Use Calculation” checkbox. Workaround: delete
unwanted calculations. (ATLS-7538)
An exception may be encountered if the window is resized. (ATLS-7673)
If the Windows font size is greater than 100% some layout items may not appear correctly.
(ATLS-7663)
Setting "Treat Missing Grades as Zero" on the reserve logic to false does not work. (ATLS-7632)
Letters with accents are not support and may cause issues opening projects (ATLS-10071)

Copyright© 2011 Mintec, inc. All Rights Reserved | MineSight® is a registered trademark of Mintec, Inc.
June 6, 2017
MineSight Schedule Optimizer (MSSO)
Multi-Ore% may not work with discrete zone items (MSSO-5192).
In Reserve Logic, only “treat missing as zero” setting is turned on automatically in MSSO 9.30.
MSSO 9.00 does not support discrete zone items in reserves.
MSSO 9.00 cut importer does not work with GSM models.
MSSO 9.00 cut importer does not work with variable bench height.
MSSO 9.00 does not automatically calculate filling sequence for orphaned subzones. Subzones
on each lift must be adjacent.
MSSO 9.0 does not show any in-lift stub if a path cannot be found from the seed to the subzone
(because they are not linked by adjacent subzones).
Material Mapping by Group may not work properly when you have overlapping material groups,
i.e., when a material bin falls into two or more material groups, and if each material group has a
different material mapping setting.
If you open an earlier project (earlier than v.8.30) in MSSO v.8.30, and if the project has
equipment planning in it, then you need to re-run the schedule calculation in order to get the
correct equipment report.
If the CPLEX engine is used, the scheduling results in MSSO v.8.30 might be slightly different
from the results calculated in earlier versions since we upgraded to the latest CPLEX engine in
MSSO v.8.30.
The Reload Haulage Data option does not work with projects that were created with earlier
versions of MSSO (earlier than v4.0). To use the haulage data (cycle time, equipment set, etc.) in
these existing projects, you need to re-create the projects in MSSO v4.0 and higher.
Refresh ARC may throw an exception (not always). If this happens, please close ARC and
restart ARC.
Performance may go down a bit after running MSSO animation for some time. This is mostly
caused by the garbage collector in .NET.
Each destination should have either subzone tonnage capacity or volume capacity. It cannot have
both subzone tonnage and volume capacity. Otherwise, the Destination Dependency, and
Destination/Phase Dependency constraints may not work.
In Analysis Report, ‘Material Ton’ should only be used for reserve report (mostly for period ‘0’).
‘Destination Ton’ is used for reporting materials moved to destinations.
In Constraints Banded Grid, just click on a cell then right click will not enable the ‘Apply To All
Periods’ menu. Users will have to rubber band (or similar) to select the cell first and then right-
click.
‘Detailed Scheduling’ option was disabled in 8.0 because the specific mining sequence calculated
by ‘Detailed Scheduling’ does not reflect the real mining sequence of cuts at all.
‘Animation by mining sequence’ option was disabled in 8.0 because the specific mining sequence
calculated by ‘Detailed Scheduling’ does not reflect the real mining sequence of cuts at all.
Some characters ( ‘(’, ‘)’, ‘[’, ‘]’, ‘{’, ‘}’ ) are reserved by MSSO and cannot appear in the
following items:
Grade name
Mining area name
Phase name
Destination name
MSSO project name and the path should not include characters like ‘=’
Reserve class names in SCD files and MSIP plans are case-insensitive.
Grade names in SCD files and MSIP plans are case-insensitive.

Copyright© 2011 Mintec, inc. All Rights Reserved | MineSight® is a registered trademark of Mintec, Inc.
June 6, 2017
 In standalone mode, if one project has multiple reserves logic within same MSSO project,
opening one of them for view/edit may open a wrong one (previously loaded one) always. But the
same steps open the correct one from MSSO View (from MS3D)

MineSight Strategic Planner (MSSP)

Grade attribute reported as “mineral content” may exceed 9 digits and “access violation” message
may be displayed on screen and “*” may result in output file.
Backward compatibility issue, MSSP V3.70 may produce a different result for the same problem
setup using the same dataset compared to V3.60 or previous versions. This perhaps was caused
by different compilers used between the two versions or achieving more feasible solutions in a
given period.
MSSP V3.70 linked with different versions of LINDO DLLs and Libraries (e.g., 64bit V7, 32bit V7,
V5, and V6) may produce different schedule results.
The mining rate summaries covering multiple periods or related to multiple periods are incorrect
in ARC reporting. (The mining rate issue can be resolved by exporting the completed report into
an EXCEL file and correcting it.)
The stripping ratios are implemented in the ARC reporting tool but not incorporated in the pre-
installed templates. (The stripping ratios can simply be added into the pivot tables if you choose
to do so.)
On “The Define Target Constraints” dialog, the checkbox “Set default range values for
mill/crushed leach ore types:” has no impact. Currently if the min and max target constraints for
an item (e.g., Type 2 mill ore) are not set, the program assumes that the constraints do not exist.

MineSight Torque (MSTorque) v5.30

Version number indicates version where the issue has been found in, not necessarily the first version
where the bug was introduced.

 General
There are issues connecting to and using remote SQL Server 2012 on 32-bit systems
(MSTORQUE-3413).
MSTorque crashes if loading very large data set (MSTORQUE-907, 1.00)
Filter by interval fails if the interval has no sample (MSTORQUE-2133, 2.50).
Cannot use unit converted values in filter (MSTORQUE-2677, 2.60).
Cyrillic characters are not properly supported (MSTORQUE-2616, 2.60).
Calculated sample attributes referencing collar geometry and units report converted values in
client applications (MSTORQUE-4135, 3.20).
Renamed or newly created coverages do not use coverage type column layout in sample grid
view (MSTORQUE-3616, 3.20).
Newly created and then deleted composites are incorrectly tracked for saving to the MSTorque
database (MSTORQUE-4810, 3.50).
Splash screen does not show the product name with Large text setting in Windows
(MSTORQUE-4988).

 Coordinate Conversion

Copyright© 2011 Mintec, inc. All Rights Reserved | MineSight® is a registered trademark of Mintec, Inc.
June 6, 2017
 Cannot convert coordinates when the first survey point is non-zero (MSTORQUE-4421, 2.60).

 Security

Dbadmin and writer roles cannot see all connected clients (MSTORQUE-3240, 3.00).
Non-existent clients with stale write-lock are shown as connected (MSTORQUE-3224, 3.00).
Sometimes users are denied login on first try when connecting to a new project (MSTORQUE-
3437, 3.00).
In the User Access Management tool, deleting a database does not automatically update the user
mapped database account (MSTORQUE-3640, 3.00).

 Project Setup

Can't delete measurement method if it is used before (MSTORQUE-2646, 2.50).

Calculated sample attributes with attributes in their conditional always evaluate to false when one
of the attributes has missing measurement (MSTORQUE-3188, 3.00).
Unexpected error occurs when renaming a sample attribute with special characters
(MSTORQUE-3706, 3.20).

 Compositing Tool

Cannot save composite data when project contains many sample attributes. (MSTORQUE-1707,
2.10).
Seam compositor displays error if input coverage has no samples (MSTORQUE-2578, 2.50).
Seam compositor displays error if majority coding is used and an attribute is used in multiple
places (MSTORQUE-2304, 2.50).
Inconsistent results when interval lengths extend beyond end of sample site (MSTORQUE-2577,
2.60).
Inconsistent results when sample site geometry is past end of sample site length (MSTORQUE-
2577, 2.60).
Unexpected Error if you re-composite and change Primary Attribute while viewing Composites
(MSTORQUE-5419).

 Copy Coverage Tool

Does not create intervals if there are no measurements in source sample attribute (MSTORQUE-
2471, 2.50).
Manually editing intervals of a copied coverage where the source has no measurements causes
the intervals to disappear (MSTORQUE-2521, 2.50).
Deleting a coverage and then creating a new one with the same name can lead to duplicate
intervals (MSTORQUE-2469, 2.50).
Overlay produces unexpected results when target intervals overlap (MSTORQUE-2530, 2.50).

 Overlay Tool

It is possible to overlay values outside of the target attribute range (MSTORQUE-2044, 2.50).

 Exporter

Exporting very large data takes unreasonably long time (MSTORQUE-2849, 2.20).
Boolean measurements cannot be exported consistently (MSTORQUE-2264, 2.50).

Copyright© 2011 Mintec, inc. All Rights Reserved | MineSight® is a registered trademark of Mintec, Inc.
June 6, 2017
 Command-line tool handles interval coordinates differently from GUI exporter (MSTORQUE-
5176).

 General Importer

Cannot parse scientific notation numbers (MSTORQUE-3248, 2.60).

AcQuire import: HOLETYPE filter is ignored (MSTORQUE-4193, 3.30).
AcQuire project setup import: does not import units GEOLOGYCODESECONDARY Fields
(MSTORQUE-4176, 3.30).
Abnormal program exit when closing the General Importer dialog after importing from acQuire
with an MSR spatial filter (MSTORQUE-5213).

 MSTorque Drillhole Views in MS3D

Refreshing a drillhole view using a new project folder may not load filters correctly (MSTORQUE-
3708, 3.20).

 Plug-in

MSTorque Manager crashes when saving ARC report while closing the application (MSTORQUE-
5260, 4.10).

 Archive

Design geometry set is created after Retrieve (MSTORQUE-5324, 4.0)

QAQC v1.0-01 Known Issues

User must manually reload or switch to another view to see updates to a Sample that was edited
on one Certificate. This only happens if user is sorting Samples by Name and have selected
multiple Certificates that have that Sample (QAQC-1738).
User can add an existing Sample to a Certificate even though the Sample cannot have a
Measurement for the new Certificate. In that case, user must remove the Sample to avoid
validation errors. (QAQC-1741).
The Upload indicator for Samples that are on multiple Certificates may not be refreshed right
away. In this case, reload (QAQC-1740).
User should avoid using commas in Lab Method naming. It is an issue when selecting Lab
Method for Uploading to Torque (QAQC-1730).
Coverage and Sample program settings are not restored between different Uploader dialog
sessions (QAQC-1693).
Tabbing does not work as expected in Certificate Importer and Uploader dialogs. (QAQC-1719).
Some settings will not be restored between Certificate Importer session if the number of
characters exceed 50. This includes Source Fields, Search String and New Value for Rules.
(QAQC-1752).
User cannot expand the Ribbon when previewing reports. Hot keys however work (QAQC-1530).
The Certificate status option at the bottom should be disabled when no Certificates are selected
in Analysis View (QAQC-1521).
Column width is reset when a new Certificate is selected in Certificate Browser (QAQC-1425).
User cannot save a chart that has no data (QAQC-1210).
Reloading charts may affect the x-axis labeling (QAQC-562).

Copyright© 2011 Mintec, inc. All Rights Reserved | MineSight® is a registered trademark of Mintec, Inc.
June 6, 2017
 The x-axis labeling scale may differ from the unsaved original chart if it's cloned. It's best to save
the chart first prior to cloning (QAQC-534).
It may not be possible to remove grouping by a column in Data Views (QAQC-484).
Error tooltip may persist when changing from Data Views to Backstage area (QAQC-610).
Torque Samples name/ID with trailing or leading white spaces may not be recognized in QAQC
which affects Uploading to Torque (QAQC-1745).
Original Measurement values are not restored using the Restore options in Open mode if
Measurements are imported as Missing (QAQC-1908).

MineSight Tools (MSTools)

MSPDConvert does not copy the MSHaulage groups tables and lift design grade (MSTOOLS-26).

Geologic
 Performance

Cancelling an operation can be time consuming (GEOL-1069).

 User Interface

The number of errors for an Event may occasionally be displayed incorrectly (GEOL-782).
In the Project Extent window, the slider control is occasionally not properly synched with the
data in the text boxes (GEOL-909).
Grade Shells event Iso-levels is not serialized (GEOL-1090).
Grade Shell | Save grade shells separately flag is not serialized (GEOL-1104)

Stope Optimizer

Does not currently support inverted z type models

Copyright© 2011 Mintec, inc. All Rights Reserved | MineSight® is a registered trademark of Mintec, Inc.
June 6, 2017