Try setting param to 0xE000:
u16* const param = (u16*)0x0000E000;
Also,
I think the first parameter of affineRotateZ is supposed to be the address of the parameter table, not the number of the world.
affineRotateZ(param, ITOFIX7_9(1), ITOFIX7_9(1), 384, 224, 0, 0, 45);
But, since the param address stored in the World attributes has to be:
(addr - 0x00020000) >> 1
where “addr” is the address in VB space, and since I don’t know what Jorge’s PARAM macro does, you might have to tweak those. But, I’m pretty sure it’s the address of the table that’s at fault.
Also, is it really “rotateZ” that you want? Your mockup looks more like a rotate around the X axis…
EDIT: Turns out it’s actually the libgccvb PARAM macro and all it does is mask a value and add it to the base of the parameter table. So, basically, affineRotateZ wants the actual param table address, but the World attributes want the one as calculated above.
So just…
//...change: WORLD_PARAM(31, (u32)param); // to: WORLD_PARAM(31, (u32)((param - 0x00020000) >> 1));
and the call to affineRotateZ and that should work.
Based on the information here, I’d say all you have to do is display vertically sync’d, page-flipped images and it should work.
There may be some signal required to turn on the 3D mode (which would require an additional cable; likely USB) but since a normal image wouldn’t look “weird” with the magical “re-polarizer” active, even with the glasses on, I’m guessing it’s always on (or has a manual button on the front).
The “driver” is probably just to tell the 3D card to start producing said page-flipped image stream, which would then automatically be in 3-D.
Of course, this is all conjecture on my part having never seen one up-close…
About the anaglyph glasses:
I think you’re right, DogP. I tested them side-by-side and the Y+B ones have a touch more cross-talk (another word for ghosting) but slightly less retinal-rivalry (which is when the contrast and/or brightness of the two images are noticably different).
However, I stumbled on a nice trick:
Since the cross-talk problem is caused by the cyan lens on the R+C glasses letting red though, and by the yellow lens on the Y+B ones letting blue through; I tried combining the two glasses; the red lens from the “Sports Illustrated” glasses and the blue lens from the superbowl glasses. I looked at the Red+Blue image.
It practically eliminated both cross-talk and retinal-rivalry!
Since I have multiples of both, I think I’m going to cut some up and make some “franken-glasses” 😀
I’ve attached my test image below. The middle is Green+Blue and doesn’t really work at all 😛 (Although it would work with Green+Magenta glasses…)
Attachments:
Like realyst says, more pictures are needed.
To that end, I’ve attached a pic (excuse the webcam quality) of all the parts of the clamp (with the legs removed).
If you have all of them, just put them together in alphabetical order and it should work.
It should not be possible to separate the clamp pieces that far without removing the cap nut (F) from the bolt (A), which are clearly both there and attached in your pic. Something’s probably broken or missing.
Without seeing the other side, it’s hard to tell what’s going on. By looking at mine and comparing it to what I can see of yours, it looks like either the spacer (B) is missing or there’s something wrong with the bolt (A).
I hope that helps.
