Has something been changed in the latest 2020.2.0 EDIT (Also happens with 2020.1.5) plugin where fog is concerned?
No matter what options I try I have to use ridiculously low values to get fog to show up the way I want and I mean 0.0001, anything over that value and everything renders black.
This has always been a major bug as far as I'm concerned.
Fog trouble again!
Moderator: juanjgon
It's totally unworkable, I've now rendered the same scene in LW2018 and everything works perfectly but in LW2019 any volume at all either doesn't work or makes render times so completely insane as to be unworkable.
I've had enough now I'm getting my money back, the development since last year has been shit.
I've had enough now I'm getting my money back, the development since last year has been shit.
The plugin is the same for all the LightWave versions, so I can't figure out how the fog rendering could be different in LW2018 and in LW2019. If you want to share the scene I can take a look at it here. Perhaps something has changed in the LW SDKs among versions that I have not seen before.
In any case, good luck in your search for the "perfect bugs-free software"
Usually, it is more constructive to report the problems with enough information to let the developers find and fix the issues that, well, complaining about the problems without more information and asking for a refund 
Thanks,
-Juanjo
In any case, good luck in your search for the "perfect bugs-free software"


Thanks,
-Juanjo
Juanjo, do you ever get fucked off with something not working the way you expect it to. I can't share the scene because it's a commercial project just like my other projects that I have had problems with. Now I am telling you that something has changed. Adding any volume at all to any scene in 2020.1.5 or 2020.2.0 makes render times go through the roof, if you can't look into it that's not my problem, it's yours.
So you think the plugin is identical regardless of what version Lightwave you are using Juanjo.
I can't post the scene but I have posted screengrabs in the Octane for Lightwave group and tagged you in the post, so you take a look and tell me there isn't a problem.
https://www.facebook.com/groups/2109382 ... 221315975/
I can't post the scene but I have posted screengrabs in the Octane for Lightwave group and tagged you in the post, so you take a look and tell me there isn't a problem.
https://www.facebook.com/groups/2109382 ... 221315975/
Can you please enable the log file in the plugin options panel and attach the logs that you get after rendering the scene in both LW versions?
Weird NDA, BTW ... you can't send me the scene by pm, but you can post renderings on Facebook
Please, posting the problems on Facebook to gain visibility is not going to help in my case 
Thanks,
-Juanjo
Weird NDA, BTW ... you can't send me the scene by pm, but you can post renderings on Facebook


Thanks,
-Juanjo
Nothing, I've been trying to reproduce this problem here and the render time in any of my test scenes including the scattering medium as environment is the same in all the LW versions. Somehow or your scene or your settings are not the same when loaded in LW 2018 or LW 2019. I've seen that the GPU memory used by the scene is not the same at all in both LW versions, so I wonder if due to the LW version the extracted scene is not the same ... perhaps the objects subdivision, I don't know. We could have a clue in the Octane plugin log files or in the statistics.
Thanks,
-Juanjo
Thanks,
-Juanjo
I can't post the scene because of the commercial elements in the scene Juanjo, I'm allowed to make and share renders or animations but I can share the items in the scene or the scene itself. I am honestly not trying to be a dick, I wouldn't have even known this was a problem if I didn't suddenly think to reinstall LW2018.
I am going to continue working in LW2018 for now based on advice from several people, for the time being Lightwave 2019 has been uninstalled but please have a look into this yourself by rendering a few scenes in both LW2018 and LW2019.
I am going to continue working in LW2018 for now based on advice from several people, for the time being Lightwave 2019 has been uninstalled but please have a look into this yourself by rendering a few scenes in both LW2018 and LW2019.
Can you send me the .lws scene file without the assets? Perhaps I could get a clue about the problem from the render target configuration. As I've said, I can't reproduce this problem using my test scenes. It is something really weird!
Thanks,
-Juanjo
Thanks,
-Juanjo