Fri, Dec 27, 1:58 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Dec 13 6:58 am)



Subject: Rendering problem: the screen appears black!


Horsepower0171 ( ) posted Fri, 17 September 2010 at 2:05 PM · edited Fri, 27 December 2024 at 1:54 AM

Rendering problem: the screen appears black!

I have 3dsMax2010+SP1 and Vue 8.4 xStream.
I have made in 3dsMax one architectural scene; I have used a mrProxyObject for the elements of the high detailed roof.
I have used Vue to create the natural environment with Terrain, Plants, Bushes and Flowers.
The problem in 3dsMax:

  • At frame 413 of my rendering, the screen result, and also the FinalGather Pass, appear completely black!
  • Next, after some keyframes the rendering becomes correctly, and after others following  keyframes, the rendering returns to black!

I have checked others camera views, and the image at frame 413 is OK.
Just the "Camera01" appears black, and also when I convert this camera to "Perspective" viewport and render it, the image is black!

I am desperate to understand what is my problem, and I don't know if this is a problem of Vue rendering engine, or a mentalray-3dsMax problem!

It can be also an occlusion object problem, but I am not sure:

  • I tried to move the "Perspective" camera viewport a lot far away, but the problem persists.

Any suggestion?

Many thanks!
Horsepower0171.


bruno021 ( ) posted Fri, 17 September 2010 at 2:50 PM

Are you using a Vue camera or a Max camera?



Horsepower0171 ( ) posted Sat, 18 September 2010 at 4:04 AM

I am using 3dsMax Camera.
The Vue "MainCamera" instead, works correctly at the critical frame 413...


bruno021 ( ) posted Sat, 18 September 2010 at 4:46 AM

Is it possible that the Max camera is going inside an object/ecosystem instance at this particular frame?



Horsepower0171 ( ) posted Sat, 18 September 2010 at 1:13 PM

I tried to delete all:

  • all the Vue elements: environment, plants, terrain...
  • all the 3dsMax object, one by one...

As the result I isolated the problem:

If I tried to delete one wheel of a 3dsMax car model: the rendering works correctly.

Thus the problem is the wheel that interact with the rendering or FinalGather.

But I think this is not a material problem (of the wheel) that compromise the rendering:

  • I tried to "SaveSelected" - the camera and the wheel - as .max file; I clicked Reset 3dsMax, and tried to Open the last file: the problem persists!
  • I tried to Reset 3dsMax, Merge just the wheel with materials and the same camera: the problem disappears and rendering works correctly.

Thus I think that the problem can be some parameters or settings, in the 3dsMax Rendering Setup Panel, inherited from Vue, that interfere with 3dsMax rendering and in particular with the wheel.

But I don't know what precisely cause this rendering error!
Help!
Horsepower0171.


Horsepower0171 ( ) posted Sat, 18 September 2010 at 2:10 PM · edited Sat, 18 September 2010 at 2:11 PM

I tried also to move a little bit the Target of Camera01 (of 3dsMax), at the same frame 413; the rendering now works correctly with the car wheel...
But if I repositioning the Taget to the same previous position, the rendering appears black!

Help!
Horsepower0171.


Horsepower0171 ( ) posted Sun, 19 September 2010 at 6:56 AM

Today, I tried to cancel all Vue elements from last Max scene.
I tried to Reset 3dsMax.
I made one new scene by selecting Import>Merge all the Max elements without Vue elements.
The rendering at frame 413 is OK !

I Clicked "Open" Vue scene file inside this Max project.
Selected the last Vue scene file:

  • The rendering at frame 413: completely black !

  • What is that doesn't function in Vue Scene file?

Help!

Horsepower0171.


bruno021 ( ) posted Sun, 19 September 2010 at 7:08 AM

Which makes me think that the Max camera gets inside a Vue element in this particular frame....Could you tra,nsfer the camera path from the Max cam to the Vue cam, and render this frame with the Vue cam and see if it renders ok?



Horsepower0171 ( ) posted Sun, 19 September 2010 at 10:34 AM

Quote - Which makes me think that the Max camera gets inside a Vue element in this particular frame....Could you tra,nsfer the camera path from the Max cam to the Vue cam, and render this frame with the Vue cam and see if it renders ok?

Yes, I have made a test with Synchro Plugin for Vue xStream, synchronized the Max Camera01 in Vue, rendered with Vue at frame 413: the result is a good rendering !

I also tried to made another Camera in Max, by moving the camera position and the target position of camera, but the rendering error, in Max, appears in another keyframe as black screen! 
I tried to render this second synchronized camera in Vue, but it renders without problems!

The problem is not an object that occlude the camera in Vue, I think...


bruno021 ( ) posted Sun, 19 September 2010 at 12:17 PM

So maybe you could use the Vue Cam to render this doomed frame, and replace it with the bad one before editing the video?



valmik ( ) posted Mon, 20 September 2010 at 2:27 AM

i have faced the same problem earlier. but it is not the problem of max or vue now ur cameras,

just let me know ur pc config, which version of windows u using 32 or 64 bit?

when i faced this prob, it was because of 32 bit windows, even after having 6 gb ram n core i-7.
but when i switched to 64 bit windows, rendering worked correctly.

if u using 32 bit windows, then this problem will surely occur, bcoz ur machine wont use more then 2gb of Ram even if u hav more then that..

do have a look at ur stats, i.e... ur no. of polygons & faces... but i m very sure this prob, occurs due to win 32 bit...


Horsepower0171 ( ) posted Mon, 20 September 2010 at 3:28 AM

Quote - i have faced the same problem earlier. but it is not the problem of max or vue now ur cameras,

just let me know ur pc config, which version of windows u using 32 or 64 bit?

when i faced this prob, it was because of 32 bit windows, even after having 6 gb ram n core i-7.
but when i switched to 64 bit windows, rendering worked correctly.

if u using 32 bit windows, then this problem will surely occur, bcoz ur machine wont use more then 2gb of Ram even if u hav more then that..

do have a look at ur stats, i.e... ur no. of polygons & faces... but i m very sure this prob, occurs due to win 32 bit...

I am using WindowsXP Pro x64Bit.
I have Intel Core2Quad Q9650; 8GB Ram Kingston, GeForce 9400GT.
I have used Polygon Counter by Utility Menu in Max; the number of polygons: 5075263.

But what interest this details in rendering process?

bruno021 has said:

Quote -
"So maybe you could use the Vue Cam to render this doomed frame, and replace it with the bad one before editing the video?"

But it is not possible!
I have a a carpaint material car, and a big house, that are 3dsMax models, with a lot of Arch&Design materials applied to them and I want render them with mentaray, not with Vue.

The strange behavior, is that: if I change the target position of the Max camera the black and bad keyframes, appears in another point of time, but not disappears totally!
Help!


bruno021 ( ) posted Mon, 20 September 2010 at 3:54 AM

Using the Vue cam inside Max will render your MR materials with MR, it's just a camera, the Vue render engine is only used on the Vue elements.



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.