v3 not exporting Alembic or ORBX from v2 file

Sub forum for bug reports
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
User avatar
aLeXXtoR
Licensed Customer
Posts: 294
Joined: Sat Oct 29, 2011 5:38 pm
Location: Russia, St. Ptetersburg
Contact:

JimStar wrote:Could you share the scene?
It's a pretty simple scene as I said. I attached it here
Attachments
test.blend
(135.18 KiB) Downloaded 161 times
Win 10 Pro 64bit | GeForce RTX 2070 SUPER 8Gb | AMD Ryzen 7 3700X | 32GB RAM
WebSite
Showreel
User avatar
JimStar
OctaneRender Team
Posts: 3816
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

aLeXXtoR wrote:Yep, I googled for the similar problems - seems like it's some blender internal problem — some effects aren't teansfered to export engine... Is it possible to return the old method of export? Via render button? :)
Old method was some clunky, Blender created a lot of empty image files next to the output file... But if it was OK for you with old method – then there is a chance I can find some workaround to make it work in a new way... Looks like Blender refreshes geometry vertices when is switching to next frame in "render" mode (the old method used this "fake rendering" approach), but fails to properly refresh the geometry when any internal module just calls its "switch to frame number X" function... This looks like a Blender bug, but I will see on Monday if I can workaround this...
Thank you for the sample scene!
User avatar
JimStar
OctaneRender Team
Posts: 3816
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

Made a workaround, must work now in 11.11.
User avatar
aLeXXtoR
Licensed Customer
Posts: 294
Joined: Sat Oct 29, 2011 5:38 pm
Location: Russia, St. Ptetersburg
Contact:

Thank you! I will give it a test in a few hours!
Win 10 Pro 64bit | GeForce RTX 2070 SUPER 8Gb | AMD Ryzen 7 3700X | 32GB RAM
WebSite
Showreel
Post Reply

Return to “Bug Reports”