Ok, your license key is now confirmed as activated. This can take up to 10 business days, and i am not in control of that process, so always good to have a valid paid membership available instead of buying it the moment you need support.
Unfortunately there was a long gap of multiple months since you asked for support first until you bought a paid membership, and my memory is not that good, so i had to reread all your posts and reacquaint myself with the issues, starting at zero. Long story short, this has already used up 52 minutes of work time, 22 minutes more than paid for by your purchase, so even before me giving any answers, we are already out of time for this.
I’ll give you 8 more minutes of my time, otherwise you’d have to buy an extra hour packages for 300 Euros + sales tax for every started batch of 60 more minutes of work time, ofc. with no guaranteed success - you pay for my time trying, not for successful resolution of the issue. As your lab doesn’t have any long-running support membership, you are unfortunately also not eligible for a discount.
Nothing obvious stands out in your posts so far that would point to a clear reason for the problems, but lets go on hunches:
I need full output for all machines tested, both the 18.04-LTS, the working 20.04-LTS and the non-working 20.04-LTS.
What is the full output of the .local/share/xorg/Xorg.0.log
on the two Ubuntu 20.04 LTS machines? I think /var/log/Xorg.0.log
would be the right location on Ubuntu 18.04 if there isn’t a Xorg.0.log at the same location as on Ubuntu 20.04. My own last 18.04 machine died a few weeks ago, so i can’t test on 18.04 anymore…
What is the full output of the xinput list --long
command in a terminal on all machines?
What is the full output of PsychHID('Devices', 3)
and separately for PsychHID('Devices', 5)
?
The way joystick queries in Psychtoolbox work, is to treat them as special “weirdo” mouse devices instead of using the low-level kernel joystick driver that is used by the jstest /dev/input/js0
command. This because it saves a lot of extra implementation work for myself and as a bonus allows us to use all the keyboard queue features we have for keyboards and mice also for joysticks, e.g., automatic timestamped recording of button presses or axis value trajectories.
So we know that your grip devices get correctly recognized and handled by the kernel due to the successfull jstest, but something seems to go wrong on some machines on the way from kernel through X-Server to PsychHID. Although i don’t have a clue yet as to what that would be.
[52 minutes used of 30 minutes paid - Membership license more than used up]
-mario