My understanding is that you don't need to do any coding to use Ogle. You do need to hand edit some configuration files (ini files) but that's not the same as writing code or scripting. And maybe not even that (see step 7 below.)
You do need to d/l and install another app called GLIntercept that Ogle uses to grab the scene. These two apps run while you are viewing a 3-D scene in a third app like Google Earth.
The instructions are as follows:
- Download and install GLIntercept 0.5 from http://glintercept.nutty.org/download.html
- Read all of its documentation, and make sure it works... There's a bunch of technical stuff here which is directed at coders, but it's basically troubleshooting to make sure GLIntercept is working. If you are non-technical you can just skip it and hope for the best.
- If you do not already have it, download the compiled OGLE plugin from http://ogle.eyebeamresearch.org/download/ (note: you want the most recent
.bin``. distribution, not the src).
- Copy the whole OGLE distribution (i.e. the directory that contains the
OGLE.dll file) into the Plugins directory for your GLIntercept installation, typically
C:Program FilesGLIntercept0_5Plugins, and rename the directory to OGLE``ogle_* to OGLE). (i.e. change the name from
- That's it, installed! To use it...
- Most of the work in getting OGLE to capture 3D data is in the configuration of GLIntercept. There are a number of settings that must be made to ensure OGLE functions properly.... they then list a bunch of settings you have to change, but it's ll right there, just do what they say on the website.
-
Here's a big help: The OGLE GUI: Someone has put together a Windows GUI app that supposedly makes all this copying and configuring a lot easier. You can try it at your own risk at: http://members.chello.at/alexan/ and give the creator feedback on the SourceForge forum.
- Run your OpenGL application with GLIntercept configured to use the OGLE plugin (as seen above).
- When you get to the view of the geometry that you want to capture, activate frame logging using whatever keystrokes you have configured with the
LogPerFrame::FrameStartKeys variable. (This is one of the settings in the GLConfig.ini file you have to edit. The GUI probably lets you set this also.)
- Be patient -- your app will freeze and it can take a number of seconds or minutes for GLIntercept to log all of the data for that frame and OGLE to generate the 3D object file for the on-screen geometry. You will know that it is done when your application becomes interactive again.
- Find the
.obj file in the directory where your application runs. Open it in...
POSER of course! 
The above is my "lite" version of the instructions found on this page:
http://ogle.eyebeamresearch.org/readme
