Ever faced a situation in which you wanted to compare different camera settings and positions?
Saveing those to a list would be great.
Camera Position Save
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.
- moronicjoker
- Posts: 22
- Joined: Tue Feb 23, 2010 5:59 am
- Contact:
Win 7|Dual GTX 480|Intel i7 920|6GB
+1 as a list (I'm hopeless with nodes !)
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
Hi guys, I had some free time, and decide to show you a trick I discovered when I played with first 2.3. It apply for cameras and lamps as well.. I made a quick video to see how to workaround and use multiple lights and cameras in scene without need of restarting the program or save multiple OCS files.
Here is the video, it's made pretty simple and fast, so ignore some mouse hover here and there
Enjoy..
Here is the video, it's made pretty simple and fast, so ignore some mouse hover here and there

Enjoy..
Vista 64 , 2x Xeon 5440 - 24GB RAM, 1x GTX 260 & I7 3930 water cooled - 32GB RAM, 1 x GTX 480+ 1x8800 GTS 512
CGsociety gallery
My portfolio
My portfolio2 - under construction
Web site
Making of : pool scene - part1
CGsociety gallery
My portfolio
My portfolio2 - under construction
Web site
Making of : pool scene - part1
Nice one Andrian !
Thinking about your approach and looking a bit in the code (that helps :=), for camera at least you have another option: after switching the camera connection from one to the other, simply enable then disable the Stereoscopic view (next to A/F) using the toolbar. It's going to update the cams too and will be faster than playing with the subsampling parameter.
EDIT: If you want to work incrementally (i.e. build new camera settings from the current) - instead of creating new camera nodes, you can right click the current Preview camera, save it as ocm and reload it. Just pay attention that when reloading the ocm, it will have the exact same position and name as the previous one so you might miss that it's been correctly reloaded /EDIT
Regards
/M
Thinking about your approach and looking a bit in the code (that helps :=), for camera at least you have another option: after switching the camera connection from one to the other, simply enable then disable the Stereoscopic view (next to A/F) using the toolbar. It's going to update the cams too and will be faster than playing with the subsampling parameter.
EDIT: If you want to work incrementally (i.e. build new camera settings from the current) - instead of creating new camera nodes, you can right click the current Preview camera, save it as ocm and reload it. Just pay attention that when reloading the ocm, it will have the exact same position and name as the previous one so you might miss that it's been correctly reloaded /EDIT
Regards
/M
This is a totally awesome trick! You made my day Andrian, now if I could use a command flag to access those nodes I could batch render from a single file! is there a thinlens flag for the command line?
windows 7 x64 | 2xGTX570 (warming up the planet 1ºC at a time) | i7 920 | 12GB