Support & Community
Introduction​
Whether you are stuck on a specific technique, have found an error in the documentation, or want to contribute your own expertise, this page outlines how to get help, and how to give back.
Email Support
Primary support channel for questions, feedback, and assistance with the knowledge base.
AI Tutor
Use our custom NotebookLM to ask questions about the methodology and get instant answers.
Community
Connect with the wider Blender ecosystem for technical troubleshooting.
The Art of Asking​
3D software is complex. When things break, the way you describe the problem determines how fast we can solve it.
The "Bad" Report:
"My render is broken. It looks weird." (This requires 5 follow-up emails to figure out what "weird" means).
The "Good" Report:
"I am using Blender 5.0. I imported a point cloud (.ply), but the normals seem flipped inside out. I tried using 'Recalculate Outside' (Shift+N), but it didn't fix it. Screenshot attached."
The Checklist for Support:
- Context: What were you trying to do?
- Action: What specific steps did you take?
- Result: What happened vs. what did you expect to happen?
- Specs: Which Blender version, addons, etc. are you using?
Getting Help​
Support Channels​
For general users of this knowledge base, support is offered via email.
📧 boudewyn.bvi@protonmail.com
For Course & Workshop Participants we have extra support tiers.
- Video calls for complex troubleshooting
- Screen sharing sessions
- Personalized (video) feedback on your project files & questions
- Access to private Signal group
NotebookLM: Your AI Tutor​
I have "fed" a dedicated Google NotebookLM on this specific knowledge base and useful resources. If you have never used NotebookLM before, think of it as a dedicated AI tutor that can understand our specific needs within our specific domain.
Why use this? Tutorials are linear; questions are non-linear. Instead of scrolling through an hour of video to find a solution to a specific problem, you can simply have a conversation about it.
How to use it:
- Open the notebook: NotebookLM for BVI
- Be Precise: Instead of "Help me with cameras," ask: "What are the steps to match a camera using fSpy data?"
- Set Context: Tell it your goal. "I am an analyst trying to verify a shadow, how do I set the sun position?"
NotebookLM is a synthesizer, not a practitioner. It is excellent at summarizing steps and finding concepts in the text, but you must still do the work. Use it to find the path, not to walk it for you.
External Community Resources​
Blender has one of the largest communities in the software world. For general 3D questions (not specific to investigation), these resources are invaluable:
| Resource | Best Used For... | Link |
|---|---|---|
| Blender Manual | The definitive "Dictionary" of what buttons do. | docs.blender.org |
| Blender Stack Exchange | Specific technical errors (e.g., "Python script failed line 40"). | blender.stackexchange.com |
| Blender Artists | Feedback on visual quality and rendering techniques. | blenderartists.org |
Contributing​
This knowledge base is a living document. Visual investigation is a collaborative field, and accuracy is a collective effort.
We welcome contributions, specifically:
- Corrections: If you spot a typo or a deprecated workflow.
- New Techniques: If you have developed a better way to handle specific data or a specific workflow.
- Case Studies: Examples of how you applied these methods in the field.
Simply email your suggestion or content to the support address. For larger contributions or ideas (like a full case study), please reach out first to discuss the best format.
Summary​
You are now ready to begin the curriculum. You know where you are going (Structure), why you are using this tool (Why Blender), what to avoid (Pitfalls), and how to get help when you stumble (Support).
Key Takeaways:
- Ask Smart: A detailed question gets a fast answer.
- Use the AI: NotebookLM is your first line of defense for quick answers.
- Reach Out: Don't stay stuck for days; don't hesitate to email for support.
- Contribute: Help refine the knowledge base for the next investigator.