I have tried many times to SAVE the default Render Target setup so that when I launch a new scene and use Octane my render target is already setup like I want. I am able to save a Preset but when I SAVE AS DEFAULT it says it saves over current config file...but nothing changes next time I launch Lightwave with Octane render.
What am I doing wrong? Using 3.0.6.0
What is the correct way of saving Default Render Target Setu
Moderator: juanjgon
The default render target file is stored in the same folder used by the LightWave config files. I've just tested it and it seems to work fine, at least in LW 2015 Windows.
Are you working with other LW version or in OSX?
-Juanjo
Are you working with other LW version or in OSX?
-Juanjo
-
3dreamstudios
- Posts: 479
- Joined: Fri Apr 03, 2015 8:55 pm
It does seem to save the file in the correct directory. The file is getting updated. Which for me is... C:\Users\Trey\.NewTek\LightWave\11.6.3 Which also answers the other question....I'm using 11.6.3. Will be upgrading to the next version of LW but have not needed anything they've done since then 
If there was a way to test that version on your side we could probably figure it out. I don't think I'm doing anything out of the ordinary.
If there was a way to test that version on your side we could probably figure it out. I don't think I'm doing anything out of the ordinary.
Weird, I am testing this feature in LW 11.6 and also seems to work fine ... can you please delete the 'LWOctane.rtd' file and try again? If the plugin saves the file, I don't understand why it doesn't read it when you enable the plugin.
-Juanjo
... can you please delete the 'LWOctane.rtd' file and try again? If the plugin saves the file, I don't understand why it doesn't read it when you enable the plugin.-Juanjo
-
3dreamstudios
- Posts: 479
- Joined: Fri Apr 03, 2015 8:55 pm
I think I just found it. It is loading from another location. I have a LocalDB folder path set and it is the same directory that Octane is loading from. However when I save DEFAULT it is saving to the Users Directory.
I'm ok with it pulling/savind from/to either..but it needs to be consistent I guess. Can you double check that on your end?
I'm ok with it pulling/savind from/to either..but it needs to be consistent I guess. Can you double check that on your end?
There's an 11.6 LW?? must be nice being on the insidejuanjgon wrote:Weird, I am testing this feature in LW 11.6 and also seems to work fine
CPU: Intel I9-14900KF | Mobo: Asrock Z790 Tachi | Ram: 128gb | Storage: 64tb | GPU: 2x Asus ROG Strix - RTX3090 24gb
-
3dreamstudios
- Posts: 479
- Joined: Fri Apr 03, 2015 8:55 pm
No..having 2017 Alpha 0.3.5 is nice! lol. Just Kidding.Rob49152 wrote:There's an 11.6 LW?? must be nice being on the insidejuanjgon wrote:Weird, I am testing this feature in LW 11.6 and also seems to work fine
I don't understand ... the 'LWOctane.rtd' file is written and read always to/from the same folder, the same folder used by LightWave to store all it's configuration files. Are you saying that your LightWave is reading the default render target from the LocalDB directory?3dreamstudios wrote:I think I just found it. It is loading from another location. I have a LocalDB folder path set and it is the same directory that Octane is loading from. However when I save DEFAULT it is saving to the Users Directory.
I'm ok with it pulling/savind from/to either..but it needs to be consistent I guess. Can you double check that on your end?
-Juanjo
-
3dreamstudios
- Posts: 479
- Joined: Fri Apr 03, 2015 8:55 pm
Yes I noticed when Ioaded up lightwave and activated octane it showed that it loaded from my x:\ directory which is set as my LocalDB path. I could only guess that was where it got the path, was from the options inside Octane. It could also be that my CONTENT directory is set there as well. But I figured it was from the options panel in Octane.
EDIT: After doing some tests. You can see below the different status updates I get. If I delete the .rt file (not rtd) in X:\ which is where my LocalDB path is set in options, I get an ERROR, HOWEVER Octane THEN loads the .rtd file stored in the USERS directory. So there must be something somewhere saying if path set pull from there...or something. Hope that helps find it. I think the current workaround is just delete the .rt file in the other location and Octane is back to normal. It might be that as versions have changed this is a file remnant and some code remnant. *shurg* But this workaround still gives an error message even though it loads correct file.
EDIT: After doing some tests. You can see below the different status updates I get. If I delete the .rt file (not rtd) in X:\ which is where my LocalDB path is set in options, I get an ERROR, HOWEVER Octane THEN loads the .rtd file stored in the USERS directory. So there must be something somewhere saying if path set pull from there...or something. Hope that helps find it. I think the current workaround is just delete the .rt file in the other location and Octane is back to normal. It might be that as versions have changed this is a file remnant and some code remnant. *shurg* But this workaround still gives an error message even though it loads correct file.
It is really weird! Your LightWave is trying to load the 'LWOctane.rt' file. This file is stored in the content directory when you use the 'Switch to LW' tool, and read also from the content directory when you use the 'Switch to Octane' tool (this is what makes possible restore the Octane scene settings after work with the LightWave native render engine).
So the questions is ... why your LightWave is firing the 'Switch to Octane' function when you enable the plugin? ... it's a mystery
It is Layout command (Octane_Switch_to_Octane), so it can be called from a script for example. Can be something related to your configuration files. Really I don't know. Perhaps you should try to remove your LW config files to see what happens.
I will investigate it, but really I don't understand how it can happen
-Juanjo
So the questions is ... why your LightWave is firing the 'Switch to Octane' function when you enable the plugin? ... it's a mystery
It is Layout command (Octane_Switch_to_Octane), so it can be called from a script for example. Can be something related to your configuration files. Really I don't know. Perhaps you should try to remove your LW config files to see what happens.
I will investigate it, but really I don't understand how it can happen
-Juanjo