CompuServe Thread

#kurta tablet and 3ds

3 messages in this thread
#80814From: Max L. ElliottFeb 2, 1994 8:35 PM
Thanks Donald. I'll take a look at my autoexec.bat. What did you select as the tablet driver in 3ds.set, SUMMA or the ADI driver? I'm hoping that SUMMA mode will work. I found out that the main reason the Kurta ADI driver doesn't work with 3ds is that 3ds wants an ADI 4.1 driver _not_ an ADI 4.2 driver, which is what Kurta supplies. 4.2 drivers work with AutoCAD but not 3ds. Bummer, that really should have gone into r3. Max Elliott
#80824From: DONALD NEWLANDSFeb 2, 1994 9:25 PM
Max, I use a "regular mouse" ($29) most of the time in 3DS. However, on occasion I have been known to pamper myself with a "luxury mouse"… I have a hard time with the mouse emulation in most tablets and find that work in 3DS is so screen/mouse dependant that getting around fast is really important–much more important than in AutoCad where I use shorthand macros, button macros and typing for most command entry. The Summa emulation would probably be a good choice if you are forced into using 3D Studio with the tablet, better I think than a "tablet mouse", although 3D Studio has never really worked very well with tablets at all…. Donald
#81009From: LCS/TelegraphicsFeb 3, 1994 11:28 AM
Max: 3D Studio can't correctly handle tablet ADI drivers. ADI 4.1 drivers that run in the interrupt mode work fine UNTIL you have to exit, whereupon you crash if the tablet generates an interrupt. While 3DS3 internally reports ADI 4.2 compliance, it cannot read ADI 4.2 event packets. The built-in SUMMA driver is marginally better, but because it uses polled-mode I/O to get tablet data, it occasionally misses an event like a button press or release. The symptom is sticking crosshairs or a drag that won't drop. Use the Kurta mouse driver and configure 3DS3 for a mouse. Life is too short to do otherwise.