Reply to thread

Message

<blockquote data-quote="gibman" data-source="post: 299913" data-attributes="member: 25430">The current internal poll for keeping this feature stands at 4:1 (the '1' being myself) in favour of ditching the whole thing.Im not sure if I am willing to make unofficial builds each week to support this thing.I am thinking most team members are not using this feature at all (ex. running all at 50hz or similar).As long as the whole thing is default disabled I personally don't see any dangers with this being included into SVN.New features in MP1 are looked down upon a bit.btw.I had the &quot;win32 API&quot; way of changing the RR working.[DllImport(&quot;user32.dll&quot;)]public static extern int ChangeDisplaySettings(ref DEVMODE1 devMode, int flags);This kills the need the for nvidia/ATI cmd lines from those not using pstrip.It still does a device reset like it normally would when changing RR within windows./gibman</blockquote>

[QUOTE="gibman, post: 299913, member: 25430"] The current internal poll for keeping this feature stands at 4:1 (the '1' being myself) in favour of ditching the whole thing. Im not sure if I am willing to make unofficial builds each week to support this thing. I am thinking most team members are not using this feature at all (ex. running all at 50hz or similar). As long as the whole thing is default disabled I personally don't see any dangers with this being included into SVN. New features in MP1 are looked down upon a bit. btw. I had the "win32 API" way of changing the RR working. [DllImport("user32.dll")] public static extern int ChangeDisplaySettings(ref DEVMODE1 devMode, int flags); This kills the need the for nvidia/ATI cmd lines from those not using pstrip. It still does a device reset like it normally would when changing RR within windows. /gibman [/QUOTE]

Verification