Hi folks! I have reported the following error in the e-on forum, but thought, I'd also post it here to see whether anyone else has had something like that: I have a very strange error in Vue 5 with a scene that was working absolutely correct in Vue 4. I load the scene successfully (with OpenGL enabled) and don't touch the computer for something more than 5 minutes. CPU load during this time stays at 100% (99% dedicated to Vue). After this time, the CPU load starts alternating a little between 90 and 100% and then Vue crashes giving me the error that "instruction '0x100f7bd9' tried to access memory at '0x000001c4'. Memory could not be written...". Now comes the interesting part: I activate compatibility mode and load the same scene and let it stand. It takes somewhat longer and after loading, the CPU load drops to next to nothing. But: Then I get a crash and an error telling me that "instruction '0x7c0013bc' tried to access memory at '0x03bee000'. Memory could not be read..." I'm using an Athlon XP2200+ with 2GB RAM and NVIDIA Geforce4 Ti 4200 graphics card that passes Vue's test as compatible. Loading a really large scene (that was not fun but workable under Vue 4 with only 512MB RAM) gives me out-of-memory errors, but I have not had the opportunity to find the limit that still seems to work. Can't say anything about base version because first thing I did after installation was putting the latest fix on. Updating graphics card drivers did not change anything about the problem. Scene has about 12.7M polys and 33MB. Anyone ever seen that effect?

I have the same graphics card, and with OpenGL enabled, it really struggles with anything more than a few hundred ks worth of polygons. With nearly three million in your scene, I would guess that the problem lies in the graphics cards inability to handle that amount of data. There was a thread about this on the E-On forum before Christmas. Try turning OpenGL off and see how you get on. Alternatively, given the known problems with Vue 5 and large scenes, it could simply be a different manifestation of the memory problem - yes, even with 2 gig of physical ram ... ...

Perhaps Vue is a jealous babe that hate to be left ignored? Could be her way to ask for attention... :P

Good to know! I seriously considered purchasing Vue 5 Infinite as an upgrade to Vue 4.5 Pro, but since I use it for extremely large scenes (my latest scene file weighs in at a hefty 300 Mb), I think I'd better keep the money. OpenGL still has problems. Newer graphics cards don't solve them (I've got a Geforce6800LE), since the hardware vendors (ATI and nVidia in any case, don't know about Matrox) don't spend resources on developing decent OpenGL support. You'll find the best OpenGL performance and stability on old cards, like RivaTNT2 based stuff.... I use OpenGL until Vue starts crashing on it, then I turn it off and expand the scene without OpenGL - usually I can increase the complexity by another 30% with OpenGL disabled.

Even with OpenGL disabled & working in wireframe mode with no previews enabled I still crash(OOM).....I have yet to find the ryhme or reason...because it's all to weird. With 5 the highest poly count I've achieved is 7mil...the lowest was 1.4mil(as in my last scene)then crash, In Vue 4 the highest I achieved and was normal for my scenes was 20-25mil polys. So go figure. I think 5 is still a work-in-process.

My biggest scene in polys with Vue 4 (on the same machine, but with less memory) was 230 million - no probs at all with that. In MB it was >500 - slow, but no problems either. Haven't tested my limits, but it's definitely not as good with Vue 5 - even when using wireframe. Usually, I don't have any issue with the graphics card with any other applications, so I'll give it a bonus in trustworthiness for now :-)

I never had crash-problems with Vue 4.2, and have them constantly with 5. I'm on a P4 1.6 Ghz, 1Gig ram, fx5950 ultra 256mb video card, and over 180 gig free harddisk space. Vue 5 definitely seems to have a problem handling large models. I am working on a very large architectural model, which I imported into V5 at an earlier stage (appr. 800,000 polys). It worked fine. After additional work on it, it went over 1mln polys. Vue 5 would still import it, but anyy subsequent action resulted in a crash ('out of memory' error). I've now split the model up into six separate parts; if I import these one after the other and then group them in Vue, everything works fine, though somewhat sluggish. If I put the group on a separate layer and hide it, there's no problem at all.