Equalizer - Parallel Rendering

https://youtube.com/devicesupport From: YouTube Help Views: 301 0 ratings Time: 03:56 More in Howto & Style

co::ObjectFactory and using co::ObjectMap to add/update/remove shared object -- which I just realize is not exposed through the API in Sequel, even though the init and frame data objects are managed through this mechanism. Have a look at the aforementioned classes, and I'm happy to figure out an

Hi, I fully agree, and this has lead to Sequel which only has an Application and a Renderer class: [link] This is the idea behind Renderer and Application implementing co::ObjectFactory and using co::ObjectMap to add/update/remove shared object -- ... [More] which I just realize is not exposed through the API in Sequel, even though the init and frame data objects are managed through this mechanism. Have a look at the aforementioned classes, and I'm happy to figure out an API to expose the ObjectMap API. [Less]

Hallo, Its a GLUT-like wrapper that's based on Equalizer 1.0.2 and more specifically the eqPly example. It provides a very simple interface so you dont have to get into all the details of this amazing but quite complex framework thats called..Equalizer ! :) It has worked well in the past for realtime interactive graphics on various

hi, my main-application class inherits from eq::Client....when i shut down my application i get an heap error...both...in debug and in the release mode. It seems that it also happens when i generally access/use the namespace\class eq::Client.....dont know why.. Bye, User_FR -- View this message in context: [link]

Hello, about GLEWX, it seems that the official 1.9.0 tar ball from sourceforge (from 2012), and I think the one that buildyard is getting down have a missigng header guard: See [link]

Hi Petros, How does it compare to Sequel? ANy chance of merging the two? At this point I would really start using an external GLEW_MX library for both projects. FindGLEWMX in Equalizer should pick it up. I hope we're using the same version? These ... [More] macros really just 'jump into' the GLXEWContext struct to look up values. You can probably just examine this struct in your debugger. [Less]

Hi Stefan, Thanks for your prompt reply ! Just to give an idea the projects consists of Equalizer , openFrameworks, an in-house wrapper around Equalizer that makes Eq usage a bit simpler for our usual application cases ( it has been used for some ... [More] time and it works pretty well ) and finally now a second wrapper that I am writing that aims to bring [Less]

Hi Petros, Nice - finally! The GLXEW_FOO macros resolve into glxewGetContext()->foo, where the context is a lookup table to the function pointers and feature bools. This function has to be defined in the context you've got the macro, and resolve ... [More] to the correct GLXEWContext.... which you can't because I just realize it's never exported from eq::glx::Pipe. I'll look into it. [Less]

No one objected today so I will soon host our project on github. -- View this message in context: [link] Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com. ______________________________ _________________