CompuServe Thread

#video post Vista prob.

5 messages in this thread
#91289From: KeyframeMar 15, 1994 8:45 AM
Help , I have 3 3d Studio systems, all running on the ATVISTA , 2 on 50mhz machines and one running at 66mhz, on one of the 50mhz machines when I render in Video Post, my vista goes nuts!!!, after the render and the processing is done, the images is displayed and then the vista goes blank , flashes and thats it, after that if I view an image from within 3ds the images views for a split second and then the display goes off again, but all my other systems work fine ??. To make the vista work again, if I run any other utils such as a program to load an image it works fine from Dos Shell, I can then view images okay from within 3ds3. What's going on……
#91350From: Jonas Ruikis [ADESK]Mar 15, 1994 12:01 PM
Phil, << what's up with my VISTA and 3ds? >> First things first. Have you downloaded the latest drivers from VIBRANT found in section #9 on the libs and called VIB3DS.zip? jonas[adesk]
#91352From: KeyframeMar 15, 1994 12:06 PM
No I havn't, when I got r3 I used the latest version of RDPVISTA but it completly slowed down everything that happend on my VGA!! I eventually swapped to the driver VistaH to get round this problem. Do you think the latest version will still have that side effect on my system ??
#91365From: Brian Rudolph [Adesk]Mar 15, 1994 12:48 PM
Phil, What differences are there between the machines that are working correctly and the one that isn't? I.e. Memory managers, RAM, SCSI Drives, VTR frame controllers, other periferals…etc.? Anything that might be causing a conflict with the Vista board? -Brian P.S. When Jonas asked about the Vibrant inline drivers, He was thinking ATI as he was writing AT Vista. So his train of thought has momentarily derailed at the station. (But it is a good idea to have the most current versions of the support files in any case.) -b
#91841From: KeyframeMar 17, 1994 5:25 AM
There is very little difference in hardware, an extra IDE drive and thats it, but I was talking to somebody yeserday who suggested that I run VISTALD GENLOCK.OUT before entering 3ds3 which I did, and for some reason, the problem has gone away (for now) I have no idea why this worked and neither does the guy that suggested it.