The project that I’ve been working on at ThoughtShop is almost ready to show off. There have been a few interesting snags that I’ve run into while getting the project all set up on the hardware that’s going to end up in the showroom.
The main issue is the way the screens are set up. The project is running on 3 screens ( one of which is a touch scren ), which are all connected to a Mac Mini. The screens are all going to be mounted vertically, with the touch screen on the bottom. The touch screen is going to be showing some interactive stuff, and the top two screens are going to be showing a 3d model.
There are a few things about this project that I think are pretty cool.
The first is websockets, courtesy of SocketIO. The project is actually composed of three parts: a NodeJS backend, and two browsers that communicate via websockets. When a user touches certain parts of the interface, that browser sends events to NodeJS, which send those commands on to the other browser.
I’m a little in love with the SocketIO library. It has made working with websockets super easy, both in the browser and inside NodeJS.
The other thing that I think is really cool about this project is that there’s a 3D portion. I’ve been using the ThreeJS library for this portion. It’s been pretty awesome. It does a great job of abstracting away the nitty-gritty of the WebGL stuff.
I did run into one interesting problem on this project. Because the Mac Mini only has two monitor ports ( a mini Display Port and a HDMI port ), we had to use a Matrox DualHead2Go. This lets us connect two monitors to the mini Display Port on the Mini. Unfortunately, the only way to have those monitors show up is as one long monitor. This screws with the way that the browser opens up when it’s told to go fullscreen – it expands across both the screens.
This causes the model to split horizontally across the two screens – which is a problem, as the screens are stacked vertically.
So, I looked into a few solutions. The first one I tried out was rendering the scene using two cameras, and splitting up the rendering area using ThreeJS’s setViewport. Unfortunately, this caused a slight issue: the two cameras view’s don’t line up. Because they’re perspective cameras, the top of one camera won’t match up with the bottom of another.
Thankfully, there was another solution.
The cameras that ThreeJS offers has a setViewoffset method, which allows developers to take the view from a single camera and split it up so that it can be rendered in multiple parts. The code ended up being pretty simple. Take a look:
This saved my bacon. Hopefully it will help someone else.