System Requirements

System Requirements and Settings

   Tips for a successful start

Supported Operating Systems  

* With few exceptions, all functions and tools in TriCAT Spaces are available for Mac users:

 Hardware Requirement

  • Standard computer or laptop: no thin (slim) client
  • Hard disk space: 1,5 GB available hard disk space
  • Main memory: min. 2 GB main memory, ideal: 4 GB and more
  • Processor performance:  2 Ghz Dual-Core CPU
  • Graphics card: min. DirectX9, Intel HD Graphics 2500/3000, recommended: Intel HD Graphics 4600 or NVIDIA Geforce GT 430, AMD Radeon HD 5570
  • Soundcard
  • Mouse
  • Headset

Please take note, that you need a headphone with integrated voice function (microphone) to participate in a session. Other configurations can produce disruptive echoes.

 

Internet Bandwidth

Minimum: DSL 3000
Recommended: DSL 6.000

Note concerning wireless networks: Make sure, that your connection is stable. Otherwise problems with the connection may occur during your session. The application is running with a low bandwidth as well, but then, the quality of the performance and depiction may variate during the session. Some of the features as the Live-Streams may not work.

Firewalls

The Windows Firewall must not block the application. Please click on Grant Access. If you do not use a standard Windows Firewall, click on do not block

Information concerning the setting in restrictive secured networks:

Ports

Either port 80 or preferably port 443 must be enabled for the TCP protocol. You can configure the Proxy-Server in the application.

SSL Certificate Request

The TriCAT Spaces Client makes HTTPS requests to different domains and checks the SSL certificate strictly for validity. For the operation of the application the SSL Inspection must be deactivated in the firewall or the proxy server for requests to the following domains:

*.tricat-spaces.net
*.tricat.net
*.tricat-dns.net

The following activities have to be allowed for the previously mentioned domains:

Updating the Application

  • requires the download of password protected archives and executables

Authenticating the Client with the Server

  • requires usage of a MS Edge User-Agent request header
  • requires usage of self-signed certificates
  • requires pass-through of these certificates via proxy etc. between client and server