OctaneRender™ 2020.1.2 [superseded by 2020.1.3]

Forums: OctaneRender™ 2020.1.2 [superseded by 2020.1.3]
VIP Information, news and announcements regarding new Octane Render commercial products and releases.

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby wallace » Mon Jun 15, 2020 12:53 am

wallace Mon Jun 15, 2020 12:53 am
noldo wrote:
noldo wrote:If i connect a mix material with displacement to a base layered material, the dispacement disappear!


Version 2.1.1 is the same.
Version 2.1.0 is ok!


Hi noldo,

I had a look at this problem and I can find the underlying issue, this fix will be in the next revision.

Thank you for reporting.
User avatar
wallace
OctaneRender Team
OctaneRender Team
 
Posts: 188
Joined: Sun Dec 18, 2016 10:38 pm

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby Padi » Tue Jun 16, 2020 11:57 am

Padi Tue Jun 16, 2020 11:57 am
Version 2020.1.2: Now working correctly with EXR DWAA & DWAB lossy compression and Cryptomatte passes. Those passes are now lossless ZIP compressed inside the same EXR file.

<- Can we add this to the list of bugfixes please mojave?

The following info passes still are still breaking. They also need to be stored as lossless ZIP as well:

- Position
- UV coordinates
- Z-depth
Padi
OctaneRender Team
OctaneRender Team
 
Posts: 24
Joined: Thu Jan 18, 2018 8:50 pm

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby divasoft » Tue Jun 16, 2020 11:30 pm

divasoft Tue Jun 16, 2020 11:30 pm
This build slave node can't define videocards. 2020.1 rc4 worsk well. Please fix it, i can't work.
You do not have the required permissions to view the files attached to this post.
User avatar
divasoft
Licensed Customer
Licensed Customer
 
Posts: 348
Joined: Thu Jul 01, 2010 3:59 am
Location: Russia

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby divasoft » Tue Jun 16, 2020 11:33 pm

divasoft Tue Jun 16, 2020 11:33 pm
funk wrote:I couldnt get this build running on my machine either.

I even went so far as to install a new copy of windows 10 on a separate SSD. I have posted screenshots and details to mojave in PM.

On a fresh install, 2020.1.2 crashes on launch (before any splash screen). I also tried installing newer nvidia drivers, but nothing changed.

2020.1.0 runs fine on the same fresh install.

After a google search, I found some info related to the event log errors, showing people having issues running AVX instructions on a CPU that doesnt support AVX. I have an old CPU that doesnt support it.

I got the same problem, but with the slave node, it just closed right after launch. The developers could not help me.
I also use a processor without avx instructions
User avatar
divasoft
Licensed Customer
Licensed Customer
 
Posts: 348
Joined: Thu Jul 01, 2010 3:59 am
Location: Russia

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby linograndiotoy » Wed Jun 17, 2020 2:57 pm

linograndiotoy Wed Jun 17, 2020 2:57 pm
Whenever texture displacement is used with an instance, moving an item makes the render go blank:
https://youtu.be/00_v1mSH-po

Displacement_Glitch.orbx
You do not have the required permissions to view the files attached to this post.
linograndiotoy
OctaneRender Team
OctaneRender Team
 
Posts: 1155
Joined: Thu Feb 01, 2018 7:10 pm

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby LewisO » Thu Jun 18, 2020 3:37 am

LewisO Thu Jun 18, 2020 3:37 am
Can anyone confirm that this version broke all osl nodes that use color inputs?
LewisO
Licensed Customer
Licensed Customer
 
Posts: 39
Joined: Mon Aug 10, 2015 7:57 am

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby LewisO » Thu Jun 18, 2020 5:37 pm

LewisO Thu Jun 18, 2020 5:37 pm
Ok Silverwing helped confirm that osl bug is related to C4D only
LewisO
Licensed Customer
Licensed Customer
 
Posts: 39
Joined: Mon Aug 10, 2015 7:57 am

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby divasoft » Fri Jun 19, 2020 11:56 am

divasoft Fri Jun 19, 2020 11:56 am
Sorry for being rude guys, but are you going to work at all? My work is now completely stopped. At first, I could not update the slave node, because it does not detect video cards, and now my c4d (2020.1 RC4) plugin has expired. Half a year ago I switched to redshift and now I decided to give the octane one more chance. And now I just have no words, just curses. Why is there a version that cannot be used in the Commercial Product News & Releases section? Do you just check Commercial builds before release? Why do fixes take so long? The guys from the redshift fix everything almost on the fly. Each of my appeals was reviewed and I was helped. From you, I see only constant problems and ignoring. It’s very difficult for me to restrain myself from saying a lot of bad words to you. I lose money, I spend time, I get angry - this is a real experience with octane.
User avatar
divasoft
Licensed Customer
Licensed Customer
 
Posts: 348
Joined: Thu Jul 01, 2010 3:59 am
Location: Russia

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby mojave » Fri Jun 19, 2020 12:38 pm

mojave Fri Jun 19, 2020 12:38 pm
divasoft wrote:This build slave node can't define videocards. 2020.1 rc4 worsk well. Please fix it, i can't work.


Have you tried using 2020.1? There's an issue other users reported which we are already looking into that could be causing this problem. Please never use non production builds for production work as they all expire after a period of time.
User avatar
mojave
OctaneRender Team
OctaneRender Team
 
Posts: 1259
Joined: Sun Feb 08, 2015 10:35 pm

Re: OctaneRender™ 2020.1.2 [current 2020.1]

Postby mojave » Fri Jun 19, 2020 12:39 pm

mojave Fri Jun 19, 2020 12:39 pm
linograndiotoy wrote:Whenever texture displacement is used with an instance, moving an item makes the render go blank:
https://youtu.be/00_v1mSH-po

Displacement_Glitch.orbx



Hi Lino, thanks for the report. We will look into it.
User avatar
mojave
OctaneRender Team
OctaneRender Team
 
Posts: 1259
Joined: Sun Feb 08, 2015 10:35 pm
PreviousNext

Return to Commercial Product News & Releases (Download here)


Who is online

Users browsing this forum: No registered users and 6 guests

Tue Apr 16, 2024 10:54 pm [ UTC ]