omegalib 2.1 released

-

Summary

omegalib is a middleware designed to ease the development of applications on virtual reality and immersive systems. Its main features are:
  • Support for hybrid systems, presenting high definition 2d and 3d content on the same display surface
  • Display system scalability
  • Support for a wide range of input peripherals (controllers, motion capture systems, touch surfaces)
  • Integration with third party higher level toolkits like Unity, vtk, Open Scene Graph, Qt.
Altough omegalib is designed mostly to run on VR systems, it can be used to develop applications on standard desktop systems as well, leveraging the power of multiple Gpu units when available
Omegalib 2.1 is mostly a bookkeeping / work-in-progress tag, before some refactoring work for omegalib 3.0

Major Changes

  • omega
    • Added support for headless master nodes on cluster configs
    • Improved equalizer code for cluster configs
    • Added preliminary support for cylindrical display configs
    • Python API redesigned to more closely match the C++ API (using boost::python)
      • Python API integrated pyEuclid for math fnctionality
    • system configuration does not need to be in app config file anymore. It is now looked up from default.cfg
    • current working dir support in clustered launcher
    • orun works without osg / vtk support
    • MouseCameraController? (control camera just using mouse, useful for SAGEPointer-based control of remote displays)
    • Added support for skybox, environment mapped shaders
    • Custom display geometry in config files
  • omicron
    • Cleaned up math library
  • cyclops
    • Major improvements in effects support
    • Added cyclops LineSet? class
    • Support for multilight shaders
    • Shadows can be enabled / disabled at runtime
    • Normals can be generated and / or normalized for loaded models
  • misc.
    • Added prepackaged binary build for windows (work in progress)
  • MissionControl?
    • Basic tool implemented
    • Basic statistics support

Comments

Post a Comment

Popular posts from this blog

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

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

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