Quote - > Quote - I'm just waiting to get my hands on the model... just wait... a month away? :twitch: I can wait... My friend has been showing me some nice renders she had done already with Dawn

All I can say is that Dawn is awesome. ;)

I bet... I am envious of my friend. But she has been doing this a lot longer than I have.

I'm just waiting to get my hands on the model... just wait... a month away? :twitch: I can wait... My friend has been showing me some nice renders she had done already with Dawn

 So... I am kind of lost... What is the Subdivision for? I know what it is, just not sure what it is being used for in this situation.

 Maybe I am wrong... all I know is that my computer does not seem to like all of the 

Image_Map_3

Texture "ImageMap_85" "float" "imagemap"

"string filename" ["C:UsersClayDocumentsDaz 3DStudio3ContentRuntimetexturesMorrisHiro4JMHiroLimbB.jpg"]

"float vscale" [-1.0]

"float uscale" [1.0]

"float gamma" [1]

over and over again with the only difference really being the number attached to the "ImageMap_

and when I get rid of all those and make others point to first ImageMap_85 with the file attached it works, when I leave all the others in it crashes... and now that isn't the only one that does it for, just an example of one of the images that comes up over and over again in the lxm file.

 I did, that is how I found the problem, that and having task manager open to watch how much ram was being used.

It wasn't much, I don't think... M4, Shorts from Casual Wear, Glynn hair, and forest from Multiplane Cyclorama. Most of the corrections I had to do was with M4

I think my explanation makes little to no sense of what I did to fix the problem...

YES! I figured out my problem and why LuxRender kept crashing! :thumbupboth: The problem seems to stem from not having enough memory on my laptop (only 2 GB) but I was able to over coming this problem by removing a lot of the references to the same picture over and over again. I had to go LXM file and just have the repeat textures check the first instance of the image and then remove all other references to those images. Once I did that, it stopped crashing on me.

Quote - > Quote -  I really wish I knew what I was doing wrong.... I get rid of all of the relative paths in the lxm file and make them constants. I make sure that all the paths are correct to images... I try to run it in LuxRender and it crashes... I live all the relative paths, I get errors in LuxRender but it still runs and renders fine on one machine, even though from what I am told it should have problems rendering correctly. I seem to be the only one having this problem. I'm running Windows 7, Poser 8, LuxPose 1.14, and LuxRender v0.7... It doesn't crash if I comment out the lxm file, but then of course everything is a nice shade of gray.

I do get errors like this in the LuxRender Log window:

[2010-09-02 14:01:43 Error: 14] Static loading of color texture 'default' failed.
[2010-09-02 14:01:43 Error: 41] Couldn't find color texture named 'Color_Round'[2010-09-02 14:01:43 Error: 41] Couldn't find float texture named 'Color_Mul_74'

and the last thing it says before crashing is:

[2010-09-02 14:03:21 Warning: 0] Parameter 'from' not used

 

[2010-09-02 14:03:21 Warning: 0] Parameter 'to' not used

Then I get a popup window saying:

Runtime Error!

Program: C:Program Files LuxRenderluxrender.exe

This application has requested the Runtime to terminate it in an unusual way. Please Contact the application's support team for more information. 

I have tried running the sample that comes with Luxrender and that goes through fine without any trouble. So I don't know what I am doing wrong that is causing so much trouble. I have been in contact with a couple of the people working on  this project and the LuxRender Devs, and both have told me that it is a problem with relative paths vs constant paths, but that doesn't make sense since I have taken out all of the relative paths. And it is not just one scene that I have tried, it's all the of the scenes I have made and tried to move over to LuxRender. 

The errors about 'from' and 'to' seem to be normal.  Though it does not seem to prevent luxrender from working.

OTOH, the other errors make me think you are using Poser Materials, which do not work with LuxPose yet.  I don't know if that has anything to do with the 'Runtime error', though I would think not. 

This is a very beginning work-in-progress, and as such does not have the ability to convert much more than Poser 4 textures.  That is changing, and probably will change rapidly soon.

Don't give up, it's only getting better!  In other words, try a simple scene with just image-based textures and see what happens.

Oh, I don't plan to give up, I want this to work. I'm just annoyed that I can't fix the problem or figure out at all what could be causing the problem.

 I really wish I knew what I was doing wrong.... I get rid of all of the relative paths in the lxm file and make them constants. I make sure that all the paths are correct to images... I try to run it in LuxRender and it crashes... I live all the relative paths, I get errors in LuxRender but it still runs and renders fine on one machine, even though from what I am told it should have problems rendering correctly. I seem to be the only one having this problem. I'm running Windows 7, Poser 8, LuxPose 1.14, and LuxRender v0.7... It doesn't crash if I comment out the lxm file, but then of course everything is a nice shade of gray.

I do get errors like this in the LuxRender Log window:

[2010-09-02 14:01:43 Error: 14] Static loading of color texture 'default' failed.
[2010-09-02 14:01:43 Error: 41] Couldn't find color texture named 'Color_Round'

[2010-09-02 14:01:43 Error: 41] Couldn't find float texture named 'Color_Mul_74'

and the last thing it says before crashing is:

[2010-09-02 14:03:21 Warning: 0] Parameter 'from' not used

[2010-09-02 14:03:21 Warning: 0] Parameter 'to' not used

Then I get a popup window saying:

Runtime Error!

Program: C:Program Files LuxRenderluxrender.exe

This application has requested the Runtime to terminate it in an unusual way. Please Contact the application's support team for more information. 

I have tried running the sample that comes with Luxrender and that goes through fine without any trouble. So I don't know what I am doing wrong that is causing so much trouble. I have been in contact with a couple of the people working on  this project and the LuxRender Devs, and both have told me that it is a problem with relative paths vs constant paths, but that doesn't make sense since I have taken out all of the relative paths. And it is not just one scene that I have tried, it's all the of the scenes I have made and tried to move over to LuxRender.

 I really wish I knew what I was doing wrong.... I get rid of all of the relative paths in the lxm file and make them constants. I make sure that all the paths are correct to images... I try to run it in LuxRender and it crashes... I live all the relative paths, I get errors in LuxRender but it still runs and renders fine on one machine, even though from what I am told it should have problems rendering correctly. I seem to be the only one having this problem. :unsure:

 I am taking about using LuxRender in server farm mode... from what I can tell, I think my problem is with LuxRender itself and not with the exporter. Because LuxRender is sending the textures to the other computers. Though I am coming across another problem as far as textures go, I have one model that I have put a Tattoo on from one of the Inked! sets and that is not transferring over, but I am think that is something relating to how the tattoo is put on since Poser is taking two images and overlapping them to add the tattoo to the skin texture.

 Hello, I've just been trying the LuxPose today. I don't know if anyone else has had this problem, (sorry I have not read through everything, so this might be my own fault) but I have set up my computer as a server so I can do most of my work on my laptop. The problem I seem to run into is that not all the textures seem to go to my computer. Laptop alone seems to render ok, but when it checks in with the computer to get what the computer has been working all of a sudden spots that did have texture have no more texture. Again, sorry if this has already been talked about...