Jump to content
RockWare Support Forum


  • Posts

  • Joined

  • Last visited

Everything posted by Mitch

  1. + Scalebars that had orientations inclined upward didn't plot correctly. + The Absolute Depth Scalebar Type was plotting negative depths. + Changed the Scalebar Type "Depth" to "Negative Depth" and "Absolute Depth" to "Positive Depth".
  2. Sorry fro the delay in getting back to you. To get the transparency to work I'd use the Utilities/Imagery/vertical (Images -> 3D Panels) program to get the images into RockPlot3D. See the Vertical_Images_to_3d.rwDat file for an example. You can then export the scene from RockPlot3D to Google Earth and the transparency will work.
  3. New versions of LogPlot8 (32-bit and 64-bit) were uploaded to the RockWare website today with the following bug fix: + The Fillbar keywords were not matching the data when they were displayed over several pages.
  4. New versions of LogPlot8 (32-bit and 64-bit) were uploaded to the RockWare website today with the following bug fix: + The Header Legend linked to Histogram now lines up correctly in the compiled log. + The Edit and Static Note borders now plot the correct width in the Log Designer.
  5. The RockPlot3D export does require a triangle mesh but you can use the Utilities/Google Earth Apps to create scenes in in Google Earth. You can either display the lines directly or create an image and display as a vertical panel.
  6. We don't see this happening here. -What version of Windows are you using? -Are you using large fonts (>100%)? -Have you modified your Window's Theme? -If you switch to DB Datasheet (eg. Stratigraphy) do you see the same effect after selecting a cell?
  7. Simple Answer: Upgrade to LogPlot 8 with unlimited length descriptions, text formatting and unicode characters. Complicated Answer: You can't increase the maximum text length in LogPlot 7. Having 2 Lithology Description columns may work but would make entering data more complicated. You can also add comments to a description by just entering just the Top Depth in the data sheet. Again this would make data entry more complicated.
  8. Hi Josh, you'll really have to explain a bit more what you're doing or you can send me a copy of your RockPlot3D file so I can see why it's not working.
  9. Hi Josh, I'm not sure exactly what kind of you're creating (voxel, isosurface, or ?), what version of RockWorks you're using, or what program you're exporting to g but I'll attempt to answer your questions. The 3D Shape file is best displayed in ArcScene, in ArcMap you'll only get a plan view of your model. You need to set up symbology if you want to see more that a mono-color output. For the TIFF export use Packbits or no compression. I'm not sure how a TIFF would help for further processing. Please include some additional information if you need more help.
  10. This was fixed and should be in the next build which should be available today or tomorrow.
  11. Hi Sabrina, having the correct coordinates only matter if you need to geo-locate the image. If you only need to view the image by itself then you can use any coordinates, Otherwise you can rectify the image using 3 known non-linear points. Use landmarks that can be found on maps or in Google Earth.
  12. Hi Christian, sorry it took so long but the versions (32+64) are up. I redesigned the export dialog to make it easier to use.
  13. Hi Christian, I found some problems with the very long exports and hope to have a new version available soon.
  14. The 64 bit version is now available. You will need a new unlocking code but there is no charge. We also recommend uninstalling the 32 bit version to avoid confusion.
  15. Hi Christian, we're going to release a 64 bit version of LogPlot8 this week which should resolve the memory issues you're having. If you need to get something out right away you should try restarting LogPlot. Windows programs can have problems with fragmented memory and then can't find a memory block big enough for certain operations. MItch
  16. The only way would be to set up a Batch operation (Data Editor | Log | Batch Compile. Mitch
  17. Hi Corey, under the Data Edit / Log Menu you'll find a menu item, Compile All Logs. This option will compile all open data files with the same settings. Provided that the Output Resolution is the same you should get the same quality when printing or exporting to PDF. However depending on the PDF driver you're using there may be more options that result in a nicer appearance. Setting margins for printers is a bit more difficult since different page sizes and printers have set margins but it s something we'll add to our feature list for future versions. Mitch
  18. Christian, I wasn't able to duplicate your problem. If you send me your LogPlot 7 Design (mitch@rockware.com) I'd be happy to take a look. Mitch
  19. Thanks Christian, from your excellent description I suspect the problem is caused by importing an LP7 Design with the units set to centimeters. I will take a look at it this morning. Mitch
  20. Hi Christian, it looks like your page width settings are invalid or your Snap Grid spacing is too small. Try the Continue button and turn off the Display of the Snap Grid (the yellow button on the LogDesigner statusbar. If that doesn't help try loading a different LogDesign file (.ldfx8) from the Windows Explorer by double clicking. Mitch
  21. It looks like a mismatch between project coordinates and elevation units. Also check that your boreholes have unique Easting's and Northing's.
  22. Size isn't the problem, the file is open exclusively by another program. If that isn't the case sometimes a program will forget to release a file. In this case you will need to restart Windows to release the file.
  23. I suspect that the problem is your model spacing. Try increasing the spacing of the nodes. Fewer nodes will process much faster. Once you have the settings you want you can decrease the node spacing though we find that people tend to set a higher resolution than they really need. A model that's 100x100x100 may not seem that big but it is 1,000,000,000 nodes.
  • Create New...