Page history
7 March 2024
28 February 2024
20 February 2024
12 June 2023
10 June 2023
8 May 2023
6 February 2022
2 November 2020
28 March 2020
3 March 2018
16 January 2018
6 December 2016
1 December 2016
19 November 2016
7 September 2016
20 June 2016
26 January 2016
22 November 2015
10 October 2015
Text replacement - " x86" to ""
m−8
Text replacement - " x64" to ""
m−52
Text replacement - "({{VersionCompatibilityVersion\|[^\|]*\|[^\|]*)}}" to "$1|}}"
m+1
10 September 2015
16 June 2015
Text replacement - "(Intel Core i[357]-\d*)k" to "$1K"
mText replacement - "{{Test Entry" to "{{testing/entry"
m+3
12 June 2015
31 May 2015
30 May 2015
28 May 2015
Text replacement - "nVidia" to "NVIDIA"
mText replacement - "(Core i[357]) ([^@-]+)" to "$1-$2"
mText replacement - "(\d+) FPS" to "$1FPS"
m−11
31 March 2014
30 March 2014
29 March 2014
→Tiling Problems
−54
→Tiling Problems
+71
no edit summary
+110
The internal res issue doesn't effect default settings, so shouldn't be listed in config section. Add a problem instead. Also I plan to do some confirmation testing here this weekend.
−192
28 March 2014
→Configuration
+10
this issue does in fact occur, just depends on the size you stretch the window to. it's a rounding difference of one pixel between elements.
+154
Revised description; Purge unconfirmed note (report back post tests if you can't confirm); Concerned that there is no problem related to progressivescan and that it seems odd that progressive scan would impact sound
−343
→Problems
−107
→Configuration
+128
→Testing
+226
→Problems: this issue is intermittent. will have to wait on a repro. prog scan disabled also causes audio issues of a different nature.
−185
Removing "Virtual Wiimote Disconnect". That is normal behavior that occurs even on real wiimotes. Hit Alt-F5 twice to fix it. I'm suspicious of progressive scan, since it sounds like a performance issue, but meh.
−275
→Problems
+459