60 fps

[Cookie]

Greg turn off the OGL tripple buffering! That makes the flickering...

[b_1_rd]

sorry to resurrect an old thread but a question on 60FPS.

Do you amend the core.ini to read as per the 'read me' file for V2. Particularly the 5/84 5/384 setting?

The following Core.ini parameters are recommended (change them if you know what you are doing):


net_mdm_client_send_every = 5                ; Client packet freq on dialup
net_mdm_client_send_size = 84                ; Client packet size on dialup
net_mdm_server_send_every = 5                 ; Server packet freq on dialup
net_mdm_server_send_size = 384               ; Server packet size on dialup
net_server_port=0                             ; Server port number (0 = default)
net_use_mdm_bandwidth_for_tcp_ip=1            ; Use modem bandwidthfor TCP/IP - 1 = Use net_mdm_ settings *

The reason for using send_every = 5 instead of the commonly used 3 is that networking code is also speeded up. Send_every = 3 means sending data every third frame (12 times per second in original GPL). Using send_every = 5 means sending data every fifth frame, which is again 12 times per second when using the 60 fps patch. Send_size parameters are not affected by the 60 fps patch, so they can be chosen as before.

[DLogan]

sorry to resurrect an old thread but a question on 60FPS.

Do you amend the core.ini to read as per the 'read me' file for V2. Particularly the 5/84 5/384 setting?...

No need to adjust the timing, unless you're serving*. All clients are forced to use what's set in the server's core.ini.

*It's optional even then. You can still use 3/84 3/384 (or even 2/ or 1/); the only difference is that the updates get sent more often (and .rpy files will be larger, so make sure you set your replayMemoryOverride value to something appropriate, I use 128000). Using 5/ timings at 60 fps gives the same update frequency (and .rpy size) as 3/ at 36fps (12 times a second).

[b_1_rd]

Great, thanks for the reply