Sun, Nov 24, 4:52 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Nov 21 4:12 am)



Subject: OpenGL problem SOLVED !!!


nirsul ( ) posted Sat, 27 October 2001 at 5:43 PM · edited Sun, 24 November 2024 at 4:42 AM

I downloaded the new driver version 21.83 from nVidia and Vue flies !

Nir Sullam


Flywaver ( ) posted Sat, 27 October 2001 at 9:24 PM

Cool...now I am using a 3dlabs Wildcat II and it doesn't work that great. Good thing I am getting a QuadroDCC next week! :) Thanks for the news. Cheers!


Varian ( ) posted Sat, 27 October 2001 at 10:36 PM

Great news, Nir! :)


MikeJ ( ) posted Sun, 28 October 2001 at 1:40 AM

Glad to hear it!



agiel ( ) posted Sun, 28 October 2001 at 10:04 AM

file_226555.jpg

Doesn't look like an improvement to me :) I was hopeful when I saw the thread in the forum, so I went and got the new drivers. This is what Vue gave me. It got much better after turning the 'background draw' option off. The problem was that, to get any meaningful image, I had to pump the instant draw quality to the maximum, which made the scene way too slow to work with. I also tested 16 bits versus 24 bits of colors on scree : 24bit just makes the scene all red. Conclusion: I am still not going to use openGL with vue.


Flywaver ( ) posted Sun, 28 October 2001 at 10:15 AM

file_226556.jpg

hehe this is what I get...there is a problem with the redraw. Sometimes I can see parts of a scene I used hours ago still in the same screen. :) This is with the 3dlabs card, with WinXP with M$ certified drivers and also tried under win2k or NT4 emulation mode. Cheers!


Varian ( ) posted Sun, 28 October 2001 at 11:21 PM

Yikes! Well at least the new driver was helpful for Nir. The OpenGL oddities with Vue 4 are so diverse from one person to the next...I sure hope E-on is able to sort 'em all out and develop cures for everyone!


Sacred Rose ( ) posted Mon, 29 October 2001 at 1:36 AM

I have to agree with Laurent the new drivers didnt help me at all...if anything they were even more painful than before for use in vue. However, the overall peformance for the drivers under 2k were excellent. My system sped up dramatically. I have a 3d Prophet MX II (GE Force 2). Steve Bell at e-on suggested I switch over to the M$ drivers and I got the same stuff as Flywaver did in his image. Guess what I did.... I switched back to my Prophet drivers and simply disabled OpenGL gain. It really is an e-on issue, because my graphics card works beautifully in every other application and in openGL games. In Vue4 it sucks big time :/


MikeJ ( ) posted Mon, 29 October 2001 at 5:32 AM

Yeah, don't know what they did.... Last night I was reading all about Open GL, and it seems to be hailed as something very solid and reliable. I hve no problems at all with anything I have which uses Open GL, except Vue 4. With my VooDoo 3 card, everything, including Vue 4 does great with Open GL. When I upgraded to the most recent driver for VooDoo 3, the Open GL in Vue 4 went to pot, though every other app worked as normal, and the few games I have (Soul Reaver, Quake II, Diablo) were smokin'! Of course, Vue 4 didn't like the newer driver at all in Open GL, so I reverted to the original. I was seeing things similar to the above, but alot of the time the viewports would simply gray-out. I wonder how many people are downloading the Vue 4 demo, seeing a bunch of crud on their screens, not looking into the problem, and simply uninstalling it?



agiel ( ) posted Mon, 29 October 2001 at 6:26 AM

They could at least turn OpenGL OFF by default. This could help showning those people that Vue works great except in the openGL arena.


MikeJ ( ) posted Mon, 29 October 2001 at 6:33 AM

Just like the Poser .BUM file import- I don't think they knew they had botched it. Hopefully next time around they'll see fit to have more beta testers. From what I understand, it was a relatively small group they had, and "by invitation only". The testers did a great job, and I know they put alot into it, but you can't catch everything...



Flywaver ( ) posted Mon, 29 October 2001 at 7:23 AM

Yeah it's definately an issue with Vue since the 3dlabs card is to date the best OpenGL cards I have tested, I even reinstalled Vue yesterday to see if it would work and I tried the CD version of vue and then 4.02 and it's the exact same thing. Honestly, I would like to see their OpenGL implementation tweaked considerably, it's really fast to manipulate the terrains but there is no detail on the meshes! :( Cheers!


Sacred Rose ( ) posted Mon, 29 October 2001 at 8:38 AM

I have to agree with all of the comments. I think a LOT of people who are downloading the demo, because of OpenGL and poser integrations, faster rendering, volumetric stuff they are pushing in the 'advert' must be undergoing all of these issues as well and simply uninstalling it as an unfit product. Which is a shame really, because it has a LOT of potential - IF - these issues are fixed. But they need to be fixed soon I think.... I can see a huge loss of 'potential' users. Not so long ago I was in chat (I hadnt received my copy of it yet), and there were 4-5 people who were raving about the vue gallery. But they downloaded the demo and it simply wouldnt run on their systems properly. 2 of them refused to re download and try again. One did...and the other was undecided. To this date....none of them have purchased or are intending to purchase vue 4. I havent heard anything from the fifth one yet. Multiply this number by all the other graphics sites and mag reviews, and u get a HUGE loss.


Flywaver ( ) posted Mon, 29 October 2001 at 9:29 AM

Yep! but I know that E-on is working on this or will soon do and I just heard there is a 4.03 version in the works. :) Cheers!


philhoole ( ) posted Tue, 30 October 2001 at 5:05 PM

My suspicion is that Nvidia drivers do not like being used in the multihthreaded manner that the Vue4 interface works. I remember reading something about this a long long time ago. As far as I know this is quite unusual in a program to have the interface multithreaded as well as the rendering process. I've tried Vue4 on an original GF DDR,GF2MX and a GF3 - they all exhibit similar problems. I haven't tried a driver later than 21.81 though


aheinz ( ) posted Fri, 02 November 2001 at 2:52 AM

I agree with philhoole, Vue is the only app mentioned in this thread that realy draws multithreaded. All others are drawing in one thread and are switching through their views. The driver developers (of cards that are mostly used as gaming cards) are not very concerned about this, because there are only very few apps using this feature. If you can afford it, buy a "real" OpenGL Card like Diamonds FireGL cards. Intresting stuff can be read here - specifically the performance of a 4-view rendering under the benchmark section. This is partly based on the multithreaded GL-driver and the optimization of the FireGL cards for professionell CAD workstations. Have a nice day ! Arthur


aheinz ( ) posted Fri, 02 November 2001 at 3:27 AM

Sorry ! Forgot the link, here it is: http://www6.tomshardware.com/graphic/00q4/001213/


Flywaver ( ) posted Fri, 02 November 2001 at 8:10 AM

Woohoo! the problem is solved here too but unfortunately it's temporary since I need to give back the card in a few weeks! :( I installed a QuadroDCC with the 21.83 drivers and just tried Vue, it works like a charm, I have no redraw problems! So, I had the redraw problems with both my GeForce2 GTS and the 3Dlabs Wildcat II 5000 and it's running perfect with the QuadroDCC so there is definately a bug somewhere. Btw, if you want the best card for under 1000$ for DCC you won't find a better one than the DCC, you will see in my review in 2 weeks. :) Cheers!


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.