omegalib 3.5 released

-
o3.5

Major Changes

  • Reorganized source: all c++ and python examples are now under /examples.
  • (3.5.1) omicron and omegalib use double precision math by default.

omega

  • Improvements to python API
  • Camera.focusOn
  • clip plane control
  • (3.5.1) fixes to SceneNode? bounding box
  • NodeComponent? API slightly changed to support more functionality for objects attached to scene nodes.
  • (3.5.1) ImageUtils::loadImageFromStream()
  • (3.5.1) Keyboard service generates button left/right/up/down events when keyboard arrows are used.

    omegaOsg

    • fixed bounding box generation
    • fixes to clipping
    • (3.5.1) Added auto near / far Z computation toggle (:setautonearfar [on|off])
    • (3.5.1) Added support for PagedLOD and DatabasePager?
    • (3.5.1) FBX support can be optionally disabled

    omegaVtk

    • re-added support for vtk python scripting
    • added support for vtk lights.
    • added support for depth peeling

      cyclops

        • Context menus can be attached to entities using a simpler API that does not require custom scripting.
        • Added support for custom model loaders
        • GPU Program assets are now fully configurable through python (using the ProgramAsset class). Programs can be reloaded at runtime using a simple command (SceneManager.updateProgram) allowing users to experiment with different shaders.

          orun

            • configurable startup script and application start function. The startup script can be used as a 'boot' script to modify applications depending on the system they are running on. The application start function (typically defined in the init script) is launched every time a new application starts and can be used to inject cutom functions (like system menus) into the application.

              omegaToolkit

                • (3.5.1) added Container:isEventInside, other improvements and fixes to ui Container class
                • (3.5.1) improved AppDrawer
                • (3.5.1) custom user data can be attached to Widget
                • (3.5.1) Button icons

                Comments

                Post a Comment

                Popular posts from this blog

                Parallel Gaussian Elimination Using MPI

                -
                Image
                In this project, we had to implement a parallel solver for linear equation systems, using a technique known as Gaussian elimination (GE). As with many other algorithms for solving linear equation systems, GE is performed on the matrix representation of the system, Ax = b, where A is the coefficient matrix and b is the vector of known values. GE works by applying a set of elementary row operations (swapping rows, multiplying a row by a non-zero number, adding a multiple of one row to another) in order to turn the coefficient matrix into upper triangular form. The algorithm has been implemented in C, using the Message Passing Interface (MPI) API. The parallel GE program measured execution times for its four main components: data distribution, Forward Elimination , Pivot row identification, Back substitution. Read the full report here
                Read more

                Parallel Beam Tracing and Visualization of 200 Million Sonar Points

                -
                Image
                For the final project in the UIC Spring 2013 Parallel Processing Class, I worked with a classmate to optimize our current implementation of a sonar beam tracer used for  The NASA ENDURANCE Project . The beam tracer is used to process the raw data collected by the ENDURANCE AUV in Lake Bonney, Antarctica, and correct sound beam paths using information about the water chemistry. The data is clustered and noise filtered to generate a final 3D Point cloud that can be visualized in our CAVE2 system. The ENDURANCE Sonar data in CAVE2. Photo(c) Lance Long. A lot of corrections and adjustments need to be applied to this data before the final results are acceptable. Some of the corrections derive from the sound speed estimation through the water column, AUV navigation corrections, water level changes and noise filtering thresholds. All this parameters influence the final result, and ideally researchers can tweak them and see the result of their actions in real time. Given the size of
                Read more

                Flickering 2D transform elements in Chrome: a simple fix

                -
                This quick post is to point out a fix to an issue I had to deal with a few weeks ago and was caused by a Chrome update. Components with absolute positioning and a 2D CSS transform started flickering when placed inside a scrollable component. A brief search online revealed several people with similar problems, but the suggested fixes were all very different. I tested several of them (including obvious changes to the z order) before finding the one that actually did the trick. What eventually worked for me was adding an empty 3D transform to the same elements with 2D transforms: transform:translate3d(0,0,0); I guess the reason why this works is that it forces elements to be drawn via a different rendering / compositing path than standard 2D elements.
                Read more