Friday, March 29, 2024 - 08:03

Horizons: Client 383.12

    Modified by on Thursday, August 6, 2009 - 05:22

    Client Build: 383.12 and 383.13 .. and 383.15

     

    383.12 Download (deprecated by 383.13)

    MD5sum: 8f8f80cc47f0afb32f3ed14307e63764

    SHA1sum: 0303b020a35cda13b179e303164693cd89b9c58a

     

    383.13: Patch to Blight to get this!

    383.13 PDB Download

    MD5sum: 30caf6a9cf505297ae2809cae31f72af

    SHA1sum: b03d3691af886c8e494d49eed234c70f17cb37ac

     

    383.14: Ran off with a .def file and was never seen again!

     

    383.15 Download

    MD5sum: c910c81324a1b845e975c44cdcde6b85

    SHA1sum: 2204bbb04bc01720bdf4051c389fe443b3314366

    383.15 PDB Download

     

    Fixes and Changes

    • Memory leaks in proptree found and fixed.
    • Message decoding no longer triggers an exception and stackwalk.
    • More memory leaks in proptree found and fixed.
    • Memory leaks in saveui found and fixed.
    • Buffer overrun in equipment window when right-clicking an equpped item

    with a very long name found and fixed.

    • Uninitialized buffer in sound manager causing crash when sound is disabled found and fixed.
    • More uninitialized buffers in sound manager found and fixed, may prevent

    future crashes and weird behavior.

    • The client will release the cpu above 60FPS, allowing the CPU to be used for other

    applications or idle down.

    • The number of terrain layers requested at once while downloading terrain has been reduced

    to shorten the client-server lag while downloading new terrain.

    • Dragon flight behavior above the max fly height has been changed to prevent "The Rift Jump".
    • 383.13: UI change to display an item's minimum and maximum level requirements if any.
    • 383.15: Possible crash point fixed: unloading a partially built sector may cause a crash.
    • 383.15: Character position updates are now sent when your character is moving, not every half second.

     

    Issues Known But Not Fixed In This Build

    • Loading terrain while the client window is minimized will crash the client.

     

     

    Issues Discovered During Testing

    • Attempting to selling a plot crashes the client. (fixed in 383.15)
    • The owner biote id for each sector isn't saved properly. The file terrain_info.def will show

    "int ownerID = 0" for almost every sector generated by the 383.x clients.

    (Fixed in 383.15)

    Incorrect build environment caused client to require a version of msvcr8.dll that may not be present on all supported platforms. (Fixed in 383.15)

     

     

     

     

    Regression Tests Passed

     

     

    Note: The purpose of comments added to this page is for feedback for this client build only.

    Comments that do not fit this purpose may be moved or deleted (with no penalty nor ill-will

    towards the author of the comment).

     

    Note 2: This client has gone to Blight as build 383.13.

     

    Note 3: 383.12 had a UI addition and was (will be) released to Blight as build 383.13, hopefully on

    Jul 21. A copy of this client can be obtained (once it is released) by patching to Blight and making

    a copy of the following files:

    • istaria.exe
    • encryption_client_lib.dll
    • pt_lib.dll
    • ptps_lib.dll

     

    Note 4: A zipped up PDB file for 383.13 is available. Download and unzip istaria.pdb to the same

    directory as istaria.exe. When the client crashes, the crash reporter should generate a stack trace

    with more useful information. This PDB file is only for 383.13.

     

    Note 5: Due to the impact of not being able to sell plots with the 383.13 client, a new build (probably 383.14) with the fixes in "Issues discovered during testing" may be pushed directly to Blight in a day or two.

     

    Note 6: 383.15 available for testing. This one should work.

    Timeout issue due to movement update change? Maybe?

    Since testing the 383.15 client, I have noticed that standing still for a long time ends up getting me dropped with an error 91 disconnect.

    I am wondering, if the client is no longer pushing its location every half second, is there any other type of keep-alive message being sent so that the server knows that "yes I'm am still here, just not doing anything. Please don't drop my connection"?

     

    Drev

     

    .

    Was that on Blight or live?

     

    I idled for over 5 hours on Blight. 

     

    .

    Order. It must just be my connection then. If I actually play, I can stay connected for hours (until I run out of memory), but if I idle, it seems to drop me. I haven't timed it, since it happens when I am afk.

    Is an ID 91 a server initiated discon or client side?

     

    Dunno.  I'd have to go

    Dunno. 

    I'd have to go ask.

     

    I do know that I've gotten error 91 disconnects while idling on Chaos with the 383.15 client, but not on Blight.  Hopefully the reason for that difference is in server programming.