Thursday, April 18, 2024 - 07:58

New client!

    Modified by on Saturday, December 4, 2010 - 18:47

    Welcome!

     

    This is the forum for feedback and bug reports for the 384.4 client
    build (and only the 384.4 client build).

     

    Direct link to the build page:  http://bristugo.com/node/1053

     

    Please create a new thread to report or discuss problems if a thread for the problem does not already exist.

     

     

    Happy crashing!

     

    Good news ! :) 

    Good news ! :)

     

    "Sorry for taking so long. :|"

    No major problem, it looks quite nice so far :) Good job ! 

     

    Edit: I just had to clear my world cache, the game was blocked on something like  "Looking game history(1)" 

    Once the chache cleared, perfect ! 

     

    So far it's working very

    So far it's working very nicely! And it's ***BEEP*** faster loading the maps than before!

     

    Only odd thing is, when loading a new area it always shows the number of tiles left then the number goes to 1 and stays like that till it's done. Shouldn't it show some more intermediate countdown?

    <= Vahrokh

     

     

    Update: I am still doing

    Update:

    I am still doing great, only got one crash porting from Dralk to Bristugo (but I had ported several times, might be the memory leak at work).

     

    I noticed the window with FPS, TexMem etc. has TexMem number lacking last digit and the mousehover shown amount is missing the decimal dot (so it looks with 5 digits like 70234MB instead of 702.34MB which is consistent with task manager).

    <= Vahrokh

     

    Soo, patched to blight,

    Soo, patched to blight, copied the rar contents over, went nice and smooth. I like this way of providing the new alpha client.

     

    First thing I noticed I had to do is clear all the world cache of Chaos since waiting 10 mins (and terrainreqqueue was at 0v0q) didnt fix it.

     

    Once cleared it started to download the terrain contents ( as i wasnt in New Trismus) and after a good 5 minutes waiting it showed the world. I have to say the 5 minute load is insane, now it just displays the world (even with loading screen off) once the whole area is loaded. Dont think making a player wait even longer is a solution.

     

    Anyhow, when I decided to go to New Trismus (had to go to a racial town first, ughh had to wait another 5 mins). But once i ported to NT it was fast! Like uhm, 5-10 sec at most. That I like!

     

    Running around a bit there at 40-42 FPS seems nice, however when I decided to turn on my terrain clutter the FPS dropped to 16 which is a lot but it didnt even display the clutter so thats very odd imho.

     

    Also a note that the 384.0 client had, the teleporter windows are messed up - the destinations arent sorted anymore.

     

    *addition to above*   1)

    *addition to above*

     

    1) Just noticed something odd. When 2 players both have the 384.4 client they cant see eachother emotes.

     

    2) When a 384.4 client uses an emote it doesnt show the player name infront of it

     

    3) debug file not in the zip?

     

    Emotes seem to miss the

    Emotes seem to miss the subject.

    IE if I

     

    /em wave I only read: "wave", not Vahrokh waves

     

    Regular client players show the whole emote instead

     

     

    Teleport destinations (I checked those to Scorpion Island) have their names in a different order than the production client. 

     

     

    Porting around should reset TexMem to a low value (I think), instead it keeps building up at each port like there are missing free() somewhere. 

     

     

    I don't know what happens exactly, but recalling to Dralk and porting to Dralk => Bristugo => Mia's edge => recall => Bristugo => Scorpion's bay => recall  reloaded the map tiles for Dralk again.

     

     

    In window mode, when ALT Tabbing from another applications, sometimes the client won't catch any keyboard press any longer. To fix it you need to ALT tab again and maybe click in the other app a while, then ALT tab back to Istaria (Windows 7 64 bit)

     

    I have no idea about how the client works, but in my application I fixed the same behavior by properly calling AttachThreadInput()

     

    <= Vahrokh

     

    In window mode, when ALT

    In window mode, when ALT Tabbing from another applications, sometimes
    the client won't catch any keyboard press any longer. To fix it you need
    to ALT tab again and maybe click in the other app a while, then ALT tab
    back to Istaria (Windows 7 64 bit)

     

     

     

     

    Im having that same issue as Vahrokh has - it been in the client a long time and its quite annoying.

     

    _every_ sort option in the

    _all_  the sort option in the guildwindow doesnt seems to work on each tab (members,calendar,structure)