Luxus Not Exporting or Opening Luxrender
spearcarrier
Posts: 686
Yes, I know everyone is all about iray right now. However on my end iray is refusing to work and is crashing on both of my computers. So while DAZ peeps and I talk that issue out, I switched back to Luxrender for the first time in years.
Windows 7
Nvidia card, can't remember which. I didn't build this thing
Daz 4.8
64 bit
Basically I have this scene built and when I tell it to use the Lux GUI, it propagates and... disappears. luxrender never opens.
I've tried both the open and the no open version of luxrender.
I changed my temp data drive to a desktop one and made sure of permissions.
i've no clue! Help?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Do you have the Luxus config pointing to the Luxrender executable?
Can you start Luxrender, manually?
I know it still works in 4.8, because I just used it Saturday. And I've even got it pointing to a shell script that will open the native Linux version of Luxrender (and since I'm dumping everything to a Linux folder, it even finds all the textures and starts rendering...). But the key thing is making sure that the Luxus config KNOWS where that Luxrender (or in my case script) lives.
Yes. It is pointed and when I don't use the gui it will render in the daz render window.
Yes, I can. I even had it open hoping that would help at one point.
Wah you lost me when you said shell script. But I get what you're saying. This is the first time I've installed Luxrender in a couple of years because I don't normally need to render this way. Normally I use 3delight for toons. The computer in question is a brandnew built install, btw. First time running a lot of stuff on it.
If it's working when you are not rendering to a file and you can open and run Luxrender by itself...then there is something blocking DS/Luxus from accessing the UI...what version of Windows and what security software?
The script is to run the Linux native version of Luxrender, instead installing the Windows version in WINE (a Windows abstraction layer for Linux to be able to run Windows programs). I used that as an example of how flexible Luxus should be...
Agree, it looks like Windows is blocking the folder were LuxRender want to save its files?
Few month ago that problem was discussed here: http://www.daz3d.com/forums/discussion/48621/P15/#734901
In your Render Settings, do you have selected the >Render to File< option? Or >New Window< ?
Try >Render to File< and point to a custom folder in your Render Library.
I have always used >Render to File< and a subfolder in my Render Library, never had any problems.
Hey. Well, I'm not sure how to fix permissions but I can tell you I always have the renders pointing to a subfolder or someplace *else*. This is so it's easy to find. =^-^= But if that subfolder has to be on anything other than the C drive, well. I find this to be a serious screwy bug! I can't move from C on this puter.
The computer in question is, as I mentioned before, a new build. I barely have anything on it and intend to keep it that way as I am mostly going to use it for rendering while I get other work done. All it has is Avast, which I installed after this problem began, Malwarebytes, and DAZ. It's running Windows 7. I have absolutely no intention of using it or internet surfing or anything like that.
Unlike my main computer it doesn't have any external drives attached to it. Sure wish I could convince it to work! Although iray is finally cooperating, I like the Luxrender version *much* better as far as looks goes, and this is after 24 hours trying to get the iray version to look decent. And it was rendering faster in the DAZ window. :-p
Is Malwarebytes in 'on demand' mode or is it active all the time?
Basically, if it's not Malwarebytes blocking the hand-off I'm not sure what is, but something is blocking the passing of the lxs to Luxrender.
The lxs file should be findable...just start it manually through Luxrender.
The Render Library is still in the Default Location and that is under Windows7 in My Documents on the C-Drive.
And I had never any problems rendering with Luxus to a subfolder in the Render Library or the Render Library itself.
Truely, I´m not an expert on this Windows-Permission-Stuff myself. But it seems Windows is denying DAZ Studio and/or Luxus to write outside of the Render Library or the Default Temp-Folder: >User<\AppData\Roaming\DAZ 3D\Studio4\temp</p>
Can you locate that Temp-Folder on your harddrive? Usually it is a hidden folder.
If you have located that folder, start the Render without the LuxRender-GUI inside DAZ Studio and you should see the LuxRender-Files there. If this is the case, at least we know: You have permission to write to this folder. ;-)
Before I begin this trek into my folders (No easy task, the sucker is rendering right now and I'm afraid if I change to a luxus render just to test I'll lose my progress. I'm not sure how far this iray continue feature goes. Stupid slow iray.)...
By render library, do you mean the content? I always have that in its own folder, in this case c:/3content. I HAAAATTTEE Windows default folders. If Windows goes kablooey, you lose your stuff. Oh the Sims genetic experiments I have lost because of that stupid feature....
My temp folder is "render temp" on my desktop. I was trying to figure out how to find the lxs file so I could do just as mjc suggested. I haven't gotten very far with that. If I'm in the right direction, I can try to find the file. But I have no idea if that works ornot because there's nothing in there atm.
Maybe I ... found a possible solution?
1. My folder was "read only". Has anyone heard me rant about Windows 7 "security* and how it's so secure I get tons of viruses but can't use my own bleeping computer? Thus I refuse to upgrade until I absolutely HAVE to? Yeah. Read only unchecked.
2. Found a lexus file in there! So now there's hope.
Thanks for your suggestions. I hope I don't have to come back with another whine... at least not today....
With Render Library I mean the folder where DAZ Studio places its renders by default:
C:\Users\Username\Documents\DAZ 3D\Studio\Render Library
... and my subfolder in there is called >Luxus<.</p>
I didn't mean to be rude and disappear guys. The brand new computer died mysteriously AND we had a death in the family among other things. :-P
Because of the computer death I have had to go back to my old computer. So 4 days ago we upgraded it to windows 7 ultimate. hahah.. iray still won't work for me. It worked 24 hours ago. It won't work now. This means here I am tonight trying to get luxus to work again. I haven't been paid in a month, I'm getting desperate.
I did go to the default folder. No file. I looked in the folder I told DAZ to render into. No file. Although there was a partial render from where I forgot to tell Luxus to use open GUI. And I'm out of options to check.
Where are you telling Studio/Luxus to put it?
Windows is kind of picky as to where things like that need to go...file ownership/permissions are a real pain in most newer Windows versions.
First of all, my condolences to you and your family!
Does the Luxrender GUI start now? Or do you still render inside DAZ Studio? Please, can you give us a screenshot simillar to the one in my last post?
In DAZ Studio, in the Menu Edit=>Preferences, what is the path for the temporary direction? Can you set back the path to the default?
see: http://docs.daz3d.com/doku.php/artzone/pub/software/dazstudio/reference/prefscontent
There should not be any issue, if all files are meant to be written to default locations.
New Window : Username\AppData\Roaming\DAZ 3D\Studio4\temp
Direct to File : Username\Documents\DAZ 3D\Studio\Render Library
Thanks guys for the speedy answers!!!! And MN-15-374... I never know how to respond to condolences, so.. thank you?
My file permissions seem to be sound. I get the usual "you can't do that" when I go into the Windows directory but beyond that I'm not getting any alarms. I've done a lot of rendering in the past couple of days with no issues; I just haven't used Lux. That being said, I have things with my usual set up of the commissions files and the library being on an external drive - which if I'd been able to do that with the one that died I probably wouldn't have lost a certain few things... Anyway. It's my usual set up that has worked for years and saved my rear many times.
So
Library goes to drive F
Commission or image in question goes to wherever I feel like putting it at the time. This could be drive c, d, f, g, or h, you get the picture
We're not sure why iray stopped working. We had upgraded/wiped the drive to solve the issue, and it worked at first. Now as of today it will load, it will start to render, it will crash. Daz and I are still going through it in circles, as this is a problem that cropped up directly after their last tweak update. (Personally I suspect it's conflicting with Adobe, as I only installed that finally last night.) Anyway, I mention this because in an attempt to trouble shoot we thought.. perhaps it's the RAM... and switched to some new RAM we had. No difference.
For the past several hours I have been tweaking the luxus render shadings by using the new window option in daz, rendering a while until I can see a problem, and then stopping it to tweak. This finally resulted in a lxs file in the folder for me to continue with but I'm not sure what I did right or wrong. When I tell it run GUI it just won't go. I sure wish I knew what I'm doing wrong there. Maybe I have the wrong GUI installed.. or... something. I admit when it comes to Luxrender, the online manual might as well be in Russian for me. And to my dismay the lxs file is not one that picks up from my last in DAZ render. I'm not sure why this is so evil to me.
Okay screenshots. Here are some. I hope I'm showing the right things.
Screenshot of Render Settings > Luxrender vis Luxus > Advanced...I'm most concerned with the path to Luxrender, which should be right at the top of the list.
And did you look in the folder that's in the image path box? When you have it set to 'direct to file'...
Please do what mjc1016 suggested first.
And second: When the LuxRender GUI is failing to start, any messages in the DAZ Studio Log File? Menu Help => View Log File
Is it possible to start the LuxRender GUI manual? There are some test scenes out there: https://www.cg.tuwien.ac.at/~zsolnai/luxrender-scenes/
Is it possible to start one of those test scenes with LuxRender?
Do you have any accent letters ( something like: é , à , ü , ö ) in folder or path names?
Now I´m running out of ideas ... :-)
Just finished re-installing everything on to Windows 10 and came up against the same problems you seem to be having. Luxus works OK in console mode but not in GUI mode.
What I found is that my problem was that I decided that while I was upgrading I may as well try out Luxrender v1.5RC1 the new release candidate and that is where the problem started. It works OK in Luxrender v1.4 the stable release version.
It seems in v1.5RC1 the install has a folder inside "C:\Program Files\LuxRender" called "luxrender" which contains some python files, these seem to screw up the Luxus exporter somehow.
My work around for this was to rename this extra "luxrender" folder to "_luxrender" and Luxus then works as before.
Don't know if yours is the same problem but it's worth checking.
Hope this helps.
Those are the Blender exporter files...Luxus SHOULD ignore those. But, that folder name is a bit troubling, because it seems that it's is being read as the main binary folder by Luxus...one folder too deep.
Anyway...if you don't use Blender, you can just get rid of that folder/those files.
You're right, it looks like it's the contents of the LuxBlend.zip (Blender add-on installer file) that is also in there.
Got me thinking about the file name and the folder name being the same (only difference is one has .exe on the end), so I tried adding a dummy folder called luxconsole and that then breaks the non gui render export. Seems like the export plugin is having trouble identifying between the .exe and the folder.
Thanks for this thread, Spearcarrier, and thanks for the solution, jetpack1961. I just had the same problem.