Itoo Software Forum
Forest Pack => Forest Pro (*) => Topic started by: NL2911 on April 25, 2013, 12:11:43 PM
-
Hi there, i upgraded my Forestpack yesterday to the new version. (Al tough i´m not quiet sure the problem occured on that moment..)
If i render with only my workstation i got differences per bucket. See attachment.
I tried a new scene, new forest object but it keeps rendering differences...
What could be the problem?
-
These are the most common causes for this issue:
- The Forest version doesn't match between workstation/render nodes
- Mixing 32 bit and 64 bit network nodes (this configuration is not supported by Forest).
- Render nodes are not loading the same proxies/xrefs files.
- Different gamma settings.
As initial step, i suggest to uninstall Forest from the render nodes, check that all files are removed, and reinstall. Also be sure Max or VRaySpawner are not running when you run the setup program.
If needed, you can see the files used by Forest here (http://www.itoosoft.com/forestpack/reference/install.php).
-
Thanks, but as i stated above, the problem also occurs with rendering only on my workstation (without any rendernodes)
I'm going for a fresh install, see if that helpes.
-
I'm sorry, i though it was a DR issue.
There are not known reasons to cause this problem. Please, try converting the Forest items to stand-alone objects, using Utilities->Forest Tools, and tell me if it fails or not.
-
i did a reinstall. no luck.
I don't know exactly if i did it your way. I did the following:
- select forest object.
- select forest tools -Objects: individual objects
- instanciate
two items used in the forestobject were converted to instance geometry,
one object turned out to be pointclouds.
-
In the same render i have a forest object--> bushes and a forestobject --> trees.
Both render fine without errors.
-
two items used in the forestobject were converted to instance geometry,
one object turned out to be pointclouds.
The idea is to check if the instanced geometry has the same problem (no Forest here). Does it fail at render or not ?
Anyway if you can reproduce the problem in a stripped scene, please send it to us. We will check it here.
-
I think there was a problem in the one or more of the models i used to scatter.
I used completely other models for the grass and its working now. (something i thought i tried already..)
Thanks
-
I seem to be getting the same problem! I'm not running on a render farm and is just on my PC, i have other forests in the scene that render fine. The grass preset renders fine. But this particular geometry doesnt. I really want to use this particular grass as it goes well this scene. It works fine for first render, but then after subsequent ones it gets worse. See attached. :)
-
Usually these problems are caused by the render engine itself, because Forest has not control over the rendering process.
Does it fail rendering the grass as a stand-alone object (no Forest)?. Please, try to reproduce the problem in a test scene, using the grass with and without Forest.
-
Thanks for the prompt response!
So i created a new scene and used the same objects and renders fine. The left is just max's object paint with a vrayproxy, the right is a forest. No weird stuff here. So the object is fine, maybe its the original scene then??
-
Probably, but what is the problem exactly ? I'm checking the original scene but cannot see any rendering issue...
Anyway, this should be suggested procedure for this, and other similar cases:
1) Remove progresivelly from the scene non-essential objects, while the problem is still reproducible.
2) Once you have a stripped scene, convert Forest to stand-alone items using Forest Tools (Utilities Panel).
3) Remove Forest Color from the materials, if used.
4) If it also fails, is a VRay problem (since Forest is no used): you must contact with ChaosGroup. If problem happens only using Forest, send us the scene to check it here.
-
I have the exact same symptom as described on top. 1 CPU (4770K i7) 3ds max design 2014, vray 2.40.04 and the latest forstpack. I will try to reproduce the problem so I can give you more details. I use only one scattered patch of grass (not a vray proxy one) and the material of the grass is a vray2SidedMtl. I get at least 2 different colors in the final render. If i chose to render the region then a different bucket discolors the render etc.
-
Ok. Please, be sure you check the possible causes listed my first post.
-
OK an update....
At first I converted Forest object into standalone objects as described. (I saved the scene but did not close down max to reopen it - I have no idea if this helps in any way). I rendered and got the same result as before. Since I have no Forest Color map I assumed I had to deal with Vray. I then remembered that SP1 for Max 2014 is out and installed it. The application was closed, updated and I rendered and the problem was gone. Unfortunately I didn't keep the original file with Forest object to try to reproduce again. I hope the above helps you in some way...
-
If you have the same problem again, please write us. Anyway, usually these type of issues are not directly caused by Forest, but by some configuration issue, missing maps or something else.
-
Well i still have this problem with some models.
I also happen to find the models i used are made with a newer version of MassFX.
If i open the model directly i get this error;
The MassFX authored in this file was created with a newer version of the plugins. Foward compatibility is not supported, so thing might not behave properly.
*IN a new scene i instanced the merged model. Checked the texture paths. Rendering --> no problem.
*Then i made a forest object for scattering. Rendering --> problems in different buckets.
*Then i used forest tools to instanciate. Rendering --> no problems.
3ds Max 2014 SP1.
1 computer rendering.
At the moment it only happens to models which i got this error with.
So maybe MassFX could be the problem??
-
Theorically this error refers to MassFX versions, but it's not related in any way with Forest. We don't use MassFX for anything.
What is the format of the failing models, standard meshes ? If you send us a test scene we may check it here.
-
Yes i think so, but i cannot delete the massfx info from the file and i only have problems when using forestpack.
I just send you the file by mail to check.
I also started a Case with Autodesk about the MassFX warning and how to solve.
Hope there's a workaround soon.
Thanks in advance!
-
Thanks for the file. Please, would you send us the textures as well ?
Regarding the problem, on your initial post there was bucket differences rendering with a single workstation (no DR). What is the case for this scene, DR or single node ?
BTW: i got no MassFX errors opening this scene (Max 2014 SP1).
-
I send the file again with textures.
I only got a Massfx warning the first time i open the file (2014 SP1)
When i was working with 2013 i always got the error. Not when i merge the file.
I rendered with only one computer; my workstation.
-
Thanks. I did render the scene using the default settings, but the problem is not reproducible here (Max 2014 SP1, FP 4.0.3, VRay 2.40.04).
Anyway, i noticed that "Distributed rendering" is enabled in your scene. Is there some difference turning it off ?
Also i see that the number of clumps between "No error.jpg" and "Error1.jpg" doesn't match. Please, would you repeat the test converting to instances ? (Forest Tools). Just to be sure both renders are done under same conditions.
I've found a thread in ChaosGroup about a random gamma issue. I'm not sure if it would be related with this problem:
http://www.chaosgroup.com/forums/vbulletin/showthread.php?70617-Wrong-Gamma/page7 (http://www.chaosgroup.com/forums/vbulletin/showthread.php?70617-Wrong-Gamma/page7)
-
The Gamma issue is still related to rendering with DR nodes.
I am rendering only with my Workstation :) please let this be clear.
When i started this thread i already spend 4 hours trying to solve the problem. The basic's are to check textures paths, render without DR, strip the scene, etc. The DR is checked probably because i did more testing after i saved the file.
Very few people got the massfx problem which makes it hard to get attention and to reproduce the problem. But i have a very strong feeling this is causing the errors. I can probably reproduce those errors with more models from different packages. All the models that fail scattering are models i got the MassFx warning with.
You can see the attachments (still errors; but less noticeable)
-
Ok, you thanks for your help. We should wait the reply from Autodesk about the MassFX error.
It's a very strange problem, because in this case Forest has no effect on the render, it just scatters the items. Please, make one additional test:
1) Create a VRay proxy from the grass clump.
2) Repeat the render, using the proxy as Custom Object.
3) Convert to stand-alone objects and repeat.
Since Forest uses internally the same VRay engine used for proxies, i want to check if there is some relation.
-
This is getting strange.
I made a proxy of the grass clump. Used the proxie with forestpack. Rendered --> no errors
Forest tools --> instanciate. Rendered --> i got errors..
I made a new forestobject, used the proxie again. Rendered --> errors
* It looks like the reflection/specular is missing in the first, but i'm not sure which one is rendering correct.
I think we have to wait for Autodesk to reply indeed.
Thanks
-
Autodesk also got the Massfx warning, which was strange because their using the latest Autodesk.
They could not reproduce the problem with mental ray.
I think i found the problem though..
I first tested with a standard material on the object; no errors.
Then i remade the vray 2sidedmaterial, rendered and i have no errors.
So i think the material got corrupted along the way..
Hope this helps!
(ps; the massfx warning was just coincidence....)
-
Finally i could reproduce the problem using proxies (no Forest). It's clearly a VRay bug.
I have reported the problem in the ChaosGroup site:
http://www.chaosgroup.com/forums/vbulletin/showthread.php?73561-Buckets-difference&p=587243#post587243 (http://www.chaosgroup.com/forums/vbulletin/showthread.php?73561-Buckets-difference&p=587243#post587243)