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

PPSSPP crashes at startup after choosing Vulkan backend (the GPU supports Vulkan) #8826

Closed
RafaelTrepaUnCarballo opened this Issue Jun 25, 2016 · 13 comments

Comments

Projects
None yet
5 participants
@RafaelTrepaUnCarballo

RafaelTrepaUnCarballo commented Jun 25, 2016

SO: Windows 10 x64
GPU: Nvidia 820M and Intel HD 4600 (I'm using the Nvidia gpu by default)

The drivers and the emulator are updated. Before the driver update which enabled Vulkan support, PPSSPP didn't let me choose Vulkan mode. Now I can choose it, but after that the emulator crashes every time I open it.

@LunaMoo

This comment has been minimized.

Collaborator

LunaMoo commented Jun 26, 2016

Make sure to switch to "Skip buffer effects" rendering mode, Vulkan is still WIP and does not work with buffered rendering.

@RafaelTrepaUnCarballo

This comment has been minimized.

RafaelTrepaUnCarballo commented Jun 26, 2016

That option doesn't fix the bug.

I want to clarify something: This crash happens any time I open PPSSPPWindows64.exe. It's not related with any game, it's the whole ppsspp emulator which crashes at booting.

Of course, I can't change the backend back to OpenGL or DirectX because the emulator crashes before I can see and open the configuration menu.

@unknownbrackets

This comment has been minimized.

Collaborator

unknownbrackets commented Jun 27, 2016

You can change it back in the ini file, or just by renaming away the ini file. It can usually be found in Memstick/SYSTEM/ppsspp.ini.

We may not be handling Vulkan init properly when there are multiple physical devices available. Vulkan exposes this differently than GL does.

-[Unknown]

@RafaelTrepaUnCarballo

This comment has been minimized.

RafaelTrepaUnCarballo commented Jun 27, 2016

So, is Nvidia Optimous and my two GPUs the cause of my crash?

I hope you guys will find a way to make compatible my GPU. Is there a way to send you data about these crashes? Some kind of logs or usage data?

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 12, 2017

How is this now?

@HarlockTheSin

This comment has been minimized.

HarlockTheSin commented Nov 12, 2017

@unknownbrackets

This comment has been minimized.

Collaborator

unknownbrackets commented Nov 12, 2017

Please try the latest git build:
https://buildbot.orphis.net/ppsspp/

We don't go back and modify past releases. What was 1.4.2 will always be 1.4.2. It will always have this bug, forever and ever.

-[Unknown]

@HarlockTheSin

This comment has been minimized.

HarlockTheSin commented Nov 12, 2017

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 12, 2017

Well, at least that's a better outcome... Really not sure, it starts up fine on all my devices that have Vulkan support.

@HarlockTheSin

This comment has been minimized.

HarlockTheSin commented Nov 12, 2017

@hrydgard

This comment has been minimized.

Owner

hrydgard commented Nov 12, 2017

Searching https://vulkan.gpuinfo.org/ , there isn't a single report from an 820M, so maybe nVidia is just quietly not supporting that model .. I'm not sure.

@HarlockTheSin

This comment has been minimized.

HarlockTheSin commented Nov 12, 2017

@RafaelTrepaUnCarballo

This comment has been minimized.

RafaelTrepaUnCarballo commented Nov 12, 2017

I'm pretty sure my 820M don't support Vulkan.There are some contradictory information in internet because it seemed originally Nvidia was going to add OpenGL support to it, but in the end no fermi GPU got Vulkan support. There's nothing PPSSPP can do.

PPSSPP no longer crashes when I select Vulkan, it warns me something is wrong and allows me to change to openGL. It's the right behaviour.

@hrydgard hrydgard closed this Nov 12, 2017

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