Original Post

Just wanted to give you guys a heads up that Alberto updated his site ( http://www.emuunlim.com/VirtualE/ ) with a demo of VEGL (OpenGL rendering to the VB over a link cable). It’s pretty slow at the moment, but the compression that he is able to get is pretty impressive, and still has room for improvement… so hopefully he’ll be able to optimize it more in the future and get reasonable frame rates.

DogP

5 Replies

Wow! Alberto has done a lot to advance the VB dev scene, and I’m glad to see his return as well as a major goal of his coming to fruition.

I’m sure it’ll be doing 50 fps stereo in no time! WOOT! πŸ˜€

I already have a cable (mostly) built, too. 😎

/me wants virtual autocad, for my sleepless architecture-student nights.

Heh, 50 FPS might be a dream for the current system. I modified it to use my USB link adapter (it does about 3-5 FPS) using the link about 1/3 of the time (and VB processing the other 2/3). So even doing no processing, it’d only get ~9-15 FPS. But he may be able to do other optimizations to bump that up.

But even at just a few FPS, that’s is really cool that you can render 3D stuff on the PC and view it in 3D on the VB.

DogP

i can only agree to runnerpack, it’s really great to have him back. πŸ™‚ i am looking forward to to all the new stuff coming, i will probably wait for an usb version of veGL before i build a cable.

I thought I’d take a stab at the math:

On IRC, DogP quoted the link at 235 Kbit/sec, sustained.

One VB screen = 384 * 224 * 2bpp / 8 bits = 21,504 bytes

21,504 * 2 screens * 50 fps = 2,150,400 bytes/sec

2,150,400 * 8 = 17,203,200 bits/sec

17,203,200 / 235,000 = 73.205106 times the link port bandwidth.

That’s quite a compression ratio to shoot for…

I don’t think RLE is gonna cut it πŸ˜‰

(BTW, I know VEGL doesn’t use RLE; it was a joke :-P)

 

Write a reply

You must be logged in to reply to this topic.