Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - MyYz400

Pages: 1
Other / Re: pulsed (pwm) leds?
« on: August 07, 2008, 05:08:26 PM »
Well I have to agree with 'inio'.  You wont save power.  LEDs draw VERY little power as it is.  The LEDs I use draw 100mA, which is about average for a typical LED.  If you were to PWM the LED, and say you ran it at 50% duty cycle, you'd use equivalent of 50mA to power the LED, yes.  However all the support electronics needed to run the LED, you'd be using 120mA just for that, no including the LED.  So yes your LED is only drawing 50mA now, but the device as a whole will be drawing quite a bit more. So even if you were to build a device that were able to draw less then 50mA, with a 50% duty cycle LED.  You'd be hard press to be really saving that much battery.  I think it would be cheaper, easier, and more space effective to use larger batteries.


I have somewhat of the same problem.  I'm running mine on a 46" 16:9 LCD (1080 res).  I still get 90+ FPS using my onboard video card, however your problem seems like mine.

When you move side to side very slowly, the image pulls away abit (almost like you took a step back) then would "POP" forward again.  Almost like a pulsating motion.  I posted this problem a few days ago in the other forum, however no one seems to know the problem.

And I'm not too sure the "Screen Height" is or should be in pixels.  It should be the physical distance of your screen.  Running on a 14" laptop screen, or in your case a HTP, regardless of resolution, should render different results.

I'm installing C on my comp at home, and taking a look at the code.  I think the calculations could be changed a bit.  I might make a small app that helps with the setting up of the config.DAT file (for those who find it difficult to understand what to input).  I want to add a few more variables to allow for a finer defined setup.

Wiimote Desktop VR/Head Tracking / VERY jerky, inaccurate head tracking
« on: August 04, 2008, 07:36:37 PM »
Ok, I've connected everything, got everything, built my IR glasses (just like johnny lee's).  I have the sample app running, all is good.  However, the screen jerk BAD.  Not as in frame rate jerky, more like pulsates.  I think the IR LEDs are "in-between" pixels which makes the program think that my head is further away by a bit, then it "pops" to the next pixel on the cam, and then it thinks i'm closer to the screen.  More or less, too strict of calculations. 

Do other people have this problem?  Has someone worked out a fix for this?  The "popping" of the screen really makes you loose the "feel" of 3D.

Also, I measured and config'ed the config.dat for my TV (which runs off the computer).  Everything in the config.dat is correct for my environment, however it just doesnt look like johnny lee's.  Could the crappiness of the YouTube video hide all these things?  Or did I do something wrong?


Pages: 1