#CFIG386 3DS for PRO
11-Apr-92 10:51:35
Sb: #12202-#CFIG386 3DS for PRO
Fm: Yost Group 76702,413
To: Rock Richardson 71320,360
I don't understand what you mean by the sentence:
"they did mention that you guys called about a problem about file not
showing up (meshes) but thought that the problem was taken care of."
I have never called the BCD people. I understand your frustration, but I
know very little about specific controllers and can't help you much. (I
wish I could.) Greg's suggestion to use QEMM to move your display memory
HIGH is a very good one.
Rock, let me tell you how we implemented the VTPADI interface for VTR
controllers within 3D Studio. First, we took all the functionality that
was in our internal Diaquest interface and we broke that out into a new ADI
type. Then, as a test, we used the Diaquest VTPADI driver that works with
Animator Pro's FLITAPE as an example. Once we got the VTPADI interface
working perfectly with the Diaquest VTPADI driver, we knew we had a working
interface. At that point, we sent out betas to the various VTR controller
companies. To be perfectly honest, since these companies had never written
ADI drivers before, they've been floundering around a little. I expect
it'll take them a little while longer to get it right. But that's THEIR
problem, not ours. That's why we went to the trouble to get the VTPADI
interface right. If I had to worry about DRIVERS, I'd never be able to
sleep at night.
– G