Keyframing
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
- cglittenberg
- Posts: 93
- Joined: Wed Nov 17, 2010 4:45 pm
- Location: Vienna, Austria
- Contact:
PLEASE put in a keyframing system for the camera position. It would really make all the difference!!!!!!!
Dr. Carl Glittenberg
Glittenberg Medical Visualizations
Intel(R) Core(TM)i7 CPU 860 @ 2.80Ghz 2.80Ghz 6,00 GB RAM Windows 7 Home Premium Nvidia GeForce GTX 480
Glittenberg Medical Visualizations
Intel(R) Core(TM)i7 CPU 860 @ 2.80Ghz 2.80Ghz 6,00 GB RAM Windows 7 Home Premium Nvidia GeForce GTX 480
- cglittenberg
- Posts: 93
- Joined: Wed Nov 17, 2010 4:45 pm
- Location: Vienna, Austria
- Contact:
Thanks, look forward to it!!!




Dr. Carl Glittenberg
Glittenberg Medical Visualizations
Intel(R) Core(TM)i7 CPU 860 @ 2.80Ghz 2.80Ghz 6,00 GB RAM Windows 7 Home Premium Nvidia GeForce GTX 480
Glittenberg Medical Visualizations
Intel(R) Core(TM)i7 CPU 860 @ 2.80Ghz 2.80Ghz 6,00 GB RAM Windows 7 Home Premium Nvidia GeForce GTX 480
Kinda agree here.adrencg wrote:I thought the whole idea of Octane was to use it as a renderer for other animation software. Why bog it down with animation, when it should focus on rendering?
On other hand Octane/plugin import/export speed should be improved for that. Obj format is a bottleneck IMHO.
Though it'd be great to be able to export whole animation to octane.. some day - far, far away

http://www.visnevskis.com
Vista64/Ubuntu, GTX470/580
Vista64/Ubuntu, GTX470/580
+1kivig wrote:[Kinda agree here.
On other hand Octane/plugin import/export speed should be improved for that. Obj format is a bottleneck IMHO.
Though it'd be great to be able to export whole animation to octane.. some day - far, far away
this is the the real question: better exporting, not keyframing

ciao beppe
The camera in Octane is one of the software's best facets.
Tracking and keyframing the camera location, rotation, fov, depth of field, and focus location would create a very flexible way of building on the good ideas we have while using the Octane camera.
Exporting the Camera info out with a reference image would give a fast way of matching unique camera setup back in your animation program.
Tracking and keyframing the camera location, rotation, fov, depth of field, and focus location would create a very flexible way of building on the good ideas we have while using the Octane camera.
Exporting the Camera info out with a reference image would give a fast way of matching unique camera setup back in your animation program.
Win 7 64bit Pro | 3.06 950 i7 | 24GB RAM | 256 GB SSD boot | 256GB and 120GB SSD for cache| 12TB RAID 0 Adaptec 6405E | TANGENT WAVE PANEL | Quadro 600 (display), 1-580GTX-1.5GB
Nonsense...bepeg4d wrote:+1kivig wrote:[Kinda agree here.
On other hand Octane/plugin import/export speed should be improved for that. Obj format is a bottleneck IMHO.
Though it'd be great to be able to export whole animation to octane.. some day - far, far away
this is the the real question: better exporting, not keyframing
ciao beppe
If you have 4mio vertices, you have 12mio floats.
It doesn't matter whether format you use, 12mio floats are 12mio data to write/handle.
A cube with 60.000 triangles to save as FBX takes the same time as to save it as obj.
Both ~5sec in Softimage.
If you can write your own FBX/Obj exporter, you can save time.
But the most plugindevs use the buildin export.
An other reason is, that it takes a lot of hours to program it and i think you don´t want to pay more for a plugin as for Octane

face
Win10 Pro, Driver 378.78, Softimage 2015SP2 & Octane 3.05 RC1,
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
Dear Face,face wrote: Nonsense...
If you have 4mio vertices, you have 12mio floats.
It doesn't matter whether format you use, 12mio floats are 12mio data to write/handle.
A cube with 60.000 triangles to save as FBX takes the same time as to save it as obj.
Both ~5sec in Softimage.
If you can write your own FBX/Obj exporter, you can save time.
But the most plugindevs use the buildin export.
An other reason is, that it takes a lot of hours to program it and i think you don´t want to pay more for a plugin as for Octane
face
from my point of view the nonsense is waiting for 180" of exporting for 30" of rendering

The strange thing is that no one here was talking about of FBX

Anyway Radiance had already answered to this question some days ago:
ciao beppeHi 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