By default, the view-ports Camera view in Blender displays the view from the camera that is set as the scene’s Active Camera.
If you split the view and in the new view select a different camera and set it as the Active Camera, the view in other view-ports set to camera view will update to display the new Active camera.
In short, by default, it seems you can’t assign different camera views to different view-ports..
But you can…
You just have to unlock the wanted view-port from the scene’s Active Camera by de-activating this button:
When the Use the scene’s Active Camera and layers in this view button is de-activated, your allowed to set an Active Camera for the specific view-port without changing the scene’s Active Camera setting, therefore not affecting other view-ports displaying the camera view.
To create constraints quickly:
- Select the target object.
- Shift + Select the object to constrain (Active Object)
- Press Ctrl + Shift + C
- Choose the wanted constraint type.
- select the constrained object to set the constraint parameters.
Alt + RMB Click a face or Edge in the loop.
In large scenes, selecting objects becomes slow.
There’s a frustrating lag and the software hangs between the time you Right-Click an object in the view-port, and the time it gets selected.
* especially if there are a lot of mesh surfaces behind it in the view-line of the mouse cursor.
The Systems settings shown below can dramatically improve this.
* You need a GLSL capable video card.
When appending items from a different blend file,
Check the Fake User option to automatically set a Fake User to the items.
This means that appended items that are not used within the file will not be deleted when closing it.
It’s useful for times when you append a whole library of materials or other assets into a file, so that you don’t have to make use off all of them before saving and closing, and they will still be available in the file the next time you load it.
In other words, you wont need to append the assets again the next time if you didn’t make use of them..
To create and edit measurement Rulers & Protractors:
- In the Tool Shelf > Grease Pencil,
Press Ruler/Protractor to activate Ruler/Protractor mode.
- LMB Click & Drag the 3D Viewport to create a measuring Ruler.
* Hold Ctrl while creating the Ruler to snap its start and end points to 3D elements.
* If a one or more measuring Rulers already exist, Ctrl must be held anyway to create a new Ruler.
- LMB Click & Drag along an existing Ruler line to turn it into a Protractor for angle measurement.
* Hold Ctrl while creating the Protractor to snap its apex to 3D elements.
- LMB Click & Drag a point in an existing Ruler or Protractor to change its location.
- LMB Click an existing Ruler or Protractor and Press Delete to delete it.
- When finished creating measurement Rulers & Protractors,
Press Enter to save them for later use of the Ruler/Protractor mode,
Or Press Escape to discard them (without discarding Rulers / Protractors that were previously saved).
To Delete all Ruler / Protractor data:
In the Properties Panel > Grease Pencil Layers,
Delete the RulerData3D Layer.
A quick Cycles rendering tip:
There are situations in which we need to render an animation with changing lighting complexity, and as a result, parts of the animation need more samples than others to be effectively rendered.
For example when the camera starts it’s movement on the outside in an exterior scene, and moves into an interior space like house or a cave, or a vehicle, in many cases, the exterior part of the animation can be rendered with much less samples than the interior part.
In such cases, rendering the whole animation with the higher sample settings will demand unneeded render time in the simpler parts of the animation.
One possible solution would be to simply render the animation in two separated render jobs with different sampling settings, one for the less demanding part and another for the more complex part and than append the two parts in an editing / compositing software. but that requires more work on the shot, more management etc.
A simple solution is to animate the sample settings in Cycles.
Make tests at different times along the animation to determine how many samples are needed at each part, and key-frame the settings accordingly.