Vue Vista 64-bit OpenGL issues

#1

Hey everyone,
I’ve been having some weird issues with Vue 6 Infinite 64-bit on Vista-64 and what I think may be an OpenGL compatability problem. The program operates just fine when performing normal operations, but, whenever I go to render either in the main view, or into a screen, the program hangs and crashes as soon as it finishes rendering where it’d usually pop up the ‘post render’ options. It crashes in both normal and compatibility mode. However, if I turn off all OpenGL functionality, the program functions just fine in wireframe, allowing me to render in the main view and in a screen with little to no other performance issues.

I’m using a Nvida Quadro4600 with the latest drivers from nVidia (which, when I run the compability test says it’s compatable, even though at startup it tells me it’s not), 2 x Quad-core xeon 3.0ghz, and 8GB of ram, so, running this program shouldn’t be anything of a performance issue hardware-wise.

One interesting thing to note, however, is that in my application event viewer, it says the faulting application is Vue 6 Infinite.eon, however, the faulting module is ntdll.dll. Don’t know if that will help determine the root of the issue or not.

Anyone else having similar issues, or have any reccomendations aside from having to grit and bare it in wireframe mode?

#2

Still no progress on the OpenGL shortcomings of Vue 6. I’m continuing to use the program in wireframe mode, but, it’s rather unfortunate.

Anyone possibly have any further developments that could help?

#3

Hi,

i have the same problem but i have another VideoCard ATI 1950 Pro
but my solution was to set the antialiasing settings from control by applikation to X6 or X4 now it works in opengl… i hope this will help…

#4

Hey, Thanks for the reply!

Unfortunately, manually setting my AA settings had no result, OpenGL still causes Vue to crash in the same way it had before.

#5

I don’t know whether you’ve figured this out, but I’ve recently had the same issue and stumbled upon this post. I’ve been working around the issue by disabling the “post render process” while in wireframe mode. After it’s gone, everything seems to work fine again with OpenGL on.

I’ve opened a ticket and E-on have been informed of this particular bug. What we have in common is a Quadro card. Don’t know if this is making the difference…

#6

I’m running an NVIDIA Quadro FX 1700 and I’m not getting any of these errors. But previously, before I upgraded, I had an ATI Radeon and that not only crashed Vue again and again, it always showed decimated meshes in the editor windows. Now I see full texturing with shadows, transparency, etc. - all in OpenGL edit mode.

I had reached my limit on frustration with all of the video problems - so I shelled out $600 for a workstation performance card - it was worth it.

Jim

#7

Aye, I’m running the Quadro 1700 as well. It might just be something specific to Nvidia’s GL driver in Vista 64 (though I’ve used a couple now with no difference). Let’s hope they get it all sorted eventually.

#8

I read an article recently somewhere that 30% of Vista problems have to do with nVidia drivers. Maybe this is related. Since as other have pointed out, newer drivers are much better, then you are basically stuck or turn off features.
M

#9

For those of you with 64bit machines

how well is Vue performing as 64bit? I am thinking of installing the 64bit version on a new machine - do you notice significant improvements in operation, rendering etc??

#10

Here, everything is WinXP 64bit and it works great! No problems…

Significant improvemnets is a tricky statement. I would say yes it is a significant improvement, but barely, but we would never go back. However, the improvements are also system wide rather than only Vue.
M

#11

hi all,

i know is an older post here, and i hope you solved out by now, otherways here is my sollution.

I had exactly the same problem as you (using an fx 550 - just changed for a fx 1700 and problem was gone too). The way i made it to work was to go into render - preferences- change the “render destination” from “render to screen” to “render to file” (no other modification was needed, and it worked fine. The only problem is that the feedback is somehow slower when you have to check your renderings on some file and not directly on screen.

hope it helps.

#12

hi all,

i know is an older post here, and i hope you solved it out by now, otherways here is my sollution.

I had exactly the same problem as you (using an fx 550 - just changed for a fx 1700 and problem was gone too). The way i made it to work was to go into render - preferences- change the “render destination” from “render to screen” to “render to file” (no other modification was needed, and it worked fine. The only problem is that the feedback is somehow slower when you have to check your renderings on some file and not directly on screen.

hope it helps.

#13

I worked this through with support at one point. The crash occurs when Vue tries to draw it’s “post processing” dialog box onto screen. I can’t tell whether it’s driver related or not. That somebody doesn’t have the problem with a Quadro 1700 and I do means it’s likely. In any case, if you put Vue into wireframe mode, render to screen and click the box to disable the post-processing screen from appearing next time, the problem goes away.

eugenV, I’ve had problems with render to disc only utilizing one processor before. Render to screen (or network renderings vue hypervue seem to multi-thread properly).

hope it helps. I’ll try to see whether the problem still exists in the newly released beta.

#14

hello flay,

this is exactly what i ment to say. I appologise if there was some misenderstunding of my quote.

#15

hello flay,

ok, i surely express myself in a strange maner. In my case fly, the render to screen give me the error so i chose to render everything to disk. Now, maybe you’re right, i’ll try to render everything in the screen and just disable the postrpocessing screen to appear. But even though, if i remeber properly, to have the postrpocession operating, with is clearly a must do, you have to enable or the render to screen or the render to disk. So i guess, what ever the solution, it has to pass by righting the file on disk, at least for the moment.

I do have one queston though,…do you experiment this problem even with the fx 1700, because i didn’t install mine yet, so i would like to know

#16

Yes, I have this problem on a Quadro 1700. Vista 64, Intel Quad-Core, 8 gigs ram.

Rendering to disc is a pain. Much better to disable the post-process dialog box and quickly test there (or in a viewport). Good luck!

#17

thanks for your reply, Flay

it’s a pitty to see the problem is still there even with a 1700, but they’ll probably work already on a solution, or so i hope, lol

#18

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.