Hi Juanjo,
Octane Utilities / Octane UVMAP does not work (LW2018). Version 3.8 also (tested long time ago).
We use this node very often.
Otherwise, great work and thanks.
Tomas Base
vizualizace.cz
team
OctaneRender™ 4.0 for LightWave™ - Beta build 4.00.0.9 XB4
Moderator: juanjgon
- VIZUALIZACE-CZ
- Posts: 18
- Joined: Sat Dec 06, 2014 8:35 pm
- Location: Czech Republic
- Contact:
Hi,VIZUALIZACE-CZ wrote:Hi Juanjo,
Octane Utilities / Octane UVMAP does not work (LW2018). Version 3.8 also (tested long time ago).
We use this node very often.
Otherwise, great work and thanks.
Tomas Base
vizualizace.cz
team
It should work, but some options related to getting the "T" texture layers info are not working due to the fact the LW 2018 has deprecated the old materials editor, so now it is not possible to get this information from the new material node.
Thanks,
-Juanjo
Nope, sorry. Perhaps it is related to the render resolution or something like that because the IPR and the final F9 rendering code is the same. You should check also the subdivision levels if you are working with the LW native subdivision/displacement because the IPR works with the display levels while the F9 rendering works with the rendering levels.electric_eric wrote:Hi,
Just started using Octane 4 for lw2015.3...loving the denoiser!
I have a fairly heavy scene that renders very quickly in IPR however the f9 render is painfully slow...any ideas why this would be happening?
Thanks in advance.
Cheers,
Simon
Thanks,
-Juanjo
- VIZUALIZACE-CZ
- Posts: 18
- Joined: Sat Dec 06, 2014 8:35 pm
- Location: Czech Republic
- Contact:
Thanks for the information. Will this node support LW2018 later?juanjgon wrote: Hi,
It should work, but some options related to getting the "T" texture layers info are not working due to the fact the LW 2018 has deprecated the old materials editor, so now it is not possible to get this information from the new material node.
Thanks,
-Juanjo
I can not imagine working without this node because it allows displacement without a classic UV map and also comfortable texture mapping.
So far, it's not so important to us, we're happy with version 3.6, but as soon as we can put these versions into production, we'd like to go to LW2018 and OCT4.
Tomas Base
vizualizace.cz
team
- stevecullum
- Posts: 4
- Joined: Sat Apr 15, 2017 12:30 pm
Thanks for the update, have a good holiday!Hi,
I don't have the details about how the new licensing system is going to work with the plugin yet, but I can say that the new plugin build including the RC1 core is going to be released soon, probably early next month after my short holiday break, so stay tuned
Thanks,
-Juanjo
- BorisGoreta
- Posts: 1413
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
LW plugon does not export fibers to ORBX file.
19 x NVIDIA GTX http://www.borisgoreta.com
BTW : The Get T button does not work in Modeler 2015.3, is that "normal" ?
Work Station : MB ASUS X299-Pro/SE - Intel i9 7980XE (2,6ghz 18 cores / 36 threads) - Ram 64GB - RTX4090 + RTX3090 - Win10 64
NET RENDER : MB ASUS P9X79 - Intel i7 - Ram 16GB - Two RTX 3080 TI - Win 10 64
NET RENDER : MB ASUS P9X79 - Intel i7 - Ram 16GB - Two RTX 3080 TI - Win 10 64
- realistic-design
- Posts: 9
- Joined: Mon Aug 31, 2015 1:36 pm
yes, always need like that.pixym wrote:BTW : The Get T button does not work in Modeler 2015.3, is that "normal" ?
Thank for this answer.
Juanjo, is there a way to have the real "Render Region No Border" feature with the crop of the image and only the region ?
Juanjo, is there a way to have the real "Render Region No Border" feature with the crop of the image and only the region ?
Last edited by pixym on Mon Aug 20, 2018 5:39 pm, edited 1 time in total.
Work Station : MB ASUS X299-Pro/SE - Intel i9 7980XE (2,6ghz 18 cores / 36 threads) - Ram 64GB - RTX4090 + RTX3090 - Win10 64
NET RENDER : MB ASUS P9X79 - Intel i7 - Ram 16GB - Two RTX 3080 TI - Win 10 64
NET RENDER : MB ASUS P9X79 - Intel i7 - Ram 16GB - Two RTX 3080 TI - Win 10 64
Yes, sorry, the plugin doesn't work on the Modeller at all (it is a Layout only plugin) so any node function is not going to work.pixym wrote:BTW : The Get T button does not work in Modeler 2015.3, is that "normal" ?
Thanks,
-Juanjo