| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
HTTP when all objects loading are done.
|
|
As a viewer architect, I would like to understand how fast each of the components of the texture pipeline can run in isolation
|
|
|
|
when the camera is still
|
|
|
|
|
|
(current, requested, full)
|
|
|
|
|
|
|
|
Destroying Frame Rate.
|
|
|
|
|
|
occlusion queries from previous frame are still pending and perform texture decode work.
|
|
|
|
|
|
and SH-2671: sometimes other avatar textures don't load
|
|
Destroying Frame Rate.
|
|
|
|
|
|
stalls in renderer by never using the fixed function pipeline if shaders are available.
|
|
|
|
and beyond: fixed the thread-safe and highest texture resolution flaws in the mesh texture uploading flow.
|
|
|
|
|
|
|
|
LLViewerFetchedTexture::forceToSaveRawImage(int,bool)
|
|
|
|
|
|
|
|
|
|
* Now called 'HeadlessClient' instead of 'DisableRendering'
* Removed most cases where we skipped certain behaviors in the client when in this mode. This gets us closer to a 'true' client, for testing purposes.
|
|
|
|
Viewer attempting to load precached images in file types that are not being used.)
|
|
very slowly
|
|
|
|
|
|
|
|
|
|
|
|
|
|
globals and magic strings, enforce naming conventions
|
|
|
|
|
|
|
|
passed on the command line, fix crash in analysis phase
|
