[opensource-dev] Slowdowns with Viewer 2.5.x for Linux (getting too many data?)
It seems that Viewer 2.5.x for Linux (both development builds and the official one that got released yesterday) don't run smoothly on my system the same way Viewer 2.4 did. Same setup, same settings, still very noticeable performances differences. Looking at Statistics bar (and the way things render in-world), it looks like feel that I'm getting too many data when entering new locations, this clogs / slows down the viewer for a few dozens of seconds. My Network/Bandwidth and Draw distance settings are default, or even less aggressive. My system is quite powerful and I usually don't get this sort of slowdowns. I still have to get more details about this. In the meantime, it would help me a lot if I could get some pointers to known existing PJIRA issues that may relate to this. Opensource Obscure http://twitter.com/oobscure - http://opensourceobscure.com/lol ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
Re: [opensource-dev] Slowdowns with Viewer 2.5.x for Linux (getting too many data?)
Could this be related to recent server changes in the interest list, or does this not happen to you on an older viewer? http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/11#11.02.01.220158 ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
Re: [opensource-dev] Slowdowns with Viewer 2.5.x for Linux (getting too many data?)
If the viewer freezes for a few seconds ever time it loads a texture then it's probably STORM-809. ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
[opensource-dev] PO Test build
Hi, Here's is a test build: http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/merov_viewer-development-import/rev/221041/index.html Containing merges of the following: * STORM-357 : Gestures button is in the pressed state after drag-n-drop but gestures list isn't visible * STORM-680 : Avaline callers are added to the Recent list * STORM-939 : Opening multiple inventory floaters causes viewer to lag or even crash * STORM-974 : UI button alignment issues in Landmark panel, About Land window, and Hardware Settings window * STORM-979 : selection outline from inventory bottom panel buttons is cut at the left side when clicked. * STORM-980 : Appearance panel / Wear button is too wide * STORM-981 : CMAKE_EXE_LINKER_FLAGS not honored when linking the viewer binary if -DLL_TESTS:BOOL=ON Please report issues in the JIRA if any. Thanks for testing. Cheers, - Merov ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
[opensource-dev] Review Request: open-2 (improved progress messages during dependency checks) and open-31 (more standardized short form option switches)
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/150/ --- Review request for Viewer. Summary --- I combined open-31 into this because that change is so small and simple that it didn't seem worth a separate commit (besides, while testing the rest of this, I really wanted the short form of --verbose). open-31 changes the short form of --version to -V, so that the short form of the more commonly used --verbose can be the lower case -v, and adds -n as a short form for --dry-run (as it is used in many versions of make, and in other commands like scp and rsync). open-2 corrects the problem that (at least in the viewer build) there is a long delay during which there are no progress messages. The delay is the configure step while packages are checked, including possibly downloading, extracting, and installing them. Increasing the logging level with the --verbose or --debug switches did not increase the amount of logging during this phase. The fundamental problem proved to be that the package checks were done in recursively invoked instances of autobuild (I am guessing that the process hierarchy is autobuild->cmake->autobuild, but it could have just been autobuild calling itself directly; this fix should work regardless of the depth of the process tree). The verbosity control options were not passed through to the child processes, and since there could be some other process in between (as cmake above), it seemed more robust (and relies less on correct configuration) to pass the verbosity control to the children through the environment. The default verbosity is now read from the AUTOBUILD_LOGGING environment variable, whose contents can be --debug, --verbose, --quiet, or the one letter forms of any of those options (if the environment variable is not set, then the default value is to log warnings and worse, as before). Any of the options used on the command line override any value from the environment. Regardless of how the verbosity level is established, the environment variable AUTOBUILD_LOGGING is set for all child processes, so that if any of those (directly or indirectly) are another invocation of autobuild, then that recursive child will use the same verbosity level as the parent (unless, of course the recursive invocation uses an explicit option). It is true that this also allows the user to set a default verbosity in the shell environment, and that works, but it wasn't really the motivation for the change and I did not add anything to the documentation about it. With that change made, the options correctly controlled whether or not logging is visible during the package checking phase. However, the resulting messages had an inconsistent level of detail - some operations (such as uninstall) were very verbose, while others (some of which might take significant time) were logged only at high verbosity levels. This led to the addition of a few short log messages at the default 'warning' level (which really has the dual meaning "something that might be a problem" and "something that should be seen at the default logging level") in order to make sure that some message is printed before any potentially long operation (downloads, extracts, installs, and uninstalls). Some other very detailed messages were changed from info to debug levels, as the information they display is really only useful when debugging either a new autobuild configuration or autobuild itself. I think that the combination of these changes makes the default verbosity reasonably informative (no long silences) without being overwhelming. (there is a failure displaying the diff for autobuild.configfile.py because it is a one word change of the logging level for a log message added by one of my other changes that has not yet been applied to the trunk) This addresses bugs open-2 and open-31. Diffs - autobuild/autobuild_main.py UNKNOWN autobuild/autobuild_tool_install.py UNKNOWN autobuild/common.py UNKNOWN autobuild/configfile.py UNKNOWN Diff: http://codereview.secondlife.com/r/150/diff Testing --- Manually verified using configuring and building in viewer-autobuild Thanks, Oz ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
Re: [opensource-dev] Review Request: open-2 (improved progress messages during dependency checks) and open-31 (more standardized short form option switches)
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/150/#review357 --- Ship it! Can this be placed as an hg changeset? I'll say Ship It in hopes a test method is forthcoming. - Nicky On Feb. 12, 2011, 1:13 p.m., Oz Linden wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://codereview.secondlife.com/r/150/ > --- > > (Updated Feb. 12, 2011, 1:13 p.m.) > > > Review request for Viewer. > > > Summary > --- > > I combined open-31 into this because that change is so small and simple that > it didn't seem worth a separate commit (besides, while testing the rest of > this, I really wanted the short form of --verbose). > > open-31 changes the short form of --version to -V, so that the short form of > the more commonly used --verbose can be the lower case -v, and adds -n as a > short form for --dry-run (as it is used in many versions of make, and in > other commands like scp and rsync). > > open-2 corrects the problem that (at least in the viewer build) there is a > long delay during which there are no progress messages. The delay is the > configure step while packages are checked, including possibly downloading, > extracting, and installing them. Increasing the logging level with the > --verbose or --debug switches did not increase the amount of logging during > this phase. > > The fundamental problem proved to be that the package checks were done in > recursively invoked instances of autobuild (I am guessing that the process > hierarchy is autobuild->cmake->autobuild, but it could have just been > autobuild calling itself directly; this fix should work regardless of the > depth of the process tree). The verbosity control options were not passed > through to the child processes, and since there could be some other process > in between (as cmake above), it seemed more robust (and relies less on > correct configuration) to pass the verbosity control to the children through > the environment. > > The default verbosity is now read from the AUTOBUILD_LOGGING environment > variable, whose contents can be --debug, --verbose, --quiet, or the one > letter forms of any of those options (if the environment variable is not set, > then the default value is to log warnings and worse, as before). Any of the > options used on the command line override any value from the environment. > Regardless of how the verbosity level is established, the environment > variable AUTOBUILD_LOGGING is set for all child processes, so that if any of > those (directly or indirectly) are another invocation of autobuild, then that > recursive child will use the same verbosity level as the parent (unless, of > course the recursive invocation uses an explicit option). It is true that > this also allows the user to set a default verbosity in the shell > environment, and that works, but it wasn't really the motivation for the > change and I did not add anything to the documentation about it. > > With that change made, the options correctly controlled whether or not > logging is visible during the package checking phase. However, the resulting > messages had an inconsistent level of detail - some operations (such as > uninstall) were very verbose, while others (some of which might take > significant time) were logged only at high verbosity levels. This led to the > addition of a few short log messages at the default 'warning' level (which > really has the dual meaning "something that might be a problem" and > "something that should be seen at the default logging level") in order to > make sure that some message is printed before any potentially long operation > (downloads, extracts, installs, and uninstalls). Some other very detailed > messages were changed from info to debug levels, as the information they > display is really only useful when debugging either a new autobuild > configuration or autobuild itself. > > I think that the combination of these changes makes the default verbosity > reasonably informative (no long silences) without being overwhelming. > > (there is a failure displaying the diff for autobuild.configfile.py because > it is a one word change of the logging level for a log message added by one > of my other changes that has not yet been applied to the trunk) > > > This addresses bugs open-2 and open-31. > > > Diffs > - > > autobuild/autobuild_main.py UNKNOWN > autobuild/autobuild_tool_install.py UNKNOWN > autobuild/common.py UNKNOWN > autobuild/configfile.py UNKNOWN > > Diff: http://codereview.secondlife.com/r/150/diff > > > Testing > --- > > Manually verified using configuring and building in viewer-autobuild > > > Thanks, > >
[opensource-dev] Forum for ATI, Apple and FBO problem
Hello, Some time ago, I've opened a bug report on Apple website concerning the problem of ATI cards with FBO which stops Mac users to use dynamic shadows. I know they are not officials, but they work quite well with Nvidia cards :). I've received an answer recently asking me for the full System Profiler Report of my machine. I was wondering if accumulating the experiences on that subject would help make the things move faster. So I've set up a forum where mac users wanting to do it could tell their experience with ATI card and join their full System Profiler Report with their experience. I would then put the link to the forum in my bug report. Do you think this could be a good idea ? Bug report : https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/24/wo/KGyze933oURhrNytyxPfAw/5.83.28.0.9 Forum : http://macati.madonie.org/ ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
