AW: [CF-Devel] cfclient issues

[crossfire-devel-admin at archives.real-time.com]

>
     
      >
     
     >
     
      > - When large parts of the map view change (like when applying an
     
     >
     
      >   exit, or casting dimesion door) there are display errors for a short
     
     >
     
      >   moment. Some tiles go black/white for a split second, then return
     
     >
     
      >   to normal. That's not terrible, but it didn't happen in older
     
     >
     
      versions.
     
     >
     
     
     
This is a latency effect.

This happens because the the mapscroll cmd and the map cmd with the
map data are 2 different commands.

And it can come in more as one mapscroll cmd before a map cmd comes.
In the time between some scrolls, if there are big areas to update or simple
lag, the scrolled map is drawn without map data - thats then the black/
white areas. After a short blink, they return to normal - thats when
the map command comes in.

I used for the dxclient & sdlclient the same base source, and there
was the effect too.

You can remove this easily when you catch the mascroll command. Instead
of scrolling the map, set a static counter. Then, when the map command comes
in, scroll the map with this counters at the start of the map command. So
it is sure that there are no unfilled map parts.

BTW, there is a same latency effect with the delinv command and the item
command,
for example for the look window.

Even the delinv is send at the top of the item command, you will notice when
you move faster over maps, that sometimes the look window flickers and/or is
late updated.

Thats too, because the delinv command comes as own package. Lag and other
latency
effects can invoke visible effects on client side.

Also here, i included the delinv inside the item command.



_______________________________________________
crossfire-devel mailing list
     
     crossfire-devel at lists.real-time.com
     
     
     https://mailman.real-time.com/mailman/listinfo/crossfire-devel