I realy realy realy hate the /&#/##//%/ vue ! :((((( Memory problem again. Why the (/%(&%#&%# do Vue refuse to use more then 1.66 GB ? My comp has been set up at 2.5 GB. I got 1GB Ram, and vue still %&#;/&%#/ up.... :( It even refuse to let me save my work :.(

Man what are you picky lately, is it your time of the month or what?. Really think the problem is not in vue.(In that case we should all have this problem.) Maybe Its a pc problem or you try to make something with 600 zillion poly's One cannot blame Vue for everthing. regards nice weekend Maria

I have trouble from time to time, but most of that is my own fault...Sharen

Alekssander, it happend to me quite often that Vue did not even let me save my work. A popup with just Vue d'Esprit and OK in and nothing more, no error message, no explanation. The computer freezes. And I have less of half of the power of your 'puter. That's why, when a scene becomes to be very heavy, I do the following (ALL OF THEM): 1. Shut down ALL resident programs, except EXPLORER and SYSTRAY in doing Ctrl+Alt+Del for each one before opening Vue. 2. In Vue I group all objects that can be grouped. 3. I HIDE every object and Layers that I have not to see absolutely 4. I disable OPENGL (needs to restart Vue) 5. I close my internet connection (normally always on) and stop my webcam, of course. 6. While working in Vue, I open sometimes "Rsrcmtr.exe" from the Window folder to see how much memory I have available to work with and close it immiately after because it also takes memory. 7. While working in Vue I save my work after each 2 or 3 changings in my scene as scene1.vue the first time, as scene2.vue the second time and as scene3.vue the third time. Then starting again for the fourth time to save as scene1.vue and so fort. If ever there is a problem, I always have a recent save from my scene. And believe me, I have scenes they need 12 minutes to save (my latest forest image is just such a sample, there are about 100 real trees and lots of other plants in, as well as lots of fog.) 8. And last, but not least, when I feel Vue becomes very slow, I save and restart my computer. All these things are very constraining, but what wouldn't I do for my love Vue? (LOL) Guitta

"Man what are you picky lately, is it your time of the month or what?." Yeah right...lol.. The problem is vue, no other software I got have this problem. No it's not the number of poly's. When I start the render, it works fine from 1-43%, vue only increas the usage of memory with 40MB. From 44-45% it suddenly increase the usage of memory with more then 1 GB. There is more then enough memory, but Vue refuse to use the rest of it..... If you had been working on a probject for months, just to find out that there is a bad "ghost" in vue, you wouldn't be very happy either... and I'm loosing time..... Have a nice weekend too, hope you got better weather in Holland. It's snowing up here, and freezing cold... Greets Alekssander

Sharen: I can't change it, and it's not my fault. Read the answer above. Guitta: 1 & 6. I have 1Gb Ram and 40 GB free on my harddrive, but vue "can't" use it. 2-5 already done that. 7 Can't change it, have to render it as it is. 8 It's not slow. The render is realy fast, but it don't use the memory correctly. Also read the answer above. Do I have to reinstall Vue?

Alekssander: 7. You CAN! save your scene as many times under different names as you like:-). That's just for security.

Guitta: Yes, but in this case no. When I try to resume render, when rendering to disc, Vue is not very happy. When that happens, I'm not very happy and write things as the first message ;) At the moment, I'm copying scenes and images as crazy, and I have started to resume render from 43 % about 3 times know.... And I am saving it 10-20 times. When the scene is 200MB, 200MB x 10 = 2000MB and so on.... I always have 99% of the scene somewhere else, but it's offcourse the last 1% I can't remember how I did. arghhh Just curios, what are you suppose to do with 100 real trees, begin as a lumberjack?

No, no, maybe my bad english... Save your scene BEFORE you render.

Alexssander tell me what the problem is and I'll tell you how to get it to render. I've rendered huge files. Bigger than that. One thing NEVER save under the same name. It don't work that way. Save it cool1.. cool2.. cool3.. like so so that it does not erase the prevoious version or rename it to backup or what ever it does with the old file. I found that fixed lots of files. If you don't think it can be done you're wrong cause if you look at my Wish picture it can be done. That's a huge huge file man. I saved it probibly over 50 times building it up to it's present size. You can't be in a hurry. Take your time, take a deep breath and count to 10. If you're making huge stuff you have to have patience or your doomed. Later on use file explorer to delete the interm files then reboot to get rid of all the temp buffers. keep the last two file for safety. You got to start you're computer up. Turn off everything start vue and render to disk. No Peeking. Walk away till it's finnished. If you don't it will not work.

One thing NEVER save under the same name. That's exactly what I try to say 3 times now to Alekssander, but my English must be so bad that he did not understand:-( Guitta

The problem is that vue don't use all of the memory available. From 0 to 43% it renders as it should. But from 43 to something (don't know yet) vue use 1Gb memory for each %. "Turn off everything start vue and render to disk. No Peeking. Walk away till it's finnished." Have done that a million times by know, and I get the same message, not enough memory. There are a lot of memory, but vue refuse to use more then 1.66 GB. When I had 512MB Ram, it stoped att 1.66 GB. I installed more and have 1GB Ram, vue stops at 1.66 GB. Same question as earlier, do I have to reninstall vue?

Ya see think of it you make a file and save it... Cool1.vue or what ever it is then you save again it saves it coo1.temp then renames the old one cool1.bak then renames cool1temp to cool 1.vue or what ever the extention is. That's once, keep doing it and the renames kill the computer. You can't do it that way. It don't work with huge files. You'll crash something.

Ok then go here: www.memturbo.com And download the program and install it. it will work for 30 days for free and your problem will vanish.

When you got the dreaded Not enough memory have File explorer sitting running on the task bar. Check C drive... Is it full? That's what killed my attempt ant rendering Wish. The C drive filled up completly. The Swap file is not suppose to exceed 4 gigs in size and you got 1 gig of memory do the swap file probibly cannot get larger than 3 gigs before that error will show up. It's out of memeory cause the swap file is too big. That Microstuff Not Vue In the what do you want in version 5 I suggested tile rendering to avoid all these problems. You guys all understand now why it's so important? Hope ya voted for it.... Work around would be to some how try tile rendering with the crop window and use a different progem to stick the final picture back together. Like cut the pictures render size in 1/2 them move the camera so only the top renders then do the same with the bottom then use a different program to stick it back together. Ya get it?

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12368&Form.ShowMessage=911576

Ya see his problem, actualy everybodys problem really is that people are pushing the envelope of what Vue can render. The problem is there coming up to the limit of what Microstuff can do in that there reaching the swap file size limit. That's not a bug in Vue it's Microstuff's bug. The swap file will not resize when it's in use. The only way to get it to resize is reboot really. Tile rendering would save us all this greef. YL your problem was a memory leak which we never ever figured out it's cause. Could be two PCI graphics card conflicting. Who knows. Now see I already though of all this before over a year ago already. Check my posts man it's documented here somewhere. The problem is the crop window you can't set it size. If you draw a crop box Vue will make that little box full screen. It shouldn't. You should be able to set it to say 1280 X 500, you can't. I pointed that out over 3 years ago with Vue 3. It's still that way. Now the big problem comes in how do you do a tile render when it's not supported in Vue. Man that's difficult cause you don't have the camera control. Like you got to keep it all simple or you can't figure it out. This would work: I got a image I want to render 5000 X 3000 say I set my camera to 90 FOV pointing 180 by 0 I tell Vue to render a pic 5000 X 1500 I set the camera to render the top 90 FOV and I got to move the camera up 45 degrees So that would be 90 FOV 180 by 45 Bottom would be 90 FOV 180 by -45 Ya get it? Now change the camera to say some other size like 28 FOV. Now what ya suppose to do? Tile rendering man would save us from this nightmare.... Hope ya all voted for it...

MightyPete: The problem is vue, nothing else....lol It renders well from 0-43% it's pure hell between 43%-46%. From 47%- (don't know yet)seems fine. The part from 43%-46 is more or less exatcly the same as everything else. More software don't help. There's enough memory, but vue refuse to use more. I have already tried another software, that has the same function. Didn't work ... lol There are 40GB free on the harddrive, and again. There's enough memory, but vue refuse to use it. 1.66GB is the limit. "Like cut the pictures render size in 1/2 them move the camera so only the top renders then do the same with the bottom then use a different program to stick it back together." Can't do that, I have to render it as it is :) YL: The problem is vue, I have tried other softwares (video and animation) and they work fine. I can even run several (vue, poser3, meta) programs at once. But vue stops 1.66 Gb, so it's not the system. :) ...lofl ... I'm going to try to reinstall vue, to find out if vue use the OS info or its own.

Well one thing having a hard drive sitting there at 40 gigs is not too smart. The location numbers get way too big. You should resize it. A 40 gig partition is too big man your just asking for trouble. Whatever memory manager your using turn it off and try the one I sent you. It works, I've used it now for over 8 years. Noticed while I was rendering Wish: That file took 110 hours to render 12 hours to render to about 43% 12 hours to render 57 to 100 % The rest is from 43% to 57% that 20 % of the image took 86 hours to render, The horizon killed it for some reason. It's normal. Yer not suppose to peek remember? It don't matter how long it takes if it never finishes it's pointless right? Give it time it will render. About the 40 gig hard drive? Your going to waste over 10 gigs just in slack space trying to keep the computer figuring out where everything is. Slack space don't show up in disk free space. Your also wasting 4 gigs just for the trash can.. Resize it.

Attached Link: http://www.melbpc.org.au/pcupdate/9611/9611article6.htm

I got 256mb RAM on a 450mhz computer and I have NEVER EVER had a memory problem or the errors you describe. Admittedly I haven't juggled huge numbers of polygons, but one time I tried a 30million polygon object and I still didn't get any memory-related errors. I did however get other anomolies. I was still able to save and render it, though. I have hunch something's not right with your computer, or the ram. Maybe Vue uses memory differently than other programs and has a problem with your ram. Which Vue update patch are you using? (Maybe theres a relevant bug fix in the latest one). Hope you get the problem sorted soon, Vue is too good a program to throw out the window :P JoeBlack

Maybe,the problem lies more on the side of the system you use :In case of using a pc ,when I upgraded to 1gb ram in my computer I had several problems with win 98 se which wasn't able to adress that ammount correctly.I had no problems with my "paralell" NT.After changing the memory adress settings in the registry it disappered.Win Me some- times has the same difficulties.Perhaps you should check that point (if you're using these systems on a pc,of course) If not maybe get the latest chip-set drivers (especially if you're running an Athlon Xp in combination with DD-rams) Fredi :-)

Maybe not. I can't find too much stuff on NTFS other than whatever ......... I don't know if there is a limit. I can't think of anyone to ask to get a answer back fast. Most computer hackers I know know better than to install XP. So it really limits the brain pool. I think your drive is to big but who know it's NTFS. Tile render it. If your getting a out of memory error it is because you have exceeded a file size. Chances are the pageswp.sys file. Install that program man. It will keep memory clear and if you get the dreaded error again you have EXCEEDED some file size in XP not Vue.... Lets all vote for tile rendering support ok?

Alekssander: Could you give your system specs, including OS and any kind of software with a dongle or a software lock, like P5 or Max? As for it only addressing 1.66 gigs, don't forget that whatever OS you are using has to have some space, as well as any other TSR or background app. And when you are hitting the swapfile hard, as in a huge render, it needs even more RAM. You're talking about 840 megs free for OS and anything else you have. That may be a lot....or it may not.

Whatever I rendered files in Vue 4.0 not 4.1 It wasn't out yet 168 meg files. Windoz 98 512 meg memory. It rendered. 176 million polys. It worked but it was interesting for sure. He's using the dreaded windoz xp. It doesn't have a too much memory issue like 98 and ME had.( there is no issue here anyway it requires a single line to be added to the 386 section of the system.ini file) It still could have a 4 gig limit on the swap file size. It probibly does. It's only a 32 bit proccesor not 64 bit. Your a xp ginny pig. Who knows. Windoz is such a pig to that it just so wasteful of system resources it's pathetic really. It may be possible to tile render it a easier way but it hard to check here cause I'm rendering in a differernt program. Cool it's finished. Actually it's not as bad as it looks. Maximize the one screen right click on it and pick select render area. Draw a box what ever size you want to render hopefully going cross the entire scene. Render it. save it. Move the box down now render it save it. Try hopefully to get it to overlap slightly just in case. Render it save it. Get out some glue and paste em back together in a different program. Problems. I don't think you can do this bigger than the screen size. You can always make your screen res bigger though just for rendering then put it back later. It's worth a try...

His specs are windoz xp 1024 meg memory and at least 40 gigs free space on c drive. He says he's turned everything off only vue and a memory manager. I think he's trying to render his chandelier. It's insane. We already seen a piece of it already posted here somewhere.

Alek... I know exactly what your problem is... I had that same problem when I first started using Vue and found out that the problem wasn't with the program but the fact that my computer was over-clocked. That was done by the people the built my computer without my knowledge. Explained alot of unexpected lockups for no reason as well. If you still have your computer motherboard manual... check it and find out what the jumper settings are for the clock mHz speed. And set it down one notch. You'll find that the problem you're having goes away! Let me know if that helps! -=> Jim! <=-

I was sure that my problem was due to vue (cpu not enough cooled) ) but it was not. Wait a little before re-installing Vue, you could lost some pics. See what LrdSatyr8 said. Check cpu frequency , if it's not that, could be air cooler. Yves

MightyPete: The memory has been set to 1GB Ram and 1,5 GB on the harddrive. That's 2.5 GB all in all. When I only had 512MB Vue used 1.66GB when I installed more it still use 1.66 GB. "The horizon killed it for some reason" Some reson? lol That could be the problem yes, but only partly. Vue don't clean up its own memory garbage. "Give it time it will render." It don't, it stops at 1.66 GB what so ever. I'm not using 40 GB, I'm using 1,5 GB. So that's not the problem. But there are 40 GB of free space. JoeBlack: The scene is not big, only 8 mill polygons. My computer works fine on other applications, vue is the problem child.. :P ..lol.. I use Vue 4.1 and Crucial 2100 DDR Ram. Rollmops: win 98 Se have a limit of 768 MB Ram. I use Win XP. Dale B: I'm going to run a test with Max later. See the answers above. MightyPete: Yes I know, I'm a ginny pig. The problem in this case is not XP. "I think he's trying to render his chandelier. It's insane. We already seen a piece of it already posted here somewhere." It's not the chandeler. The chandeler works fine. :) LrdSatyr8: I doupt that my computer is over-clocked, but I can always take a peak. Never know what people do sometimes. But other applications runs well. Vue don't.

Man your hard to understand. Hay man XP hidden files all over the place if your telling me you got a 5 gig partion well that's you problem make it bigger say 10 gig. Remember the trash can takes up 10% even when empty that's 500 meg right there. Ya can figure a bunch more of hidden files I've heard almost a gig could be on a xp machine according to the guys at windows annoyances.com. It reserves space all over the place....

Like think of this you're I think I finally get it your telling me you got a 5 gig partion right and 40 gig free space not in that partion. It don't exist to the first partion. It's not there you can't write to it from the first partion. Then I think your telling me it's got 2.5 gig free space right? Garbage can takes up 10% of 5 gig that's 500 meg you only got 2 gig free then you got a file allocation table that could easily be 400 meg no problem. so you got 1.66 gig left what is the mistery the drive fills and it crashes. That's not Vue that's your computer is screwed up cause it's not set up properly... What is the mistery here? D'oh !

Then he never comes back to explain again what the hell he got there......... Like your not running Linux man Windozs is a pig, it wastes space all over your drive. Micronot don't care they got plenty of cash to buy bigger drives.... Don't think so? Search for mscreate.dir Search all the drives, Find any? They should be hundreds all empty wasted space cause microduffs are to stupid to delete them after they install more garbage on your computer... The garbage can takes up 10% of your drive COMPLETELY EMPTY... They don't deduct it from the usable space though cause they don't want you to know that there software is a pig. IE HIDES files all over the place so they know exactly where ya been on the web so they can send you spam... It never ends.........

I write again: When I had 512 MB Ram, vue used 1.66GB. when I installed more, 1GB all in all. Vue use 1.66 GB. This has nothing to do with the harddrive. Vue refuse to use more then 1.66 GB, what so ever. Other applications run fine, vue don't. If it was XP or the comp, all apllications should stop at 1.66 GB, they don't ;P , if it was trash or spam, vue should stop at different places, But it stops exactly at 1.66 GB. not a k more, or less. If I stop it a 100 MB short of the limit, I'm not aloved to save it, beacause that takes to much memory, and I get the same message. Not enough memory. I can then run other application, so theres enough memory, but vue refuse to use it ;P When I have finnished rendering what I'm rendering at the moment, I'm reninstalling vue, to see if it is a programming mistake.

YL: I take a backup before I reinstall, so I'm not losing anything :)

You're the only one having this problem !!!!!! Lots of people are using Vue on XP I think we would have heard lots about it by now if people were having problems rendering a file that's only 8000 polys, Don't you think? Have you tried a different file? Maybe you got a mesh leak or somthing happening there, a divide by zero or something.

I love vue, and I have a smaller windows system than you do, but I NEVER "render to disk" after having read of many problems in doing this, and I do not stop a render and then try to resume. If Vue has RED numbers down in the lower right and I know the scene contents are getting "heavy" I do save often (I am able to save to the same file name, it creates a .bak file of the previous and saves it new for me) and I use only vue 4.01 patch... I have heard how glitchy XP HOME is, but that XP PRO is the fix for it... (costs a lot though).. I use win98se still. I remember some folks saying there is no finished picture when the render is done or hangs, but I think it ended up in one of vue's folders when that happened, so it was there anyway... I do hope you can figure out what is going on.. I don't think you would be so angry if you did not want to use Vue so much... It IS worth the effort to try to figure out things.. OH and having small partitions on a hard drive is bad stuff.. it limits the swap file of windows... I learned the hard way NOT to divide up my large hard drives.. For safe keeping I will make an archive folder, and burn the things I want to keep to CD as soon as there is enough. XP is not fun, the home version, anyway.. I go nuts trying to help my friend FIND things, find ways to control her settings.. all those nice friendly things are now hidden in xp home.. microsoft made a BAD mistake with this stupid version and had to fix it in pro... (or was that on purpose to force people to 'upgrade' to pro?? grrrrr!) Lyne

Just to make a small correction, the link regarding partitions and clusters relates to a pre-win98 form of FAT (FAT 16). It is possible there are newly formated FAT16 partitions around, but unlikely. FAT32 allowed for smaller cluster sizes (the real cause of slack space) and NTFS (often XP machines are formatted with this) has even more control. If your machine came with XP, it might be formatted win FAT 32 (the 98/ME table) which is clunky but somewhat more expediant than NTFS (there is more book keeping required for the security features). I know you can translate a data filled partition from FAT->NTFS, but I wouldn't want to risk going the other way. Not sure which to recommend. If you have XP, and mutiple partitions, you should be able to add additional swap files. I don't use xp, but it would be in the Control Panel->Administrator Tools->Manage Computer ish area (that is close to where I find it using win2k. Of course, you will have to run it as administrator to change swap file stuff. I don't know where the fault lies. I have rendered rediculously large scenes without much difficulty (100Ms polys). I have noticed that switching from vue to browser sometimes leaves vue hung, so I don't do that anymore. One suggestion, make sure you have at least the same swap space as ram (or 150% as much). Try and keep the swap file from getting too fragmented (yes, it resizes upwardly on demand with win2k and XP) If you suspect you have a fragmented swap file, Norton can take care of it, or you can .... disable swap file, reboot, defrag, re-enable swap and set it to a good high number I had some really annoying crashes a few weeks back and reinstalled. It runs fine now (actually had to reinstall Win2k recently....kept failing to load logon mgr), so there was probably a bad sector that took out a critical file during a recent shut down. It can't hurt to try that method(though it is unpleasant to reset all of those personlized folders back up) We all know how much windows likes to have stuff reinstalled :) Hope you can read all this mess :0 Eric

I have had a lot of trouble with render to disk, but my solution and it may help for you Alekksander is to render to screen at 1600x1200x600 DPI and then resize/sample it in Photoshop or some paint program. This method seems to work pretty well for me to get huge renders suitable for print... Just a thought...

I'm using win 98se with 1024 mb ram now (for playing!). Even win 2000 pro has performance problems in certain configurations with the memory adressing when you get over a certain limit.Win xp home and pro are the newest, but certainly for some applications not the best os'ses (that's why they released their service-pack lately). Perhaps You should try to install Vue in a different partition,could be a problem with the virtual memory used by you os and Vue at the same time (page file sys). :-)

Eric thanks for explaining. I tried to ask my hacker buddies but there too smart to install Xp. It really drains the brain pool. Ya I know that's old and outdated but it explains slack space. I can't find info on NTFS and what it quarks are and no buddies to ask around here about it. Roolmops. You got 1024 meg in se? Did you have to add a line to the system 386 section of the system.ini file? I've been wanting to talk to somebody that actually did have 1 gig on se cause there is to much BS going around about it cause of micronots attemt to sweep the bug under the carpet instead of admitting they're goofs. ie 1 gig example: [386Enh] MaxPhysPage=40000 ie 756 meg example: [386Enh] MaxPhysPage=30000 If you haven't and are experiancing problems you might want to try it It just limits the table size. All memory is still available.

Hey mighty pete, here's more ntfs BS than any sane person should want :) http://www.digit-life.com/articles/ntfs/ I scanned it, and it seemed to have some useful info, though it is very pro MS (I'm not) I use win2k, because I can't afford a mac at this time, and there is really no alternative out there for consumer apps (Love linux, but there isn't a strong enough emulator that I can afford that doesn't drain the apps performance to a useless level....hopefully things will be very different in a year or so) Alekssander, something I thought about shortly after I left an earlier message, is the opengl stuff. Now that brings my system to it's knees and makes it beg for a cycle or two (I have it set to pretty low quality) Perhaps, if you are rendering a large scene, you should turn opengl off. When you think about those millions of polygons periodically being traversed and applied to some drawing algorithm, it is quite a demanding thing, indeed. It's worth a shot. I know my machine (750 mhz) is pretty much useless when the quality is turned up and I have a complex scene (menus take seconds or minutes to respond). Simply put, it is really a lot for the machine to handle. Try doing without it. As for vue and memory, I am a programmer, and I can think of a few odd things that could lead to vue having a limit, but I doubt that is the case. Most likely, the message you have given is due to a new operator returning null which is due to the OS having nothing left to give the app. I guess it is possible to blame Eon, but I suspect the real problem lies elsewhere. Just a thought, Eric

Found that link yesterday. Ya I read all of that. Very dry. Stuff I want to know is not there. You can tell I'm not a micronot fan, it shows, don't know why. I figure the whole tech industry is going to crash actually. Everyone is waiting and nobody is coming up with a solution to M$. This 98SE I got here is my last M$ product ever. I had enough already. I think a lot of people out there think that way. Linux better get it together. We need to be able to run things like Vue on Linux. Or E-On is going to have to start writing for Linux cause it's coming. M$ has already lost over 200 Billion dollars and they still don't get it... Just as aggnorant as ever. Weird bugs and patches. Where do you want to patch today?

go to control panel>system properties>advanced tab>settings>set to custom: remove all but the smooth edges of screen fonts. then hit ok. stay on the advanced tab & go to visual effects>performance options>advanced tab>virtual memory>change>custom size & set it to whatever you need say 2gigs (2500 approximately) also remove all the "extra" fancy stuff that has to do with the new improved gui for windowsXP & then go to the vue.exe & right mouse click (go to the compatibility tab & set compatibility mode: set for windows98/me, disable visual themes & turn off advanced text services for this program. hit OK. & that should get some of the memory resources back for you & help in rendering larger files for vue or something else. if that does not help, then you're on your own. try emailing vue to see what they say.

hi, how small are may problems on my Mac when i read this discussion. :-)) But one question Alekssander. Is it absolutely clear that the problem is not in the file you have produced? I have seen a lot of beautiful images from you where your system never seemed to have any problems. So for me this is an indication, that the scene you are working on does have a problem. Could you send it to somebody else (another system) to test that? Thats what i would do first. I know that 200 MB are not easy sent, but at the moment it looks like that everybody is poking with long sticks in the fog (or in deep snow - in your case) I had problems with Vue files from time to time that scenes suddenly became corrupt. Especially after a system crash while working on that scene. Bad luck.