#R4 won't run, R3 does
10 messages in this thread
Hi, Gary – Last time I checked in was when my R4 would not run, though
R3 did. Well, I have isolated the problem, though not solved it. I
waited until now to get a BIOS upgrade for my Stealth Pro VLB video
adapter in the hopes that the troubles would go away. They didn't
(except for my Windows woes). All the problems I'm having, even the
invalid matlib messages, stem from the video driver used for the main
display. Material Editor and Render Display work fine, as far as I
can tell. I can run R4's Main Display with the generic vesa
compatible Vibrant drivers in any available mode. When I set the
driver to my specific video card (as I do with 100% success in R3) I
can only open and render little files. If I try a good-sized one,
like my current 100,000 face project it freezes (at various points,
seemingly at random) and, after rebooting, won't work at all
correctly until I change drivers (all within the in-line Vibrant
collection) after which it starts all over. So I can get by with the
vesa compats, but it then runs s – l – o – w as molasses.
Having narrowed it down to this point, who should I work with to get a final
resolution?
Thanks for the help…
David Taffet
Hi David,
<< Having narrowed it down to this point, who should I work with to get a final
resolution? >>
Vibrant posted msgs that a new set of drivers that will appear in the
near future. Nik's on vacation this week, but I'll make sure theat he
sees this bug report.
Thank you, Jonas. Mucho appreciado
DT
Jonas – Presumably Nik is back from vacation…? What's his ID? I'd like to get
into a dialog about my video problems. Thanks.
David Taffet
Hi David,
Nik's ID is 70421,76.
Jonas' comment about trying different versions of the Vibrant drivers
(including this upcoming version) is a good one. I'm assuming that
the exact same vib3ds.vlm file that works with r3 isn't working with
r4. (Is that correct?) If so, it was just a fluke that it worked
with r3, albeit a lucky one.
Keep working with Jonas on trying different ideas, and I'm sure that
you'll eventually work it out.
Ahh, hardware. My nightmare beyond nightmares…
– G
I'll work with Jonas.
I guess it was a fluke that the R3 driver worked, but didn't Vibrant
change some things in order to be able to do the fast previews and
all that? The other thing (that I was thinking) is that my first
video chipset was v.1.11, which was probably close to the one Vibrant
engineers were using when they wrote the drivers included w/R3. By
the time R4 came out, I still had that old video BIOS. I got the most
current one from Diamond and a plethora of Windows problems went
away, but not my R4 problems. So much for that theory. Anyway, my
chips must be falling, chronologically, around those used by Vibrant.
Or they were not given accurate info by Diamond… jeez, I don't
know! Must be the coffee talking…
DT
P.S. I have tried a large number of the drivers with R4 that are not
specified for my card. Except for the "vesa compatible" selections
they all behave basically the same as the specific. No worky…
Nope. Nothing was changed in the vlm code to support fast preview
(that's an entirely different vlm). You've got me completely
stumped.
>> You've got me completely stumped. <<
🙁
DT
>> I'm assuming that the exact same vib3ds.vlm file that works with r3
isn't working with r4. (Is that correct?) <<
Yes, sir.
DT