docskellington / pcsx2-1.4.0-rr Goto Github PK

I pulled in the lastest source for LilyPad which seems to have a few "input modes" as well as explicitly mentions pressure sensitivity and clearly has calculations for it. https://github.com/PCSX2/pcsx2/blob/master/plugins/LilyPad/LilyPad.cpp#L414

However I am still only getting flags of 1's and 0's for buttons pressed it seems. I am wondering if it is because I use an Xbox360 controller (to my knowledge not pressure sensitive). If that is the only problem then it would be nice for the TAS emulator to just use whatever the max force is, but like you mentioned, I have no idea how to find where PCSX2 uses the array buffer. The values are thrown on it and then it throws an interrupt and the trail ends there.

I think a potential solution might be to look into the different query options for LilyPad, but if the problem lies in the controller type like I mentioned then I might try reaching out to some of the PCSX2 devs to get some information on how the emulator handles pressure sensitive inputs so the "max force" value can be thrown on the buffer instead.

Hey, just trying to get started and I seem to be running into issues just getting it to build / run on a fresh master/movie branch.

Whenever I try to hit the "Boot from ISO" buttons I hit an access violation from one of the wxWidgets libraries.

I've installed the DirectX SDK, tried VS 2015 and 2017, and even tried installing wxWidgets locally. I'm using the pcsx2-suite.sln file. Was wondering if you had to set something else up that isn't mentioned in the readme or if its a problem unique to my environment that I'll have to figure out.

I've successfully merged the latest changes here into 1.5 https://github.com/xTVaser/pcsx2-rr/tree/existing-rr You can make a fork of pcsx2 and commit the changes, or I can add you as a collaborator, whatever you want to do, let me know. I feel like you should probably own the fork as you have done more than me :).

As I was going through the merge I marked issues with comments that begin with // TODO TAS, I havnt tested full functionality, only confirmed that movies from save-states still record and play properly, havn't tried from power-on yet. Also I noticed that holding down space-bar to frame-advance seems to be broken after the merge, but looking back it also doesnt seem to work on the current Movie branch?

You have to do a release build, or atleast not use the debug version of GSdx as it massively slows down the game.

This continues the work on #3.

So, I added some wxSpinCtrl to handle pressure in the Virtual Pad.
@xTVaser, could you please check if this works?

I'll do the KeyEditor later.