HP Z620 HP Remote Graphics Software 5.4.7 - Page 130

Auto Launch, Game Mode

Page 130 highlights

aggressive quality reduction. The Minimum update rate is a target. The available bandwidth may be too low to maintain the target rate. Valid settings are 0 to 30 updates per second. Auto Launch On Microsoft Windows beginning with RGS 5.4.0, the RGS Receiver supports file association. The user can create property files with the extension ".rgreceiver" using the same format as the RGS Receiver configuration file. See Setting property values in a configuration file on page 165 for more details. For example, the file "hostname.rgreceiver" could be used for creating a property configuration file for connecting to the system with name "hostname". If the user double clicks or opens a file with the ".rgreceiver" extension, the RGS Receiver will be automatically started and the property file read and applied. Create a folder in the user's home folder to safely store Auto Launch configuration files. See Auto Launch session properties on page 186 for property details. Game Mode Game Mode is a toggle feature accessed via Hotkeys on page 147 introduced in RGS 5.4.0. When operating in normal cursor mode, RGS synchronizes the cursor movements of a Sender to a controlling Receiver by placing the senders cursor at the same absolute coordinates of the receivers cursor. Some applications rely on a relative movement of the cursor to interact with a 3D environment. These applications may programmatically readjust the cursor position after a movement is detected. In the default mode of operation where RGS is moving the cursor to an absolute position, these applications may have erratic behavior or cause a loss of cursor control. Game Mode is an attempt to provide better cursor control for such applications. Game Mode is a toggle on the Receiver to supply the Sender with relative cursor movements. This will enable applications that rely on relative movements to be controlled with RGS. Game Mode is enabled and disabled by pressing the hot key followed by the 'G' key. By default, the key sequence is 'Shift Down, Space Down, Space up, G'. When Game Mode is enabled, the cursor will be locked to the receivers Remote Display Window. The Remote Display Window Toolbar can be enabled, but interacting with the Remote Display Window Toolbar is not possible when Game Mode is enabled. The Receiver is dependent on the Sender for updating the cursor position. Network connections with a high latency may not be suitable for use with Game Mode. The Remote Display Window can be repositioned without leaving Game Mode. When a connection is terminated, Game Mode will be disabled. RGS may not be suitable for full screen games. The techniques used by games to quickly draw to the screen will often prevent RGS from being able to extract the contents of the remote frame buffer for display. This is often seen as partially rendered scene or a completely scrambled scene. A game that works in a windowed mode may be able to be controlled when Game Mode is enabled. However, the extremely high frame rates and low latencies required to successfully operate some games are not possible with the current RGS protocol. See Application support on page 14 for the official description of supported applications. 114 Chapter 6 Advanced capabilities

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247

aggressive quality reduction. The
Minimum update rate
is a target. The available
bandwidth may be too low to maintain the target rate. Valid settings are 0 to 30 updates per
second.
Auto Launch
On Microsoft Windows beginning with RGS 5.4.0, the RGS Receiver supports file association. The user
can create property files with the extension ".rgreceiver" using the same format as the RGS Receiver
configuration file. See
Setting property values in a configuration file
on page
165
for more details. For
example, the file "hostname.rgreceiver" could be used for creating a property configuration file for
connecting to the system with name "hostname". If the user double clicks or opens a file with the
".rgreceiver" extension, the RGS Receiver will be automatically started and the property file read and
applied. Create a folder in the user's home folder to safely store Auto Launch configuration files. See
Auto Launch session properties
on page
186
for property details.
Game Mode
Game Mode
is a toggle feature accessed via
Hotkeys
on page
147
introduced in RGS 5.4.0.
When operating in normal cursor mode, RGS synchronizes the cursor movements of a Sender to a
controlling Receiver by placing the senders cursor at the same absolute coordinates of the receivers
cursor. Some applications rely on a relative movement of the cursor to interact with a 3D environment.
These applications may programmatically readjust the cursor position after a movement is detected. In
the default mode of operation where RGS is moving the cursor to an absolute position, these
applications may have erratic behavior or cause a loss of cursor control. Game Mode is an attempt to
provide better cursor control for such applications.
Game Mode is a toggle on the Receiver to supply the Sender with relative cursor movements. This will
enable applications that rely on relative movements to be controlled with RGS. Game Mode is enabled
and disabled by pressing the hot key followed by the ‘G’ key. By default, the key sequence is ‘Shift
Down, Space Down, Space up, G’.
When Game Mode is enabled, the cursor will be locked to the receivers Remote Display Window. The
Remote Display Window Toolbar can be enabled, but interacting with the Remote Display Window
Toolbar is not possible when Game Mode is enabled. The Receiver is dependent on the Sender for
updating the cursor position. Network connections with a high latency may not be suitable for use with
Game Mode. The Remote Display Window can be repositioned without leaving Game Mode. When a
connection is terminated, Game Mode will be disabled.
RGS may not be suitable for full screen games. The techniques used by games to quickly draw to the
screen will often prevent RGS from being able to extract the contents of the remote frame buffer for
display. This is often seen as partially rendered scene or a completely scrambled scene. A game that
works in a windowed mode may be able to be controlled when Game Mode is enabled. However, the
extremely high frame rates and low latencies required to successfully operate some games are not
possible with the current RGS protocol. See
Application support
on page
14
for the official description
of supported applications.
114
Chapter 6
Advanced capabilities