|
|
Rendering problems on laptop
About Truespace Archives
These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.
They are retained here for archive purposes only.
Rendering problems on laptop // Tech Forum
Post by wal // Jan 9, 2009, 8:02am
|
wal
Total Posts: 2
|
I am trying to render out frames to compile into a video... however, some frames have a black bar- like an un-rendered area- at the bottom of the frame.
Not every frame. But a lot of frames tho.
There's no pattern either. It's not every 3rd frame. It's irregular and intermittent.
Some "bars" or un-rendered areas are thicker than others.
What I am using is Truespace 5.2. I've tried 7.6, but it almost wants to lock up every time I open it.
My laptop is an HP Pavilion, AMD Dual core with a NVIDIA graphics cars. 2 Gigs of ram running Vista.
I would really, REALLY like to know how to stop this. This is for a contest, and time is running out.
Thank you.
Chris |
Post by Norm // Jan 9, 2009, 2:07pm
|
Norm
Total Posts: 862
|
Is this showing up in the final images or is this just showing up on monitor as render happens? |
Post by wal // Jan 9, 2009, 9:19pm
|
wal
Total Posts: 2
|
They appear on the final renderings. You see them when viewing individual frames, and when converting to a video, it becomes a very noticable flicker on the bottom of the frame.
thanks. |
Post by TomG // Jan 10, 2009, 9:17am
|
TomG
Total Posts: 3397
|
Hard to tell what that might be. Is the machine being left alone to render? Could be if other processes are running that they are grabbing disk access while tS is trying to write to the file or something. It might be that swapping away from tS as having focus to another app could do that, for instance. Or maybe anti-virus stepping in with a scan. Not sure.
So I'd be sure the machine is doing nothing else. Could also be a memory issue, how many frames are you rendering? Rendering them in smaller batches might help.
If you are rendering to an image sequence, I would just re-render the affected frames standalone (assuming you don't have 50 of those or something).
You might also want to try turning off multithreading for the renderer. Could be that something is grabbing the core and so one core is completing its task, while the other fails to get through its work before the next frame is started.
HTH!
Tom
EDIT - PS I would try rendering one of the frames on its own anyway, to make sure it isnt something in the frame itself (a shader or geometry problem). If it renders fine standalone, then continue with the "no other apps running, no switching focus, no multi-tasking" approach. If it still shows the problem rendered on its own, then its something in the scene.
Also, is your machine going into standby or sleep mode? Laptops do that, and that could also interfere with frames rendering or being written - could be it goes to sleep, then tS wakes it up again when it writes the next image or part of image to disk, or something - yes, guessing here :) But hoping something out of this might diagnose the problem! |
|
