» 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

For vvvv.exe

/o "path to patch"
/r "path to patch"

/o opens the patch given by path. This argument followed by a path can be specified any number of times.

/r opens the patch given by path as root patch. This argument can only be specified once, since there can only be one root-patch.

Note
The path can be relative to vvvv.exe or absolute.
If there is a space in the path you have to use quotes: /o "my project/patch.v4p"

/allowmultiple

Allows multiple instances of vvvv to run.

/dontregister

Prohibits 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:PortNr

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 Boygroup (VVVV Server) Network Port. Also see Boygrouping and MultiBoygrouping.

/server

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

/clockport PortNr

Changes the default port 3334 of the boygroup time synchronization system to the specified port. This can be used to avoid port conflicts with multiple vvvv instance on the same machine.

/dda DeviceID

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 DeviceID 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.)

/dx9

Since beta32 vvvv defaults to Direct3D 9Ex mode. use this flag to run the legacy dx9 mode, see cross-process-texture-sharing-depth-rendering

/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.

/showexceptions true OR false

Enables or disables the exception dialog. By default the exception dialog is disabled in beta releases and enabled in alpha releases.

/artnetsendport PortNr
/artnetreceiveport PortNr

To specify a different than the default port (6454) for DMX (Network Artnet Sender) and DMX (Network Artnet Receiver).

For setup.exe

/unregister

Same as pressing the "unregister all" button.

/silent

Just do it, don't show the window.

/log

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

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

~3h ago

xd_nitro: oh it's a contribution not forum. doh! multitouch-stack-revived

~3h ago

xd_nitro: hey y'all - anyone up for doing some sponsored work on multitouch-stack-revived?

~20h ago

tonfilm: @all please update your VVVV.OpenVR pack, important bugfix: vvvv.openvr #htc #vive #oculus #rift #vr

~24h ago

~1d ago

id144: @joreg i'm not sure where to start with the requests, everything i know is wrong and yoghurt

~1d ago

joreg: only 5 requests but already 20 proposals for #node17 workshops. keep'em coming: node17-call-for-workshops #vvvv #vl #visualprogramming

~1d ago

joreg: the 2016 numbers are out: vvvv-in-numbers-2016 thanks everyone for contributing #vvvv

~1d ago

skyliner: thanks for the numbers!

~2d ago

bo27: Anyone around LA area? Let's meet for beer+vvvv+business(optional)

~3d ago

eno: Last in a series of #liveAR shows https://youtu.be/75qzxi5LG-0?t=18m10s , proudly made with #vvvv