Viewports

• multiple views on the same scene in one renderer
• each viewport can have its own transformations
• all rendering is done per viewport, not graphevaluation!
• applications: side-by-side stereo, quadview (left, top, bottom, free), show details of scene
• ViewPort Transform, Transformations Index, Crop Transform
• display different stuff in different viewports
• via shader: VIEWPORTCOUNT, VIEWPORTINDEX

DirectX Devices

• memory of textures/meshes is allocated per device (doubled memory use on single card if in dualview)
• VideoTexture (EX9.Texture) only runs on one device!

• span mode: one dx-device spanning multiple monitors
• dual view: one dx-device per monitor

• Device (EX9 Auto)
• /dda 1

Camera Perspective

• as long as 2d content, never mind
• with 3d content perspective is important
• every projector cannot have its own perspective
• the whole view must be one spectator-perspective
• it only looks correct for the spectator from one point
• compare cave (headtracking) also only correct for one position!
• scene has to be rendered with one perspective
• throw it back onto a virtual replica of the screen
• view it again from the virtual perspective of the real projector

• perspective problems
• with very wide views (unrealistic distortions on the sides)
• special case t-gallery: perspective not per projector, but per object
• with circular views

• spectator vs. projector

MultiScreen Renderer Setups

• Multiscreen (EX9)
• Softedging
• from one graphic card
• dual/trippleheads
• from multiple graphic cards
• from multiple PCs
• boygrouping

Boygrouping

• demos
• egosoccer
• lufthansademo
• tgallery
• bmw how-to-project-on-3d-geometry?

• commandline parameters
• Boygroup (Network Client)
• Boygroup (Network Server)
• bridges
• bangs, lfos, dampers

• debugging on clients
• multiboygrouping
• RemoterSA
• vnc

1. laptop (projektor)
2. 1 pc (projektor) + tripplehead + 3 monitore
3. 1 server (projektor) 2 clients (je 2 monitore)
4. 1 client (projektor) 2 server