I noticed that the 5.02 update build number has gone from 273045 to 273412 on e-on's site. They sure were quiet about that one. Am I the only one who missed that? SMT

Well, I caught it, beacause I'm visiting daily LOL....I'll add at the risk of getting flamed, Still getting OOM messages as well as many others as indicated over at e-on, can't seem to get beyond 2.5mil polys. Other can't even get beyond 100,000 before OOM crash. And yes, I've reported all issues to tech support & we are working on it, as well as many others :) and no it's not my hardware. That said, I'm looking forward to Vueing again very shortly, I hope.

Message edited on: 11/22/2004 19:10

Message edited on: 11/22/2004 19:12

Yeah. They don't seemed to have fixed it. I'm curious as to when the "out of memory" messages are happening for most people. For me it's: 1. Loading a large scene. 2. Importing a large 3D model. 3. Saving a scene or VOB. 4. Welding geometries. 5. Changing the smoothing angle on a hi-poly oblject. 6. Just simply letting the program run too long. Interestingly, I don't ever seem to get the error when rendering. BTW: I now have 2 gigs of RAM and a 256 meg video card. The OOM's have nothing to do with the actual memory available. SMT

I, too have loaded this latest update, and seem to be having a bit more luck...tho' this is relatively speaking as I was having NO luck at all previously! As for the OOM's that I do still get, it's mostly when I get up there in the Mb dept...generally all it takes is about 150Mb or so for my machine to start acting up...running 1gigRAM on a 3.0GhZP4 with over 140Mb free. I use a lot of Posers in my images, so this is a real PITA for me. I have attempted, in testing, to crash it with poly's and have got up to close to 10mil before I experienced any extreme sluggishness! As for running the prog too long I feel I have to keep it running in fear that IF I do come out I won't be able to get back in '-)! Would definitely be interested in hearing what others are experiencing here as well? ==steve==

If I remember rightly, the new build of 5.02 was announced a while back on the e-on registered forums. Vue 5.02 is running flawlessly for me, but maybe my scenes are not quite as complex as yours.

just to humour me ppl, what os,cpu and graphics card (include drivers and updates to) are you guys using (the ones that have problems of course)

I'm still getting OOM's but it seems to have to do with file size and not polys at all. When a scene gets around 180,000 kb I'm in trouble and I start saving backup files. I am also working with tech support to try to resolve this issue.

Ya know? I think my VUE5 just doesn't like playing with .pz3's at all '-(!
I am currently working on a scene that was zipping along smoothly until I loaded a simple .pz3 weighing in (in VUE5 with textures and all) at a whopping 17.9Mb! At that point...following a simple adjustment in orientation of the pz3...what do I get?, but the dreaded OOM notice! I was able to save this one...not that that matters as I have gotten to the point where I now save after EVERY little tweak in fear of OOM's '-)... however the fact remains that this scene, as it stands now, is only 71.2Mb and just under 2.9MilPolys with no procedural terrains and sunlight only!! I do believe that I should be able to construct just a bit bigger scene here without the fear of losing it setting in so early, don't ya think '-)?
My system specs are above, but I am running WindowsXPHome on a 3.0GhZ/160GbHD(140Mb free)/1gigRAM P4 with a GEForceFX5200 vid card with, I believe?, the latest drivers.

I am running WInXP Pro SP1 - will be SP 2 after tonight. GEForce FX5200 128k(latest drivers from Nvidia - going back did not help)...2 gigs of Ram, P4 2.6GHZ processor. 250 gig HD with 100+ free. I get OOMS, when saving, scatter-replicate then drop to floor, causes OOMS, moving around procedural terrains. IMHO, this latest release caused me more problems. The one prior I was able to complete a scene with 7+mil polys....with the newest update I can't get near 3mil polys before OOM. Both scenes are somewhat similiar in nature. I haven't had a crash when importing PZ3's though. I also have noticed when I load my latest scene...in the preview window, all the procedural terrains are missing, until, I click on them with the layer. My Vue preference are all off, except wireframe...no openGl(even though my card is compatible), no background draw. Sys tray only has clock/volume knob/disc detector open. AFter obeserving the mem ususage Vue is NOT using all the avail mem at it's disposal.

Guys, instead of posting it all here, let E-On now, flood there user board with these messages! Why, since I'm getting the feeling that E-On really isn't taking these OOM's and other Mem related problem to serious at times. Also keep in mind that the update still isn't official, it's in beta. The auto update feature of Vue 5 doesn't recognize any update yet.

There IS quite a lengthy thread already at the e-on user Forum regarding these very issues with what seems to me to be some very knowledgeable users chiming in! As for e-on's response to these posts, they seem, to me, to be very evasive in their answers up to this point. I keep telling myself to just ride this out and things WILL get better, but it is such a disappointment after waiting so eagerly to make the move from v4 to v5 to have so many issues with it! ...resuming my "things WILL get better" chant now... ==steve==

Every once in awhile I run into OOM. The main issue that I still have is it crashing with procedural terrains. I haven't used those very much but I am starting to. *** P4 3.4Ghz/610Gb HD space(250,200,160)/1Gb RAM/ATI X700 Pro 256Mb PCIe

Just to chime back in at this point, I'm running Windows XP home, sevice pack 2 on a P4 2.54 GHz with an ATI Radeon 9600 XT. SMT