#AA Pro 1.0 w/Summasketch
8 messages in this thread
I am having a problem using my Summasketch II Plus digitizer with AA Pro
1.0, the cursor seems to stick sometimes, and can take as long as a couple
of seconds to get going again. Can anyone help me to resolve this?
Thanks, Dave
P.S. What are the new features with AA Pro 1.3?
This has been a recurring problem with AA that so one seems to care enough
about to fix. We have complained here endlessly. I am just hoping that 1.3
fixes it!
Keep hoping Doug. I've seen the flipping of the cursor with a Summasketch
II tablet happen with AniPro 1.03
Chuck Jameson
Silver Tongue Software
How about the NOVM feature? Does it work with 1.3?
Doug,
Little hope there. I've got a problem right now with a Summasketch
III hanging for 30-60 seconds in AAPRO 1.3, usually when making a menu
pick, or touching the screen edge. Also locking up on some side menu picks
in 3D Studio.
Kevin Krell – Computer Support Associates
Guys:
Based on my experience with the quality of the drivers provided by Summa, I
would first look at Summa as the problem but since the Summa is directly
supported by AP, then I would guess that Summa gave the Yost group the
wrong specs <wide grin>.
C#
I have been using a SummaSketch II Plus for about a year with both Animator
1.0 and Animator Pro 1.3. Version 1.0 running under Windows would cause
stop and go performance each time I started the program and continue until
I used the configuration menu to respecify the use of the tablet. Then it
was fine the rest of the execution.
Under 1.3 I have been unable to get it to run under windows without the
stop and go action of the stylus. Very disappointing. So I have been using
a second set of DOS configuration and autoexec.bat files to run only
Animator. Running bare bones on a 486 50mz it runs fine with the tablet.
This Summasketch problem you are having is tantalizing. Could you let us
know what files cause the problem you're having running AAPro 1.3? I note
that you said that a special bootup disk will allow you to run AAPro 1.3
properly with your setup. I would be interested in the autoexec and config
files you normally load, in case we can determine which line(s) cause the
conflict. It's even possible that a parameter adjustment to one of the
lines might take care of your problem. (hopefully!)
Also, if anyone else out there is having problems with digitizers and
AAPro, I'd appreciate hearing from them, with a description of the problem
and the circumstances, and any theories! It would be great to get this
information together so our QA dept can do some work to track this down.
Thanks.
Nik