Several moths ago when Karba was here I asked to repair the Octane proxy bug.
I asked for it because I work seriously with Octane day by day making money.
Probably the developers think that Octane is a toy to do experiments with cg.
I'm really frustrated.
The issue:
if you create a proxy object into a scene where the scale is set in centimeters and you merge this object into a scene with scale set to meters you will get a wrong render.
The scale proxy is ok the rendered object is huge.
Don't waste your time with scripts
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)
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)
-
gabrielefx
- Posts: 1701
- Joined: Wed Sep 28, 2011 2:00 pm
- Attachments
-
quad Titan Kepler 6GB + quad Titan X Pascal 12GB + quad GTX1080 8GB + dual GTX1080Ti 11GB
- The system units are set to centimeters.
- The plane is created.
- The plane is exported to Octane proxy file.
- New scene is created.
- The system units are set to meters.
- The just created proxy file is imported into newly created proxy-object.
What I'm doing wrong?..
- The plane is created.
- The plane is exported to Octane proxy file.
- New scene is created.
- The system units are set to meters.
- The just created proxy file is imported into newly created proxy-object.
What I'm doing wrong?..
-
gabrielefx
- Posts: 1701
- Joined: Wed Sep 28, 2011 2:00 pm
I'll send you the Evermotion Vray tree I converted.
The original tree was modeled in centimeters, I created the proxy, merged into a meters scene.
The proxy was visualized ok when I merged it in the new scene but was rendered huge.
I saved the scene, closed Max, started it again and the proxy object was visualized huge in wireframe. I scaled it manually and was rendered ok.
I closed Max, started again, I loaded the same scene and the proxy tree was visualized tiny.
Crazy behavior!
It seems that switching scenes between different scales the proxy model is not updated.
In few fords switching from different scenes without quit Max some imported-merged Octane proxies aren't updated.
Probably some 3d libraries were created without reset the scale.
I'll send you the original model.
regards
The original tree was modeled in centimeters, I created the proxy, merged into a meters scene.
The proxy was visualized ok when I merged it in the new scene but was rendered huge.
I saved the scene, closed Max, started it again and the proxy object was visualized huge in wireframe. I scaled it manually and was rendered ok.
I closed Max, started again, I loaded the same scene and the proxy tree was visualized tiny.
Crazy behavior!
It seems that switching scenes between different scales the proxy model is not updated.
In few fords switching from different scenes without quit Max some imported-merged Octane proxies aren't updated.
Probably some 3d libraries were created without reset the scale.
I'll send you the original model.
regards
quad Titan Kepler 6GB + quad Titan X Pascal 12GB + quad GTX1080 8GB + dual GTX1080Ti 11GB
gabrielefx
My question was rhetorical.
Regarding the "crazy behavior": please, do not post the "bug reports" on some old four-version-ago versions without even reading the changelogs of the new versions. It was already fixed exactly after the previous report regarding proxies display scale...
My question was rhetorical.
Regarding the "crazy behavior": please, do not post the "bug reports" on some old four-version-ago versions without even reading the changelogs of the new versions. It was already fixed exactly after the previous report regarding proxies display scale...
JimStar wrote: Changes of the 2.0 version
- ...
- Fixed one more Octane proxy preview scaling issue: in the case the scene unit scale was adopted from loaded file having proxies in it.
- ...
oops =DDD.. Gab, Guess it's time to switch =p
-
gabrielefx
- Posts: 1701
- Joined: Wed Sep 28, 2011 2:00 pm
Hi Jim,
you wrote don't switch to the latest release because it is not compatibile with the old Max projects.
All my projects are critical and I merge tons of Max objects , created with previous versions of Octane, in new scenes.
For you what's the full stable release without this issue?
I always update Octane for Max but I think your are developing a version that can't read the old scenes.
you wrote don't switch to the latest release because it is not compatibile with the old Max projects.
All my projects are critical and I merge tons of Max objects , created with previous versions of Octane, in new scenes.
For you what's the full stable release without this issue?
I always update Octane for Max but I think your are developing a version that can't read the old scenes.
quad Titan Kepler 6GB + quad Titan X Pascal 12GB + quad GTX1080 8GB + dual GTX1080Ti 11GB
gabrielefx
I'm sure there are still a lot of other issues in previous versions, not only this one. I'm working hard on making 3ds Max plugin better, but I can't develop two different branches of 3ds Max plugin in parallel in addition to a lot of other plugins I develop. So, you can continue to work in previous versions for your old projects - you will just be working in the same versions having the same issues you've always worked with... The new versions may have already some issues fixed - so when you will be ready you can move on... Just check the newest changelogs before reporting the bugs of previous versions...
I'm sure there are still a lot of other issues in previous versions, not only this one. I'm working hard on making 3ds Max plugin better, but I can't develop two different branches of 3ds Max plugin in parallel in addition to a lot of other plugins I develop. So, you can continue to work in previous versions for your old projects - you will just be working in the same versions having the same issues you've always worked with... The new versions may have already some issues fixed - so when you will be ready you can move on... Just check the newest changelogs before reporting the bugs of previous versions...