Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
eduke32 not launching
#1
Hi!

I can't seem to figure out why the eduke32 port won't launch for my Frankenpi (RPi 3 A+ in a Freeplay Zero Kit) I can get prboom (Doom) and wolf4sdl (Wolfenstein 3D) to work fine. When I try to get it to launch it just goes back to the "Ports" screen. Has anyone encountered this problem and found a solution? I am also running an old image because that is the only one that will boot in my A+ (18111301) if that makes a difference. I have read the "official" guide and it just says "the eduke32 port from the raspi-config repo should work."

Thanks in advance!
Reply
#2
As far as images go, have you tried the most recent CM3 release (Freeplay_CM3_19110701.img.gz)? It might boot on your 3A+, and it would have a newer RetroPie.

I assume you've read through this.
https://github.com/RetroPie/RetroPie-Set...e-Nukem-3D

Maybe try the new SD image and get back to us if that worked or not.
Card Fighters' Clash 2 English Translation ( http://cfc2english.blogspot.com/ )
Neo Geo Pocket Flash Cart and Linker Project ( http://www.flashmasta.com/ )
Avatar art thanks to Trev-Mun ( http://trevmun.deviantart.com/ )
Reply
#3
(11-15-2019, 09:00 AM)Flavor Wrote: As far as images go, have you tried the most recent CM3 release (Freeplay_CM3_19110701.img.gz)?  It might boot on your 3A+, and it would have a newer RetroPie.

I assume you've read through this.
https://github.com/RetroPie/RetroPie-Set...e-Nukem-3D

Maybe try the new SD image and get back to us if that worked or not.
I have actually tried all the new images, and they all had various issues, whether it be a white screen or no inputs registering. I went back to the old faithful and it seems to work perfectly.
Reply
#4
I don't mind downloading a new setup script and installing the new version from raspi-config and redoing the input drivers if it means I'll get better versions of all the cores and ports. But I've been fiddling with it for a couple of days just trying to get the whole thing working again because I borked my working install (don't ask) so I guess I want to know if it'll actually be worth it.
Reply
#5
I installed this port a will ago (on a CM3) without problems.

Does verbose logs option available when you start this port? (I am not home)
If not, you can try to start it via terminal to get some output.

Also, some time, if locations are Ok, this is a folder or a file permission that make the troubles.
Reply
#6
(11-15-2019, 02:32 PM)TexasPorcupine Wrote:
(11-15-2019, 09:00 AM)Flavor Wrote: As far as images go, have you tried the most recent CM3 release (Freeplay_CM3_19110701.img.gz)?  It might boot on your 3A+, and it would have a newer RetroPie.

I assume you've read through this.
https://github.com/RetroPie/RetroPie-Set...e-Nukem-3D

Maybe try the new SD image and get back to us if that worked or not.
I have actually tried all the new images, and they all had various issues, whether it be a white screen or no inputs registering. I went back to the old faithful and it seems to work perfectly.

Just so we're on the same page here...
Do you mean that the other SD images had problems working AT ALL on the 3A+?  Or do you mean that they had problems with Duke Nukem?
Card Fighters' Clash 2 English Translation ( http://cfc2english.blogspot.com/ )
Neo Geo Pocket Flash Cart and Linker Project ( http://www.flashmasta.com/ )
Avatar art thanks to Trev-Mun ( http://trevmun.deviantart.com/ )
Reply
#7
Also, we used to have a 3A+, but we accidentally killed it during a test. We can't help a ton, because we don't have one to try. I'm not really sure why it isn't working, though.

If you got a white screen, that may mean that the LCD driver isn't working. I think the default LCD driver was the one in use on the old image. The new image probably uses https://github.com/juj/fbcp-ili9341/ as standard. The code repository got an update for 3A+ in August, but maybe that isn't in the build on the Freeplay image. If you have HDMI, you could switch LCD drivers and reboot. Then it may work well.

No inputs would typically point to a problem with the mk_arcade joystick driver. You may just need to recompile/reinstall it.
Card Fighters' Clash 2 English Translation ( http://cfc2english.blogspot.com/ )
Neo Geo Pocket Flash Cart and Linker Project ( http://www.flashmasta.com/ )
Avatar art thanks to Trev-Mun ( http://trevmun.deviantart.com/ )
Reply
#8
(11-15-2019, 05:24 PM)Porcinus Wrote: I installed this port a will ago (on a CM3) without problems.

Does verbose logs option available when you start this port? (I am not home)
If not, you can try to start it via terminal to get some output.

Also, some time, if locations are Ok, this is a folder or a file permission that make the troubles.

Hi Porci,

I will try to see if it spits out logs but I don't recall seeing that option in the pre-launch config menu. I'll try in terminal to see what it says.

Also, I did read that an update to the port required you to put the .grp files and separate .cfg files in individual folders for the expansions, but nothing for the actual main .grp file. If you know of where I should put the main file, I would greatly appreciate it.
Reply
#9
(11-16-2019, 02:41 AM)Flavor Wrote:
(11-15-2019, 02:32 PM)TexasPorcupine Wrote:
(11-15-2019, 09:00 AM)Flavor Wrote: As far as images go, have you tried the most recent CM3 release (Freeplay_CM3_19110701.img.gz)?  It might boot on your 3A+, and it would have a newer RetroPie.

I assume you've read through this.
https://github.com/RetroPie/RetroPie-Set...e-Nukem-3D

Maybe try the new SD image and get back to us if that worked or not.
I have actually tried all the new images, and they all had various issues, whether it be a white screen or no inputs registering. I went back to the old faithful and it seems to work perfectly.

Just so we're on the same page here...
Do you mean that the other SD images had problems working AT ALL on the 3A+?  Or do you mean that they had problems with Duke Nukem?

At all.
Reply
#10
(11-16-2019, 06:19 AM)TexasPorcupine Wrote:
(11-15-2019, 05:24 PM)Porcinus Wrote: I installed this port a will ago (on a CM3) without problems.

Does verbose logs option available when you start this port? (I am not home)
If not, you can try to start it via terminal to get some output.

Also, some time, if locations are Ok, this is a folder or a file permission that make the troubles.

Hi Porci,

I will try to see if it spits out logs but I don't recall seeing that option in the pre-launch config menu. I'll try in terminal to see what it says.

Also, I did read that an update to the port required you to put the .grp files and separate .cfg files in individual folders for the expansions, but nothing for the actual main .grp file. If you know of where I should put the main file, I would greatly appreciate it.


It was almost 1 year ago and I don't really remember what I did exactly :S

Can you try to remove, reinstall the port and start it without editing anything. If my memory don't fail me, the shareware package was already install by default.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)