Recent Posts

Pages: [1] 2 3 ... 10
1
PS Vita / Re: [Release] BGFTP - Background FTP server
« Last post by Graphene on February 24, 2020, 12:10:39 AM »
Updated to v1.2

Added photo0: and music0: virtual drives.

Updated to the latest version of libvita2d_sys:
- Some UI changes
- SceShell overlay in main application should work properly now.
2
PS Vita / Re: [Release] libvita2d_sys - libvita2d for system mode applications
« Last post by Graphene on February 23, 2020, 10:47:01 PM »
Fixed the way shared fb is swapped. SceShell overlay shoud work properly now.

Framebuffer swapping in libvita2d_sys is now performed automatically. vita2d_swap_buffers() does not exist anymore.
3
PS Vita / [Release] BGFTP - Background FTP server
« Last post by Graphene on February 22, 2020, 02:38:38 AM »
Background FTP server for PS Vita.

Works simultaneously with any game, including enlarged memory mode games, and in sleep mode. BGFTP can send various information to user via notifications.

More information and download: https://github.com/GrapheneCt/BGFTP



4
Reverse Engineering / vshPowerSetPowerSwMode
« Last post by Graphene on February 21, 2020, 06:37:22 PM »
int vshPowerSetPowerSwMode(int mode)

returns 0 if successful.

mode values:
0 - press does nothing, long press opens shutdown menu like usual;
1 - press does nothing, long press immediately shuts down;
2 - press immediately suspends, long press opens shutdown menu like usual;
3 - press immediately suspends, long press immediately shuts down;
4 - same as normal?
5 - same as normal?
6 - same as normal?
7 - press suspends as normal, long press immediately shuts down;
5
PS Vita / [Release] libvita2d_sys - libvita2d for system mode applications
« Last post by Graphene on February 16, 2020, 10:59:11 PM »
libvita2d_sys is modification of libvita2d designed to be used in applications running in system mode. That means that you can use such applications without closing games.
https://github.com/GrapheneCt/libvita2d_sys
6
PS Vita / [Tutorial][Windows] VS Code with VitaSDK
« Last post by dots_tb on February 16, 2020, 03:44:42 AM »
What is VS Code?:

SonicMastr told me to try VS Code again...

Visual Studio Code is the latest meme/botnet code editor from Microsoft that everyone is using to program now. It is similar to Visual Studios in allowing IntelliSense except more lightweight, cross-platform, and in an attempt attract neck beards to this botnet, offers more customization.

IntelliSense in action with VitaSDK (Code Auto-completion)



IntelliSense in action with VitaSDK (Code Parameter Information)




Of course, with this demographic comes the emulation of annoying configuration that doesn't work out of the box in order to give feed into a superiority complex that these neck beards so desire.

What Will This Tutorial Cover?:


This will be a brief overview on getting VS Code to work with VitaSDK installed through msys2 on Windows. This includes building and setting up the headers. This is just what worked for me and may not apply to your system (ex: if you are using a dated 32 bit machine). I don't really know how to use this thing, so I'll just tell you everything I had to do.

You will need:



Installing msys2 and VitaSDK:


Since they have detailed steps on their respective websites, I will just give notes on installing. If you already have it installed, make sure you have the dependencies listed below.

Install msys2 first, downloading the 64bit version (ex: msys2-x86_64-*.exe). Install it then SCROLL DOWN and follow the remaining instructions on the website!

Then attempt to install VitaSDK through the Windows instructions on their website, except use the following dependencies instead:
Code: [Select]
pacman -Su make git cmake tar mingw64/mingw-w64-x86_64-libwinpthread-git python mingw-w64-x86_64-cmake mingw-w64-x86_64-toolchain
For doing exports, if you don't know where the .bashrc file is:
Code: [Select]
nano ~/.bashrc

This will open a text editor, paste the export information into there and restart your terminal.

After this, continue with the install of vdpm and hopefully it will work for you...

Make sure the following is in your Windows User PATH environment variable. I cannot give instructions for this since it is different for every version of Windows, a quick google search will tell you how to do this:

Code: [Select]
C:\msys64\mingw64\bin
C:\msys64\usr\local\vitasdk\bin


Setting up a Project (Part 1):


Install and open VS Code.

Drag and drop the source folder of the desired project onto VS Code.

By source folder, the directory that contains the CMakeLists.txt file.

VS Code should automatically detect and prompt you to install the CMake Tools and C/C++ extensions by Microsoft.

If not, click on the Extensions button on the left side bar, search for C/C++ and CMake Tools (not CMake) and install them respectively (I already have them installed).



After both extensions are installed, it is now time to configure CMake Tool. Because CMake defaults to Unix Makefiles and Windows obviously does not use a Unix file system, errors will occur. Thus, the following section is dedicated to fixing this issue by using minGW, which uses Windows Paths. I think...

Hit the key combo CTRL+SHIFT+P to open the "Command Palette" and type Settings json and look for "Open Setttings (JSON)"



Add the following to your settings.json:
Code: [Select]
    "cmake.buildDirectory": "${workspaceRoot}/build/${buildType}",
    "cmake.configureOnOpen": true,
    "cmake.cmakePath": "C:\\msys64\\mingw64\\bin\\cmake",
    "cmake.generator": "MinGW Makefiles"

By doing this, we are changing the CMake generator type to MinGW to allow it to build within windows and we are using the MingW64 cmake. The rest is maybe optional. I don't know.

Be sure you have all your commas and keep the syntax proper.

Example settings.json:


Now open the Command Palette again, and type "cmake" and look for "Edit User-Local CMake Kits"



Add the following code to the now opened cmake-tools-kits.json:
Code: [Select]
  {
    "name": "VitaSDK",

    "toolchainFile": "C:\\msys64\\usr\\local\\vitasdk\\share\\vita.toolchain.cmake",
    "preferredGenerator": {
      "name": "MinGW Makefiles"
    },
    "environmentVariables": {
      "VITASDK": "C:\\msys64\\usr\\local\\vitasdk",
      "CMT_MINGW_PATH": "C:\\msys64\\usr\\local\\vitasdk\\bin"
    }
  },

With this config, we are setting the VitaSDK enviromental variables along with setting the path to locate the compiler binaries. We are also hard-coding the location of the toolchain cmake file (normally set by the cmake file in the project).

Be sure to mind your brackets, commas, and curly braces.

Example cmake-tools-kits.json:



Make sure you saved all your files and now CMake should be configured.

Look at the bottom left corner of the Window, you should see "No Kits Selected", click on that and change it to "VitaSDK".



You should be able to build now by clicking the "Build:" button in the same bottom bar area.

If it doesn't work the first time:
  • Navigate to the location of the source folder and look inside it.
  • Make sure there is no build folder.
  • Open the command palette and then type Developer Reload and reload the window
And with luck, it should configure CMake and allow you to build the project.

Setting up a Project (Part 2):

You will have to do the following with every new opened project.

Open the command palette, then type c++, looking for "C/C++: Edit Configurations (UI)"


Add a new configuration called VitaSDK and set the compiler path to the following:
Code: [Select]
C:\msys64\usr\local\vitasdk\bin\arm-vita-eabi-gcc.exe



Scroll down and un-collapse Advanced Settings then look for and set the Browse Path to the following:

Code: [Select]
C:\msys64\usr\local\vitasdk\arm-vita-eabi\include



This should set up IntelliSense.

The nightmare is over and now you can enjoy using VS Code. You can try setting up other things like Davee's gdb thing, but it is not as stable as I would like it to be.

If you need help: https://discord.cbps.xyz
7
Reverse Engineering / Re: SharedFb and sceGxmInternalForVsh sample
« Last post by Graphene on February 12, 2020, 11:50:23 PM »
Updated the sample

- Removed unnecessary code
- GXM memory is now mapped (total size is 5MiB)
- Added vsync value (60FPS or 30FPS lock)
8
Reverse Engineering / SharedFb and sceGxmInternalForVsh sample
« Last post by Graphene on February 09, 2020, 09:58:39 PM »
This sample demonstrates how to use shared framebuffer and initialize GXM in PS Vita applications running in system mode: https://github.com/GrapheneCt/SharedFb-PSV

If you have been using NoSharedFb plugin, unistall it before using this application.

It draws squares moving from top to bottom of the screen. Color of the squares will be green if GXM was initialized successfully and red if initialization failed.
9
Reverse Engineering / Dumping addcont IDs
« Last post by cuevavirus on February 08, 2020, 04:30:15 PM »
https://github.com/cuevavirus/AddcontIDDumper

Need PrincessLog to received the dumper output.

This can be helpful for creating fake DLCs.

This only works when the game calls sceAppMgrDrmOpen which requires one of the parameters to be the addcont ID. If the game calls sceIoDopen on addcont0: then sceIoDread to check for available addcont, then the IDs cannot be acquired.
10
PS Vita / Re: [RELEASE] DolcePolce - PSTV Blacklist Patch that just WORKS
« Last post by laz305 on February 07, 2020, 09:29:59 PM »
Thanks for this. Works way better!!!!!!
Pages: [1] 2 3 ... 10