3Dconnexion Forum

No problem Josh, Apology for not returning the post earlier - worked 48 h during this weekend... Anyway - I browsed quickly through the code. During the quick fly-over I could not see things like (simplified for the message) TDx.TDxInput.Device myMouse3D; TDx.TDxInput.Keyboard myMouse3DButton; TDx.T...

Ah ... warranty, shmarranty ... gimme the hammer

Got it - this closes the thread.
Thanks JWICK!

Hi Omniflux, Sorry for the late response - just did not have a chance to get to my mailbox. I will definitely try the ideas. In the mean time JWICK also helped me resolve some other problems which were resolved. For whatever it is worth these are the two postings - Differentiating between Roll and S...

Just in case - This case has been resolved.
Some of the resolution is also mentioned in another post of mine (also closed):
"Differentiating between Roll and Spin"

Markus - many most sincere thanks.

Thanks JWICK Works like a charm. Due to the different approach I had to rewrite the entire joystick handling - but the good news is that with your unit now the coding is much simpler and faster. I still maintain that there is a large market for users wanting the unit to register as joystick out of t...

Great - will check as soon as I get to a dev PC
Many thanks Jwick!

in addition to the above. Here a sample situation. When you zoom (Tz) and push the unit forward you may (depending on how careful you are holding it) get noise components which are both as Roll Forward and/or Spin. To handle the intention correctly and prevent the camera from faithfully representing...

It is the C# sample you posted. It does not look like there is a bug in it though - looks fine: Tx.Text = sensor.Translation.X.ToString("#.######"); Ty.Text = sensor.Translation.Y.ToString("#.######"); Tz.Text = sensor.Translation.Z.ToString("#.######"); Rx.Text = senso...

Did anyone program something beyond the C# example given here? If "yes" will appreciate any tips on the following It appears that the Spin and Roll Forward/backward are registered with the same output parameter - in the C# example it is given with "Ry". The only visible different...

Hey ... again on the weekend ... huh ... :) But ... you NAILED it! All running fine off my x64. I can bet money that the fix is the same for my x32 reported issue. To return the favor I will not stop at "Thank you man" ... :) Now - for the rest of the interested - here the summary one more...

Hi JWICK,

Last time you worked over the weekend. Just to mention here - have your weekend
I am hoping somebody else will be able to cover today. If not then we talk again Monday.

So far JWICK helped establish that there is a problem compiling a C# proect with this DLL on a x64 OS Now I find the same problem (slightly different message) also on x32 ... So - what am I doing wrong - Any tips will be appreciated: The following happened on BOTH XP Prof x32 as well as on XP Home x...

Hi JWICK,

No rush on this one - but to help me plan my dev cycle - any estimate on when do you see this problem fixed?

Many thanks and Happy New Year!

Yep - we are on the same page. I will try to play in the mean time with the RBC9 driver offered on this forum. Downloads are (to the best of my info) on rbc.duckinegg.com Anyway - I think the management of development 3DConnexion must be having headaches by now from all the noise around the Joystick...

You are right - Thank your very much for pointing this out. I should have been more explicit. I meant I would not mind paying a reasonable fee to the company for a product developed and supported by them - i.e. They include a "standard" version for free but want some sort of payment for th...