CompuServe Thread

Vibrant for Cirrus 5434

16 messages in this thread
#105638From: Chris Edgington @PanaceaJun 3, 1994 3:54 PM
All Cirrus mode codes are upward/downward compatible, so you should be able to choose a Cirrus 542x selection for the 5434. -Chris Panacea
#106078From: Tien NguyenJun 6, 1994 1:07 PM
Chris, Thanks for your answer but I tried to select 542X and the driver told me that it could not find the appropriate display device. Do you know of anyone using the Kelvin 64 with Vibrant driver? Regards Tien Nguyen
#106223From: Nik Grant [adesk]Jun 7, 1994 8:04 AM
"Do you know of anyone using the Kelvin 64 with Vibrant driver?" I am sorry that I do not know the answer to your question. However, I wanted to mention that Kelvin support has already been requested. I do not know of plans to implement it though. Do you have the latest VIB3DS.ZIP drivers for Rel3 of 3DS? They've been posted less than a week here, and if you don't have them may help. Nik (Sorry, I missed the beginning of this thread)
#106276From: Jun 7, 1994 10:57 AM
Nik – You guys posted 1.0.3 here??!?!?!? Bad Autodesk… The 1.0.3 I sent to David Ang was a pre-release… not a production build. It should NOT have been posted yet. I was planning on sending the production version today. Can you please make sure that whoever put it up knows about this! Thanks. PS: I'll send mail to David Ang! Chuck Walbourn – Vibrant Graphics
#106283From: Paul LindJun 7, 1994 11:24 AM
Isn't it fun?
#106421From: M. G. BATCHELORJun 7, 1994 11:34 PM
Chuck, You may remember (a while back) me documenting a very unusual ERROR #18 upon entering the materials editor which occured randomly (using early rev. Viper VLB)… well, something just happened which may have given me a clue as to it's cause: I hadn't seen that error in months except once while using the Yost's new IPAS routines. At the time it was happening more frequently, I was using BLACKBOX's Flock.axp a lot. I just started a project for the first time in months using Flock, there was nothing else in the scene, and I got the ERROR 18 again several times. Therefore, I'm almost certain that certain axp's or remotely, loading an *.asc file or MERGING a *.3ds (both required using Flock) causes the problem. Thought I would pass it on. BILL
#106433From: James BieblJun 8, 1994 12:54 AM
Bill or Chuck I get the same "error 18 unknown error…" message using the PAR dpspar.pxp for texture mapping the PAR's .ani files onto an object, when I flip to the rendering screen. Pressing any key blacks the screen, hitting any key again breaks me off from the render and sends me back to the KF.Also when flipping to Medit the first time after loading the .pxp. Hitting any key blacks the screen, hitting any key again brings me back to where I was. (editor,KF etc) The next time (immediately after the first) I go to medit, all's fine again. Of course I'm using Chuck's new alpha version. <BG> JB Sorry-Using Viper p9000vlb.
#106509From: M. G. BATCHELORJun 8, 1994 12:30 PM
That's exactly what happens when I go to the Materials Editor – only the first time – and then I get another more specific error message which I've documented before. I'm using the latest *_production_* version though. BILL
#106594From: James BieblJun 8, 1994 11:27 PM
Bill >>Materials Editor – only the first time – and then I get another more specific error message I'll bet it's "Cannot initialize…..80×34 characters". Maybe we'll track it down. JB
#106700From: M. G. BATCHELORJun 9, 1994 12:46 PM
Yes, it was something like that. I had previously documented it to Vibrant. BILL
#106456From: Nik Grant [adesk]Jun 8, 1994 7:37 AM
"The 1.0.3 I sent to David Ang was a pre-release… not a production build." Whoops, we apologize. There was a misunderstanding about the "Postability" of the file. This will be replaced with the Production Build. Nik
#106500From: Jun 8, 1994 11:40 AM
No problem. This time there were no changes… I'll be sending the production build later today to David Ang @ Autodesk. Chuck Walbourn – Vibrant Graphics
#106479From: Yost GroupJun 8, 1994 9:57 AM
Chuck, it's my fault… I thought it was a release version and I asked them to post it. – G
#106501From: Jun 8, 1994 11:40 AM
Again, no harm done. Our European office got a few calls, so they wanted to know why we hadn't given them the release… Chuck Walbourn – Vibrant Graphics
#106577From: Yost GroupJun 8, 1994 10:09 PM
At least in this case there was no difference between the pre-release version and the production version. (lucky for me 🙂 – G
#106275From: Jun 7, 1994 10:57 AM
I assume that you mean the Orchid Kelvin 64? We have been trying to get an Orchid Kelvin in house for some time… We have had several reports of people trying to use the Vibrant driver without success. I'll put in another request for the board. Sorry for the incovience. Chuck Walbourn – Vibrant Graphics