Issues with ports (lr-prboom, eduke32)

quicksilver

@Zering just to be thorough, you aren't overclocked are you?

Can you try to launch yquake2, when it fails to load can you go to /dev/shm/runcommand.log and post the output here?

Zering

I'm not overlocked no, although I think my armfreq is something like 100 higher than by default (I got the Pi like that).
And sorry, I was unclear, it's not that the game doesn't launch. I can select Quake 2 from Emulation Station, I can get into the menu, then the game bombards me with failure messages which scroll too fast for me to read, after which it hangs. I can try and see what the .log says after that though?

quicksilver

@Zering wait are you on a original pi model b?

Zering

I think so, I bought it secondhand two years ago and I didn't pay attention to the make ; judging by pictures on Google I'd say I have a Pi 3 B.

mitu

@Zering Original Model B means Pi 1B, not Pi 3B.

Zering

Oh okay, then no.

quicksilver

@Zering if you look at the top of the board there should be some small writing on it that says what model it is. Can you see what it says or post a pic? Just want to be 100% sure you are using a pi 3b. If you have a pi 1b, it might explain some of the issues you're having.

Zering

Just checked the top of the board, and it says Pi 3 Model B v1.2. Don't know why I never thought of checking the board itself for a model designation.

Zering

Update : I've managed to get Quake 2 working. The issue was I'd copied over pak0.pak, pak1.pak, pak2.pak from my GOG directory. Yquake2 apparently only needs pak1.pak to function. I had to setup the controls myself and I get a prompt saying they're not mapped every time I use my controller (even though they are), but it seems to work. So thanks to everyone for all the help.

Zering

Hey guys, I'm still struggling getting eduke32 to work properly. I saw in the post about the release of 4.6 that the module had gotten an extensive overhaul, so I tried an install from source. I got an error.

link text

My next stop is to uninstall then reinstall the module entirely, but if anybody has any ideas, I would very much appreciate it.

mitu

Install from binary, it should get you the same package.

Zering

I have an option to install from a pre-compiled binary, but it was pre-compiled before the latest image so it wouldn't have the changes to the module that 4.6 brought right?

And if it does does it mean that eduke32 is essentially broken and unplayable?

mitu

@Zering said in Issues with ports (lr-prboom, eduke32):

I have an option to install from a pre-compiled binary, but it was pre-compiled before the latest image so it wouldn't have the changes to the module that 4.6 brought right?

I don't understand how you think package updates work, but if you install from binary, you get the latest binary for your system, no matter which version of RetroPie you're on. The 4.6 is just a version tag, as long as the package has not been modified - and it hasn't - before the release, you'd get the same binary if you would be running 4.5.18, 4.5.19, etc.

And if it does does it mean that eduke32 is essentially broken and unplayable?

No, I don't understand why you think so ? Just because it doesn't work for you, it doesn't mean it's not working for other users.

Please install from binary, then provide a crash log from /dev/shm/runcommand.log if you want to diagnose this issue.

Zering

@mitu I don't understand what information you want me to provide, there is nothing in the directory you've just indicated.

It doesn't crash when I install from binary, and for the most part the module works, but it crashes and kicks me back to Emulation Station after a few minutes of gameplay, ie. if I try to save or load.

Is there a different log for that type of crash that I can access and copy here?

mitu

@Zering said in Issues with ports (lr-prboom, eduke32):

It doesn't crash when I install from binary, and for the most part the module works, but it crashes and kicks me back to Emulation Station after a few minutes of gameplay, ie. if I try to save or load.

Then you should have a log file in /dev/shm, called runcommand.log. Get the contents of the file and post it here. If you reboot your system, then the file will be deleted, so it's important you look for it immediately after the crash.

Zering

@mitu All right, seems easy enough.

If the system hangs and I have to do a hard reboot, can I find a log for that as well?

mitu

@Zering said in Issues with ports (lr-prboom, eduke32):

If the system hangs and I have to do a hard reboot, can I find a log for that as well?

Not sure, but your should install SSH and access the Pi via WinSCP or FileZilla. The interface/game might be locked, but the system might still work.

Zering

@mitu I've got WinSCP. The reason I was asking is I've just tried reproducing the crash on eduke32 and instead of sending me back to ES the game just hung on the loading screen. If it hangs, what can I do with WinSCP to try and find a solution to the issue?

mitu

@Zering Same advice - try to get a log file.

Zering

@mitu So I managed to find a log file after the latest crash (it didn't hang this time, it went back to ES when I tried to load my game). It's a whopping 14000 lines, is that normal?

link text

Trying to make sense of this thing is like reading chinese backwards with blinders on to me, so if anybody can offer any guidance I'd be very grateful.