There are several preliminary tasks required to operate multiple computers from one.
Some operations would be better suited to use the Remote Control to copy or move data as required. Or just do it manually...
Task 1. It is necessary to set the computer(s) network IP address as static rather than a (random) generated one.
Task 2. It is suggested to Set a drive on the Commander as Shared so the data can be accessed and changed by the Drones.

There are several methods of operation.
Op 1. Operating Remote Control Drones to perform individual tasks.
Op 2. Tasking a Drone to perform a task.
Op 3. Running a 3D Viewer and farming out the background visualization computations to the Drones.

Task 1. Set the computer(s) network IP address
{start with one autosensed and then change it to that Manually and adjust the others from that ones last number}
IPAddress192.168.0.1 and 192.168.0.0 are used for a pair of null-cable networked computers. Subnet mask 255.255.255.0 on both.
On [ ] TCP/IP Properties TAB SHEETS PAGE
IPAddress
169.254.126.198 for the Commander (server) computer
169.254.126.197 ... 196 ... on the other computers {VR GIS uses 99 as the default Drone}
Subnet mask
255.255.0.0 {Same on all}

The computer IP address is different for each computer. The Port they communicate on must be the same for them to transfer the information. The Port is different for kinds of tasks and operations... These are the default VR GIS numbers... see Internet Protocol information for the 'Standard' Port numbers and their use.
RC Port : 23
Task Port(s) : 2345
View Port(s) : 3456...

Task 2. Set a drive on the Commander as Shared

2.1. Decide which computer is the Commander (server) and which ones are the Drones (clients). The Server..Client names may be reversed from normal use here, i dont know, thats why i named them Commander and Drones. Usually this is easily determined by the newest computer being the Commander and the others becoming Drones. It is advised that the Commander have a 3D graphics card set to 32 bit color. The Commander Computer will run VR GIS. Due to the importance of the Commander and the possibility of connection interruptions during multi-tasking, it is suggested that the Commander not perform critical tasks. Drone computers will do the Tasks.

2.2. For VR GIS to work (efficiently), all Drones must run .. access data from the same files on the Commander. We'll do this by mapping the Commander VR GIS drive as the same drive to all Drones, including the Commander. Start by sharing your Commander VR GIS drive.

2.3. Map the shared drive as the same drive letter on the Commander and Drones. I chose the W drive. (I use Z for the CD Rom... As drive letters are assigned from A,B,C,D,... it leaves room for auto-fill use and allows the drive letters to become 'static'.. not changing... Hard drives will normally be assigned letters per their order of linking into the network.)

Op 1. Operating Drones by Remote Control to perform individual tasks.
Start VrRcDrone on a different computer and Press the Connect button.
Start VR GIS on the Commander computer and Select RC from the Tools Menu
Set Drone IP Address and Select Connect to Drone from Menu.
The Drone computer screen is visible ... use the mouse to Remotely Control the Drone

Op 2. Tasking Drones to perform tasks.
Start VrTaskDrone on a different computer.
Select which Tasks are to be available from list on the left.. they will appear on the list on the right. Press the Connect button.
Start VR GIS on the Commander computer and Select Task from the Tools Menu
Set Drone IP Address and Select Connect to Drone using the Button
Once connected available tasks can be selected from Drop Down list.
Change Priority or get updates on progress using the Command List

Op 3. Running a 3D Viewer

3.1. Launch VR GIS on the Commander and Select View from the Tools Menu
Set Drone IP Address and Select Connect to Drone using the Button
??Add the following Options to the Config page and Press the Set button. The IP address entered should match (be) the IP address of the Commander.??

3.2. While we're about it, let's change the Paths so they point to the new drive we just mapped on the server. In this example, I changed my drive letter to W. These changes will not be saved to the project file unless you have a project loaded, so load one, make the changes, save it, and quit.

3.3. Start VR GIS again, load the project, and confirm that the values have 'stuck'.

3.4. On each of the Drones, open the VR GIS folder on the newly mapped W drive and start VR GIS. Since we're using the Commander project file and the Drones VR GIS drive is mapped the same as the Commander, you shouldn't get any paths warnings. The ?render? message should be the only announcement you get.

3.5. Opening the Status Log should confirm what you already know.

3.6. Just to be sure, check the Preferences settings.

3.7. Launch VR GIS on the Commander computer. The ?Resources? page is where we add Drones network identification. Enter the first Drones IP address in the Find Drones box and click OK. If there's anything in the DNS Suffix box, delete it. Add the remaining IP addresses of any other Drones available.

3.8. Your Drones IPs will be listed in the Available Drones window. Use the Add Drones button to add them to the Drones Used window. 12. This would be a good time to Save the Drones List so you don't have to enter them again next time.

3.9. Go to the ?Render? File page and Browse for the project you want to render.

3.10. Add Project. ?? Dunno, this should be done per project.. with entered data being saved and loaded per project

3.11. Go to the Commander Info page and Press Start Render (Project) to start the Drones rendering (Project). Messages will confirm that the Drones have been found, project loaded, and frame rendering Project started.

3.12. Status Logs on the Drones will log rendering operations in progress and the Render Control window will pop up with its own information and progress.

3.13. The Commander Render File page will show rendering Project progress for all Drones.