» Commandline Parameters
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

Commandline Parameters

French | Russian | Italian


Built-in Commandline Parameters

VVVV defines a few parameters to startup vvvv.exe with in order to achieve certain goals. Here they are:

/o [path to patch]

Opens the patch given by path. The path can be relative to vvvv.exe or absolute. Note that if there is a space in the path you have to use quotes, like e.g. so:

 /o "my project/callmenames.v4p"

Any number of /o arguments followed by a path can be specified.

/r [path to patch]

Opens the patch given by path as root-patch. The path can be relative to vvvv.exe or absolute. Note that if there is a space in the path you have to use quotes, like e.g. so:

 /r "my project/_root_my project.v4p"

/r can only be specified once, since there can only be one root-patch.

/allowmultiple

Allows multiple instances of vvvv to run.

/dontregister

Probihibts registration of addflow, directshowfilter and .v4p filetype

/shutup

Finishes your project in a clean way: starts vvvv without patch windows. Only renderers are displayed. Only the ALT-F4 shortcut works.

/client [ServerIP:Port]

Start vvvv as boygroup client connecting to the pc specified via [ServerIP]. Specifying a port is optional. The default (if omitted) is 3333. Note that if you specify a different port here you need to specify the same port via Boygrouping (Network Server) Network Port. Also see Boygrouping and MultiBoygrouping.

/server

Start vvvv as boygroup server. Also see Boygrouping and MultiBoygrouping.

/dda X

Short for "dummy device adapter". Only needed if you're having troubles with a renderer that is supposed to go fullscreen on a monitor other than the primary immediately after starting up a patch.
Specify as X the device ID of the monitor a renderer is supposed to go fullscreen on. The device ID can be found by using the graphic-drivers "Identify" option where it prints large numbers on all connected monitors for identifying their order. Take this number minus 1 (i.e. the primary monitor is 0, which you'd never have to specify since this is the default anyway.)

/debug

Starts vvvv in Debug Mode.

/logstartup

Use this if you have troubles starting vvvv. With this flag vvvv logs all steps it does on startup into a .txt file, placed next to vvvv.exe. You can then post that textfile to the forums bug-section and hope that we can help you identify your problem.

/nodelist [path]

Generates a path/nodelist.xml file for all nodes found beneath the specified path.

Using your own Commandline Parameters

Note that you can also specify your very own commandline parameters and read their values from within a patch via the node Args (VVVV). See its help-patch for further information.

Automation

args.txt

In vvvvs main program directory, just next to vvvv.exe you can create a file called args.txt. If present this file is parsed and its content is concatenated to the parameters specified via commandline. This is a simple way to specify commandline parameters. A # on the beginning of a line in that file denotes a comment. Comments are not being interpreted by vvvv.

Registry

For what ever reason, you may want to add additional startup options for .v4p-files on rightclicking them in explorer. Open (/o) and Open As Root (/r) are allready there. Search the registry for

 HKEY_CLASSES_ROOT\VVVV\Shell

and see what you can do.

Batch Files

It may be handy to use different .bat files for calling vvvv.exe with different parameters.

Shortcuts

Make a shortcut to vvvv.exe and rightclick it to edit its properties. There in the Target field you can simply add commandline parameters.

anonymous user login

Shoutbox

~6h ago

Urbankind: circuitb:Wrongcop is epic! :)

~7h ago

joreg: @tobi: use GetSlice() as the patch i referred you to is demonstrating. or start a forum thread with your patch.

~7h ago

TobiTobsen123: hmm yes i can see the values...but how to handle them as seperate values? I need to forward them via TCP/IP...

~8h ago

joreg: @tobi: OSCDecoder helppatch has a section: OSC_Advanced (bottomright) that demoes decoding of multiple messages

~9h ago

TobiTobsen123: I'm using an OSCDecoder, it receives two arguments...works but how can I seperate the arguments into two seperate values

~11h ago

u7angel: @mediadog, make it a forum question.

~12h ago

u7angel: @mediadog, tty renderer ?

~14h ago

microdee: however non-conductive objects are invisible for this so the pencil and the sticks in the video are still a mysteries