PDA

View Full Version : missFastSkin render problem

pgland
03-27-2005, 05:37 PM
Hello

I`m having a really wierd problem when I am rendering out my character with the miss_fast_skin shader. It has been working great for a while, and the shading network hasn`t changed. The problem is though that the lightmap generation takes ages if I zoom the camera quite close up to the feet. It is fine for closeups on any other part of the body and renders in seconds.
Sometimes parts of the lightmap re-render and the percentage complete in the output window is all over the place.
I sometimes get this message printing over and over again, but I have no idea what it means.

PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 progr: 51.0% sss lightmap generation
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
PHEN 0.2 progr: 51.0% sss lightmap generation
PHEN 0.2 warn 052017: mi_matrix_solve: A is singular

And sometimes(quite often) It never makes it at all and crashes! I really don`t get it, it seems to be proximity and view dependant, but just on one part of the body!
I was hoping someone might have some insight into this, I would really appreciate some help!
xDETOXx
03-28-2005, 09:02 AM
I'm in the same boat with the exact same warning message and render problem. Sometimes it works, sometimes it doesn't.

sketchy.
Synthesizer
04-05-2005, 05:53 PM
Hmm, I just got the same warning. It hasnt crashed or anything yet, maybe just slowed the lightmap generation down.
pgland
04-11-2005, 06:50 PM
Hello. I was wondering if any of you guys managed to solve this problem. Its really starting to worry me now! I haven`t got rid of it at all. I have tried rebuilding the shaders and the lights in the sence. And even rebuilding the model its happening on. It was working until I was about halfway through the rebuild on my model and then it stopped!
The new model I built was not rendering from exactly the same camera positions as the old model. It renders fine unless I zoom the camera right up to either the feet or the wrists.

Does anyone know what the error means? Or have any idea how to debug it, I don`t seem to be able to find any info on it at all?

PHEN 0.2 warn 052017: mi_matrix_solve: A is singular
Synthesizer
04-11-2005, 07:12 PM
Hmm, I just checked, and it appears that has gone away on its own :shrug: I am still getting this though:

RCFG 0.2 warn 542002: angle between normal and geometry normal > 90 degrees

Which appeared around the same time as the A singular thing.
onni
04-12-2005, 05:10 PM
Hi Guys,

I had the exact same problem with this error message: mi_matrix_solve: A is singular, when using the Miss_fast_simple_maya_shader. I tried all kinds of stuff and found out, that I'm not getting any error messages, if all objects, that have this shader are framed in the render camera. Right now, I'm animating the visibility of my objects. As soon, as they cannot be seen in the rendered camera, I turn the visibility off. It sounds strange, but now all my renderings work great, and those, that worked before are even faster......

hope, this helpes you as well....

Good Luck!
Onni
***
pgland
04-15-2005, 11:03 AM
Hi Onni, sorry I didn`t reply sooner, i`ve not been near my computer for a while.
Its a wierd problem, thats for sure, but I only have one mesh with misss on it in my scene. You are right though, when it is fully framed, it renders fine, but when just a tiny portion of it is in frame, the render stops.
I have been deleting the polys that are out of shot, and this seems to make it work. It is a bit of a hassle but do-able.
Thanks for the help onni!
CGTalk Moderation
04-15-2005, 11:03 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.