Jump to content
RockWare Support Forum


  • Posts

  • Joined

  • Last visited

Everything posted by Mitch

  1. Yes you can import DXF files for visualization in RockPlot2D or RockPlopt3D but turning these files into a grid is a bit tougher. If the DXF information contains the elevations then you can import the DXF as points and then use one of our griding algorithms to turn those points into a grid that can be used for further analysis. Without the elevations there will be little you can do without manually didgitizing thecontours. You can't expect the contours generated from your gridded data to closely match the original contours. The best algorithm to use depends on the density of the lines on the original dxf. If they're fairly close over your area then Closest Point might be the best otherwise you'll need to use the interpolated methods (inverse distance, kriging, etc.).
  2. * Raster symbols with a very small height sometimes displayed larger than they should.
  3. I'm afraid not. However if you size the font based on the second files requirements it will be fine once the 2 files are combined.
  4. Does the second file have a much larger coordinate range than the first? Scaling text in OpenGL is a bit tricky and varies depending on the coordinate ranges.
  5. Unfortunately OpenGL provides very poor tools for text placement and sizing. Your only alternative is to use the offsets however this won't provide consistent results from one diagram to another.
  6. Hi Christian, a couple of things come to mind. First I suspect you're using a large output page size. Since LogPlot has to allocate a large enough bitmap to duplicate the page on the screen this can cause problems. If your final output (printer, pdf) can be divided into smaller pages this will help reduce the resource requirements. Have you tried using another LogDesign (one of our samples) and seeing if the problem still occurs? Second, many new computers have very high resolution displays compared to older computers. Reducing the screen resolution may help. If you are continuing to have problems please send your LogDesign (.ldfx) to support@rockware.com so that we can look into your problem. Thank you, Mitch Wolberg
  7. A new build of RockWorks 17 has been uploaded. - The Vertical Exaggeration that is stored within RockPlot2D files is now used when setting the Best Fit scaling within the RockPlot2D program. - Color tables opened within the ReportWorks Color Legends dialog are now sorted properly. -: Stratigraphic superface and subface maps now display the correct z-minimum and z-maximum within the Confirm Contours dialog. - Stratigraphic isopach maps now display the correct z-minimum and z-maximum within the Confirm Contours dialog. - The solid Kriging now accommodates a broader range of data sets (i.e. z-range < average distance). - The grid Kriging now accommodates a broader range of data sets (i.e. z-range < average distance). - Creating a stratigraphy model with a "base plate" no longer fails (i.e. the base plate grid is now set to the project dimensions). - The program will now copy the data correctly if the user creates a new project based on an existing project in which the user elects to copy only the Enabled boreholes. - The program will now automatically rebuild the System folder if it's missing from the project folder. - The "Swath" option that is used for including boreholes within profiles is now available for all licensing levels. - The "Snap" option that is used for picking boreholes for sections, profiles, and fence diagrams is now available for all licensing levels. To download the most recent build, please visit: https://www.rockware...Demo.php?id=165 To read the detailed revision list, please visit: https://www.rockware...t_revisions.htm Enjoy! RockWare Support
  8. The size limitation goes away with SQLite and its faster than Access. However very large amounts of P-Data will still slow you down, just not as much. On the processing side multi-core processing for many algorithms, 64bit memory space and improved design help speed things up. Of course if you use the larger memory space to make larger models there will be a performance penalty. I'll let our Database guru Jim Jackson chime in with more specific details.
  9. * LogPlot was replacing some commas and periods in non-numeric fields when the Windows Regional setting were not for the US. * The new keyword entry dialog now issues a warning for keywords longer than 60 characters.
  10. * Batch compiling logs with Lithology entries with non-default Contact lines caused the keyword and contact to be plotted incorrectly.
  11. Sorry, no snap to point though we'll consider adding this option in a future release.
  12. As stated in the help file: Vertex Snap uses the Shift key Line Snap uses the Control key Smart Snap uses the Control + Shift key Show Snap Points uses Ctl+Alt+S and can also be activated from the View menu It is hard to remember unless you use it often which is why there's status message that appears at the bottom of the screen as soon as a line drawing tool is selected.
  13. - Strike and Dip symbols with Strikes greater than 270 degrees are now plotted correctly using the Right Hand Rule. - The Stiff Map diagram size limits have been removed.
  14. I don't think a bug report or screenshot will help in this case since we now know what you were doing. Unfortunately I can't duplicate the error and it may be a unique event. If it keeps occurring you should run Check Database Integrity (BH Manager/File/Check Database Integrity) to see if there are problems with your database.
  15. The CPU processing, which allows you to change display options, is slower than the graphics card. We have made performance enhancements in newer versions and we'll continue to improve the software with future versions.
  16. - Vertical Column dividers weren't being displayed in deviated boreholes when clipping was enabled. - The Earth Apps Extract menu was using the wrong file filter mask. - Loading an RCL in the 2D Striplog Designer caused the summary to be displayed under the axis settings. -The Low option for Grid Declustering was not working. - In the Stratigraphy Picker the displayed formations were not being updated when changed in the Stratigraphy Types Table. - Using the Cutout option in RockPlot3D to remove either the top or bottom of a Voxel Model caused an Access Violation.
  17. Edward, are you saving the polygons to a table or perhaps filling the polygons with a pattern from a Stratigraphy, Lithology or Aquifer table? Those are the only operations I can think of that include a Dataset. If you can provide the step by step instructions to repeat this error we can help you figure out a solution.
  18. 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.
  19. No, it will come out the same size unless you adjust the size of the image.
  20. 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.
  21. 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 support@rockware.com.
  22. Sounds like you're not setting the Pixels Per Inch at the top of the Export dialog.
  23. 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.
  24. 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.
  25. 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.
  • Create New...