Kohmei, I found out why we didn't experience the same bug.
In the end, all N3DS / Gateway users have BOTH bugs.
The 3D fuzzy/interlaced-effect bug:
Switch off 3D completely -> switch off N3DS completely -> switch on N3DS -> launch GW emunand -> enable 3D from there and you'll get the 3D fuzzy/interlaced bug you report in your post #16.
I'm getting the 2D <> 3D brightness bug because I start the chain with 3D enabled before launching emunand:
Switch on 3D -> switch off N3DS completely -> switch on N3DS -> launch GW emunand -> if at this point you switch off 3D (back to 2D), you'll get the Brightness reduced bug (brightness of top screen is lower than bottom screen). If you close/reopen the screen at this point (standby), the brightness of the top screen gets back to normal (matching the bottom screen).
In both cases, putting the N3DS in standby for a sec solves the issues. Still wished GW fixed that proper.
In the end, all N3DS / Gateway users have BOTH bugs.
The 3D fuzzy/interlaced-effect bug:
Switch off 3D completely -> switch off N3DS completely -> switch on N3DS -> launch GW emunand -> enable 3D from there and you'll get the 3D fuzzy/interlaced bug you report in your post #16.
I'm getting the 2D <> 3D brightness bug because I start the chain with 3D enabled before launching emunand:
Switch on 3D -> switch off N3DS completely -> switch on N3DS -> launch GW emunand -> if at this point you switch off 3D (back to 2D), you'll get the Brightness reduced bug (brightness of top screen is lower than bottom screen). If you close/reopen the screen at this point (standby), the brightness of the top screen gets back to normal (matching the bottom screen).
In both cases, putting the N3DS in standby for a sec solves the issues. Still wished GW fixed that proper.
Last edited by TheShadowRunner,