SonicMastr / godot-vita

Godot Engine Vita Port based off of Stary2001 and EIREXE Contributions utilizing PVR_PSP2
https://godotengine.org
MIT License
244 stars 17 forks source link

Changing the game's title gives Error 0xF0030000 on install #37

Open Bunkai9448 opened 1 year ago

Bunkai9448 commented 1 year ago

Godot version: https://github.com/SonicMastr/godot-vita/releases/tag/3.5-rc5-vita1

OS/device including version: Target: PS Vita 3.65 Henkaku ENSO Developed in: Windows7 Home Premium, Service Pack 1

Issue description: When I try to change the project name it always give me the same installation error: Error 0xF0030000 However when I used one of an existing game, like the "Squash the Creeps (3D)" example, it runs without problem. Everything else is exactly the same in all senses. I've also tried to create a new project but they all fail at installation with the same (0xF0030000) error.

Steps to reproduce: Create a project with default name and try to change it in the export options. (Actually, I also tried to create a new project from scratch but it gave me the same error)

Minimal reproduction project: VPK working and VPK failing attached (change the zip files to vpk)

No_error-Squash the Creeps (3D).zip No_Error

With_error-Ice-Puck.zip With_error

Bunkai9448 commented 1 year ago

For those who have the same problem, I have tested that as long as you keep the param_sfo/title= from the first export, you can change everything else and keep creating new vpk games.

That makes me believe that the project name is not changed during the linking with the eboot.bin which crash the installation. (In fact, that's the only thing I haven't been able to edit. By process of elimination it has to be that ).

Hope this helps

ZFhuang commented 1 year ago

Although the Editor version mentioned here is different from yours, both have encountered the same issue (0xF0030000), which might have been resolved already. I think using an updated Editor may help solve this problem, and you can download the latest Editor from this link.

astearon commented 11 months ago

Although the Editor version mentioned here is different from yours, both have encountered the same issue (0xF0030000), which might have been resolved already. I think using an updated Editor may help solve this problem, and you can download the latest Editor from this link.

Actions have expired artifacts, where could i get them?

ZFhuang commented 11 months ago

Although the Editor version mentioned here is different from yours, both have encountered the same issue (0xF0030000), which might have been resolved already. I think using an updated Editor may help solve this problem, and you can download the latest Editor from this link.

Actions have expired artifacts, where could i get them?

This is the Windows version I downloaded before it expired.

Bunkai9448 commented 7 months ago

Can confirm it's fixed in the updated version 3.6.beta from a few days found at (artifacts from) https://github.com/SonicMastr/godot-vita/actions/runs/8011699088

fossqueen commented 4 months ago

The artifacts are expired again. Would love to try a later linux build of the editor! Get the original post's error code.

Bunkai9448 commented 4 months ago

I saved this from the fork mentioned here https://github.com/SonicMastr/godot-vita/issues/44#issuecomment-2127756730 which was also pushed to the main and I believe is the lastest build:

https://drive.google.com/drive/mobile/folders/1V5qrh8WDSELDV8_Y_O0OZBgPGvOH8WCH/1BVB0QqglTw30s4_ZbT1RnObyh60Cr-nk/1LssUnFWgzMrOwStsE6GO8lxMaRFD-3C-?sort=13&direction=a

Hopefully it helps until a new release is made.

PS: Don't forget to update the templates before the export or the editor itself won't be enough.

thatoneham commented 1 month ago

im having the same issue and the drive is privated. could i also get the file?

Bunkai9448 commented 1 month ago

im having the same issue and the drive is privated. could i also get the file?

sorry, I thought it was open, you should be able to get it now.

thatoneham commented 1 month ago

while your still here the issue with 0x80101104 will be fixed with the new editor?