search

nbcloud / fluorescence

Automatically exported from code.google.com/p/fluorescence
GNU General Public License v3.0
0 stars 0 forks source link

time-out when standing still too long #10

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. log in (obviously)
2. stand around - it doesn't matter what else you do, just don't move
3. after about 30 Seconds a "connection to server lost" appears and you're back 
at login screen

What is the expected output? What do you see instead?
"Connection lost" should ony happen when client doesn't react anymore (due to 
internet connection loss or crash). Right now the idle timer is at about 30 
seconds to 1 minute.

What version of the product are you using? On what operating system? If
this is a performance problem, please also include your PC specs.
Win 7 32-bit, MULs from Arx Obscura, client-release from 01.07.2012

Please provide any additional information below.

Please attach your fluorescence.log file.

Original issue reported on code.google.com by metaj...@gmail.com on 2 Jul 2012 at 7:12

Attachments:

GoogleCodeExporter commented 8 years ago 
I just implemented the ping packet to fix this issue, and send it every 20 
seconds if no other packet was sent. 

It's actually weird - the only reason the OSI client stays alive is because it 
spams an unknown packet 0xBF:0x24 all the time. The actual ping timeout in 
RunUO would be too small for the OSI ping interval...

Anyways, fixed :)

Original comment by spin@fluorescence-client.org on 5 Jul 2012 at 7:58