![]() |
filenamecache
I was wondering why filenamecache was implemented? Using filenamecache (if it is very large) can be extremely devastating on your framerate for some reason. I was running graal at half screen JUST so I could move until I disabled using filenamecache, now it runs nice and smoothly.
|
Using filenamecache is slowing you down?
Well it is a workaround around the damned slow NTFS which can take minutes to list just a few thousand files. But Graal needs to know where it can find the graphics, so it is remembering the filenames and modification time in FILENAMECACHE.txt and saves it a few second after the download of files has finished. The next time Graal is starting it already knows the location of the files and doesn't need to scan the whole folder. Accessing a file can still take some moments if the NTFS drive is huge and fragmented, can't do something about that though. |
how do you disable it?
Edit: i am having a huge problem where the graphics when i load up graal, they won't show and i deleted the filenamecache and now its taking forever for graal to load up |
Quote:
A few friends of mine have also seen drastic changes in their framerate by disabling it. |
Quote:
|
Quote:
|
According to my cache list, I have 28783 files in my Graal folder that are accessed by FILENAMECACHE.txt
|
| All times are GMT +2. The time now is 03:16 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
Copyright (C) 1998-2019 Toonslab All Rights Reserved.