Chaosforge Forum

  • March 26, 2019, 07:10
  • Welcome, Guest
Please login or register.



Login with username, password and session length
Pages: [1]

Author Topic: Steam Link Hardware and Other Streaming Device Bug?  (Read 194 times)

ThePoliticalGaymer

  • Private
  • *
  • Offline Offline
  • Posts: 1
  • Lost Soul
    • View Profile
Steam Link Hardware and Other Streaming Device Bug?
« on: February 12, 2019, 11:19 »

Bug Severity:  C Grade, hardware compatibility

Frequency:  100%

Description:  Using the Steam Link hardware wireless/wired streaming device, and streaming to a 55' HD TV, when the user launches Jupiter Hell, the screen remains unchanged and the game's title screen music plays.

Note:  This bug was only verified on Steam Link Hardware and not on any others, such as nVidia Shield as one example.

Additional Note:  It is recommended, as most gamers are aging, and their eye sight requiring larger screen to see text and gameplay, that this issue be addressed.
Logged

Kornel Kisielewicz

  • God Hand
  • Apostle
  • *
  • *
  • Offline Offline
  • Posts: 4406
    • View Profile
    • http://chaosforge.org/
Re: Steam Link Hardware and Other Streaming Device Bug?
« Reply #1 on: February 12, 2019, 11:38 »

Unfortunately I don't have access to Steam Link, nor do not know anybody who does, so I cannot reproduce.

OTOH, we will be completely changing the rendering backend next major version, so maybe it will work then!
Logged
at your service,
Kornel Kisielewicz

Roland LaGoy

  • Lead Composer & Sound Designer
  • DevTeam
  • Sergeant
  • *
  • *
  • Offline Offline
  • Posts: 68
  • The Howling Of God
    • View Profile
    • Bandcamp (Downloadable OSTS)
Re: Steam Link Hardware and Other Streaming Device Bug?
« Reply #2 on: February 13, 2019, 08:41 »

Ok, hey! I own a Steam Link and just tested Jupiter Hell on it going from a desktop pc to the Steam Link (wired) to a (45'' HD) television. Annnnd yeah, the main menu is frozen on the television :/ , but the game is running fine on the host PC. Hopefully, as brought up, the next major version will resolve said issue. *fingers crossed* :)
Logged
Pages: [1]