support@vu.city    0808 168 3931 - Monday to Friday, 9am - 5:30pm GMT
VU.CITY Website    Log in
Search / ask a question...  

Installation, network, and security setup

Download components

VU.CITY Desktop is comprised of a light-weight app (~500MB) and a large 3D model/data directory (London, for example, is ~20GB). To download the app installer, log into the online dashboard, and click the download link in the top right corner. The 3D model cannot be downloaded directly, rather it is downloaded and managed by the VU.CITY app.

After successfully launching for the first time, VU.CITY will create a directory at C:\VUCITY and attempt to download the 3D model into this directory in the form of in-app updates. Please do not skip these updates the first time you log in, as you will need to download all of them for the app to function normally and the 3D model to be complete. This directory can be relocated to enable sharing assets between multiple users over a network, however you will need to edit VU.CITY's global config file (detailed below) for the app to know where to find the directory. If VU.CITY cannot find a directory at the location specified in the global config file, it will create a new directory at C:\VUCITY and ask you to download all updates again.

Directories

The VU.CITY executable is installed to C:\Program Files\VUCITY\VersionNumber\

VU.CITY's main directory (for 3D assets, data layers, metadata etc) is C:\VUCITY

Tools within VU.CITY will store user data such as screenshots in C:\Users\UserName\Documents\VU.CITY

VU.CITY will store logs in C:\Users\UserName\AppData\LocalLow\VUCITY

If your corporate software environment uses software restriction policies (SRPs) or group policies that restrict app behaviour, please ensure VU.CITY has the appropriate access to the above locations, else the app may fail to launch or otherwise function correctly. While you can change the location of the main directory, do not attempt to move the executable or any of the surrounding files/folders.

Network firewalls

If your network environment restricts outgoing traffic, please note VU.CITY accesses various IP addresses from the following domains:

  • *.unity.com/
  • *.vu.city/
  • *.googleapis.com/

Due to the nature of cloud computing, the individual IP addresses returned by these name servers will change over time. This means a static list of IP addresses cannot be guaranteed. If your security setup requires static IP addresses, we will do our best to keep the following list up-to-date as and when we find that IP addresses change:

Unity:

  • 35.186.231.177
  • 35.186.194.186

VU.CITY:

  • 35.246.97.91
  • 35.197.208.210
  • 35.197.217.44
  • 35.189.82.145
Google cloud services:

  • 216.58.192.0 - 216.58.223.255

Note VU.CITY initially makes DNS queries via port 53 to identify which IP address can be used in the current session, following which all subsequent requests are made via port 443 (HTTPS). If the app attempts to contact any IP addresses not listed above, please let us know.

HTTPS inspection

Inspecting HTTPS traffic between the VU.CITY app, and Google's Cloud infrastructure is a known cause for intermittent and lost connections with VU.CITY Drive. This can prevent users from saving and loading their work, so we recommend your security setup does not involve HTTPS inspection.

Proxy servers

VU.CITY can work behind some proxy servers (the more transparent the proxy, the more likely it will work), however it is unable to read .PAC files. If therefore your setup involves the use of a .PAC file, you will need to edit your environment settings to give VU.CITY a gateway out. To do this, right-click the Windows start button, then choose System. In the System Settings, choose Advanced System Settings, then click on the Environment Variables button. Inside here, add a user variable as follows:

Name: HTTPS_proxy
Value: http://proxy-ip:proxy-port

NOTE: replace 'proxy-ip' with the actual IP of your proxy, and replace 'proxy-port' with the relevant port number.

If your proxy address contains a username, remember to substitute the '@' symbol with %40. So the formatting of the Value field would be http://username:password%40proxy-ip:proxy-port

Third party security software

Some third party security packages (CyberArk, Sophos UTM, 6 Degrees etc) screen apps to verify their trustworthiness before allowing them to launch and function normally. To reduce the chances of security software like this blocking VU.CITY, we code-sign our app.

If you have followed all of the above regarding IP addresses, proxy servers, and SRPs, however you are still unable to launch or sign into the VU.CITY app, it may be that your security software is blocking VU.CITY from launching or accessing your network. In this scenario, you will need to configure your security software to trust VU.CITY, or if that option isn't available, escalate it to your security software provider.

Alternatively, use VU.CITY Cloud.

Updating the VU.CITY app

VU.CITY Cloud is always up to date.

Updates to the VU.CITY desktop app require that you download a new installer from the online dashboard. If you are managing multiple installations of VU.CITY, the installer will need to be run on each computer individually.

If you are using a shared network asset directory, updating the VU.CITY desktop app will require some additional steps to ensure your shared directory continues to work as expected.




Privacy Policy  |  Cookie Policy
© 2022 All rights reserved VU.CITY Limited