CompuServe Thread

#DXF3DS

3 messages in this thread
#7940From: CSA/CAJan 18, 1992 2:57 PM
Chris, You are experiencing some Targa+ problems due to operator error (well, mostly). Use either Autodesk's RDPADI RDPTARGP.EXP to render to the Targa+ with 3D Studio, or the RCPADI Truevision supplied on your Targa+ disks (if not on your disks, get it from your dealer). The Animator Pro driver Autodesk supplied is ok for FLITAPE, but I wouldn't use it for rendering. When using Truevision's .DRV for Animator Pro (in which Animator Pro actually runs ON the Targa+), it throws the Targa+ into an 8-bit color mode (just like VGA, huh?), but does not reset on exit. Execute TMODE to reset to a mode that TIPS+ and other applications will like. I usually set TMODE to 640×480 for Animator Pro, then do a TMODE 11 (512x486x32-bit) when done. Kevin Krell – Computer Support Associates
#7983From: Chris YancharJan 19, 1992 1:05 AM
Kevin: You're a miracle worker!!!! I did an ol' tmode 11 and my baby was back to her old self. 3d Studio works now and so does Animator Pro. And Animator doesn't give me those memory error messages either. Why exactly did it give that message anyhow? Or does anybody really know…whooo wheee whooo whooo… No, seriously. I understand the Tmode deal to get 3ds goin' again, but why did it bother Animator since Animator was the one who put the board in 8 bit mode in the first place? Weird stuff dude. <grin> Chris Yanchar P.S. : Why you're thinking of an answer I going to put my NEW Lantastic network together. <More problems…please…please give me more problems> But don't worry, I'll only badger you on my Targa, 3DS, and Animator Pro problems. Oh ya! Kevin, how come it's……….
#8043From: CSA/CAJan 20, 1992 1:02 PM
Chris, Glad it's worked out. The Targa+ driver for Animator Pro is checking for a valid 16- or 32-bit mode initially, than switches to 8-bit under the driver's control. Kevin Krell – Computer Support Associates