Troubleshooting
ActionBoards creates a storyboarding workspace and many behind the scenes efficiencies to grease pencil and scene navigation. Despite this ActionBoards is only an add-on for Blender and not a custom cut. The advantage of this is it can be more easily updated for future Blender releases, though this comes at the cost of some default Blender actions being accessible that can damage your file if used incorrectly.
ActionBoards has many behind the scenes functions running that help to prevent these add-on breaking actions from taking place, but here are a few things as a user to keep in mind to further prevent issues:
Makes Sure ActionBoards’ Hotkeys Are Active
Before working with ActionBoards make sure that you have installed and activated the add-ons hotkeys. The hotkeys disable the default object delete to prevent essential objects from being deleted, which adds stability to the program.
Disable Other Add-ons with Hotkey Conflicts
Using other add-ons at the same time as ActionBoards may cause hotkey conflicts. If a hotkey isn’t working, make sure to turn off all other add-ons.
Do Not Disable ActionBoards with Working File Open
ActionBoards creates many custom variables that it requires to run. If the add-on is disabled while your storyboard file open Blender looses those variables. If for whatever reason the add-on is disabled while your working file is open, do not save it. Similarly when updating ActionBoards, do not have your working file open, the same issue will occur.
Do Not Delete or Rename Essential Objects, Scenes, or Collections
Do not delete or rename any element of the ActionCamera Rig, 3D Grid, Workspaces created by ActionBoards, the Thumbnails Scene, Editorial Scene, or BG Assets Collections. (ActionBoards requires these to run properly. Rename protections are in place, though not being a custom cut of Blender the delete functions are still accessible manually)
Only Create and Delete Scenes Using ActionBoards’ Tools
When creating or deleting Scenes use ActionBoards’ Scene Tools, and not Blender’s default. (You can still add non-storyboard scenes regularly but do not name them SC.### as that naming convention is reserved for Storyboard Scenes.)
Compartmentalize Large Projects
Blender is a 3D software so rendering time may be longer compared to popular 2D storyboarding software. So, it’s best practice to keep each Blender Storyboard File bellow 12mins of length (less if using heavy assets). If you are working on a longer project, consider creating a Blender file for each sequence.
Approximate Rendering Times
Every 1 second of video rendered takes approximately between 2.1-2.6 seconds to render. (Benchmarked using an RTX 2070 Super graphics card, at 1920x1080px, with Material Preview rendering)
If you are experiencing abnormally long rendering times you should lower your project resolution and/or swap out your 3D models for lower-poly ones.
Program is Rendering Even if Appearing Non-responsive
When using the rendering options in the Editorial Workspace, the rendering indicator may disappear after a few seconds and the program will appear to be frozen. Don’t worry the program hasn’t crashed it is just using all it’s power for the rendering.
Multi-window Workflow Not Supported
Having a duplicate of your blender workspace open in another windows causes issues with the scene/workspace navigation system, which may lead performance bugs and potential corruption of the Blend file.
Periodically Make Backup Files
When working in any 3D software it is best practice to periodically make a duplicate copy of your work in case of a crash. As 3D software is generally more prone to crashes and file corruption than 2D art programs.