Wed, Nov 27, 4:02 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Nov 26 6:57 am)



Subject: Rendering


whtbearfan ( ) posted Wed, 30 July 2003 at 10:38 PM ยท edited Sun, 24 November 2024 at 12:35 AM

Well I am wondering if this thing finished or not. I was rendering to disk a rather large pic and I got a message of Stopped! Render time: 16h03'05" The picture looks done when I looked at it in photoshop, but I thould it said Finished! when it was done. Also in your opinion is rendering to screen or disk faster? Can you render something that is 5600 x 4400 pixels to screen or not?


wabe ( ) posted Thu, 31 July 2003 at 1:02 AM

To your question. "Stopped! Render time..." means that someone has interrupted the rendering. Ppushing a mouse button probably by accident (thats why i take away my mouse when i am rendering big files). If it looked finished, lucky you. It means the render was nearly finished anyway. Rendering to screen is limited by the resolution of your monitor (as far as i understood). And wether rendering to disk is faster or not - others can tell better than i can. I don't have the feeling really, but i haven't done some real tests.

One day your ship comes in - but you're at the airport.


Sentinal ( ) posted Thu, 31 July 2003 at 2:21 AM

I've never tried rendering to the screen at a higher res than my screen res, why don't you create a blank scene, ie just the atmosphere and have ago? As to whether screen or disk is faster, dunno never tried, but once again why not try it yourself with a blank scene? I cannot think of a reason why the times should be that different, disk speeds and graphic cards speeds should be pretty irrelevent at the rendering stage.


gebe ( ) posted Thu, 31 July 2003 at 3:51 AM

Rendering to disk is lots slower then to screen. Nobody knows why. For sure your render has been interrupted while rendering if you got "stopped". Have a look at the upper and bottom borders of your image, maybe you can see some more pixels there:-) Guitta


Jackie ( ) posted Thu, 31 July 2003 at 7:07 AM

Stopped?! Do you have a Cat? LOL I have always rendered to disk, mainly because I render large, and I always get the "Image size is too big and may cause problems error..." when I try to render to screen.


gebe ( ) posted Thu, 31 July 2003 at 7:11 AM

Yes, you cannot render bigger then your screen. You must do it on disk. What I wanted to say is, if you have the choice, say for a 800x600 or 1024x768 render, to render to disk or render to screen, Vue is much slower when rendered to disk:-)


Jackie ( ) posted Thu, 31 July 2003 at 7:14 AM

Looks like I need a much bigger screen! LOL say uh, 3000x3000 ought to to it! :) Can you imagine!?


lingrif ( ) posted Thu, 31 July 2003 at 8:55 PM

I'm a newbie to this forum. Been using Vue for about two months and loving every minute of it. I visit the forum daily. I've learned so much from reading the postings, the tutorials. And I'm grateful for all the freebies posted here. I'm intimidated by the talent I see here - I've got a long way to go before I post anything. But, I thought I'd share this little tidbit. My screen resolution is at 1280x1024 (the max) and I can render 1600x1200 easily. When it finishes, I have to move it down with my mouse so that I can see the right corner to save.

www.lingriffin.com


whtbearfan ( ) posted Thu, 31 July 2003 at 9:12 PM

Okay everyone, something isn't right. I rendered on two different machines and both of them came up with Stopped! Render Time: The machines are in two different rooms. So what's the deal. Does this have to do with the fact I am doing an Ultra rendering or the size, the 300 dpi or what?? I have done three renders in the same number of days and all have said Stopped, but the picture comes up well in Photoshop. Is this just a glitch??


TheWingedOne ( ) posted Fri, 01 August 2003 at 6:58 AM

Have you installed the most recent update? Right now it's 4.12 (Vue 4.2 seems to be just around the corner). That might help, though I'M just guessing since I never experienced this error message. Phil


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.