Emulator Issues #7568: On Linux, when Render to Main Window is disabled, nothing is rendered to the screen. - Emulator - Dolphin bug tracker

Issue template

Template list

Template for note

Template list

Actions

Copy link

Emulator Issues #7568

closed

On Linux, when Render to Main Window is disabled, nothing is rendered to the screen.

Added by archshift over 9 years ago.

Status:

Fixed

Priority:

Urgent

Assignee:

Lioncash

% Done:

Operating system:

N/A

Issue type:

Bug

Milestone:

Regression:

Relates to usability:

Relates to performance:

Easy:

Relates to maintainability:

Regression start:

Fixed in:

Description

This affects all games on Linux, and was first noted with this commit. Nothing is rendered to the screen; it remains black although the emulation is running (sound can be heard).

A workaround can be achieved by changing the screen size in any way, including toggling fullscreen.

History
Notes
Property changes

Actions

Copy link

Updated by MayImilae over 9 years ago

Priority set to Urgent
Operating system N/A added

The commit in question was merged into master from PR#740 in 4.0-2484 -> https://dolphin-emu.org/download/dev/e266635f404bd59bb9d93ad34492ea33d236ae6a/

Needs confirmation, I don't have linux so, someone else can accept it.

Actions

Copy link

Updated by florian98.rg over 9 years ago

Can confirm. Happens on my Linux Mint installation using a HD7970

Actions

Copy link

Updated by glennricster over 9 years ago

I can confirm this as well running Ubuntu 14.04.

Actions

Copy link

Updated by skidau over 9 years ago

Status changed from New to Accepted

Actions

Copy link

Updated by Anonymous over 9 years ago

Is this just an issue to track things that were already fixed in PRs?
https://github.com/dolphin-emu/dolphin/pull/789

maybe some of armada's PRs?
If so, why?

Actions

Copy link

Updated by archshift over 9 years ago

This issue has nothing to do with armada's PR (or it shouldn't). That PR can't be accepted right now (it's waiting on Jasper's branch) so this issue should be used to keep track of it as well as let users know that we've acknowledged the problem.

Actions

Copy link

Updated by MayImilae over 9 years ago

Even if something is fixed in a PR, the issue report should remain until it's fixed in master. That's what the "FixedInPR" tag is for, after all.

Actions

Copy link

Updated by archshift over 9 years ago

To clarify, by "that PR", I meant #789.

Actions

Copy link

#10

Updated by mdeguzis over 9 years ago

This affects my RetroRig project as well (https://github.com/ProfessorKaos64/RetroRig/issues/88). Thank you for accepting the issue. Render to main window works for now, but hopefully this is fixed soon.

Actions

Copy link

#11

Updated by kodiacktech over 9 years ago

I'm unsure if this is related to this issue, but after changing the render window and having an area that should have black borders (i.e. going 16:9 -> 4:3) seems to cause graphics corruption. As an example, I started SSBM with 16:9 forced, then toggled to 4:3. You'll notice that there's a bunch of broken graphics where there should be black borders.

http://i.imgur.com/7ZwwuJg.png

Linux Mint w/ kernel 3.16
Radeon R9 290
fglrx-updates (Catalyst 14.6 Beta)

Actions

Copy link

#12

Updated by archshift over 9 years ago

I noticed that too, but can you move that to a new issue? It's possible that it's caused by the same PR, but it is really a completely different problem.

Actions

Copy link

#13