Genvid Forum

Genvid Technologies

Genvid SDK 1.22.1 - Patch

Welcome to Genvid Technologies SDK 1.22.1. This is a bug fix release. See the
previous release notes for more information on the 1.22.0 release.

Minor Changes and Other Fixes

  • [unity] Unity plugin is now compatible with the latest Unity
    2019.3.x version.
  • [unity] Fixed an issue that was logging an error despite
    performing a successful SubmitGameData.
  • [toolbox] Added upgrade notes and a legacy version of the
    ConsulTemplateTool that users can use if they are affected by the
    backward compatibility break of ConsulTemplateTool.

Known Issues

Compose window isn’t available if behind a proxy.

Future versions of Bastion will have a remote server to allow access from
different machines. The current version has limited support for this and is
likely to encounter some problems if the Bastion host lives behind a cluster
firewall (like on a Amazon EC2 machine).

As a workaround, you can create VPN connections to the Bastion machine so the
local IP of the machine is accessible from the client machine.

The application doesn’t work properly after Windows comes back from sleep.

Nomad has some difficulties with sleeping jobs, including itself. This is
unlikely to get fixed in Nomad, but shouldn’t happen in a production
environment. The best workaround at present is to not allow Windows to go to
sleep when you are running the service, or simply to restart the service with
a genvid-bastion reinstall. (Unfortunately, genvid-bastion restart is not
sufficient).

The YouTube stream isn’t properly reset after a gvencode restart.

If you stop and quickly restart the services, the YouTube streaming service
considers it part of the same streaming session. Although this may be
desirable most of the time, this could lead to showing up as the previous
session due to the long latency between the services and the actual view which
can create some delay in the stream. A future version will provide a proper
way to request a new stream. Until then, you can either reset your stream key
from the YouTube dashboard or simply wait a little longer (about 5 minutes
should be enough) before restarting the service.

Audio captures microphone or infinitely loops.

When using the WASAPI audio auto-capture mode, every sound going through the
machine’s default audio-device gets captured. This includes system alerts and
microphone input, as well as your web browser. When test-viewing your game
stream using the same local machine running the game, the game will also
capture its own audio stream with ~10s of latency. This yields some echo with
progressively worse sound quality since it is compressed every time it is
streamed.

You can disable audio in 2 ways:

  • Set settings.encode.input.silent to true in your
    configuration. (The default setting.)
  • Use our raw audio-capture, which is now the default setting in
    Unity.

Standalone player with Firefox not working.

The readable streams must be enabled in Firefox for the standalone player to
work properly. You must set dom.streams.enabled and
javascript.options.streams preferences to true from the about:config
URL.

Auto-cut checkbox state is stored locally only.

In Studio, the state of the auto-cut checkbox in Scene Widget is only stored
in local storage: Clearing the browser cache will also clear user input. Also,
if auto-cut is turned “on” before the Studio session ends, it will be set back
to “off” by default when you start the Studio session again.

Studio can not take inputs of the same control from multiple windows.

If Studio is opened in more than one browser window and inputs are received
from different sources to one control, the final value will then bounce
between the different inputs instead of updating it to the latest one. For
example, in Audio Mixer Widget, if a user changes the slider of Master Gain to
20 db and another user then changes it to 0 db, the slider handle will bounce
between 20 db and 0 db instead of being set to 0 db. Inputs from different
windows to one control is not recommended until we resolve the issue.

Only one application not running with Nomad is supported for the Genvid SDK

If an application using the Genvid SDK is launched without Nomad, a default
session name is assigned to it. This is useful when testing your application
in the Unity engine, Unreal engine or simply booting your application
manually. Currently, the Genvid SDK is unable to support multiple applications
launched this way unless you change the environment variable
GENVID_SESSION_NAME with a unique name. Otherwise, we recommend to use Nomad
to launch your applications to avoid this issue until a fix is integrated into
the Genvid SDK.

Twitch and YouTube Synchronization Advisory

During testing, we’ve found some synchronization issues when broadcasting via
both Twitch and YouTube. See the Twitch and YouTube
sections for details and workarounds for each.

Log definition limitation

If the value is different than stdout and stderr, than specific filenames need
to be unique on the stack (2 jobs cannot have the same log filename, ex:
default.out)

Load tester sample is not functionnal

The current version of the load tester sample is not usable due to errors in
its script which prevent it from running as documented.

Azure reports requested instance size not available

On Azure, we are using a compute instance type Standard_NV6 for the game
machine. For some accounts, only the promo version of this instance type is
available (Standard_NV6_Promo).

When doing the Terraform setup on the Azure module, you may encounter the
error: The requested size for resource ‘XXXX-game-1’ is currently not
available in location ‘XXXX’

As a workaround, you can go to your Terraform Settings page and change the
instance_game_type to Standard_NV6_Promo, then go to Commands page and try
Plan apply -> Apply again.