PPSSPP 1.7

[Henrik]

What's new in 1.7.0
-------------------
* Fix for insta-crash on Galaxy Note 9, some Xiaomi devices, and the new nVidia Shield (#11441)
* Vertex range culling on most platforms, fixes DTM: Race Driver and similar (#11393)
* Major speed boost in some Gundam and Earth Defense Force games (#10973)
* Fix for issues with post processing shaders in GL 3+ (#11182)
* Fixes to sound output switching on Windows (WASAPI) (#11438)
* Detects DirectInput devices when running (#11461)
* Simple Discord integration (#11307)
* New debugging APIs (#10909)
* Task switching made a lot more robust (fixes GPD XD problems) (#11447)
* Texture decoding optimizations (#11350)
* Tons and tons of miscellaneous bugfixes and compatibility fixes

[Abbanon]

Congratulations to PPSSPP's 1.7 release!

[D-Mac]

Henrik, the Android version can not be downloaded. The other two yes.

Thanks you.

Edit: it works now.

[RoskoDaneworth]

I have a feeling 1.7 has issue with detecting DirectInput devices alongside with Xinput.
Im playing on xbox360 wired controller, plugged via usb-hub, and while ppsspp running both my keyboard and controller with a period of several seconds stop responding, hovering over 1 command, then they "reload" and start working again and then it all repeats. While i wrote this text i barely made it cuz of this issue. If i close ppsspp, everything seems fine.
1.6.3 had absolutely no problems, played 7 hours straight yesterday.

[[Unknown]]

Can you try testing different git builds of PPSSPP to figure out when that happened, and post it on GitHub?

Versions can be found here: http://buildbot.orphis.net/ppsspp/index.php?m=fulllist

The fastest way is to test by halves. v1.6.3-588-g61e38b453 is the same as v1.7, so if you test around ~v1.6.3-294-* then you can cut the possible causes in half. Should take 9 tries or so to zero in on the culprit.

But it's probably that querying DirectInput on your system locks up USB, which is strange, so don't forget to post info about your system and OS version in the GitHub issue.

-[Unknown]

[RoskoDaneworth]

I dont have GitHub, so i ll write here.
Version v1.6.3-559-g5a224d7a2 - work fine, no kb/controller problems
Any version past v1.6.3-560-g52e2e0763 - masssive problems, windows stops reacting to both devices properly, so i have to unplug-plug them (after closing ppsspp) so they work normally. I dont know what was changed in "Windows: Detect DirectInput devices after launch" but it causes massive failure of devices in my pc.

OS: win10 Pro x64 ISO from Microsoft site(https://www.microsoft.com/en-us/software.../windows10 ) Version 1803

[[Unknown]]

Hm, it does ask Windows what devices exist periodically. I'm guessing you have a driver on your system that locks up every time it's asked if it's a DirectInput device and plugged in.

We could either time it and hold off on running it if it takes too long, or maybe add a setting to disable. Many people have reported no issues and are happy they can plug their controller in after starting PPSSPP, but I'm sure you're not the only person with a driver that is slow and bad.

-[Unknown]

[RoskoDaneworth]

Does it have something to do with usb-hub ? I'm usuing it to plug multiple devices as my motherboard has only 4 ports: 2 usb 2.0, 2 usb 3.0 - first two used for mouse and kb, 1 3.0 for external HDD (where emulators and games are stored), and last one for hub, where controller, pentablet and avermedia card plugged.

[TkSilver]

Are you using the avermedia usb card at the same time?
I am not sure (and too lazy to google lookup) the amount of data it is using over the 3.0 interface, but could easily imagine a situation where it is hogging the bandwidth or making frequent enough requests that it could be a part of the issue.

One simple test would be to unhook the pentablet, avermedia card, and controller from the hub. Plug in the avermedia card to the USB 3.0 port by itself and use the hub with the keyboard or mouse and the controller on one of the 2.0 ports since either of those should not come close to saturating a 2.0 interface. If this works then I don't mind sugesting some solutions to you in a seperate thread (to keep this one clean and so others with similar issues can more easily find help in the future) if you want it.

[Henrik]

1.7.1 is now out, with some minor fixes.

[Padoverc]

On android, what's the best way to backup all my saves/dlc/etc? Just copy the psp folder to my SD card?

[[Unknown]]

(10-29-2018 08:46 AM)RoskoDaneworth Wrote:  Does it have something to do with usb-hub ? I'm usuing it to plug multiple devices as my motherboard has only 4 ports: 2 usb 2.0, 2 usb 3.0 - first two used for mouse and kb, 1 3.0 for external HDD (where emulators and games are stored), and last one for hub, where controller, pentablet and avermedia card plugged.

I'm not sure - but try the latest git build (NOT v1.7.1, but v1.7.1-2-gd89e12016 or newer.) It may fix the issue for you. Would be great to hear if it does.

(11-02-2018 12:41 PM)Padoverc Wrote:  On android, what's the best way to backup all my saves/dlc/etc? Just copy the psp folder to my SD card?

Yes, that's all you need to do. Specifically, PSP/SAVEDATA for game saves (same as backing up from a PSP) and PSP/PPSSPP_STATE for save states.

-[Unknown]

[Mugen3x]

I think there's a little bug on 1.7.1 with the savestates..i think
Tried to save my progress in last raven with the savestates and the emulator suddenly crashed for an unknown reason, could someone check that out?

[[Unknown]]

You need to mention what device, etc. If it crashes when creating a save state, it's almost always caused by a device not having enough RAM. We tried to improve this several releases ago (so that it will simply not save state at all in this case, but at least not crash), but it can still crash.

-[Unknown]

[RoskoDaneworth]

(11-02-2018 12:54 PM)[Unknown] Wrote:  I'm not sure - but try the latest git build (NOT v1.7.1, but v1.7.1-2-gd89e12016 or newer.) It may fix the issue for you. Would be great to hear if it does.

Yes, it works. "dinput-slow Windows: Check for devices on Windows events only" did its job, didnt encounter this hovering problem yet. Will have to play more later, to fully reassure it. You are amazing