How might the projected image be best locked to the gameboard?

mikew

I'll ask this here as I have one of the earliest beta kits and the performance may be related to that.
Anyway, is there a way to improve how the projected image 'locks' to the board?

Using Spacedog's excellent DX266 demo as an example, the scrolling text at the start and the 'recube' logo that's in the lower right corner during the demo move around a fair bit with respect to the board.
In the video that Spacedog posted from the event he attended, the image looks a lot more stable, so there should be room for improvement in my setup.

Now, I'm using an Intel Gen8 i7NUC with integrated graphics, but the effects in the demo seem to be rendered smoothly and I thought the reprojection was mostly handled locally in the glasses.

While I'm now running with the Rev15.1 installation, this has been a bit of issue all along.

mikew

Thanks for the answer!
I've tried other programs with a more powerful PC and haven't really seen much of a difference, but don't think I've tried DX266. I'll do that when I get back to one next week.
The NUC is good enough for most of my computing needs, but when I need some extra GPU ooomph for VR for example, I just connect it to an eGPU (Radeon 5700) over Thunderbolt 3 which works quite well.
I'm not sure if an eGPU this is ideal for T5 though, as it entails a 2-way trip to the GPU which is sitting on the end of a cable.

EDIT: Looks like I'm replying to myself, but I'm pretty sure I pressed the 'Reply' button under Spacedog's post....

Spacedog

hi mikew, thanks for trying the demo

I wrote it using rev14.1 of the T5 sdk, and made my own script for board locking objects. I made a gameobject called 'boardscale' and initialized it's transform to the origin location and scale of the game board, then altered it's transform position scale rotation inversely to any movement of the game board in runtime, any child of this 'boardscale' object will appear locked to the game board. since rev15, objects childed to the game board itself will behave the same for position and rotation, but not for scaling, this is a more intuitive way of doing this going forward, T5 need to add scale to the code there still.

regarding performance, DX266 needs at least a Nvidia GTX 980, or AMD R9 390 graphics card, the video from deadline was recorded from my laptop that uses a GTX 1060, the Gen 8 Nuc is really good computationally, but GFX might not update fast enough to deliver the frames to lock everything down, reprojection can do lots but it not a magic bullet, I'd recommend you try it on a gamer PC and see it it's improved any. even with the best hardware you can break the effect if you try to by shaking your head at juuuuust the right speed to confuse the IMU, but generally the head tracking is solid for normal natural use