• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: VWR-2161
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Normal Normal
Assignee: Steve Linden
Reporter: Steve Linden
Votes: 7
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
1. Second Life Viewer - VWR

Change 'Graphics Card Memory' radio buttons to 'Texture Memory' slider

Created: 14/Aug/07 11:52 AM   Updated: 24/Apr/09 04:01 PM
Return to search
Component/s: Graphics
Affects Version/s: 1.18.2.0
Fix Version/s: 1.19.1.4

Issue Links:
Duplicate
 
Relates
 


 Description  « Hide
The "Graphics Card Memory" option disguises the actual usage of the option, which is to calculate how much texture memory is used by the viewer. The viewer makes a calculation based on this value and the amount of system ram available. On some systems this calculation is inaccurate (e.g. running multiple viewers, running multiple monitors, etc). This option should more accurately represent how it is used and should provide more flexibility. Some adjustments to the default calculations may also be in order.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Steve Linden added a comment - 14/Aug/07 12:02 PM
Per VWR-778, systems should be allowed to exceed the texture memory available on the card, e.g. even a 16 MB video card should be able to allocate 64 MB of textures if they wish to trade off performance for visual quality. This tradeoff should be indicated in the preferences.
Also, despite the potential performance issues, minimum default value should probably be 32 MB, even for 16 MB cards (although this is way below the minimum spec for SL, but for those willing to suffer...)

Seg Baphomet added a comment - 14/Aug/07 02:12 PM
I see no solution here, just a restatement of the problem.

You're also confusing two issues. There's two limits at work here, the overall limit for decoded textures cached in RAM, which is what VWR-733 and VWR-788 are concerned with, and the amount of textures actively in use in OpenGL, which is what VWR-914 is concerned with. You seem to be talking about the first issue here, in which case VWR-914 is related but not a dupe of this issue.


Nicholaz Beresford added a comment - 14/Aug/07 03:05 PM

Actutally my recommendation would be to have both ... a setting for the bound textures and one for the RAM texture cache. I have not fully thought it through, but with possible misinterpretation of the graphics card memory and probably other stuff (like running other graphics heavy applications in the background or the Mac problems with the viewer not leaving enough unbound video memory) I'm not sure it is a good idea to do away with the video memory setting.

However, I'd fully applaud a manual configuration for the texture buffer size.


Nicholaz Beresford added a comment - 14/Aug/07 03:10 PM

Oh, btw, I have been asked for settings for video boards with 320 and 640MB memory.

leliel Mirihi added a comment - 18/Aug/07 10:28 AM
i attached a patch to VWR-860 that adds 192, 320, 640, 768, 1024, and 1536

McCabe Maxsted added a comment - 08/Sep/08 02:08 AM
This was fixed some time ago, not sure exactly when. Resolving.