Another new release of scummvm_mod (pull request to Cpasjuste made).
www.github.com/rsn8887/scummvm/releases
Now it is possible, with R held down or with super small stick movement, to really move the mouse pointer _very_ slowly if needed.
Changelog:
1.07
- Increased resolution of slow analog pointer motion
1.06
- Slow analog ('modifier'+stick) made slower
Yet, another release? You seem to be really engaged with this project atm. Good to see someone beeing that passionate about this great project that brings us Lucasfilm Games, Sierra On-Line and Revolution Software games to our beloved handheld systemNew release vpk here (pull request to Cpasjuste made)
Thanks for all the help @rsn8887 . I don't have a lot of time to develop this days as you may have see but I'll see sev (and you) as soon as I go back to "work".@cpasjuste, can you chat with _sev in the ScummVM channel? He can give you dev access to mainline ScummVM. The vita branch has now been merged. I am setting up a buildbot for official Vita dailies. See my scummvm repo - I did a force push so all the Vita commits are squashed into a single merge. You could use "git branch backup" and then pull the mainline scummvm master to be up to date.
Some changes to the build procedure had to be made to merge with mainline correctly. I detailed it with a few changes to readme-psp2.md.
Basically, it is still possible to just pull the mainline scummvm and do
./configure --host=psp2
make psp2vpk
But vita2d_fbo.h, libvita2d_fbo.a, libvitashaders.a and all the shader headers have to be installed in the $VITASDK/arm-.../lib and .../include directories for it to work.
That's a good news, this should give a great frame boost. Good find once again@cpasjuste: It's been a pleasure to contribute.
BTW: Do you remember what was the crash you experienced when you changed optimization -O3, -O2 etc.? How to reproduce? I remember you went back to -O1 because of some crash.
For the scummVM vita nightly buildbot builds, I changed to -Os to get rid of a crash when using "configure --enable-all-engines --host=psp2." There are so many unstable/wip engines added that the file size becomes too big unless I use -Os to reduce it.
I would like to test for your crash so that I am not getting that optimization-related crash you mentioned before.
EDIT: I think I found the culprit.
-O3, -O2 or -Os causes crashes on startup of "Full Throttle" and "The Dig."
Those are fixed by adding the "-fno-optimize-sibling-calls" compiler flag. Then everything seems to work.
The optimization flags "-Os -mlong-calls" are the best because those fix crashes on startup when "--enable-all-engines" is configured. Without -Os, all the statically linked engines increase the executable file size too much and cause a crash on startup. But with -Os the file size is kept small and there's no crash.