This file documents the changes made to Seep3D since the release of Version 1.0. The numbers in parentheses after some items refer to a Knowledge Base article with more information. These Knowledge Base articles may be found by visiting the GEO-SLOPE web site at http://www.geo-slope.com.
· It is possible in some cases for Seep3D to allow creating adjacent regions with incompatible faces. In the past, Seep3D would create such regions and could save the file, but on opening the file Seep3D would display an error message and exit. Now it will instead display a warning and continue. The analysis can even be solved and results can be viewed, but there will be a no-flow boundary along the incompatible region boundary. (KB699)
· Changes were made to the OpenGL acceleration mode detection to avoid crashes or hung systems on certain platforms.
· A bug was fixed which prevented some very small vectors from being displayed.
· Added a /nosplash command-line switch to avoid displaying the splash screen.
· Two bugs were fixed related to determining whether a point was inside or outside of a solid. (KB645, KB648)
· Fixed a bug which could cause the solver to display the error “Floating point error”. (KB602)
· Fixed a bug which could prevent Seep3D opening some files. (KB530)
· Now supports FLEXnet 10 licensing.
· Fixed a bug which could cause Seep3D to crash when loading some .gss files. (KB501)
· Fixed a bug which could cause Seep3D to crash if the name of a Free Point was changed. (KB497)
· Fixed a bug which would prevent Seep3D from opening a file that contained a Free Point that was not part of a region. Now Seep3D will open the file correctly, but will refuse to solve it. (KB512)
Please note: Our supplier of the FLEXlm licensing technology has made a change to the system to improve security. Unfortunately this means you will need to acquire a new license file in order to use versions 5.15 and later. Your existing license file will not work after you upgrade to version 5.15. Please contact GEO-SLOPE to have a new (free) license file emailed to you.
·
Fixed a bug which caused an “internal
error” in some cases while viewing surface contours. (KB492)
· Fixed a bug which caused the “Number of Nodes” and “Number of Elements” entries in the Mesh Data tab of the Analysis property sheet to be displayed as “<Missing>”. (KB350)
· Added a delay to dragging region points, edges and faces. Now the mouse must move a couple of pixels before the drag operation actually starts. This avoids the problem of accidentally invalidating a mesh by simply clicking on a face, for example.
·
A bug has been fixed which caused the
application to crash when deleting a free point that was not also a point in
the domain. (KB480)
·
Occasionally it would be impossible to
attach a new region onto existing regions in the domain even though the
geometry was valid. This was due to a
bug in the collision detection scheme.
The proposed new region was thought to intersect existing regions and
was therefore prevented from being created.
This has been fixed.
·
A bug was fixed which could cause
an error message to be displayed after solving if a cut plane was not entirely
inside regions.
· Before solving a transient analysis, the steady-state analysis on which it depends must first be solved. Previously, Seep3D would allow the transient solve to start, but if the steady-state analysis had not yet been solved, the transient solve would never finish. This has been fixed by not allowing the transient solve to start until a steady-state solution is available. (KB470)
· A bug was fixed which could cause Seep3D to crash while solving a transient analysis if its steady-state analysis was deleted.
· A bug was fixed which could cause Seep3D to crash while viewing a single-point function.
· Fixed various errors opening .gsp files.
· A bug was fixed which could cause an “internal error” in some cases while results were being generated.
· If no Result Plane exists in the Result Set, then Surface Contours are not drawn. Seep3D now warns about this case. A more thorough solution will be implemented in a future release. (KB471)
· General performance improvements: Seep3D now loads solution files in about half the time required by version 1.0. (KB337)
· In some cases Seep3D would generate an error about an invalid memory access and close. The error was related to memory corruption caused when viewing point, line, surface or solid properties with a Steady State Analysis.
· In some cases Seep3D was unable to obtain results for result objects (ResultPoints, ResultLines, ResultPlanes). What was happening is a point, where results were required, was very slightly outside a region boundary. This point was considered as being inside the region if it was extremely close to the region boundary, but not quite on or inside it. When results were requested from the finite element mesh this same point was considered as being outside the mesh and hence results could not be found for it (an error was generated). The checking for whether a point is inside or outside a region or element is now consistent.
· It was possible to generate regions that were inside-out or that intersected other regions. Seep3D now validates that new regions are created correctly. Note that this change does not fix cases in existing files; however existing invalid regions can still be selected and deleted.