Tips & Tricks

Node Optimization

  • Start with a clear goal: Before building your graph, jot down what you want to achieve so your node structure stays focused and purposeful.
  • Build in layers: Lay out main nodes first (scene, subject, output), then add details like lighting, effects and attributes. Complex graphs become far easier to manage.
  • Use meaningful labels: Name each node for its role (e.g. “Main Light – Warm”, “Hero – Confident Pose”)—indispensable in big graphs.
  • Colour‑code or group nodes: If the editor allows, group lighting, materials, etc. visually so you can scan a graph at a glance.
  • Duplicate & adapt: Clone node groups for similar scenes and tweak only what’s different.
  • Keep connections tidy: Crossed wires slow debugging; align and route links clearly.
  • AdvancedUse attribute and effect nodes to add realism—subtle reflections, weather, custom materials. Stacking effects (rain + neon + fog) can yield striking looks.
  • ProSplit very large graphs into sub‑graphs or modules to simplify collaboration and troubleshooting.

Prompt Engineering

  • Be specific and visual: “Soft golden light at sunset” beats “light” for predictable results.
  • Use reference images & keywords: Guide the AI with style terms like “cyberpunk, rainy, Tokyo”.
  • Experiment with variations: Duplicate a graph, tweak one node (mood, colour, angle), quickly compare.
  • Mix and match styles: Combine presets, materials or effects for fresh aesthetics—bold combos often shine.
  • Document your best prompts: Save graphs and notes whenever something works. Your future‑you will thank you.
  • AdvancedChain multiple effect/attribute nodes for layered looks (e.g. “rain + neon reflections + fog”). Negative prompts help suppress unwanted elements.
  • ProReverse‑engineer favourites: dissect a reference image into scene, subject, lighting, then rebuild it in Verlo to learn new tricks.

Workflow Tips

  • Use templates and presets: Kick‑off with a product‑shot or character‑design template to save time and ensure consistency.
  • Preview and iterate often: Run the graph frequently—don’t wait until the end.
  • Undo/redo is your friend: Experiment freely knowing you can backtrack instantly.
  • Keep your workspace tidy: Cull unused nodes and links regularly; clutter breeds bugs.
  • Collaborate and share: Trade graphs for feedback, inspiration and troubleshooting.
  • AdvancedUse versioning or snapshots to store project stages—great for large teams or multi‑week builds.
  • ProAutomate repetitive tasks with scripts/macros when supported—huge time‑saver on big jobs.