Update README.md

ferrellsl · Jun 4, 2023 · d2a86ad · d2a86ad
1 parent a7bdb82
commit d2a86ad
Showing 1 changed file with 2 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -46,15 +46,14 @@ Usernames with spaces will probably not work properly and remains untested.
 
 The code has now been moved over to Visual Studio 2019 and I decided it was time to put this release on github as John and I are not young men anymore.  We're both retired but I won't divulge our ages!  LOL!
 
-Users who wish to create VRML models should note that QuikGrid generates VRML version 1.0 files which are ancient and many more modern applications that purport to read/write VRML files no longer support VRML 1.0.  To address this issue, I've added a converter/updgrade tool in the VRML 1.0 to VRML 2.0 Converter folder.  I've also added a new VRML Viewer app in the VRML Viewer folder.  The viewer is based on the Coin3D library version 4 and is 64-bit, so it will load very large models and is not prone to crashing as the earlier loader was.  I've successfully loaded VRML2.0 files that were in excess of 500MB in size.  See the Usage.txt for more info.  You can drag and drop a VRML2.0 file onto the executable to load/view it, or use the command line.  It also has a GUI.  The sourcecode for the viewer can be found at:  https://github.com/glls/gl3dv  A sample VRML file of Wizard Island is located in the Sample Data folder.
+Users who wish to create VRML models should note that the latest version of QuikGrid generates VRML version 1.0 and 2.0 files thanks to the work of Volker Enderlein of Coin3D.   The default is 1.0 output.  To switch to 2.0 file output, go to the Edit menu and select Output Options and place a checkmark in the box for VRML2 output. There is also a VRML Viewer app in the VRML Viewer folder.  The viewer is based on the Coin3D library version 4 and is 64-bit, so it will load very large models and is not prone to crashing as the earlier loader was.  I've successfully loaded VRML2.0 files that were in excess of 500MB in size.  See the Usage.txt for more info.  You can drag and drop a VRML2.0 file onto the executable to load/view it, or use the command line.  It also has a GUI.  The sourcecode for the viewer can be found at:  https://github.com/glls/gl3dv  A sample VRML file of Wizard Island is located in the Sample Data folder.  Windows 10/11 also include 3d Viewer and 3D Builder apps which will render VRML2.0 files but they will often fail to render extremely large files. Volker also optimized the VRML output which has significantly reduced the size of VRML files generated by QuikGrid.
 
-I don't recommend loading large VRML1.0 terrain models with the viewer as it literally takes hours to render VRML1.0 files.  A 280 MB VRML1.0 file of Crater Lake takes 2 hours to render while the same file converted to VRML2.0 renders in seconds even though the VRML2.0 file is 534 MB, or nearly twice the size of the VRML1.0 file.
 
 KNOWN BUGS:  
 
 1.  If the user tries to access the help menu from within QuikGrid after opening a data file or a grid file, they'll receive an error message that help isn't available.  The workaround for this is to open the help file from within QuikGrid BEFORE importing/loading a dataset or grid file.  Help will then function properly for the rest of your session even if you choose to close and re-open the Help file.  Another option is to just double-click on the QuikGrid.chm file whenever you need it.  I'm unsure why this happens and haven't been motivated enough to find the cause and fix it.
 
-2.  On some systems, QuikGrid refuses to run or shuts down immediately unless it has been configured to run under "Windows 8 Compatibility Mode".  I'm unsure why this occurs, but after running it successfully in compatibility mode, you can go back and set it to run natively and it will continue to run properly thereafter.
+2.  On some systems, QuikGrid refuses to run or shuts down immediately unless it has been configured to run under "Windows 8 Compatibility Mode".  I'm unsure why this occurs, but after running it successfully in compatibility mode, you can go back and set it to run natively and it will continue to run properly thereafter.  EDIT:   This bug appears to be fixed with Volker's latest commits.  There was a memory overwrite bug in Utility.cpp that he caught and fixed.
 
 BUILDING: