#Tablet Problems in R3
18 messages in this thread
I have a Numonics Master Grid that I am using in SUMMA mode. In R3
the pointer always seem to get caught in the middle. This problem
multiplies it seems when I have a system running as a slave out on my
network. The problem isn't there if I hook up a mouse. (This
problem would sometimes happen in R2, but disappeared after I added
more memory.) In R3 it makes the tablet completely unusable as a
pointer. One event that always triggers this catch, to the point
that I need to reset my tablet, is using the slider selection bars.
Is this a bug in the program or is there something I am not setting
up correctly?
Our tablet code works very well with Summa devices, and that's all I
can guarantee. For non-Summa devices doing emulation, it depends
upon how well their emulation works. You might ask them if they've
got an ADI 4.1 (not 4.2) DGP driver for their tablet, specifically
for 3DSr3.
The reason why the problem multiplies when you've got a slave running
is because your NET POLLING is happening too often. Turn that
parameter way down in your 3DSNET.SET file and it should help it
considerably.
I have the exact same behavior using a Kurta XGT (in Summa emulation
mode). I gave up for a while as I haven't found the time to chase the
problem down. John Tissavary has the same tablet (Kurta) and,
apparently, everything works fine (I haven't heard him complaining
about it which, for sure, means it works <g>). In my case, I just
turn the tablet off and on and it goes back to work for while.
I would complain, but I don't use summa emulation mode, I use mouse
mode. I tried Summa emulation mode and it was definitely freaky, and
somehting I'm not EVEN considering tinkering with untill I get net
rendering flawless.
Calcomp Drawing Board II's Summa emulation mode doesn't work with 3D
Studio either. Does anyone actually write ADI drivers for 3DS to
work with tablets?
Ian.
..Does anyone actually write ADI drivers for 3DS to work with tablets?
R3's built in SUMMA support is MUCH more solid than R2's was. Also, I have
heard talk that Summagraphics is developing a new 3DS ADI driver for their
tablets to eliminate a few glitches.
Wish I could get my Calcomp to work…sob.
Me too, my Calcomp 33360 dbII does make a nice mouse.
Dennis
Maybe R4? How 'bout it Yost group?
Anyone can write an ADI driver — including the manufacturer of the tablet. No
need to wait for R4, just bug the tablet people.
– Jack
I'm trying, I'm trying! I don't think Calcomp thinks that there are enough
users to justify writing a driver just for 3DS. Why is it that ADI drivers
that are written for Autocad do not work for 3DS. What's the point of having a
universal driver interface if a separate driver has to be written for each app?
When I bought the tablet, I thought…no problem…everyone has ADI drivers;
little did I know that they only work with Autocad. Would you consider
adjusting 3DS so that we could ride the Autocad wave and use their drivers?
Ian.
>> Anyone can write an ADI driver…
He, he, he… Yeah, right! <g>
Gus:
>> >> Anyone can write an ADI driver…
>> He, he, he… Yeah, right! <g>
Quit picking on Jack! I'm sure he ment write _about_ an ADI driver – he is
the documentation guru, after all, not the programmer! <g>
Greg Pyros
Whatsa matta, Gus, can't you write an ADI driver? I wrote several just last
week, but then got bored and threw them out. <g>
– J
OK. Gary can't seem to find a problem with tablets on his end. But
I guess I am not the only one having problems. By reducing the
polling on the network, as Gary suggested, I was able to make the
tablet at least workable, but it still freezes when ever I use slider
bars. When this happens I have to completely reset that tablet.
This doesn't cause any loss of work, but is a real pain in the
@#$@. If anyone finds a solution I think there are a lot of us who
would like to hear it.
Remember, the internal drivers are only Summa-compatible, and you're
using a non-Summa tablet in an emulation mode that is probably not
100% Summa-register compatible.
I have a Summasketch II Plus and get similar problems as those listed
particularly in the keyframer module.
We spent quite a bit of time getting the Summa II, II+ and III
working fine here, and the QA dept. here put it rigorously through
its paces. If you're having problems, it's due to something specific
to your machine.