View Poll Results: Which single basic server/client function needs to be addressed first?

Voters
92. You may not vote on this poll
  • Lack of fall damage.

    1 1.09%
  • Monster collision detection.

    12 13.04%
  • The spawning system.

    42 45.65%
  • The frame rate.

    29 31.52%
  • Other

    7 7.61%
  • None, engine is fine as it is.

    1 1.09%
Results 1 to 20 of 49

Thread: Room for improovement: BASIC server/client foundation. Which first?

Hybrid View

  1. #1

    Default Re: Room for improovement: BASIC server/client foundation. Which first?

    Quote Originally Posted by Fratricide View Post
    I think its funny that several people still think of the client having a memory leak.. There is no "real" leak. It is only presumed as a leak because the way the client doesn't readily release your memory back to your system. The terrain update fixes most of that because of the way they adjusted the way it utilizes the data. Previously.. it wanted to hold all the graphics data that it was given for your current journey through Istaria. It now enables the client to release data for areas in which you are no longer near. This does 2 things.. it frees up your memory.. but it also requires your HDD to work more when you are trying to port all over the place transporting goods.

    Memory leak it was not.. memory hog.. it was...
    id say you could argue that both ways depending on how you define

    "memory that it doesn't need" you can argue that it doesn't need to store things that you near, but you can also argue that it does in case you want to go back there.

    personally id say that it is probably a bit of both, as I dont think can really justify it "needing" 2+ gig of memory .5-1 gig maybe but 2+ is two much.

    edit: you could argue that it is not a leak because it is not an un intentional use of memory but you could also argue that you wouldn't really intend memory usage to grow to that much

    but i don't really think this thread is intended for the discussion of the techicalities of what exactly constitutes a memory leak or a resource hog
    Last edited by fireblade; September 21st, 2007 at 04:22 PM. Reason: missed something

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •