Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rendering Error In Blade Runner #155

Open
Zombeaver opened this issue Nov 13, 2019 · 12 comments
Open

Rendering Error In Blade Runner #155

Zombeaver opened this issue Nov 13, 2019 · 12 comments

Comments

@Zombeaver
Copy link

Blade Runner seems to have a weird issue where all the areas that should be pure white are instead transparent:

Standalone ScummVM 2.1.0:

Base Profile Screenshot 2019 11 13 - 13 37 28 66

Retroarch ScummVM 2.1.0:

RetroArch Screenshot 2019 11 13 - 13 35 25 69

Standalone ScummVM 2.1.0:

Base Profile Screenshot 2019 11 13 - 13 37 46 13

Retroarch ScummVM 2.1.0:

RetroArch Screenshot 2019 11 13 - 13 36 35 09

Standalone ScummVM 2.1.0:

Base Profile Screenshot 2019 11 13 - 13 37 50 41

Retroarch ScummVM 2.1.0:

RetroArch Screenshot 2019 11 13 - 13 36 41 75

@levonnn
Copy link

levonnn commented Nov 15, 2019

Having the same issue.

@Zombeaver
Copy link
Author

FYI, this is still present after the 2.1.1 update.

@ner00
Copy link

ner00 commented Jan 15, 2021

I came across this issue too, and it's even worse if you want to play with subtitles - they're unreadable:
This issue seems to have been present in all versions. Don't know if it is caused by the core or a fronted interaction.

ScummVM 2.1.0 (Windows standalone)
Blade Runner on ScummVM for Windows

RetroArch v1.9.0 (5e551dd92b) / ScummVM core v2.1.1 (8081781)
Blade Runner on RetroArch

OS: Win10 20H2

@asciibeats
Copy link

@ner00
Copy link

ner00 commented Jul 5, 2022

@asciibeats Thanks. I actually only use the core based on upstream source now. I grew tired of this broken and abandoned core from libretro.

@asciibeats
Copy link

You mean non-libretro? I have not been willing to go that far, but i understand. Also i should have mentioned that i had to add a line to the Makefile to make it work for me. Hopefully diablodiab's backend will become official and we can go back to up-to-date releases.

@ner00
Copy link

ner00 commented Jul 9, 2022

I'm not sure what you mean by non-libretro.
I'm using the backend with the upstream source to build the core, and it seems to me that you're also doing exactly that, maybe it was me who didn't explain properly.

As for the ls line you mentioned for the makefile, I didn't have that issue, but then again the last time I compiled the core was on the 26th of June, maybe it's an issue introduced since, although I find it very strange. Are you using scummvm's dev docker image to compile the builds or a full-fledged dev environment? I'm using the former.

@asciibeats
Copy link

maybe it was me who didn't explain properly

Na, my mistake. I was too tired to read properly. According to a comment to my pull request the problem was just introduced.

@Zombeaver
Copy link
Author

@asciibeats Thanks. I actually only use the core based on upstream source now. I grew tired of this broken and abandoned core from libretro.

Would either of you care to share the compiled Windows x64 core with the fix? I have experience compiling Retroarch cores but I don't quite understand how to use the backend / how it works based on the description. Sorry, a little out of my depth on this one.

@ner00
Copy link

ner00 commented Jul 13, 2022

Here's a build using the latest sources: scummvm_libretro-win_x64.zip

@Zombeaver
Copy link
Author

Here's a build using the latest sources: scummvm_libretro-win_x64.zip

Thank you so much! Really looking forward to trying this out.

@Zombeaver
Copy link
Author

That seems to be working great @ner00 thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants