OctaneRender® for 3ds max® v2022.1 - 13.17

Forums: OctaneRender® for 3ds max® v2022.1 - 13.17
Sub forum for plugin releases
Forum rules
Any bugs related to this plugin should be reported to the Bug Reports sub-forum.
Bugs related to Octane itself should be posted into the Standalone Support sub-forum.

Re: OctaneRender® for 3ds max® v2022.1 - 13.17

Postby merid888 » Fri Mar 31, 2023 3:34 am

merid888 Fri Mar 31, 2023 3:34 am
Nice update, but I can't repoduce the objects of cosmos bye CoronaRenderer, only Vray objects can do it, any comment to know why happen this ?

Thank you OctaneRender team.
Attachments
None Color or Texture_Denoised_beauty.jpg
Cosmos.jpg
W11 x64 Bits Workstation, 32 Gb 3200 Mghz DDR4 Corsair, Asus X570 Plus Wifi, Ryzen 9 5950x 3.4 Ghz, M2 WD Black-SN850x 1 Tb, Corsair H100i RGB PLATINUM, 1 RTX A4000 16 GB, 1 Power Supply Corsair RM850x.
User avatar
merid888
Licensed Customer
Licensed Customer
 
Posts: 814
Joined: Sun Aug 28, 2011 10:48 pm
Location: Merida

Re: OctaneRender® for 3ds max® v2022.1 - 13.17

Postby coilbook » Fri Mar 31, 2023 7:45 pm

coilbook Fri Mar 31, 2023 7:45 pm
When rendering using this version renderers just quits rendering before it starts rendering the first frame sometimes with this message "Cannot import a regular grid from an empty voxel buffer."
coilbook
Licensed Customer
Licensed Customer
 
Posts: 2985
Joined: Mon Mar 24, 2014 2:27 pm

Re: OctaneRender® for 3ds max® v2022.1 - 13.17

Postby merid888 » Mon Apr 03, 2023 12:20 am

merid888 Mon Apr 03, 2023 12:20 am
Hello colinbook, but what it that means this "Cannot import a regular grid from an empty voxel buffer." ?

Thank you for response me

Is the same error, object texturizaded in Corona but I can't visualize in OctaneRender
Attachments
No texture Corona_Denoised_beauty.jpg
Same error, no texture in Objec created with Corona
W11 x64 Bits Workstation, 32 Gb 3200 Mghz DDR4 Corsair, Asus X570 Plus Wifi, Ryzen 9 5950x 3.4 Ghz, M2 WD Black-SN850x 1 Tb, Corsair H100i RGB PLATINUM, 1 RTX A4000 16 GB, 1 Power Supply Corsair RM850x.
User avatar
merid888
Licensed Customer
Licensed Customer
 
Posts: 814
Joined: Sun Aug 28, 2011 10:48 pm
Location: Merida

Re: OctaneRender® for 3ds max® v2022.1 - 13.17

Postby neonZorglub » Wed Apr 05, 2023 4:23 am

neonZorglub Wed Apr 05, 2023 4:23 am
PromotsAdmin wrote:1. when checking "Overwrite default Render Element folder" octane creates the new folders before the rendering begins (as soon as I press the render button)
2. I'm rendering locally and not on a remote computer so there are no issues with writing permissions and such, I'm only use deadline to send a batch of max files to render over night.
3.using "Overwrite default Render Element folder" option is saving me the hassle of creating manually folders for each render element (sometimes there's a lot) creating first and second scene is even more time consuming.
4. another issue is that when saving any of the cryptomatt render elements, octane save two files, first file named:"file_name_0001" and a second file name:"file_name_0001Oct" having the "Oct" in the end of each frame is preventing adobe after effects to recognize the files as a sequence and forcing me to put all the render in a different folder and use the "Force alphabetical order" when importing the files
4. another issue is the frame numbering when using deadline, I'm getting "file_name_00010001","file_name_00020002","file_name_00030003" and so on, this causing adobe after effect to think there are missing frames between one frame to another also forcing me to put all the render in a different folder and use the "Force alphabetical order" when importing the files


Hi PromotsAdmin,

I updated several things in the new version (13.18) that should help: viewtopic.php?f=80&t=81452
-fixed the double save of cryptomatte exr
-In Preferences, Main Settings tab, set Output Image renaming mode to Never. That should avoid adding 'Oct' to the filenames
-For the double numbering, that's strange, it might be that Deadline adds it's own numbering..
Could you try the new option 'Custom output digit count', and set 0. On normal rendering, 0 should not be used, as this would always use the base filename without any number, overwriting the same file for every frame. But with Deadline, this might work..
If not, could you try another digit number instead of the default 4, like say 3.. and see if you get names like out_002002 (both parts using 3 digits) or more like out_0002002 or out_0020002, that would indicate that Deadline adds a 4 digits part..

I'm still investigating the folder creation issue...

Thanks
neonZorglub
OctaneRender Team
OctaneRender Team
 
Posts: 897
Joined: Sun Jul 31, 2016 10:08 pm

Re: OctaneRender® for 3ds max® v2022.1 - 13.17

Postby neonZorglub » Wed Apr 05, 2023 4:29 am

neonZorglub Wed Apr 05, 2023 4:29 am
coilbook wrote:1. There is a bug with phoenix liquids motion blur direction. It goes diagonally and doesn't follow particle motion blur. I posted this problem before. It happened since you quit supporting phoenix vertex motion blur.

2. your phoenix octane particle modifier scale is way off. You need a half of a meter particle like a foam to look like it is 5 centimeters

In the image water falls down Thank you


hi coilbook,
Thank you for reporting this issue, and the other issues too.
I'll look into it asap.

The 3dsMax handling of missing texture has also annoyed me for a long time.. It's time to add a Texture Relocator dialog ;)

Thanks
neonZorglub
OctaneRender Team
OctaneRender Team
 
Posts: 897
Joined: Sun Jul 31, 2016 10:08 pm

Re: OctaneRender® for 3ds max® v2022.1 - 13.17

Postby coilbook » Tue Apr 11, 2023 12:59 pm

coilbook Tue Apr 11, 2023 12:59 pm
neonZorglub wrote:
coilbook wrote:1. There is a bug with phoenix liquids motion blur direction. It goes diagonally and doesn't follow particle motion blur. I posted this problem before. It happened since you quit supporting phoenix vertex motion blur.

2. your phoenix octane particle modifier scale is way off. You need a half of a meter particle like a foam to look like it is 5 centimeters

In the image water falls down Thank you


hi coilbook,
Thank you for reporting this issue, and the other issues too.
I'll look into it asap.

The 3dsMax handling of missing texture has also annoyed me for a long time.. It's time to add a Texture Relocator dialog ;)

Thanks

Thank you! Would be amazing!
coilbook
Licensed Customer
Licensed Customer
 
Posts: 2985
Joined: Mon Mar 24, 2014 2:27 pm

Re: OctaneRender® for 3ds max® v2022.1 - 13.17

Postby PromotsAdmin » Sun Apr 16, 2023 1:33 pm

PromotsAdmin Sun Apr 16, 2023 1:33 pm
Hi PromotsAdmin,

I updated several things in the new version (13.18) that should help: viewtopic.php?f=80&t=81452
-fixed the double save of cryptomatte exr
-In Preferences, Main Settings tab, set Output Image renaming mode to Never. That should avoid adding 'Oct' to the filenames
-For the double numbering, that's strange, it might be that Deadline adds it's own numbering..
Could you try the new option 'Custom output digit count', and set 0. On normal rendering, 0 should not be used, as this would always use the base filename without any number, overwriting the same file for every frame. But with Deadline, this might work..
If not, could you try another digit number instead of the default 4, like say 3.. and see if you get names like out_002002 (both parts using 3 digits) or more like out_0002002 or out_0020002, that would indicate that Deadline adds a 4 digits part..

I'm still investigating the folder creation issue...

Thanks

Hi

Thanks for the fix and updated version, the double numbering now fixed when setting the digit count to 0, with deadline it renders 4 digits. as you predicted when setting the digit count to 3 its saves the file with 4 digits followed by 3 digits ex:0001001.
hopefully you will figure out the folder creation issue soon :-)

Thanks!
PromotsAdmin
Licensed Customer
Licensed Customer
 
Posts: 21
Joined: Tue Feb 28, 2017 11:20 am
Previous

Return to Releases


Who is online

Users browsing this forum: No registered users and 3 guests

Thu Apr 18, 2024 1:36 am [ UTC ]