If you have made your own tutorial patches, please upload them here.

If you have made tutorials regarding a specific node please link it to the according OnlineHelpPage of the Reference

---

also see the Video Tutorials by our fellow west

---

• Tutorial Folder
• Clipboard Patches
• General Tutorials
  • QuickAccessToNeighborPatches.v4p (1.19 Kb)
  • SHIFTandCursorkeys.v4p (4.32 Kb)
  • SpeedScrollingInLargePatches.v4p (20.64 Kb)
  • VisibilityOfPins.v4p (21.89 Kb)
  • VisibilityOfPinsIOBoxes.v4p (21.00 Kb)
  • VisualizeSwitchWithIOBoxColor.v4p (38.74 Kb)
  • HowTo edit wrong Paths quickly
  • Make helppatches not only for Modules
  • Referencing Textures
  • TransformationHierarchy (Tutorial)
  • keepCleanStructureInPatches (Tutorial).v4p
  • BinSize (Tutorial).v4p
  • HowTo Make Patches Portable
  • SpreadingSpreads (Tutorial).v4p
  • SpreadRenderStates (Tutorial).v4p
  • Angles in 2D
  • ViewProjection (Tutorial)
• Specific Node Tutorials
  • ArbitraryPoint (Tutorial).v4p
  • FiducialTracker (Tutorial).zip
  • IObox (Value) Advanced
    • how to force IOBox (Value Advanced) to boolean bang subtype
  • SwapDim (Tutorial).v4p
  • VideoIn (Tutorial).v4p
  • Create Enum (Tutorial).v4p
  • HowTo use XFile (EX9.Geometry Load)

---

Tutorial Folder

having subfolders for tutorials in the modulesfolder has some advantages: all contained patches are accessible via nodelist... ...assumed their naming sticks to the naming conventions for modules. so it is recommended to name a tutorial patch somehow like YourThing (Tutorial).v4p. this makes migration to the next betaversion much easier. the leading [ ] squarebrackets aren't necessary: they only cause this folder being listed at the top.

---

Clipboard Patches

more and more often you'll realize being busy doing the same clicks again and again:

• configure an IOBox to make it look the way you prefer.
• typing Xpath (XML) or RegExpr (String) expressions you know you did before.
• configuring a Renderer (EX9) depthbuffer on, antialising on

surely you are familiar with this.

---

simple make a patch which keeps the naming conventions of ((modules? and save it into your modules folder.
of course best solution is having a dedicated Clipboard folder.
fill this patch with your custom configured nodes an/or patchlets.

---

Having the right name it will show up right next to its related node in the nodelist. e.g. IOBox (String Clipboard).v4p IOBox (String)

now you have fast access to an archive
copy/paste into your project patch.

---

please also consider sharing your hints and clippings with the community

---

---

a first one:

SetPatch (VVVV Clipboard).zip (10.23 Kb)

contains many preconfigured + (String) nodes.
some of their pins have default contents and were set hidden/invisible. easily cascade them to build a hierarchy to use with SetPatch (VVVV)

---

---

General Tutorials

---

some little new ones:

QuickAccessToNeighborPatches.v4p (1.19 Kb)

http://vvvv.org/tiki-download_file.php?fileId=1814

SHIFTandCursorkeys.v4p (4.32 Kb)

http://vvvv.org/tiki-download_file.php?fileId=1815

SpeedScrollingInLargePatches.v4p (20.64 Kb)

http://vvvv.org/tiki-download_file.php?fileId=1816

VisibilityOfPins.v4p (21.89 Kb)

http://vvvv.org/tiki-download_file.php?fileId=1817

VisibilityOfPinsIOBoxes.v4p (21.00 Kb)

http://vvvv.org/tiki-download_file.php?fileId=1818

VisualizeSwitchWithIOBoxColor.v4p (38.74 Kb)

http://vvvv.org/tiki-download_file.php?fileId=1819

and here the older ones:

---

HowTo edit wrong Paths quickly

how to use free XML Marker to edit patches with empty or missing nodes

---

Make helppatches not only for Modules

When you stick to the Conventions.NodeAndPinNaming you can make helppatches for almost everything:

---

Referencing Textures

if you want to use some of the textures which are provided with vvvv you can make use of the node SystemFolder (File) to be sure that those texture is found on any other vvvv-users computer.

---

TransformationHierarchy (Tutorial)

by kalle

download TransformationHierarchy (Tutorial).zip

---

keepCleanStructureInPatches (Tutorial).v4p

some more hints from kalle

download keepCleanStructureInPatches (Tutorial).v4p

---

BinSize (Tutorial).v4p

from kalle
ever wondered about that BinSize-Pin?

download BinSize (Tutorial).v4p

---

HowTo Make Patches Portable

from kalle
Your mates complain missing/empty nodes in your patch? check this.

HowTo Make Patches Portable

---

SpreadingSpreads (Tutorial).v4p

this one is from elektromeier

download SpreadingSpreads (Tutorial).v4p

---

SpreadRenderStates (Tutorial).v4p

a small one from kalle

download SpreadRenderStates (Tutorial).v4p

---

Angles in 2D

gregsn starts writing about Angles in 2D. click link to see own page.

---

ViewProjection (Tutorial)

by gregsn
did you ever wonder why Camera (Softimage) is connected with separate transforms for view and projection?
download ViewProjection (Tutorial).v4p

---

Specific Node Tutorials

---

ArbitraryPoint (Tutorial).v4p

how to use ArbitraryPoint (Transform) / ArbitraryPoint (Transform Vector)


^{by kalle}

---

FiducialTracker (Tutorial).zip

how to use FiducialTracker (FreeFrame DShow9)


^{by kalle}

---

IObox (Value) Advanced

how to force IOBox (Value Advanced) to boolean bang subtype

^{by kalle}

---

SwapDim (Tutorial).v4p

how to use SwapDim (Spreads)


^{by kalle}

---

VideoIn (Tutorial).v4p

problems with VideoIn (DShow9) ?


^{by kalle}

---

Create Enum (Tutorial).v4p

Want to know how to make your own Enums using CreateEnum (Enumerations) ?
follow these 6 steps.


^{by west}

---

HowTo use XFile (EX9.Geometry Load)

How to XFiles using XFile (EX9.Geometry Load) with different materials (including a box as .x)


^{by phl}