mupen64plus-gles2n64 small screen in the bottom left hand corner still not fixed following instructions.
-
@full-pixel you didn’t fill out https://retropie.org.uk/forum/topic/3/read-this-first but if you’re running kms driver/latest rapsbian (which we don’t support yet) it would be the same issue as pi4. the issue is gles2n64 run via kms.
-
Sorry I didn't see that. I was posting multiple versions of this thread in more than one place so got too ADHD I guess....
So you're saying that I need to downgrade Raspbian? To which version?
Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..)
3a+
Power Supply used: (If using a Pi)
A 5.13v 3amp output usb power bank of generic brand of which is plugged into a power switch and then the pi.
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest):
4.7.1-rpi2_3.img
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used)
https://downloads.raspberrypi.org/raspios_armhf/images/raspios_armhf-2021-05-28/2021-05-07-raspios-buster-armhf.zip on to top of this. I used etcher to install it and then just installed retropie on top of it.
Installed on top of Raspbian's newest OS.
Mednafen, transmission (and it's user interface), retropie, other than basic full installed software.USB Devices connected:
usb splitter with: USB sound card, dongle for mouse/keyboard handheld, 3.5'' lcd monitor (plugged in with an inverter that changes the 5v to 10v while halving amp I think) (sometimes n30 pro duo controller)
By the way with only the usb mouse/keyboard and nothing else it still gives the undervoltage warning randomly. The amps output by the usb power bank are volatile or whatever. I've tested it and it bounces a lot though I don't know if that's normal, up and own. It never browns out though sometimes refuses to turn on initially until I flip it off and try again.
Controller used:
n30 pro duo controller and or the generic keyboard/mouse device with it's wireless dongle (using n30 pro duo wired, not bluetooth
Error messages received:
Undervoltage warning. Also "lv10: VolumeControl ::init() failed to find mixer elements" if I recall.
Verbose log (if relevant):
Guide used: (Mention if you followed a guide)
https://forums.raspberrypi.com/viewtopic.php?t=56070 but also the one mentioned in the OP about fixing the offset screen.
File: (File with issue - with FULL path)
It's in the normal location of n64 roms and more than one n64 game, they all play tiny.
Emulator: (Name of emulator - if applicable)
Basically n64 but lr-mupen64plus crashes, gliden64, it's second version, the rice one too, they don't change resolution past being very small at the lower left, the three (hi resolution versions I didn't try).
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)
My win7 netbook is locked out of the bios so can't use linux, the computer that can has no Internet access, so It'd be sort of silly to sit for an hour squinting at my tiny 3.5'' screen copying all of the default config files when I came to get non-default ones to fix an issue. Otherwise I'd just copy the text files. I could sue the pi to do that but don't feel like breaking two sd's of the same os at once (I cloned it). I don't have access to the Puppy Linux thrift store PC I bought for accessing properly Linux partitions or I'd do it. Can I do this later? I'm not sure where every single config files can be found without using the console, I swear it's hidden often, some configuration files. I'm not great with the console and the pi sending the logs out I don't know how to do, if there is such a feature. It hates my router also, ssh nor samba work with the rpi3a+ though it can access the Internet though that is neither here nor there, I simply never connect it to the Internet unless installing the software. How would I export the files to pastbin from the pi itself using the Internet? I'm far too much of a noob for that but maybe tomorrow I'll sit and type everything i find on it manually while staring. Sorry.
How to replicate the problem:
It just always happens with every n64 game.
-
@full-pixel said in mupen64plus-gles2n64 small screen in the bottom left hand corner still not fixed following instructions.:
@dankcushions
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest):4.7.1-rpi2_3.img
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used)
https://downloads.raspberrypi.org/raspios_armhf/images/raspios_armhf-2021-05-28/2021-05-07-raspios-buster-armhf.zip on to top of this. I used etcher to install it and then just installed retropie on top of it.
Installed on top of Raspbian's newest OS.
Mednafen, transmission (and it's user interface), retropie, other than basic full installed software.i don’t really understand what you’re saying here. you e mentioned 3 separate images: 4.7.1-rpi2_3.img, 2021-05-07-raspios-buster-armhf.zip, and latest raspbian. only one of these is active at one time - installing a new image wipes the previous.
i would expect n64 to work full screen on 4.7.1-rpi2_3.img at default settings and emulator. i would not expect it to work on latest raspbian (which we don’t yet support)
-
Is it possible to dual boot yet? Any time I've tried to dual boot anything like lakka and retropie with another daily driver OS it never would work out (at least through the composite. Switching sds will require me to dismantle my device I make and the sd card splitter I read about that I could buy need to be unplugged to be reset of which defeats it's purpose.
What older version of raspbian do I use? Are you saying no version of raspbian can install the newest retropie?
I copied lots of files by the way but didn't upload them yet:
Because I'm a noob and always burned out it's 21 items.....
I can't imagine getting dual booting right and it'd waste space on the sd even if I did get it right....
Edit: But I meant that I installed retropie on top of the latest raspbian to be clear. I'd figure that'd be no different than having the latest raspbian so I copied the files I recently downloaded, their names. What's the difference? Isn't retropie just tweaked raspbian anyway? I don't get it.
-
Also pastebin.com won't let me paste for some reason. It says 'please wait' forever.
one file would be:
#gles2n64 Graphics Plugin for N64
#by Orkin / glN64 developers and Adventus.
config version=2#Window Settings:
window width=400
window height=240
multisampling=0
auto resolution=0#Framebuffer Settings:
framebuffer bilinear=0
framebuffer width=640
framebuffer height=480#VI Settings:
video force=0
video width=320
video height=240
video stretch=0#Render Settings:
enable fog=0
enable primitive z=1
enable lighting=1
enable alpha test=1
enable clipping=0
enable face culling=1
enable noise=0#Texture Settings:
texture 2xSAI=0
texture force bilinear=0
texture max anisotropy=0
texture use IA=0
texture fast CRC=1
texture pow2=1#Frame skip:
auto frameskip=1
target FPS=20
frame render rate=1
vertical sync=0#Other Settings:
update mode=1
print FPS=0
ignore offscreen rendering=0
force screen clear=0
flip vertical=0
tribuffer opt=1#Hack Settings:
hack banjo tooie=0
hack zelda=0
hack alpha=0
hack z=0 -
Also, about just using normal retropie, I can't get ssh nor samba to work and the file transferring became impossible for me to figure out without doing it within raspbian. I tried putting it into another computer, puppy linux, but that didn't work either for some reason. Even if I were okay with flip flopping SD's lakka doesn't work with composite though does link usb (despite my voltage problem I COULD do that) to the files and retropie I just can't get to work that well even on it's own. I enabled usb transfers but didn't see the usb drive inside of retropie, only outside of it in the gui that raspbian has.
The small console text does not help either. In raspbian it's easier to see.
-
@full-pixel said in mupen64plus-gles2n64 small screen in the bottom left hand corner still not fixed following instructions.:
Also, about just using normal retropie, I can't get ssh nor samba to work and the file transferring became impossible for me to figure out without doing it within raspbian.
Install the desktop on RetroPie and start it from EmulationStation - https://retropie.org.uk/docs/FAQ/#where-did-the-desktop-go.
-
I have it where it boots to console as it is and typing startx + enter to get to the gui or emulationstation + enter to get to retroarch already.
I've messed inside the console trying to change settings and also in retroarch but I'm pretty sure that if it's possible to fix it for a pi 3 that I'm goofing it. The very tiny size.
Or am I missing the point of something here? I'm an eternal noob really.
-
@full-pixel said in mupen64plus-gles2n64 small screen in the bottom left hand corner still not fixed following instructions.:
What older version of raspbian do I use? Are you saying no version of raspbian can install the newest retropie?
not the latest. but if you're new you should follow first installation and use the official image, which has a supported version of raspi os: https://retropie.org.uk/docs/First-Installation/
dual booting, manually installing, i feel like you're adding layers of complexity to this. official retropie image with the default n64 emulator will not show this issue as far as i'm aware. transferring roms/files is all covered in the docs.
and if the n64 games don't work still, verbose log please: https://retropie.org.uk/docs/Runcommand/#launch-with-verbose-logging
-
I'll have to design my frame to have easy access to the sd I suppose (or get retropie to read txt files so it can be a book reader along with a video game playing device) but why does that link's video not match what's written? Also why can't you just directly paste in the roms and or bios into the directories if you were to say put the retropie sd into a Linux machine with access to roms and bios? If you can isn't the instructions making things more complex than they need to be? If you have to use two computers anyway why does it have to be ssh, samba, or this odd creation of a pi specific usb (and relinking directories using a console to make sure that the usb works (along with turning off the usb transfering)).
-
I don't understand what I'm doing wrong with the console. It's not working.
First I Disable USB ROM Service script within retropie's gui, then exited to the console and:
sudo mv -v /home/pi/Retropie/* /media/usb0/ mv: cannot stat '/home/pi/Retropie/*': no such file or directory
Then I tried
sudo mv -v /home/piRetropie/* /media/usb)/dev/sda1
And it told me 'cannot stat'
Then I tried just to see if I was doing things backwards
/dev/sda1
And it told me permission denied basically.
But on the bright side the non-usable retropie has much better resolution and scaling than my raspbian + retropie so far.
And like I said before the video doesn't match.... I'd try basically transferring the roms but this spare sd is only 16 gb and my other raspbian is 32, my roms are too big for it.
Edit: I've been forced to forgo most of my psx titles to compensate and just use retroarch's blue bios tier file manager to copy things over other than most of the psx. I suppose that's what I have to do.
Edit: can't I just put a library folder in the root of the retropie's sd and then use nano or something to read txt files? Possibly neither here nor there, but the gripe behind wanting to have two OS's is that I can't read a book.
-
You need to use the proper casing when entering the commands you've copied from the docs. Linux filesystems are case sensitive and
/home/pi/Retropie
is not the same file as/home/pi/RetroPie
(1st command you posted) - the error tells you the file/director cannot be found. The rest of the commands are similar, you've omitted characters or added some extra ones - make sure you follow the exact syntax of the command from the doc page, othewise you'll get errors.You can use
mc
(or just start File Manager from the RetroPie system) for a file manager with text interface, if you want to navigate/copy/view files and not enter commands manually. -
Regardless sound isn't working no matter the fact that it can detect my sound card so that's my current issue. That and I accidentally pasted in my small psx collection outside of the psx folder and it would not let me delete it for some reason to try again within it's file manager. Also I tend to pay attention to case so I'm not sure that's the issue with how it was getting my F6 and F7 mixed up and other things.
It only lets you select through the jack and not usb sound card despite detecting the sound card within it's gui. I just don't get it. I'd use lakka but they don't easily work with composite and most of it's nightly versions were allowed to be deleted. Lakka easily links to usb but is it's own ball of troubles.
It plays nicely in fullscreen though, after I pasted the n64 and such in. Just no sound so I may just go ahead and do without n64 considering it's making my pi only able to do one thing, play games (silently). Mednafen has the same issue of silence with my usb sound card on the newest raspbian os but the older plays the have sound while being extremely slow, even gb emualtion. This begs the question should I downgrade my retropie to get the sound driver working? For the record both 2018 raspbian and 2021 actually have sound output, just not in mednafen for the newer and for the older it works in both.
Is it normal for the keyboard to start glitching the F's around though?
Edit: I guess it needed a reboot. The sound is working but I think I'll just connect it to a puppy linux next time I want to paste files around, thanks. Though I've not done it yet as this card is merely primarily "my n64 emulator distro" anyway as it is.
-
@full-pixel said in mupen64plus-gles2n64 small screen in the bottom left hand corner still not fixed following instructions.:
It only lets you select through the jack and not usb sound card despite detecting the sound card within it's gui. I just don't get it.
The audio menu is for configuration only for the on-board audio. If you want to use an USB soundcard, then disable the onboard sound and the system will use automatically the external USB card.
-
I probably did that too, trying to turn it off, before rebooting but assumed the rebooting fixed it. I had edited my post saying that it was working while assuming the reboot did it. Thank you for the clarification as otherwise people reading my posts would be mislead if they had the same issue.
It's working okay now all things considered. I'm surprised at how well the scaling works as on the raspbian + retropie the text is harder to see and the borders are a bit off even in the terminal. I should try to copy retropie's font to my other sd cards with raspbian + retropie on them to make the console more visible.
-
It's working okay now all things considered. I'm surprised at how well the scaling works as on the raspbian + retropie the text is harder to see and the borders are a bit off even in the terminal. I should try to copy retropie's font to my other sd cards with raspbian + retropie on them to make the console more visible
Glad you got it sorted out, actually RetroPie is using Raspbian (RPI OS) Lite underneath, so there's no specific font that's included in RetroPie.
Maybe the borders' position have something to do with the Overscan settings for the display ? Or you may try to increase the font size from the Setup script, as explained here ?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.