2011-06-22, 23:09
CrashX Wrote:Would be nice if it was GUI setting instead of Advanced Settings for now temporarly so that is easier to test it ?
temp to test it before it becomes default
CrashX Wrote:Would be nice if it was GUI setting instead of Advanced Settings for now temporarly so that is easier to test it ?
jacky89 Wrote:I created an advancedsettings.xml file and entered the following text into the file. However, it doesn't do anything on the 06/26/2011 nightly build. Am I missing something? Thanks.
<advancedsettings>
<gui>
<algorithmdirtyregions]2</algorithmdirtyregions>
<visualizedirtyregions>true</visualizedirtyregions/>
</gui>
</advancedsettings>
gabbott Wrote:You have a ] where you need to have a >
pieh Wrote:<visualizedirtyregions>true</visualizedirtyregions/>
should be
<visualizedirtyregions>true</visualizedirtyregions>
Hitcher Wrote:I've been testing it out and the only problem I found so far was the Settings in XeeBo -
http://youtu.be/lGc4LAzKqZU
Sranshaft Wrote:Decided to try out the dirty regions feature and ran into a pretty big problem as can be seen in the screenshot:Sranshaft,
Debug log is here.
To those that didn't have any problem with this feature can I ask you: what build are you running? Could this be a problem with the graphics card? Drivers are up to date, I'm just wondering if this is another ATI vs. nVidia issue.
<visualizedirtyregions>true</visualizedirtyregions>
wyrm Wrote:Sranshaft,
If your issue is the red and green regions its because you are using the codeThis is for skinners to see what dirty regions are being picked up. Set the above to false and you will be using dirty region code without the visualisation.PHP Code:<visualizedirtyregions>true</visualizedirtyregions>
Wyrm (xTV-SAF)
jmarshall Wrote:Make sure you let us know what those issues are