DICE PACKS BUNDLE
  1. #1
    Octavious's Avatar
    Join Date
    Oct 2015
    Location
    El Reno Oklahoma Central Time Zone
    Posts
    249

    Fantasy Grounds map textures and memory limits

    Hi, I have read somewhere in this forum that the maximum size map is 2048 X 2048 and if too many textures are shared with players that FG memory will cap at some point..

    My question is... if that is so.. then does FG release its allocated memory block for a texture if it is unshared after it was shared ?

    thanx for any reply .


    *************** The only constant in the universe is change. *****************

  2. #2
    LordEntrails's Avatar
    Join Date
    May 2015
    Location
    -7 UTC
    Posts
    17,534
    Blog Entries
    9
    2048x2048 is the recommended limit. You can actually go much higher than this if you only have a single image shared. Because of the way images are loaded by the client, all shared images are in memory so it is really the sum total of all shared images that impact the process size limit.

    I'm not sure if the memory is released when the image is unshared, or if it is just not used the next time the player client launches. You should be able to easily tell by watching the process size of a player client and then unshare a large image.

    Problems? See; How to Report Issues, Bugs & Problems
    On Licensing & Distributing Community Content
    Community Contributions: Gemstones, 5E Quick Ref Decal, Adventure Module Creation, Dungeon Trinkets, Balance Disturbed, Dungeon Room Descriptions
    Note, I am not a SmiteWorks employee or representative, I'm just a user like you.

  3. #3

    Join Date
    Jun 2013
    Location
    Isanti, MN
    Posts
    2,922
    Quote Originally Posted by LordEntrails View Post
    I'm not sure if the memory is released when the image is unshared, or if it is just not used the next time the player client launches. You should be able to easily tell by watching the process size of a player client and then unshare a large image.
    Most OSs, including the major 3 supported by FG, do not release memory when it is freed - they just mark it as available for the process it was assigned to, and future memory requests from that process are satisfied from the "freed" memory first before allocating more from the system pool. It's not returned to the system pool until the process ends. This is a limitation of older CPUs on which the OSs are based which has been carried forward for backward compatibility; besides it's more efficient - you do not make a new system call just because memory is freed, and it also usually eliminates a future system call for a memory allocation the next time memory is requested (the process already has memory available).

Thread Information

Users Browsing this Thread

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

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
5E Character Create Playlist

Log in

Log in