Omegalib 4.0 released

-
This is the first release in the omegalib 4 series. This series driving feature is the support for multi-instance / multi-view immersive applications.

Notes

Sound API changes All sound paths in applications need to switch to use relative paths. 
This version adds auto-update support for windows. The omegalib windows binaries are pulled from https://github.com/febret/omegalib-windows

Major Changes

omega
  • Added Color from omicron. Added Color.isValidColor
  • Added per-tile runtime camera controls: isHostInTileSection, setTileCamera.
  • pointerSize config option
  • Automatic multi-instance port adjustment for NetService
  • on the -I multi-instance switch, the port pool can be left unspecified. It will be set to 100 by default.
  • 4.0.2: omegalib can built using an external omicron installation
  • 4.0.2: python interpreter now does module lookups in the current script directory.
  • 4.0.2: fixed performance issue with SceneNode bounding box on-demand update.
  • 4.0.2: Extended Actor class is now derivable from python to create custom scriptable actors.
  • 4.0.2: Added global hitNode function for simpler node/ray intersection testing.
  • 4.0.2: Added windows auto-updater
  • 4.0.3: Added config support for inverted stereo (see invertStereo in ConfigReference)
  • 4.0.3: Added run flags to control PythonInterpreter.runFile
  • 4.0.3: FIX script running with relative paths was broken.
  • 4.0.4: Fixed inverted stereo
  • 4.0.6: Fixed keyboard/mouse camera orientation issue
cyclops
  • Major revision of the Material API. Materials have a lot more properties and flags. Multiple material layers can be added to an entity, without having to use the setEffect string. setEffect is not just a shorthand version of adding material layers to an Entity.
  • 4.0.1 FIX incorrect handling of -t transparent effect flag.
  • 4.0.1 FIX material state issues (issue #11)
  • 4.0.5 Material setlit, getLit (only working for fixed-function pipeline materials)
  • 4.0.5 FIX Text3D color issues
omegaToolkit
  • 4.0.2 Improved widget creation python API.
omicron
  • Improved sound asset management: sound assets now get copied automatically to the sound server.
  • NOTE FOR APPLICATION DEVELOPERS All sound paths in applications need to switch to use relative paths.

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