Topic: Extreme lag during render time

[Dreamcube017]

I created a small video (about 30 seconds) and when I save to 720p mp4 video, it sits at the first frame and says it'll be done in an hour. It says it took 3 seconds for the first frame, but does not advance to the next.... or if it does, it doesn't show it. The mouse pointer also moves very slowly. I went away from Lumion and came back about twn minutes later to see it was still sitting on the first frame. It said 0 hours and minutes remaining with 0 seconds, so I clicked and it jumped ahead a few frames. (I just clicked on the white bar under the picture.) When it went ahead, it then said 83 seconds and remaing time was 34 hours... WHAT!? That CAN'T be right.  I think that was a miscalculation as it jumped ahead a few minutes later, but while rendering, the program seems somewhat unstable as it makes things very jerky. Are we not suppose to do anything else on the computer while it is rendering?

Has anyone else had this happen?

What other things is it doing if it's all in realtime anyway?

Specs:
win7 Home 64 bit
Intel Q6600 2.4 GHz
4 gigs of Ram
NVidia GTX 260

If anyone could help, that'd be great.

EDIT: Just tabbed back over and now it says 75 hours of time remaing with 162 seconds... ?

I remember using the old demo of version 1 and although the mouse pointer would hang, it never did anything like this... I hope this finishes by morning.

[Dreamcube017]

ha pretty funny.

Something's not right.. now it says 153 hours?? I could've just opened fraps and recorded it that way.

While things light Lightwave are rendering, I can do other things on the computer and it will continue to render.

This is just like using 3DS Max or Maya.... but WORSE because it's still like on frame 3! Something's not right.

I know this is the free version so I can't expect much support, but this is pretty much going 100% against the very thing they were trying to market the software for. Ease of use and speed... easy, yes. Speed... I think not. Hmm... I'll test.

[Dreamcube017]

Thanks.

I took your advice and just opened the Red Rock scene and move the camera around. It is indeed rendering much faster. So this brings me to believe that it was a combination of the object and/or the material. It was a highly reflective material with a lot of post effects. So next I'll try that same material on a simple object and then try the object with a simple material to see what causes more problems.

Ah, the flaws of user error. Thanks again for your advice. Should've tested this before hand.

[Dreamcube017]

Here is what I was trying to render. This is just a screen capture of the realtime view.

At one point it says it would take 1500 hours to render.

http://www.screencast.com/t/I3nBOGcc

[cpercer]

Lumion can not run in the background.  All rendering is paused if you switch to another window.  The large rendering time is displayed when you reactivate the Lumion window and the approximate render time remaining is recalculated.

Your model does not look too complicated for Lumion, nor would the effects slow it down much if at all.  Also, it is highly doubtful that any screen capture software could match the quality of the Lumion output.  The best practice is to render to an image sequence, then compile using VirtualDub or similar.

Cool effects, btw.

[Remko]

If we let Lumion run in the background all your other applications are unusable. I guess the Windows multitasking system can not handle the heavy GPU load. We tried several things to give the rest of the OS more time but nothing helped. So, we decided to stop rendering al together when you switch to another application.

[Dreamcube017]

Lumion can not run in the background.  All rendering is paused if you switch to another window.  The large rendering time is displayed when you reactivate the Lumion window and the approximate render time remaining is recalculated.

Your model does not look too complicated for Lumion, nor would the effects slow it down much if at all.  Also, it is highly doubtful that any screen capture software could match the quality of the Lumion output.  The best practice is to render to an image sequence, then compile using VirtualDub or similar.

Cool effects, btw.

I am a nearly broke college student looking for a job... image sequencing is not possible at this time... (unless I missed a checkbox somewhere)

I left the program open and it still read a rather large amount of time.
I'll give it another shot. Thanks.

Although I'm curious to know what is Lumion doing while it renders it? All the frames are right there because I'm looking at them. Does it need to pass them somewhere else or is there some extra final touch it puts on the final output that we don't see in realtime?

[Morten]

image sequencing is not possible at this time... (unless I missed a checkbox somewhere)

The information you're looking for is right at the top of the Tips & Tricks thread
http://lumion3d.com/forum/index.php?topic=638.0

Although I'm curious to know what is Lumion doing while it renders it?

In 3-star mode, Lumion applies 16x sub-pixel anti-aliasing to get rid of jagged edges. Filtering is applied to all effects at their maximum quality levels, all trees/plants are visible at the best level of detail and the landscape and the shadows are set to the highest possible detail levels. After anti-aliasing and filtering have been applied to the image it is finally compressed and saved in the output format you have chosen.

[Dreamcube017]

Gah, and of course I would miss that.

Thanks so much!