Ive been browsing through some old threads on this topic. The main advice that seems to return all the time is: switch it off. So whats the point of it? I recently installed a nVidia GeForce fx5950 256 Mb on my PC (XP home, 60 G harddrive, Pentium 4 1.6 Mhz, 1 gig RAM). The Ati Radeon 9800 Pro that went before it made Vue crash and Sketchup dysfunctional. On the Sketchup forum nVidia came out as by far the best for 3d graphics applications (as opposed to games), and my new card works terrifically with Sketchup. So why do I get images like the one attached when OpenGL is on in Vue? Not to mention other weird stuff: I delete objects and they dont disappear (except form the prview window) - they even re-appear after I close Vue and then open an empty file. I zoom out but Vue immediately zooms back to the initial view. Etc. With a brandnew $450 card installed Im not really prepared to accept that these are "card issues" (as one of the answers ran on an earlier thread); I rather think its a Vue issue, and it would be nice if something could be done about it...

I've programmed some Open GL stuff, and I've got to you tell that these issues ARE 'card issues' within certain limits.

The point of OGL was supposed to be a non-platform-specific API to allow programmers to write code according to a set of PD standards and be sure of it running correctly on any supporting OS. The card manufacturers were the first to screw this idea up by issuing their own modified versions, to to optimise for their chipsets. Then Apple decided to add some mods for the Mac OS, Microsoft responded with a few more mods and...

So now we've got a cross platform standard that isn't even standard on a single platform. It may be naiive of a developer to try and 'do it by the book' and expect it to work, but if you don't have infinite resources, where else can you start?

John

PS Surprised you've had problems with ATI, they're about the best at following the specs.

There are some professional cards available from ATI and nVidia. They are more expensive, but do they do a better job with Vue. Any experience? Any recommendation? At the moment I have a Geforce Ti4200 and Vue doesn't like this card/driver.

OK, if the problem is the card and not Vue? Then why does no other 3D application have any problem with the same cards? I could start to list all 3D applicaion I have tried that have no problem at all using the same cards and I can assure you that it will be a long list. I know that Vue uses some OpenGL stuff that other program not use but if so those functions shold not be used if the card not supports it. The real joke is however his. Vue Esprite is a consumer /semi pro product, and as such it does not support consumer cards but rather needs a pro card. Vue Pro is however marketed against the proffesionals but for some strange reason it works well on consumer cards. Figure that one out if you can? The real problem, as I se it is that you buy it and think it will work but it does not. If they have had a list of supported/unsupported cards at there site and one buys it anyway then one would not feel ripped off and get so mad about it.

It is said that if you have nVidia cards you should have them updated at nVidia's site. Also i had problems with openGl so simply turn that off and Vue works fine. Not much advantage using openGl anyhow.

I have a GeForceFX 5900 w/256MB and whenever I start Vue Pro it says "Your video board/driver could not be located on our list of Qualified Hardware. Blah blah". I'm using the latest WHQL certified drivers on Windows XP Pro, so I don't get it. Despite the "warnings", OpenGL works, but veeeerrrry slowly (on a Dual 2.66GHz HT-enabled, 2GB RAM machine). If the darn thing can't work with the latest hardware with the latest certified drivers (but everything else does - Vue d'Esprit, C4D, LW, Maya, UVMapper, RealModeler, DAZStudio, Deep Explorer), there's something funky about Vue's implementation, huh?

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone

Well, honestly I second that.

The dialog box warning about an unsupported card just means Vue hasnt been tested with that particular card, not that its sure to cause problems. Historically, we've had more problems with nVidia cards than ATI, and yes, its the drivers. Card makers update their drivers constantly, and they are in a death race to get out new and better support faster than each other. I know it sounds like a load when we say its the drivers, but well, it is. I recommend reading CPU (computer power user) magazine, which is a great hardware oriented magazine -- it also covers a lot of cool new technology. They spend a lot of time reviewing cards and card technology, so when there's a card with flakey drivers they usually report it. Best regards, Lynn Fredricks e-on software

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=1417411

In our FAQ above you find Video cards that works with Vue and Pro for sure. Just have a look:-)

Lynn: If it is the drivers only, then why does OpenGL Work well in VuPro while it don't work at *all in Vue d'Esprite using the same drivers? If it is the drivers only, then why does it work with **all other 3D applications on the market that I have tested, except Vue d'Esprite. *(well it does not make the program crash but it is 20-100 times slower than OpenGL in other 3D applications) ** I have run around 10-15 3D applications on my computer.

The OpenGL implementation in Vue d'Esprit 4 uses a less sophisticated feature set of OpenGL than Vue Pro. What it "touches" in OpenGL is different from Vue Pro, because the code base is significantly different. When an application uses OpenGL, its supposed to be able to say "hey OpenGL, gimme this and this and this", and the response should be the same on any platform, Windows or Mac, and with any video card/drivers. So there are three parts at work here: the application, video card/drivers, operating system implementation of OpenGL. If everything has been implemented according to "spec" by all three, then there isnt any reason why it shouldnt work. But it often doesnt happen that way because developers cut corners, or cause something to write into a memory space where it shouldnt, or create some kind of conflict that messes up the others and not document it so we can try to find a workaround of some kind. I dont experience the same problems you are experiencing, but then again, Im certain we have different configurations of just about everything. My wish for mid-range graphics card designers is that they would spend as much time on OpenGL conformance as they do with DirectX. Best regards, Lynn Fredricks e-on software

Thank's Lynn. I hope you leave that 'less sophisticated feature set' behind in future releases of Vue d'Esprite (i don't expect it to happen in v4) so that also the consumer version of Vue will work better in the future. ;)