Having some difficulty in Vue4, I'm able to render out at as large as 1600x1024, but when I go to render out a larger image, i.e. to file, Vue seems to dissappear / lock up. I am reluctant to close the app, but it doesn't show it progressing.. Is it still rendering? I'm trying a 4000x3000 render at Ultra... or will this take me a week? Machine = 1.6Ghz, 512Mbs Ram. Thanks!

It will take a week and if you don't have your computer set up just almost perfect you'll have problems. You should be rendering to disk with such a size but that in itself is tricky cause you have to save the file with the render settings you want to render it then render it to disk. You basically can give up using your computer for anything else till it's finnished unless you know how to put Vue from normal cpu usage to idle. I do that then I don't have as many problems cause Vue willl let go of the processor a bit if I go check my mail. The biggest problem with rendering such a large size is the swap file can consume your entire c drive before it finnishes cause it will only get resized when it'x completly finnished. We need tile rendering. The other thing I do is hide everything so like make sure all the views are on hidden layers then when you check it from the screen saver it don't have to try to update all the wire frame views in the background. Just forget it exists and it will render......

thanks for your help! Hmm.. I guess it will take a week! I'm at 1600x1200 right now, and it says it will take about 3 hours... SHEESH! And I DON'T have a slow machine either! 1.6Ghz, 512Mbs But when I tried to render to disk, everything just seems to dissappear... or Vue seems to lock up.. wtf? Maybe I have something set wrong? What are the settings you usually use? Kltuzo

No you can render that size but when you render to disk it sorta forgets about the screen and just think it or it could take hours just to do a single line at a really huge size so it will also take hours to update the screen so it appears dead when it's hard painting your picture.Best way is to use two computers one that you can walk away from and one to use in the mean time. That's how I did mine. I've rendered bigger. You want to look at last years renderosity magazine contest threads that should be here on this form somewhere. There is a whole ton of threads there about rendering big pictures and the problems with it. See all the submissions needed to be also done print size that was the killer. Ya sure it might say 3 hours but it will take another 10 hours to do the antialasing pass and that don't show up on the counter. I just finnished one it said 3 hour 45 mins and it took a total of 17 hours to finnish completly and if you got any glow it will do two more passes after all of that that totally seems that Vue is locked up cause it don't update the screen at all on those passes till it's completly finnished. We need tile rendering and that's as simple as that. All of those problems would vanish, Hopefully it's in the next version cause it has been suggested. It's stupid trying to render a big picture all at once. Computers can hardly handle it and if anything goes wrong you got nothing to show for it. If you where tile rendering you'd only have to do the tiles over again that got munched. Mojoworld has tile rendering in version 2 but I suggested that for Vue way before that program came out. Like last year already during that contest.

The best way to see if vue is locked up or hard at work is check the proccesor usage. I use a little program called Wintop cause it's tiny and adds almost no load to the processor it self unlike micronots bloat viewer... If it's locked up it will be using no cpu power and if it's hard at work it should say around 98% cpu power.

Attached Link: http://www.dewassoc.com/support/useful/wintop.htm

WinTop

Attached Link: www.blehq.org/

Then I use a program called Process Viewer 2000 to actually change the cpu priority of Vue to idle from normal. it;s almost the same program really but I like Wintop and just use the other program for that single function. You got to be carefull with that one cause it has to stay on the task bar if you change the cpu priority and also it does not auto update you got to do it manually. Also the changes of course don't stick so if you restart Vue you got to set it to idle again I can't seem to connect with this place right now though.

Hmm.. so my overnight render, that I killed was probably working ot then! DOH! I went into processes, saw it was doing something, but I wasn't patient enough, and just Killed Vue.. =< NUTZ!!! sigh I wish it woudl give SOME feedback when it renders to DISK.. it just looked like a normal dead app. Is this what you get when you render to DISK only?

Oh BEWARE if you bring up stupid windoz task manager it WILL REPORT VUE DEAD ! you have been warned. you got to use wintop or something to monitor the proccessor. It's the way it works it only updates the screen when it writes to the screen and that's the way all windows apps work, problem is the time between is huge on huge renders like it could take hours for it to do a single line. It don't matter if you render to disk or the screen it's the way windozs works. It doesn't have a seperate proccessor for the screen so it has to wait in line for a opening on the clock cycle. It's a serial computer, one thing at a time. Wintop and some apps will work cause there only 16 bit and if you put Vue to idle it will give up proccesor resourses faster then if it's set to normal so basically if you do that then use the computer lots to do other things while it renders it will of course take even longer to finnish. Like I'm rendering right now. I'm always rendering but I try to limit my activity while it renders. Like I serf the web limited and that's about it. I don't start up anything big and wait till it's finnished to do other work.

Hmm.. interesting.. Very helpful stuff... Have you tried the Network Rendering? I have 2 other 'puters that I could call upon for rendering power if need be...

No I haven't I don't think that'll work, If you think that way you are in for a suprize, it's not really network rendering unlike Mojoworld. If you do a animation it will do alternate frames on different puters. Single pictures your out of luck. Mojoworld will divvy up the tiles onto seperate networked machines and the last one to finnish will put the tiles into one big render for ya. The best way to do it and the way i've done it in the past. The fastest machine gets the render job. Use the other puters in the mean time to keep you from going nuts waiting for it to finnish. Just forget that machine exits till it's all done. Make sure you have about 3 gigs free on c drive before you even start for room for the swap file. Write E-On and suggest tile rendering in case they forgot !

SO no dice for Network processing then.. Man.. DOH! Mover is JSUT
for SEPERATE frames then .. for the animation. Ahh.. oh well... I
always thought the newer 1+ GHZ computers now have enuf speed to
render out something nicely.. I guess not.. =

I've heard that Bryce is slower yet??? Is this true? Holy cow..
Anyways, just checked the RenderCow PDF, and it does indeed only
allow for rendering on a network PER anim, NOT per FRAME. =<
SIGH oh well.. I guess I now have to wait 5 hours for my render!
=

Attached Link: http://www.starbridgesystems.com/

It don't matter how fast you think your computer is even if you had a 20 gig machine you could bring it to it's knees with Vue or Mojoworld for that matter. What your trying to do with a computer can't really work well unless it was a true parallel computer. Your trying to paint a picture one photon at a time. It takes forever. You can't be in a hurry. You can speed it up by really carefull planning and grouping. How much? If you do a good job on your scene and plan it well and group it properly you can cut the rendering time into 1/4 or more. You got to try to limit the math the computer has to do in order for that single photon of light exiting the camera to find the light source. If it's got to look at every single element in your scene 8 times or more for every photon it will take forever to render. See a parallel machine could do a whole bunch of photons at once. Like I say forget the damn speed we need multi prossesors! Why are we still building single or even double proccesor machines? We should have a thousands of them under the hood. Even 200 MMX's would blow away a 2 gig machine. The whole way the computer world works is wrong. You got to look at starbridge systems computer it has NO proccessor, none, it's all memory. You put in the data on one side and it comes out the other finnished. the memory self configures itself like a proccessor on the fly and it's really fast like terra bits fast and it's totally parallel. They call it hyper computers and they blow almost everything away. There not that expensive but there not cheap and you right now have to write your own software by the looks of it though the memory operating system is already written. You use another computer to feed it data. Windows 98 belieave it or not ! Till we all have that sitting on our desktop it will be wait and wait cause the computers are the bottle neck right now. Get that puppy o your christmas list !

To do a really big render you can with a bit of math and a bit of planning you can actually do tile rendering in Vue right now one square at a time what you need to know is the exact focal length cause 18 mm is exactly 90 degress FOV. So ie: Say i want to render a picture 1000 X 1000 at 90 fov but my computer is trash and can't handle it. Tile rendering without the support. Ok say I got my scene and it just happens to be set so the camera is pointing south 0 degrees and it's sitting level so it's sitting at 90 pitch. I can't render this impossible size so I figure that i'll do 4 500 X 500 renders than paste em all back together when it's finnished. So set the camera first to 32 mm which is now 45 degrees FOV tile upper right 135 pitch and roll -45 render then 135 pitch roll 45 then the bottom two are 45 pitch 45 roll, and finally 45 pitch -45 roll. See easy and you could split that up across 4 computers to get the job done in 1/4 of the time ! Hun can a borrow your computer for a few days? ! D'oh !

Hey! I like the tile-rendering idea! Finally a creative approach to enable "network rendering". ;) Will hook up my old P3 over the weekend and give it a shot . . . thanks for the hint. ta, -Sascha.rb

As it is impossible to do tiled renders to disk, you only can do it for render to screen. I do it in stripes, much easier then tiling otherwise. Guitta

You can do it to disk to if you save each camera view as a seperate file but strips is a great idea also.

oh beware there is things that do not work if you try this. Lens flare could be a problem and having the sun set to follow the camera will goof ya up good. Pointing at camera is ok. Avoid lens flare even though you can actually set it up so that it will render properly across the gaps avoid it. Add it later if you need it it's easier. (post process)

Funny in a way this is exactly how I do all my renders. I mean all of them. I break them up into 6 pieces and do them them one piece at a time. If one goofs up whatever I just rerender it. Otherwise I'd need 6 times at least the computer power and I don't got that here right now. One piece takes about 17 hours to render so it's acceptable. Otherwise my computer would be locked up for weeks at a time.

Attached Link: http://atm.rm.it/

Hi there, regarding Process Viewer 2000: apparently, it has been discontinued. I personally use ATM ("another task manager") for setting process priorities. It's almost a combination between PV2k and WinTop; you get Wintop's overview and PV2k's task management. ATM lets you even set priorities for seperate threads in an application. Oh, and it's free, too. If you need a task manager for Win9x, give it a shot. ta, -Sascha.rb

Ya but how do you download it? Why do people write such silly pages? You go there to download it but there is no link to download it from only mirrors of the same page. That's ok though I downloaded it anyway. I did a search on google and got it from somewhere else. That's the second silly page I ran into today, They're breeding !