I've only tried it in p3d. I tried it and got the same thing in P3d 5. Several stutters, and several very long freezes. Reverted back to That driver has never failed me.
I WILL in the near future try the new driver again. I've also deleted my P3d cfg and established a new one. I'll see if that makes a difference. There's been so many changes in the last few days with P3d, Active Sky, and the Hotfix that the new driver may have been the straw to break the camel's back. Perhaps cleaning up things like I mentioned might make a difference.
Yep as I suspected the latest driver is actually fine after investing a bit of time in doing it properly - proper DDU uninstall of old one, delete nvidia CP profile, delete and recreate p3d. I DID go back to the new driver, Everything now seems to work beautifully. I've made numerous flights both long and short, and the new driver has not caused any stuttering, pausing or freezing issues.
I delete shaders every day, apply Season Manager, and fly with Active Sky. I may be just "wanting it to be true", but it all works great now.
Time will tell, of course. You need to be a member in order to leave a comment. Sign up for a new account in our community. With the proper timing from the Vesa connector and 5v power from USB the emitter system has all the data it needs to be able to do it's thing in standalone mode.
I guess Nvidia thinks otherwise and purposely left this capability out. Well now I am ticked off. I could return it all for a refund but how long will that take and I just want to watch my own personally created 3d videos using stereoscopic player. No other 3d glasses are in stock right now anything with DLP link is sold out. I am a seasoned and experienced electronics engineer so I think I could make this work in stand alone mode despite the Nvideo anti-consumer approach.
Your diagram of the waveforms is exactly the info I need to move forward. I am prepared to hack my Nvidia emitter with a microprocessor if necessary. I know IR drive signals are easy to create with the correct timing parameters. So the question I have to ask you about your diagram is how did you measure these voltages currents? Any help or further clarification is greatly appreciated.
I think I figured out your diagram. The uS was throwing me off. I suspect this value of time could well be adjusted to "tune" the glasses to minimize ghosting.
Obviously the time between the two waveforms in your chart is dependent on the screen frequency. It doesn't really matter since I will pick up the screen timing from the DLP 3d Vesa 3 pin connector. It will let me experiment more until I'm ready to go to SW only with a processor. Well at least that's my starting point. I'll report back on my results. First, I used a photodiode with a pull-up resistor to get voltage change according to IR pulses. I updated the graph with these more precise timings.
The shutters doesnt shut off instantly after the command are sent, they take 2. I personnally do this to have the same color on left and right image on my 85Hz DLP projector. It also eradicate a light red ghosting I had with standard timings. Your timing chart worked perfectly!!
Thank you for posting it. I will now move to a uController PIC 12f The FPGA is impractical for a real solution but is great at being flexible in getting something working quickly. I also will experiment with timing. Right now I do a simple edge detect of the DLP sync signal and then start the timing sequence from your diagram. Next I want to do an internal DLL which will allow me to slide the timing back and forth around the sync signal.
I also want to experiment with the us both off timing. I'm kinda new to 3d. Any recommendations for a 3d test source for evaluating ghosting? I have some ideas but maybe the experts already have something? Thanks again for the info!
I programmed my Atmega8 in C, it runs currently on the internal 8Mhz oscillator, but i will upgrade my circuit with a 16MHz crystal to get more accurate timings. I program in Assembler for the PIC. I will probably do a simple fsm based on a timer count. I think I can get 3 uS resolution with this technique. Eventually when the timings are solidified I will permanently code them in. It has an internal osc so the hw is very simple.
I plan on putting it all into a FOB like infrared emitter with a 3. Power comes from the DLP so this is a pretty easy project I figure. The hard part is done thanks to your diagram. Could you please post the circuit? I also want to sync my 85hz DLP. Re: Hacking Nvidia 3DVision Post by Petrus » Thu Apr 29, pm As you can see, for the moment its just a bunch of wires that connects to different pins of the micro controller, no need of schematic for that.
The only interesting part would be the Comparator that converts the IR pulses from Nvidia's emitter to TTL voltage, here is the schematic : And the circuit board in the bottom is a TTL to RS level shifter i use it for debugging purpose.
I'm not very common with advanced stuff like micro controllers. I'm trying to sync my 85hz DLP projector. Make this for xp too. ShadowDuke , Apr 11, Nice writeup. At least some of the older drivers have nvts.
Prophet , Apr 11, ShadowDuke; no it wasn't by me. It was by a member who seemed to have an old deactivated account I think the named contained the word "Wolf"? I've never actually modded XP drivers, so if you do it or have done it let me know if I added the correct info. It does contain helpful screenshots though! You can find it in the lower section of the first post.
Nice work Now people have a tutorial on how to edit them Next time someone asks, i can guide him here Thanks Cyber. BetA , Apr 11, Even though i recently found out how to do this myself this is a great guide which will be used alot, Well done Cyberdyne.
Veteran , Apr 11, I added some supplementary pictures. Anything else I should add? Veteran , Apr 12, Yeah, that is what motivated me to simply put the individual list's of strings and device ID's on pastebin, and tell you what to search, what to copy, and where to paste it while using myself as an example.
0コメント