LogoLogo
Quick Links
  • Arcware Cloud
  • Arcware Cloud Platform
    • Getting started with Arcware Cloud
      • Sign up and sign in
      • Select a Plan & Creating your Tenant
      • Creating your Tenant
      • 04. Creating your first project
      • 05. Upload and manage your Unreal packages
      • 06. Setting up your project
      • 07. Preview and share the stream
      • 08. Upgrade your Tenant
      • πŸ‘‘09. Organization
      • πŸ‘‘10. Add-ons
      • 11. Help Center
      • πŸ‘‘12. Customer Support
    • πŸ‘‘Add-ons guide
      • Direct Flow
      • Asset Management
    • Advanced settings
      • 01. AFK Module - User inactivity
      • 02. Max instance run-time
    • Common Arcware Cloud Questions
  • Unreal Engine Setup
    • Set up Pixel Streaming in your own project​
      • 01. Core Settings
        • 01.1. Plugin
        • 01.2. Pixel Streaming Input / Json messages
        • 01.3. Resolution
        • 01.4. Camera Aspect Ratio
        • 01.5. Framerate
        • 01.6. Mouse
        • 01.7. Touch Input Setup for Mobile
        • 01.8. DirectX version
      • 02. Optional Settings
        • 02.1 Touch Controllers
        • 02.2 Playing Media files
    • Using the Arcware Pixel Streaming Template Project
      • Template Overview
      • Getting Started
        • 01. Template download
        • 02. Arcware Blueprints
          • 02.1. Arcware GameMode
          • 02.2. Arcware Player Controller
            • 02.2.1. Sending and Receiving Json messages
            • 02.2.2. Creating and Testing Your Own Events
          • 02.3. Arcware Pawn
            • 02.3.1 Change Movement Mode
            • 02.3.2 Set Collision Channels
            • 02.3.3 Add new camera views
          • 02.4. Arcware HUD
        • 03. Packaging your project
  • ARCWARE FEATURES
    • Screenshot Functionality
      • Frontend Overview
        • Web UI
        • In-Game UI
      • Blueprint overview
  • Web Integration
    • ⬆️PixelStreaming WebSDK
      • Implementing the stream on your app
        • Getting Started
        • Code examples
          • Javascript + HTML
          • React
          • VueJS
          • AngularJS
        • Migration from @arcware/webrtc-plugin
        • Best practices
      • Configuration
      • Interacting with the Stream
        • Stream Container
        • Video Element
        • Customizing the User Interface
        • Handling Dynamic Content
        • Stream Display Customization
      • Interacting with Unreal Engine
      • In depth
        • Ticket destroyed.
        • Events handlers
        • Disconnect
        • ConnectionIdentifier
        • Settings-Menu
        • AFK-module
      • Showcase
    • ⬇️WebRTC Plugin
      • Getting started
      • Props and Types
      • SizeContainer, container and videoRef
      • Enabling the audio
      • Afk-module
      • Interacting with Unreal Engine
      • Example WebRTC Plugin Applications
        • React
        • AngularJS
        • VueJS
        • Plain HTML
Powered by GitBook
LogoLogo

Arcware Cloud Platform

  • Getting started​
  • Add-ons guide
  • Common Arcware Cloud Questions

Unreal Engine Setup

  • Set up Pixel Streaming in your own project​
  • Using the Arcware Pixel Streaming Template Project
  • Common Unreal Engine Questions

Arcware Features

  • Screenshot Functionality

Web Integration

  • PixelStreaming WebSDK
  • WebRTC Plugin

Copyright 2024 - Arcware GmbH

On this page
  • 1. Description
  • 2. Properties
  • 3. Defaults
  1. Arcware Cloud Platform
  2. Advanced settings

01. AFK Module - User inactivity

Arcware Cloud user portal - Advanced Settings

PreviousAdvanced settingsNext02. Max instance run-time

Last updated 1 year ago

1. Description

The AFK (away from keyboard) module is used for controlling the behaviour of user inactivity. It is located in Arcware's WebRTC Player and thus tracked and controlled in the browser.

Nevertheless, there are three locations from where the WebRTC player can source the AFK settings.

  1. Property settings directly in frontend

  2. Project settings on platform

  3. ShareID from platform

If there are no settings in any of the three locations, then no user inactivity is tracked and if someone leaves the stream open in the browser it will continue running until it hits the limit of "maximum instance run-time".

Regardless of the settings of AFK module, if the "maximum instance run-time" kicks in, the session will be forcefully disconnected from the platform side. Please see the section on "maximum instance run-time"

2. Properties

  • Overwrite afk-module (Only for options in project settings and ShareID)

  • Enable timeouts

    • Warn timeout

    • Error timeout

    • Action timeout

The "overwrite afk-module" option governs if the settings made in either project settings or share ID should overwrite the settings made in frontend, regardless if they are event present there or not. Whereas the ShareID would on top overwrite the values set in project settings.

Priority => ShareID Settings -> Project Settings -> Frontend Settings

if none are present, no user inactivity is tracked

The "Enable timeouts" will tell the frontend module if user inactivity should be tracked or not. This way one can forcefully disable / enable tracking of user inactivity on frontend, regardless of all the settings made there. If "Enable timeouts" is set to true, then frontend will track user inactivity in three stages: Warn, Error, Action. The time set always goes on top of the previous stage.

"Warn timeout" is the time of user inactivity until the player shows a message to warn about the inactivity.

"Error timeout" is the time after the warning appeared until an error message is shown for user inactivity

"Action timeout" is the time the error message stays active on the screen and how long finally should be waited for a call to action of the user to interact with the stream to stop the user inactivity. When the action timeout is finally expired, the frontend will close the connection.

The total time from last user Action to closure of the session is the sum in seconds set up in all three stages.

3. Defaults

When working with the WebSDK, no defaults are set for the AFK module. The frontend developer is responsible on their own to set up values.

When previewing the project via the Arcware platform or with a ShareID link, if no custom AFK values are set, then the defaults AFK values are imposed by Arcware. The AFK module is active with following default values:

  • Warn: 600

  • Error: 60

  • Active: 10

Recommendation: Enable the AFK-module in project settings and control the behaviour for user inactivity in accordance with your needs.

AFK properties