Hello,
My must wanted feature is a better animation process because relaunching Octane for each frame takes 15min with biggest files and are cooked in 20 seconds only. Another point will be a fixed axis for textures because when objects move ,textures "slides" if they are proceduraly made in octane.
Hope this will corrected soon. Netherless, thanks Octane team for your great works !
Question for Developers: What's Coming Next?
-
LudovicRouy
- Posts: 216
- Joined: Sat Apr 03, 2010 5:05 pm
- Location: FRANCE
- Contact:
1+
Portfolio: http://www.tres31.com/site/
http://www.flickr.com/photos/tres31/
sr2 mobo / dual Xeon E5620 3.2Ghz / geforce gtx 480 + geforce 580 3gb msi twin frozr III / 20gb RAM
http://www.flickr.com/photos/tres31/
sr2 mobo / dual Xeon E5620 3.2Ghz / geforce gtx 480 + geforce 580 3gb msi twin frozr III / 20gb RAM
Hi,
I have a couple of suggestions for the developers concerning matting.
It would be great if you could use the "transparent background feature on a material level or object level. Essentially a mask material for compositing.
Another idea would be having a "display only selected" button at the top near the AF, clay render, etc. buttons. This would help with bake times and would speed up scene tweaking by giving you the option of only working on/showing the object you have selected while hiding everything else.
For clarification, All the hidden or masked objects would still affect the highlighted objects reflections, lighting, AO, etc, they would just not be displayed. Max has this feature under "Make visible to camera" that allows you to simply check on or off the ability for the object to be viewable or not by the camera.
Anyway, I just thought these could be added to the backburner for feature request.
I have a couple of suggestions for the developers concerning matting.
It would be great if you could use the "transparent background feature on a material level or object level. Essentially a mask material for compositing.
Another idea would be having a "display only selected" button at the top near the AF, clay render, etc. buttons. This would help with bake times and would speed up scene tweaking by giving you the option of only working on/showing the object you have selected while hiding everything else.
For clarification, All the hidden or masked objects would still affect the highlighted objects reflections, lighting, AO, etc, they would just not be displayed. Max has this feature under "Make visible to camera" that allows you to simply check on or off the ability for the object to be viewable or not by the camera.
Anyway, I just thought these could be added to the backburner for feature request.
I dont know if this is the right place to ask but, i like the Live DB feature, it's handy but it makes me think how come we dont have our one reusable material database (home) next to it?
high regards
high regards
win 8.2 / 64 / systemmem 27Gb / gtx 750Ti & asus stricks Gtx 780 6Gb
IIRC, it will be present in the final 1.0 (at least it should be, because is a needed feature)polytek wrote:I dont know if this is the right place to ask but, i like the Live DB feature, it's handy but it makes me think how come we dont have our one reusable material database (home) next to it?
Since it's related: The option to not save (just link) images in the .ocm files would be also needed, because is much more handy than saving them.
SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
cgmo.net
Brilliant news about the instancing. I just wonder how is it possible? Not so long ago, i asked for it and Abstrax claimed it cannot be done without ditching OBJ, cause OBJ does not support it. So the question now is, is OBJ going to be replaced for something else?
Anyway, i look forward to it. Its probably number one on my wishlist, alongside possibility to have sun + HDR lightning combo and light passing through glass. Please make this happen as fast as you can.
Oh, and the 360 camera for making of those pseudo 3D renders would be nice too.
Anyway, i look forward to it. Its probably number one on my wishlist, alongside possibility to have sun + HDR lightning combo and light passing through glass. Please make this happen as fast as you can.
Oh, and the 360 camera for making of those pseudo 3D renders would be nice too.
Intel Core i7 980x @ 3,78GHz - Gigabyte X58A UD7 rev 1.0 - 24GB DDR3 RAM - Gainward GTX590 3GB @ 700/1400/3900 Mhz- 2x Intel X25-M G2 80GB SSD - WD Caviar Black 2TB - WD Caviar Green 2TB - Fractal Design Define R2 - Win7 64bit - Octane 2.57
I'd like to see the transition from obj to fbx. to support things like cameras, lights, etc. Or maybe both obj and fbx
Hi guys,
OBJ is an object format, eg it only holds a collection of mesh triangles/quads in object space.
After the next release is out (2.5), with the new renderkernel and multi-gpu rewrite,
this is the next big feature to get developed.
We are not going to adopt fbx or collada, as these are very complex fileformats with a lot of differing implementations,
it was planned to implement a fileformat like these in the initial roadmap at the beginning of 2010, eg FBX or Collada,
but after evaluation/tests we have decided to use OBJ (for now) as an object format and build our own custom octane XML scene import fileformat.
The specifications for it will be published in advance, once they are finalized, after the next release (2.5) is out.
Radiance
OBJ is an object format, eg it only holds a collection of mesh triangles/quads in object space.
After the next release is out (2.5), with the new renderkernel and multi-gpu rewrite,
this is the next big feature to get developed.
We are not going to adopt fbx or collada, as these are very complex fileformats with a lot of differing implementations,
it was planned to implement a fileformat like these in the initial roadmap at the beginning of 2010, eg FBX or Collada,
but after evaluation/tests we have decided to use OBJ (for now) as an object format and build our own custom octane XML scene import fileformat.
The specifications for it will be published in advance, once they are finalized, after the next release (2.5) is out.
Radiance
Win 7 x64 & ubuntu | 2x GTX480 | Quad 2.66GHz | 8GB
You should probably remove Collada from the list of features (@ http://refractivesoftware.com/features.html) if you aren't planning on including it.radiance wrote: We are not going to adopt fbx or collada, as these are very complex fileformats with a lot of differing implementations,
it was planned to implement a fileformat like these in the initial roadmap at the beginning of 2010, eg FBX or Collada,
but after evaluation/tests we have decided to use OBJ (for now) as an object format and build our own custom octane XML scene import fileformat.
radiance wrote:Hi guys,
OBJ is an object format, eg it only holds a collection of mesh triangles/quads in object space.
After the next release is out (2.5), with the new renderkernel and multi-gpu rewrite,
this is the next big feature to get developed.
We are not going to adopt fbx or collada, as these are very complex fileformats with a lot of differing implementations,
it was planned to implement a fileformat like these in the initial roadmap at the beginning of 2010, eg FBX or Collada,
but after evaluation/tests we have decided to use OBJ (for now) as an object format and build our own custom octane XML scene import fileformat.
The specifications for it will be published in advance, once they are finalized, after the next release (2.5) is out.
Radiance
Thanks for the news about file format support. I'm glad RS is going to provide a robust file format. Let's hope it has lots of compatibility with other apps.