You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is Kernel or Xorg related, all that I know is that even if the x resolution restriction (box.x2 = 640;) placed in the code is changed to allow for additional resolutions such as 320x240 it doesn't work. As shown below, this is the normal 640x480 display on a NTSC Wii console using the Cube driver:
...and this is a 320x240 display on the same console (switched via xorg.conf).
I later took a snapshot using a desktop utility while using 320x240 and it turned out as expected (resembled the 640x480 image), so it appears that it's only the display driver (either Kernel or Xorg) that has the bug.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is Kernel or Xorg related, all that I know is that even if the x resolution restriction (box.x2 = 640;) placed in the code is changed to allow for additional resolutions such as 320x240 it doesn't work. As shown below, this is the normal 640x480 display on a NTSC Wii console using the Cube driver:
![image1-640x480](https://camo.githubusercontent.com/b5ecf341d0df6f1b59f633f2340936ea80f7d1bf3f585a7fa828e31c274b9657/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f333339373631372f313535353639312f31346363376431652d346537382d313165332d386563372d6131353865663834636332312e706e67)
...and this is a 320x240 display on the same console (switched via xorg.conf).
![image2-320x240](https://camo.githubusercontent.com/521f16dd1ecff5c0ef411cd0bf35ee10695d6d16cf7a2a7a70484d4f982b6f56/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f333339373631372f313535353730342f64303862376266342d346537382d313165332d393865612d3762643933373432353137302e706e67)
I later took a snapshot using a desktop utility while using 320x240 and it turned out as expected (resembled the 640x480 image), so it appears that it's only the display driver (either Kernel or Xorg) that has the bug.
The text was updated successfully, but these errors were encountered: