-
Notifications
You must be signed in to change notification settings - Fork 6
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
Current status? #13
Comments
I think a merge with upstream would be ideal. I don't know of any critically breaking TAS bugs at the moment, and other than #12 Lua seems to be working as well as it has been since it was added (I havnt done much work on the Lua side of things myself, just attempting to fix bugs). The main concern that comes to my mind before a merge is:
Other than that, the TAS tools are working and its just quality of life improvements and small bug fixes going forward so I see no reason to hold off on the merge after we figure out the best way to go in terms of the docs. I've also kinda heavily modified the main solution file to make building and debugging easier for us, so I would want to exclude that from the merge. |
When you want, the honor of a PR is all yours.
Github wikis are like totally unconnected repos AFAIU.
Or you could drop some idea on PCSX2#2342 |
Yes wikis are separate repos you're right. I don't really have any suggestions for the solution files, it was more just me deleting things that were not relevant to debugging these tools. I'll work on cleaning things up in preparation for that PR soon. |
Again @gocha @DocSkellington @pocokhc (hope I'm not to bother, otherwise just unsubscribe)
Follows PCSX2#1923
Hi.
I was wondering how much you still have to be considered complete?
AFAIK this is the most recent tas/lua fork of pcsx2, and I (we?) were wondering if you were planning to merge upstream.
The text was updated successfully, but these errors were encountered: