search

pumpitupdev / pumptools

A collection of tools to run Pump It Up games.
The Unlicense
22 stars 7 forks source link

NX2 Doesn't open #52

Closed Getze56901 closed 1 year ago

Getze56901 commented 1 year ago

Bug report

NX2 Doesn't open the game

Description

The game doesn't open and send this command line

](https://cdn.discordapp.com/attachments/814772510024925224/1059669092258299914/image.png) ## Affected games and versions NX2

Pumptools versions tested

1.12

OS and hardware specs

concubidated commented 1 year ago

Is the data correctly setup? Looks like the piu binary is missing. Can you show the contents of your nx2 directory? image

voidderef commented 1 year ago

Is the data correctly setup? Looks like the piu binary is missing. Can you show the contents of your nx2 directory? image

To be even more specific, can you run the following commands and paste the output here?

ls -la /mnt/hgfs/20_nx2
ls -la /mnt/hgfs

Also, please post how you run the game, full command, plus the full output of what appears to be piueb that you are running. It should create a logfile called piueb.log iirc.

It also appears, due to the hgfs folder, that you are accessing your note via a shared network mount, is that correct? Bringing this up to let you know that, at least myself, have never run nor tested these games from a network mounted folder. Theoretically, it should not matter, but experience over the years has shown that network mounts always create issues with weird symptoms. I advice to move the data to your local disk first, verify you get the game to run, then try moving it to the network mount and see if that also works. That might save you a lot of time and frustartion if you run into issues because of that.

piotr25691 commented 1 year ago

Is the data correctly setup? Looks like the piu binary is missing. Can you show the contents of your nx2 directory? image

To be even more specific, can you run the following commands and paste the output here?

ls -la /mnt/hgfs/20_nx2
ls -la /mnt/hgfs

Also, please post how you run the game, full command, plus the full output of what appears to be piueb that you are running. It should create a logfile called piueb.log iirc.

It also appears, due to the hgfs folder, that you are accessing your note via a shared network mount, is that correct? Bringing this up to let you know that, at least myself, have never run nor tested these games from a network mounted folder. Theoretically, it should not matter, but experience over the years has shown that network mounts always create issues with weird symptoms. I advice to move the data to your local disk first, verify you get the game to run, then try moving it to the network mount and see if that also works. That might save you a lot of time and frustartion if you run into issues because of that.

On the offchance, I got a window popping up only to say "WAITING LOCK DEVICE... PLEASE CHECK ATTACHED LOCK DEVICE IS INSTALLED CORRECTLY", how do I fix that?

piotr25691 commented 1 year ago

Is the data correctly setup? Looks like the piu binary is missing. Can you show the contents of your nx2 directory? image

To be even more specific, can you run the following commands and paste the output here?

ls -la /mnt/hgfs/20_nx2
ls -la /mnt/hgfs

Also, please post how you run the game, full command, plus the full output of what appears to be piueb that you are running. It should create a logfile called piueb.log iirc. It also appears, due to the hgfs folder, that you are accessing your note via a shared network mount, is that correct? Bringing this up to let you know that, at least myself, have never run nor tested these games from a network mounted folder. Theoretically, it should not matter, but experience over the years has shown that network mounts always create issues with weird symptoms. I advice to move the data to your local disk first, verify you get the game to run, then try moving it to the network mount and see if that also works. That might save you a lot of time and frustartion if you run into issues because of that.

On the offchance, I got a window popping up only to say "WAITING LOCK DEVICE... PLEASE CHECK ATTACHED LOCK DEVICE IS INSTALLED CORRECTLY", how do I fix that?

Have these logs and screenshots to check what did I screw up causing the game to give me what appears to be a dongle error:

piueb.log pumptools.log

image

voidderef commented 1 year ago

Is the data correctly setup? Looks like the piu binary is missing. Can you show the contents of your nx2 directory? image

To be even more specific, can you run the following commands and paste the output here?

ls -la /mnt/hgfs/20_nx2
ls -la /mnt/hgfs

Also, please post how you run the game, full command, plus the full output of what appears to be piueb that you are running. It should create a logfile called piueb.log iirc. It also appears, due to the hgfs folder, that you are accessing your note via a shared network mount, is that correct? Bringing this up to let you know that, at least myself, have never run nor tested these games from a network mounted folder. Theoretically, it should not matter, but experience over the years has shown that network mounts always create issues with weird symptoms. I advice to move the data to your local disk first, verify you get the game to run, then try moving it to the network mount and see if that also works. That might save you a lot of time and frustartion if you run into issues because of that.

On the offchance, I got a window popping up only to say "WAITING LOCK DEVICE... PLEASE CHECK ATTACHED LOCK DEVICE IS INSTALLED CORRECTLY", how do I fix that?

Have these logs and screenshots to check what did I screw up causing the game to give me what appears to be a dongle error:

piueb.log pumptools.log

image

The log doesn't show any errors or anything odd looking. The dongle requests also seem to be dispatched successfully by pumptools. This doesn't mean that decryption suceeds as the emulation is operating on a rainbow table.

What's the version of NX2 you are trying to run? Where did you source the data from?

The only supported version is 1.54 as outlined by the documentation

piotr25691 commented 1 year ago

Is the data correctly setup? Looks like the piu binary is missing. Can you show the contents of your nx2 directory? image

To be even more specific, can you run the following commands and paste the output here?

ls -la /mnt/hgfs/20_nx2
ls -la /mnt/hgfs

Also, please post how you run the game, full command, plus the full output of what appears to be piueb that you are running. It should create a logfile called piueb.log iirc. It also appears, due to the hgfs folder, that you are accessing your note via a shared network mount, is that correct? Bringing this up to let you know that, at least myself, have never run nor tested these games from a network mounted folder. Theoretically, it should not matter, but experience over the years has shown that network mounts always create issues with weird symptoms. I advice to move the data to your local disk first, verify you get the game to run, then try moving it to the network mount and see if that also works. That might save you a lot of time and frustartion if you run into issues because of that.

On the offchance, I got a window popping up only to say "WAITING LOCK DEVICE... PLEASE CHECK ATTACHED LOCK DEVICE IS INSTALLED CORRECTLY", how do I fix that?

Have these logs and screenshots to check what did I screw up causing the game to give me what appears to be a dongle error: piueb.log pumptools.log image

The log doesn't show any errors or anything odd looking. The dongle requests also seem to be dispatched successfully by pumptools. This doesn't mean that decryption suceeds as the emulation is operating on a rainbow table.

What's the version of NX2 you are trying to run? Where did you source the data from?

The only supported version is 1.54 as outlined by the documentation

Well, the version is in fact 1.54 when I looked back into the data link I got, so I don't know what is exactly happening. There must be something else going wrong.

voidderef commented 1 year ago

Is the data correctly setup? Looks like the piu binary is missing. Can you show the contents of your nx2 directory? image

To be even more specific, can you run the following commands and paste the output here?

ls -la /mnt/hgfs/20_nx2
ls -la /mnt/hgfs

Also, please post how you run the game, full command, plus the full output of what appears to be piueb that you are running. It should create a logfile called piueb.log iirc. It also appears, due to the hgfs folder, that you are accessing your note via a shared network mount, is that correct? Bringing this up to let you know that, at least myself, have never run nor tested these games from a network mounted folder. Theoretically, it should not matter, but experience over the years has shown that network mounts always create issues with weird symptoms. I advice to move the data to your local disk first, verify you get the game to run, then try moving it to the network mount and see if that also works. That might save you a lot of time and frustartion if you run into issues because of that.

On the offchance, I got a window popping up only to say "WAITING LOCK DEVICE... PLEASE CHECK ATTACHED LOCK DEVICE IS INSTALLED CORRECTLY", how do I fix that?

Have these logs and screenshots to check what did I screw up causing the game to give me what appears to be a dongle error: piueb.log pumptools.log image

The log doesn't show any errors or anything odd looking. The dongle requests also seem to be dispatched successfully by pumptools. This doesn't mean that decryption suceeds as the emulation is operating on a rainbow table. What's the version of NX2 you are trying to run? Where did you source the data from? The only supported version is 1.54 as outlined by the documentation

Well, the version is in fact 1.54 when I looked back into the data link I got, so I don't know what is exactly happening. There must be something else going wrong.

Do you have other versions like NX or NXA that you can test? What's your ubuntu and kernel version?

piotr25691 commented 1 year ago

Is the data correctly setup? Looks like the piu binary is missing. Can you show the contents of your nx2 directory? image

To be even more specific, can you run the following commands and paste the output here?

ls -la /mnt/hgfs/20_nx2
ls -la /mnt/hgfs

Also, please post how you run the game, full command, plus the full output of what appears to be piueb that you are running. It should create a logfile called piueb.log iirc. It also appears, due to the hgfs folder, that you are accessing your note via a shared network mount, is that correct? Bringing this up to let you know that, at least myself, have never run nor tested these games from a network mounted folder. Theoretically, it should not matter, but experience over the years has shown that network mounts always create issues with weird symptoms. I advice to move the data to your local disk first, verify you get the game to run, then try moving it to the network mount and see if that also works. That might save you a lot of time and frustartion if you run into issues because of that.

On the offchance, I got a window popping up only to say "WAITING LOCK DEVICE... PLEASE CHECK ATTACHED LOCK DEVICE IS INSTALLED CORRECTLY", how do I fix that?

Have these logs and screenshots to check what did I screw up causing the game to give me what appears to be a dongle error: piueb.log pumptools.log image

The log doesn't show any errors or anything odd looking. The dongle requests also seem to be dispatched successfully by pumptools. This doesn't mean that decryption suceeds as the emulation is operating on a rainbow table. What's the version of NX2 you are trying to run? Where did you source the data from? The only supported version is 1.54 as outlined by the documentation

Well, the version is in fact 1.54 when I looked back into the data link I got, so I don't know what is exactly happening. There must be something else going wrong.

Do you have other versions like NX or NXA that you can test? What's your ubuntu and kernel version?

I do not. I'm running Ubuntu 22.04 LTS on the 5.15 kernel

I fixed the problem by using Ubuntu 20.04 LTS instead

voidderef commented 1 year ago

Is the data correctly setup? Looks like the piu binary is missing. Can you show the contents of your nx2 directory? image

To be even more specific, can you run the following commands and paste the output here?

ls -la /mnt/hgfs/20_nx2
ls -la /mnt/hgfs

Also, please post how you run the game, full command, plus the full output of what appears to be piueb that you are running. It should create a logfile called piueb.log iirc. It also appears, due to the hgfs folder, that you are accessing your note via a shared network mount, is that correct? Bringing this up to let you know that, at least myself, have never run nor tested these games from a network mounted folder. Theoretically, it should not matter, but experience over the years has shown that network mounts always create issues with weird symptoms. I advice to move the data to your local disk first, verify you get the game to run, then try moving it to the network mount and see if that also works. That might save you a lot of time and frustartion if you run into issues because of that.

On the offchance, I got a window popping up only to say "WAITING LOCK DEVICE... PLEASE CHECK ATTACHED LOCK DEVICE IS INSTALLED CORRECTLY", how do I fix that?

Have these logs and screenshots to check what did I screw up causing the game to give me what appears to be a dongle error: piueb.log pumptools.log image

The log doesn't show any errors or anything odd looking. The dongle requests also seem to be dispatched successfully by pumptools. This doesn't mean that decryption suceeds as the emulation is operating on a rainbow table. What's the version of NX2 you are trying to run? Where did you source the data from? The only supported version is 1.54 as outlined by the documentation

Well, the version is in fact 1.54 when I looked back into the data link I got, so I don't know what is exactly happening. There must be something else going wrong.

Do you have other versions like NX or NXA that you can test? What's your ubuntu and kernel version?

~I do not. I'm running Ubuntu 22.04 LTS on the 5.15 kernel~

I fixed the problem by using Ubuntu 20.04 LTS instead

I was about to answer that I never tested anything never than 18.04 LTS and I am still running that version. Therefore, I have no idea if any changes on the OS, libraries or the kernel might have introduced new issues.

Still, thanks for letting me know that 20.04 LTS works (as well). Will update the documentation accordingly with a note for now.

I consider this issue as solved and close it. Feel free to open a new one if you encounter any other problems.

Getze56901 commented 1 year ago

Tested in 20.04 LTS and i have the dongle error pumptools.log piueb.log

0

piotr25691 commented 1 year ago

Tested in 20.04 LTS and i have the dongle error pumptools.log piueb.log

0

While this does not cause the issue, you are also missing the libasound2-plugins package.

Please run sudo apt install libasound2-plugins to resolve an error in the log.

voidderef commented 1 year ago

Tested in 20.04 LTS and i have the dongle error pumptools.log piueb.log

0

Checking the logs for errors, you are apparently not running it as root, which is a requirement for many parts of the game itself.

[E][2023/01/07-12:19:44:330] Running as non-root user, game likely to crash!
[E][2023/1/7-12:19:44:558][hook-core-piu-utils][piu-utils.c:110] Process not running as root which is required for the game to work correctly.

Please pay attention to what the log output is saying. This message is there for a good reason.

Further errors are clearly pointing towards stuff going wrong:

[E][2023/1/7-12:19:44:560][patch-usb-mnt][usb-mnt.c:20] Creating directory /mnt/0 failed
[E][2023/1/7-12:19:44:560][patch-usb-mnt][usb-mnt.c:26] Creating invalid indicator file /mnt/0/invalid failed
...
[E][2023/1/7-12:19:44:560][patch-usb-mnt][usb-mnt.c:20] Creating directory /mnt/1 failed
[E][2023/1/7-12:19:44:560][patch-usb-mnt][usb-mnt.c:26] Creating invalid indicator file /mnt/1/invalid failed
...
[E][2023/1/7-12:19:44:567][sec-microdog40d][microdog40d.c:67] Binding socket failed: No such file or directory

And there is also clearly an error with the dongle part sec-microdog40d.