Jump to content
RockWare Support Forum

Mitch

Admin
  • Content count

    551
  • Joined

  • Last visited

Everything posted by Mitch

  1. Rockplot 3D slow rendering

    HI Joseph, there's a couple of possibilities. One is that users with more memory and faster CPU's tend to make bigger models which take more time to draw. We have made some improvements to drawing speed since RW14, especially for Iso-Surfaces. The second is counter intuitive. OpenGL doesn't scale to multi-threading very well since it uses state based model. It may be that the single thread on your old CPU might have more processing power than one of the cores of your 8 core machine. The good news is that those other cores are free for other applications while you're waiting for RockPlot3D to render. Though we do offer hardware acceleration most of the processing takes place in the CPU so it offers very little advantage. BTW Molly got your file and it seems to work fine on her 4 core machine using RockPlot3D 14.
  2. Importing images to Rockworks 2D

    No, it will come out the same size unless you adjust the size of the image.
  3. Importing images to Rockworks 2D

    The problem is that we're using PNG as our internal storage format which isn't as efficient as JPG, especially for photos where there is a very large number of colors. JPG is a lossy format which loses quality with compression and gets worse every time it is saved. PNG is a lossless format which means you don't lose quality with compression which is why we use it. Every choice is a compromise and in this case we chose quality over size.
  4. Importing images to Rockworks 2D

    Hi Edward, RockPlot2D is storing your raster image as a PNG file thanks to the previous changes you mentioned. The one possibility I can think of that the file is so much larger is that the original format is much more compact (1 bit Tiff for example) than a true color PNG (internal format). If that's not the case then please send a copy of your original image to [email protected]
  5. PDF export (and others)

    Sounds like you're not setting the Pixels Per Inch at the top of the Export dialog.
  6. PDF export (and others)

    PDF is an Adobe proprietary format with no official documentation. The export dialog allows you to enter the Pixels Per Inch and the Size in Inches, you can easily calculate the final size of your raster image from that. At 300 ppi and a width of 4"and a height of 3" will give you a an image 1200x900 pixels.
  7. PDF export (and others)

    Hi Edward, we've looked into vector PDF export in the past and the problem is that the available tools have not been satisfactory. The PDF format is very complicated which makes it difficult for us to write our own export. Another more viable option might be the SVG format but I haven't seen too many editable graphics programs for this format but I would consider adding that in the future. The scalability of the line widths is based on the output resolution.When exporting a rater file you need to consider at what size and resolution it's going to be used and adjust the scaling and pixels per inch accordingly.
  8. Snapping to lines and verticies in RW2D

    The snap points are not user defined. Lines should snap to other vertices in lines, rectangles, polylines and polygons. For Smart Snap they should snap to Stratigraphic Columns in logs.
  9. - The Line Map azimuth filter wasn't working. - Loading an RCL into the 2D Striplog Designer caused the design summary to be displayed in the current item menu. - The Grid Declustering wasn't initializing the minimum and maximum node values leading to inconsistent results. - Editing the Stratigraphy Table in the Stratigraphy Picker wasn't updating the Picker's formations. - The Image Rectify program failed when an output file had an invalid extension. Now a warning is generated. - Adding a Cut Out to an Iso-Surface that cuts the full XY extents was causing an Access Violation Error. - The Lithology Modeling Algorithms weren't being correctly set. - The SCAN_BOREHOLES command in an RCL file wasn't causing the main forms Project Dimensions to update. - In RockPlot3D a cutout that extended to the maximum of Easting and North (IOW removing the top or bottom) of an Iso-Surface caused a Access Violation Error. - The Show and Save RCL options for Lithology Modeling were showing the algorithm setting for generic modeling. - Running the SCAN_BOREHOLES command in an RCL script wasn't updating the Project Dimensions display on the main form. - The Symbol and Label options for Krajewskigram were shared with the Scattergram menu but weren't being displayed. - In the Utilities EZ Map and Grid Map points without Z values are included in the Symbols and Labels. - The menu settings for using Scientific Notation in Color Legends was being ignored. - The Google Earth Export from RockPlot3D no longer falsely reports that Google Earth is not installed. - The weighted averaging with distance filter for I-Data gave inconsistent results. - The Utilities / Grid / Profile / Multiple program was updating the profile end points for the additional profiles. - The Borehole Manager / Location Map was always using the Elevation for calculating Stratigraphy Elevation Labels even when Collar Elevation was selected. - The Utilities - Survey to 3D Diagram the Plot Station Label checkbox wasn't being used. - The Utilities - Survey Programs were requiring Unit Settings for columns that weren't being used. - In the KML Extract Programs the coordinates weren't being captured if the user's Regional Settings were not using the US number format. - Clipping polylines in RockPlot2D sometimes included line segments outside the clip boundary. - Images imported to RockPlot2D from the RU/Imagery menu couldn't be hidden by disabling their layer. - In RockPlot3D Color Legends Custom Color Table data was being saved but weren't loaded when an RP3D file was opened. - Any file operations in RockPlot2D after exporting a Shape File caused an Access Violation.
  10. Its come to our attention that users are getting this error when exporting a Google Earth file from RockPlot3D even though Google Earth was installed. The problem is that Google has changed their Windows Registry entries so that our version check no longer works. Until we post a new version you can just ignore this error. Note: We were checking the version because of one buggy release of Google Earth (7.1.1.1580). If you're getting output that is all white you probably have this version and should update your copy of Google Earth.
  11. Snapping to lines and verticies in RW2D

    Perhaps it would help if you could show and example so we can see what's going wrong and what you're trying to do. Are you using the Vertex and/or the Smart Snap options?
  12. * Restored the Project Manager's preview for LogDesign files. * Updated the wording in the License Manager.
  13. Revisions; (012) Bug Fix (04/22/15/MIW): Exporting RW2D files to a raster format using RCL scripting now sizes vertically exaggerated diagrams correctly. (011) Bug Fix (04/22/15/JCJ): The LAS Import program correctly imports LAS files with wrapped lines (this bug was introduced in November of 2014). (010) Bug Fix (04/16/15/JCJ): The LAS Import program no longer fails if the project is configured to measure point data from the borehole collar. (009) Bug Fix (04/16/15/JPR): The Utilities / Map / Pie-Chart Map program now selectes the X and Y midpoint coordinates from the correct column. (008) Bug Fix (04/13/15/JPR): The object markers (the red dots that appear when clicking on a RockPlot2D object) for bitmaps within 2D striplogs are now properly registered with the image. (007) New Feature (04/10/15/JPR): A new option titled "Limit To Column Width" has been added to the Bitmaps section of the 2D striplog design sub-menu. This new feature extends the capabilities of the bitmap plotting as described below; Aspect = Preserve / Limit To Column Width = True: Fill the designated vertical column (shown in red within the example below) while preserving the aspect ratio. Advantage: Images always extend to base of designated interval. Disadvantage: Images may laterally extend beyond the right-edge of the image column. Aspect = Preserve / Limit To Column Width = False: Adjust the images such that right edge of an image will never extend beyond the right edge of the image column. Advantage: Images never extend beyond right edge of image column. Disadvantage: Base of the images may not extend to the depth of the designated interval. Aspect = Stretch / Reduce: Independently stretch or reduce the horizontal and vertical dimensions of the bitmap to fit within the designated depth interval and column width: Advantage: Fills entire interval regardless of the original image aspect ratio. Disadvantage: May produce strange looking bitmaps. (006) Bug Fix (04/10/15/JCJ): The SQL-Server interface now delimits strings within 2D striplog queries with a single quote rather than a double-quote. Please note that this does not effect the Access/MDB version which accepts either format.
  14. Easy Cross Section, Rock plot 2D

    Sorry but your attached data didn't make it so it's not very clear what you're trying to do. If you can't attach the data consider sending it to support or give us a description of what the data contains. xy coordinaates? elevations, stratigraphic tops or ...? what format?
  15. * The MSVC100 Run Time DLL's have been added to the installation programs for older Windows Operating Systems.
  16. * An embedded DLL file that could cause problems with older Windows versions is now installed separately.
  17. UPDATE: A new version (7.6.132.167) has been uploaded that fixes this problem. Users running XP or Server 2003 may get these errors running the current version of LogPlot 7. Download and install the Microsoft Visual C++ 2010 Redistributable Package (x86) from MIcrosoft. (http://www.microsoft.com/en-au/download/details.aspx?id=5555).
  18. * Some modifications were made to the pLog Cloud Connect data import to provide more information to users who aren't signed up for the service.
  19. Error in the GUI of RockWorks 16

    Thanks Rudy for your help in resolving this problem. Who knew another program (Kapersky Anti-Virus) could cause this problem. Here's Jim's blog entry: Fixing Unreadable RockWorks Menus Posted on November 12, 2014 by Jim Reed If you ever encounter unreadable RockWorks menus with dark filled rectangles hiding the underlying text (see example below) … … you’re probably running an older version of Kaspersky Internet Security that apparently garbles the Windows theme/style settings. Fortunately, the solution is very simple: Update your Kaspersky software to the latest version and the problem will go away. Special thanks to Rudy Abo at TU Freiberg and Rafael Maricca at LMD Innovative.
  20. LogPlot 7.6.130.165

    * Opening a RockWorks 15 Borehole in LogPlot now brings in all Location fields (including Name) except for BH ID. * The RockWorks 16 Project Notes and Borehole Comments are now imported as Notes.
  21. Error in the GUI of RockWorks 16

    We're not sure what's going on but we'd like to send you a test program so that we can narrow down the problem if that's okay with you.
  22. Error in the GUI of RockWorks 16

    Another thought, are using something other than the Windows 7 Basic Theme? (Control Panel - Personalization)
  23. Error in the GUI of RockWorks 16

    Hi Rudyabo, This isn't a problem we've run into before but I suspect it has more to do with your color settings or video driver. What video card do you have? What color settings are you set for (256, High, True Color or...)? Have you tried changing any of these settings? It varies with the video driver but you can get at this information by going to the Control Panel - Display - Screen Resolution - Advanced Settings. This dialog lists info on your video card and driver and has a button labeled "List All Modes" which should show you different resolution and color options.
  24. Unable to copy/paste

    We do try to correct things as quickly as we can. I'm surprised that this hadn't come up earlier.
  25. Unable to copy/paste

    Its fixed and available for download.
×