Hacking Help compiling h-encore-2 on Windows 10

  • Thread starter Thread starter Codiak101
  • Start date Start date
  • Views Views 1,579
  • Replies Replies 3

Codiak101

Member
Newcomer
Joined
Mar 8, 2021
Messages
16
Reaction score
9
Trophies
0
Age
37
XP
162
Country
United Kingdom
I've setup a MinGW environment on Windows 10 to compile Vita app source code. I have this project where I want to be able to swap out different config.txt files when loading CFW. I want to develop a solution to loading different plugins depending on whether you play the Vita in handheld or in a custom dock on the TV. My Vita is on version 3.70 so the plan is to mod the boostrap menu of h-encore-2 with options for the 2 config.txt files.

Compiling the h-encore-2 source code creates a system.dat file. This file is in the release on github, so I figured I'd swap out the file with my one and follow the install process as normal. I can load CFW with the original file, but with my compiled file it errors. I haven't made any changes for the mod, I just want to make sure I can compile the same file in the release first.

My compiled file isn't the same as the release version though. My one when opened in Notepad looks like characters aren't formatted, whereas the release file is UTF-16 with Chinese characters. I've tried converting my file to UTF-16 and changing the unicode when compiling again, but neither of these works.

I've been stuck on this for some time, am I even on the right track to solving this or do I need to take a step back and solve it another way? Thanks for the help.
 
I've setup a MinGW environment on Windows 10 to compile Vita app source code. I have this project where I want to be able to swap out different config.txt files when loading CFW. I want to develop a solution to loading different plugins depending on whether you play the Vita in handheld or in a custom dock on the TV. My Vita is on version 3.70 so the plan is to mod the boostrap menu of h-encore-2 with options for the 2 config.txt files.

Compiling the h-encore-2 source code creates a system.dat file. This file is in the release on github, so I figured I'd swap out the file with my one and follow the install process as normal. I can load CFW with the original file, but with my compiled file it errors. I haven't made any changes for the mod, I just want to make sure I can compile the same file in the release first.

My compiled file isn't the same as the release version though. My one when opened in Notepad looks like characters aren't formatted, whereas the release file is UTF-16 with Chinese characters. I've tried converting my file to UTF-16 and changing the unicode when compiling again, but neither of these works.

I've been stuck on this for some time, am I even on the right track to solving this or do I need to take a step back and solve it another way? Thanks for the help.
Should just downgrade to 3.60+enso and use emergencymount then I can swap config.txt anytime u want
 
I'm open to configuring existing apps/plugins. I have a dock_config.txt and a portable_config.txt for the separate plugins I'd like to use depending on what mode I'm in, and obviously a config.txt for what's currently used. It would be nice to not have to swap these around manually, in fact the dock one has a plugin that stops the Vita buttons working as it's locked to connecting a ds4 controller. What can I use to identify different config.txt files and have a menu where you select what one you want to load?

The only downside I can see is the Vita will need to be restarted with the new config.txt which is why it would have been good to set it when exiting h-encore-2.
 

Site & Scene News

Popular threads in this forum