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

Update README.md for 1.6 #10954

Merged
merged 2 commits into from
May 26, 2018
Merged

Update README.md for 1.6 #10954

merged 2 commits into from
May 26, 2018

Conversation

hrydgard
Copy link
Owner

Looks too short, I must have forgotten a lot of things...

@Leopard20
Copy link
Contributor

Leopard20 commented Apr 22, 2018

I assume you could add "Fixing crashes on backend switch".
Or maybe just simplify it to "Lots of crash fixes"!
There was also a memory leak issue that you fixed. There is more but not sure if you want to get into too much detail!

@unknownbrackets
Copy link
Collaborator

Some random thoughts of potential other items (some probably too detailed to include):

-[Unknown]

@Leopard20
Copy link
Contributor

Leopard20 commented Apr 22, 2018

@unknownbrackets
I may have a few ideas where to put the new save state undo feature.

  1. Just simply put it between Load state and Back here:
    screenshot_2018-04-22-20-51-50-599_org ppsspp ppsspp

  2. Another idea is putting it between Back and Delete in savedata manager:
    screenshot_2018-04-22-20-55-57-481_org ppsspp ppsspp

  3. Replace Back with Undo and put an X in the top left or right corner (or maybe ditch it completely, since you can go back by clicking in the empty area)

  4. Or maybe if you feel like making it more user-friendly (and less confusing), you could make a small picture-in-picture (PIP) window in the lower right corner of either of those windows that displays the previously saved state with a text saying "Undo" in the middle of it.

Also make sure you implement a confirmation dialog that says something like "This deletes the current savestate. Are you sure?". Don't want people to accidentally lose their precious savestate!

Another 5th idea that just popped into my head!
5) 3 + when the confirmation dialog pops up, display the previous state and say "Replace current savestate with the previous one?"

If you guys could spare a bit of time it might be a good idea to fully implement this feature for v1.6 (not good leaving sth unfinished, am I right?!)

If you're short on time maybe not do the PIP thing (if you like it) till v1.7.

@unknownbrackets
Copy link
Collaborator

not good leaving sth unfinished

Definitely good to finish things, but this is a dangerous mentality. PPSSPP is still unfinished. It's better to leave things unfinished than try to build Rome in a day. What we have now is already a lot more awesome than 1.5.4.

The train's gotta stop to take new passengers at some point, can't wait until we're at the end of the line for that.

My worry about the UI anyway is awkward and tiny touch areas.

-[Unknown]

@Leopard20
Copy link
Contributor

Leopard20 commented Apr 24, 2018

You're right. Better to do sth right than rush things. I just wanted to share my ideas.

@vnctdj
Copy link
Contributor

vnctdj commented May 10, 2018

@hrydgard I think we should mention my last pull request, it may interest some users like Linux distribution packages maintainers.
Maybe the following:

Added "--version" command line option for SDL and Qt platforms (#11028)

@ghost
Copy link

ghost commented May 11, 2018

I think 1.6.0 is ready 👍😀

@marosis
Copy link

marosis commented May 15, 2018

Yes. I think too!👍

@Leopard20
Copy link
Contributor

Well, 1.6 is gonna be the same as the latest git build. So you can just stay on dev builds and avoid switching builds every time a new stable build comes out (you're probably gonna have to switch to dev again anyway, e.g for issue reporting)

@unknownbrackets
Copy link
Collaborator

Actually 1.6.0 is gonna have a complete PS2/PS3 emulator, a special "superultrashader" that will make 10x render resolution look good in all games and run faster than 1x on even the weakest mobile devices, and a checkbox to download extra RAM and ISO storage space for low-memory devices.

None of this code has been tested or seen by anyone yet, so it's possible that when it first sees the world it will be so buggy that it won't even exist.

All the improvements in git since 1.5.4 were just the prep work for these great features that we decided could be made public. The code name of this update is PPSSPP: The Emperor's New Clothes Edition.

-[Unknown]

@iOS4all
Copy link

iOS4all commented May 16, 2018

Wow it’ll be very nice at least to support ps2 games on this amazing emulator.
We really hope we can get a Nintendo Switch port as well.

Thanks a lot for your efforts.

@Leopard20
Copy link
Contributor

@unknownbrackets
Please also add a PS4 emulator! Maybe even create PS5 while you're at it! 😂

@hrydgard
Copy link
Owner Author

Some people should maybe check their sarcasm detectors :)

Again I'm gonna have a busy weekend but I'll really try to get it out next week...

@Leopard20
Copy link
Contributor

Leopard20 commented May 16, 2018

I hope you don't mean me! Because then you need to check yours!😉

@unknownbrackets
Copy link
Collaborator

Please also add a PS4 emulator! Maybe even create PS5 while you're at it! 😂

Yes, PS5 emulation should take very little time to add. I bet it will run all the PS5 games that have been released to date with very little effort.

-[Unknown]

@Leopard20
Copy link
Contributor

Leopard20 commented May 19, 2018

Yay!!! Thank you! 😂

P.S: I meant create the PS5 console! But given the limited time frame you have, emulation will suffice! LOL

@ghost
Copy link

ghost commented May 19, 2018

Add also PS ViTa please 🙇
hahaha 😂✌

@Leopard20
Copy link
Contributor

Is it just me or is this thread really turning into a joke?!

@hrydgard hrydgard added this to the v1.6.0 milestone May 26, 2018
@hrydgard hrydgard merged commit 29164c4 into master May 26, 2018
@hrydgard hrydgard deleted the readme-1.6 branch May 26, 2018 09:27
@ghost
Copy link

ghost commented May 26, 2018

YES FINALLY!!!
1.6.0 is going to release 🎇🙌🎉

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

Successfully merging this pull request may close these issues.

6 participants