Interesting... So, I had Win 98 SE on one HD, and Win XP Pro on another, in a dual boot, and I have an Nvidia GeForce FX 5700 video card with 256 MB video RAM (1.5 GB system RAM). Anyway, Vue 4's Open GL with the 4.22 update patch doesn't work right under either Win 98 SE or XP Pro... But yesterday I decided I wanted to upgrade my Win 98 to Win 2000 Pro, so I went to Staples and bought Win 2000 Upgrade edition (Had to reformat everything because Win 2K wouldn't allow itself to install with XP there, even when I removed my SATA Drive which has XP on it, but that's a whole other story...). Anyhow, I succeeded in installing Win 2000 Pro, and installed Vue 4 on it and before even updating to 4.22 I tried the Open GL, and it worked...PERFECTLY (!). For a while, that is. I used it alot and all seemed to be well...until I switched from render-to-main view mode into render-to-screen mode, and then all went wrong. Switching back to main view didn't fix it, neither did installing the 4.22 patch. Not complaining, of course, I just find it strange. Anyone else here using Vue 4 Open GL on Win 2K?

or not using OpenGL on W2K Pro? lol! I have the same NVidia card as you, updated drivers, 1G system DDRAM. Open GL might work for a few minutes (both Vue 4 and Vue 4 Pro), then performance starts to deteriorate and then the crashes begin. I got tired of "discussing" the issue with E-on, and just turned Open GL off and cruise along happily in wireframe.

I was using W2K Pro a while back and learned quickly that there's no way to guarantee getting Vue's OpenGL to work with a standard 'domestic' graphics card. A lot depends on the driver. Early nVidia drivers seemed to work to for me, later ones didn't, then they did, then they didn't. Same situation with my new ATi card under XP Pro. Agree with Djeser: turn off OpenGL. If you're planning on creating complex scenes, you'll have to disable OpenGL to allow quick moving of objects. May as well turn it off sooner as later. :-)

Yep..been trying it under W2K Pro as well as XP Pro for a couple days now, with the same results no matter what I do: On-Off-On-Off.... Works for a little while then goes flooey on me. It's almost like it has a built-in timer in it to disable itself. ;) I thought maybe it could be a RAM thing at first, but I have a gig and a half of RAM, not to mention 256 MB of vid RAM, so I can't see that as being the problem. shrug But dammit, I like the way it looks when it's working! Nothing but a tease... ;)