badjware / aws-cloud-gaming Goto Github PK

Once the gpu driver is installed, there is a second display that appears in windows. We should remove one of them to only have one appear.

@KetchupBomb, yours seems to be the the most developed fork since then (in terms of number of commits and most recently updated, see https://useful-forks.github.io/?repo=badjware/aws-cloud-gaming). This issue could serve as the primary discoverability mechanism. Are you interested in maintaining your fork for other users? If so, consider responding positively here and opening up the issues section on your fork.

See #13.

Assignees:
Labels:

Simple problem with a simple fix: terraform fmt

Assignees:
Labels:

Hashicorp publishes an official http Provider which can perform HTTP requests, removing the implicit curl dependency.

Northern California (us-west-1) doesn't have an "a" Availability Zone identifier:

$ aws ec2 describe-availability-zones | jq -r .AvailabilityZones[].ZoneName
us-west-1b
us-west-1c

This can cause an error when the module randomly picks "a" from the default list of ["a", "b"].

Assignees:
Labels:

Looks like the TeamMachineSetup scheduled task causes your Parsec account to get logged out on every reboot. This happens because it checks if the instance has any user data configured and if so, attempts to auto-login to a Parsec teams account. Because your guide uses instance user data for auto-configuration, this behavior is triggered (and since no teams configuration is present, it attempts to log in with an invalid account).

Disabling the scheduled task fixes this issue for me (but there is probably a better way too).

The code block to download the licensed Nvidia driver:

This logic ought to inspect the file(s) found when listing the Bucket contents, rather than assuming the file type.

Currently, only the drivers for g4 instance type are downloaded and installed. g2 and g3 instances requires different drivers.

https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/install-nvidia-driver.html