Question for Genius Tablet users

[jpbouza]

has anyone managed to recreate the stylus trick with the new FDI file in Intrepid or in Jaunty??

For those who doesn´t know, there was a trick that consisted on renaming the wizardpen driver to ¨stylus¨ in the Xorg.conf file. That made Blender think that you had a stylus and it detected the tablet´s pressure sensitivity.

Unfortunately, with the new Xserver, the parameters of the tablet are defined in an FDI file, and I don´t know if it is possible to get the trick working with it.

[Felix_Kütt]

the new 'buntu uses HAL(HID?) I believe witch is why it might not work.

that is all I know, though.

[N30N]

I made a FDI file the other day to get my new Wacom tablet working with hot plugging. The following is the rule you'll need to get blender to recognize your tablet (I assume you know how to make the match rules).

<merge key="info.product" type="string">stylus</merge>

[jpbouza]

N30N you're a Genius!! I added your line and it worked!!!

Here's my FDI in case anyone has the same problem:

<?xml version="1.0" encoding="ISO-8859-1" ?>
<deviceinfo version="0.2">
<device>
<!-- This MUST match with the name of your tablet -->
<match key="info.product" contains="UC-LOGIC Tablet WP5540U">
<merge key="input.x11_driver" type="string">wizardpen</merge>
<merge key="info.product" type="string">stylus</merge>
<merge key="input.x11_options.SendCoreEvents" type="string">true</merge>
<merge key="input.x11_options.TopX" type="string">5619</merge>
<merge key="input.x11_options.TopY" type="string">6554</merge>
<merge key="input.x11_options.BottomX" type="string">29405</merge>
<merge key="input.x11_options.BottomY" type="string">29671</merge>
<merge key="input.x11_options.MaxX" type="string">29405</merge>
<merge key="input.x11_options.MaxY" type="string">29671</merge>
</match>
</device>
</deviceinfo>




Thanks a lot!!

[Lamoot]

I bought a tablet a few days ago and I'm having similar problems on Linux, in GIMP it works fine but not in Blender. I read your guides but I'm bit confused what exactly to include in the fdi file, where do I put my tablet's name and similar.

Can anyone help me writing the text I need to include in the file? My tablet is a "Wacom Intuos3 6x8" as it's recognized by GIMP.

[N30N]

Originally Posted by Lamoot Can anyone help me writing the text I need to include in the file? My tablet is a "Wacom Intuos3 6x8" as it's recognized by GIMP.

The FDI file I linked to above should work fine (no modifications needed).

[Lamoot]

I made a file containing the text you posted. I named the file cutom_wacom.fdi and put it into /etc/hal/fdi/policy folder. Still, it behaves in Blender as a regular mouse, no pressure sensitivity or anything like that.

In GIMP I only had to set the tablet in the preferences again and then it worked properly.

Am I missing something here?

Here's the text from my custom_wacom.fdi file

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
    <device>
        <match key="info.capabilities" contains="input">
            <match key="input.x11_driver" contains="wacom">
                <match key="input.x11_options.Type" contains="stylus">
                    <merge key="info.product" type="string">stylus</merge>
                </match>
                <match key="info.product" contains="eraser">
                    <merge key="info.product" type="string">eraser</merge>
                </match>
                <match key="info.product" contains="pad">
                    <merge key="info.product" type="string">pad</merge>
                </match>
                <match key="info.product" contains="cursor">
                    <merge key="info.product" type="string">cursor</merge>
                </match>
            </match>
        </match>
    </device>
</deviceinfo>

[Michael W]

Originally Posted by Lamoot I made a file containing the text you posted. I named the file cutom_wacom.fdi and put it into /etc/hal/fdi/policy folder. Still, it behaves in Blender as a regular mouse, no pressure sensitivity or anything like that. In GIMP I only had to set the tablet in the preferences again and then it worked properly. Am I missing something here? Here's the text from my custom_wacom.fdi file <?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="info.capabilities" contains="input"> <match key="input.x11_driver" contains="wacom"> <match key="input.x11_options.Type" contains="stylus"> <merge key="info.product" type="string">stylus</merge> </match> <match key="info.product" contains="eraser"> <merge key="info.product" type="string">eraser</merge> </match> <match key="info.product" contains="pad"> <merge key="info.product" type="string">pad</merge> </match> <match key="info.product" contains="cursor"> <merge key="info.product" type="string">cursor</merge> </match> </match> </match> </device> </deviceinfo>

It's temperamental on mine too.... Often it works fine if the tablet is already plugged in when booting up but not after hotplugging.....

sometimes it just doesn't seem to work...

[Lamoot]

It's temperamental on mine too.... Often it works fine if the tablet is already plugged in when booting up but not after hotplugging..... sometimes it just doesn't seem to work...

Ah, rebooting solved the problem

Thank you both for your help.

[N30N]

Originally Posted by Lamoot I made a file containing the text you posted. I named the file cutom_wacom.fdi and put it into /etc/hal/fdi/policy folder. Still, it behaves in Blender as a regular mouse, no pressure sensitivity or anything like that. In GIMP I only had to set the tablet in the preferences again and then it worked properly.

I assume since you had to reconfigure GIMP, the product was identified as a stylus (you can also check with lshal | grep stylus).

Originally Posted by Lamoot Here's the text from my custom_wacom.fdi file

Providing that was a bit redundant don't you think?

Originally Posted by Michael W Often it works fine if the tablet is already plugged in when booting up but not after hotplugging.....

Sound's like you didn't even remove the device from your xorg.conf? I can unplug and re-plug mine all day with no problems.

Try your distro's forums for more support (It's easier to track do the problem when you running the same old stuff).

Edit:

Originally Posted by Lamoot Ah, rebooting solved the problem

[Michael W]

Sound's like you didn't even remove the device from your xorg.conf? I can unplug and re-plug mine all day with no problems. Try your distro's forums for more support (It's easier to track do the problem when you running the same old stuff). Edit:

Nope, it's not in xorg.conf

Any other program that supports pressure works fine with me hotplugging, (eg gimp,mypaint, anything run under wine, inkscape..)

Only blender doesn't work after a hotplug.

Distro forums are no use as this is a specific blender problem

lshal | grep stylus gives

michael@michael-lumiere:~$ lshal |grep stylus
  info.product = 'stylus'  (string)
  input.x11_options.Type = 'stylus'  (string)
michael@michael-lumiere:~$ A

checking with xsetwacom list dev -->

michael@michael-lumiere:~$ xsetwacom list dev
stylus           stylus    
pad              pad       
cursor           cursor    
eraser           eraser    
michael@michael-lumiere:~$

weird that they show up twice.. i guess its "type" and "identifier"....

The devices show up properly in wacomcpl..... (one entry for each)

I'm using ubuntu 9.04 64bit....

Can't find anything on the ubuntu forums specific to blender....


Running blender under wine will always work, just native that doesn't after hotplugging...

It MUST be a blender issue... I wish it could be configured like gimp, that way I could use multiple sylii with different settings...

[N30N]

Originally Posted by Michael W Running blender under wine will always work, just native that doesn't after hotplugging...

I haven't been able to reproduce this so far, perhaps you can provide specific steps to reproduce this?. I'm using the latest SVN of blender and the CVS of the linuxwacom drivers so maybe it's already been fixed up stream.

Originally Posted by Michael W Distro forums are no use as this is a specific blender problem

Indeed, sorry I misunderstood your problem before.

[Michael W]

I'm also using latest SVN of blender but using the wacom drivers from the repositories...

EDIT: maybe i should just try thelatest drivers ;-) EDIT

It seems it might not be blenders fault after all...

I've just found out that the repository version puts an .fdi for wacom at

/usr/share/hal/fdi/policy/20thirdparty/10-wacom.fdi

this must be conflicting with the other one at

/etc/hal/fdi/policy/custom_wacom.fdi


the "third party" one looks like this:

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->

<deviceinfo version="0.2">
  <device>
    <match key="info.category" contains="input">
      <match key="info.product" contains="Wacom">
    <merge key="input.x11_driver" type="string">wacom</merge>
    <merge key="input.x11_options.Type" type="string">stylus</merge>
        <append key="info.callouts.add" type="strlist">hal-setup-wacom</append>
        <append key="wacom.types" type="strlist">eraser</append>
        <append key="wacom.types" type="strlist">cursor</append>
        <append key="wacom.types" type="strlist">pad</append>
      </match>
      <match key="info.product" contains="WALTOP">
    <merge key="input.x11_driver" type="string">wacom</merge>
    <merge key="input.x11_options.Type" type="string">stylus</merge>
        <append key="info.callouts.add" type="strlist">hal-setup-wacom</append>
        <append key="wacom.types" type="strlist">eraser</append>
        <append key="wacom.types" type="strlist">cursor</append>
        <append key="wacom.types" type="strlist">pad</append>
      </match>
    </match>
    <match key="info.capabilities" contains="serial">
      <match key="@info.parent:pnp.id" contains_outof="WACf001;WACf002;WACf003;WACf004;WACf005;WACf006;WACf007;WACf008;WACf009;WACf00a;WACf00b;WACf00c;FUJ02e5">
        <append key="info.capabilities" type="strlist">input</append>
        <merge key="input.x11_driver" type="string">wacom</merge>
        <merge key="input.x11_options.Type" type="string">stylus</merge>
        <merge key="input.x11_options.ForceDevice" type="string">ISDV4</merge>
        <merge key="input.device" type="copy_property">serial.device</merge>
        <append key="info.callouts.add" type="strlist">hal-setup-wacom</append>
        <append key="wacom.types" type="strlist">eraser</append>
        <match key="@info.parent:pnp.id" contains_outof="WACf008;WACf009">
          <!-- Serial tablets with touch capabilities -->
          <append key="wacom.types" type="strlist">touch</append>
        </match>
      </match>
    </match>
    <!-- N-Trig Duosense Electromagnetic Digitizer -->
    <match key="info.product" contains="HID 1b96:0001">
      <match key="info.parent" contains="if0">
       <merge key="input.x11_driver" type="string">wacom</merge>
       <merge key="input.x11_options.Type" type="string">stylus</merge>
      </match>
    </match>
  </device>
  <!-- Match the Wacom Bluetooth A5 pen tablet -->
  <device>
    <match key="info.capabilities" contains="input.mouse">
      <match key="info.product" contains="WACOM">
        <match key="info.product" contains="Tablet">
          <merge key="input.x11_driver" type="string">wacom</merge>
          <merge key="input.x11_options.Type" type="string">stylus</merge>
          <append key="info.callouts.add" type="strlist">hal-setup-wacom</append>
          <append key="wacom.types" type="strlist">eraser</append>
          <append key="wacom.types" type="strlist">cursor</append>
        </match>
      </match>
    </match>
  </device>

</deviceinfo>

/etc/hal/fdi/policy/custom_wacom.fdi


My custom looks like this:

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
    <device>
        <match key="info.capabilities" contains="input">
            <match key="input.x11_driver" contains="wacom">
                <match key="input.x11_options.Type" contains="stylus">
                    <merge key="info.product" type="string">stylus</merge>
                </match>
                <match key="info.product" contains="eraser">
                    <merge key="info.product" type="string">eraser</merge>
                </match>
                <match key="info.product" contains="pad">
                    <merge key="info.product" type="string">pad</merge>
                </match>
                <match key="info.product" contains="cursor">
                    <merge key="info.product" type="string">cursor</merge>
                </match>
            </match>
        </match>
    </device>

</deviceinfo>

Now, I need to know how to merge the two because if I replace the 3rd party one wholesale I get no buttons, and the stylus moves in relative mode rather than absolute, and obviously If I remove the custom one I get no entries in wacomcpl or "xsetwacom list dev"... edit... i get no entries in wacom cpl using either file on its own, it only works with both files... edit

I'm guessing the smart thing to do would be to add buttons and absolute mode to the custom file?....

... or should I be looking to just merge the two together completely?

It's still strange that the two fdi files only cause an issue with blender pressure sensitivity and no-where else....

[basse]

it's a problem of naming the devices .. sadly, i don't know enough about it, but seems like actually it's not xorg (or ubuntu) bug, but more like programs that are using the devices.
gtk apps for example work fine, but qt and blender don't because they are getting the names xorg provides, and not the actual device names. or something like that.
search for for jaunty+qt+wacom for more information.. i actually posted bug report of it..

.b

[Michael W]

Originally Posted by basse it's a problem of naming the devices .. sadly, i don't know enough about it, but seems like actually it's not xorg (or ubuntu) bug, but more like programs that are using the devices. gtk apps for example work fine, but qt and blender don't because they are getting the names xorg provides, and not the actual device names. or something like that. search for for jaunty+qt+wacom for more information.. i actually posted bug report of it.. .b

Interesting!

I'm sure it could be fixed "blender side", by adopting however GTK do it.. It looks like it's fixed in QT...

I just don't get why it works "sometimes"... makes me cling to a hope that it can be resolved by me......

[N30N]

Originally Posted by Michael W I've just found out that the repository version puts an .fdi for wacom at /usr/share/hal/fdi/policy/20thirdparty/10-wacom.fdi this must be conflicting with the other one at /etc/hal/fdi/policy/custom_wacom.fdi

Multiple FDI file's shouldn't be a issue. To make sure repeat the steps needed to stop it working with blender, then check if lshal | grep stylus matches what you posted above and if it dose then FDI files are not the cause of the problem.

Originally Posted by basse gtk apps for example work fine, but qt and blender don't because they are getting the names xorg provides, and not the actual device names. or something like that.

The whole point of this thread was about getting hal to rename the devices, thus fixing your issue. I just installed pencil (a qt application) and again had no problem with hot plugging.

Originally Posted by Michael W It looks like it's fixed in QT...

Yup, next version.

[Michael W]

Originally Posted by N30N Multiple FDI file's shouldn't be a issue. To make sure repeat the steps needed to stop it working with blender, then check if lshal | grep stylus matches what you posted above and if it dose then FDI files are not the cause of the problem.

..Hmm, then it's not an FDI problem (that output WAS from when it's not working

that said, i have a tablet PC (ok, so you can't hotplug that) It works consistently, but I did have to use the latest driver from linuxwacom as it's a USB touchscreen rather than serial...

I'l try the latest drivers tomorrow!

[psychotron]

Hi,

I have genius mousepen tablet running with 'wizardpen' driver on ubuntu 8.10
I add 'stylus' line to FDI file

but I have problems with buttons and pentip assignment
when I click stulys button or touch tablet surface it's still behave like middlemouse click and I'm always rotating whole scene
for example pentip is also behave like leftmouse click at the same time...

what's wrong?
where can I assign tablet button/pentip?

[jpbouza]

I don´t know....That happened to me in Hardy (8.04) and I could never fix it. I found a way to make it work in blender that consisted on pressing ALT while drawing, and I think that I had to disable the "emulate 3 buttons mouse" option too.

Anyway, that is solved in Jaunty...

I´m not sure if it was an Ubuntu issue or a driver issue...Did you download the latest driver 0.7.0 alpha 2???? Maybe you have alpha 1.

I made a tutorial on getting the wizardpen working on jaunty, you can check it out here

[Michael W]

try here...
http://digitalbluewave.blogspot.com/...epid-ibex.html

It's for your version of ubuntu.
i'm not a genius tablet user, so it may not help. I never used this guide