@mitu

I've just installed LXDE and try again but nothing changes. I don't know if it helps but if i power off the display and/or detach from VGA it doesn't work; only thing is to close ES. I still think it is an ES issue...i don't know.

I will do other tests.
Thanks

@simpleethat thanks for the info. Yeah, they are both 16x9, 1080 is 1920x1080 and 720p is 1366x768. I think everything is set to 1920x1080 on my pi currently. Hoping to find out if I have to change any settings to step down to 1366x768 (720p) for proper framing?

@mitu I haven't noticed anything strange with hdmi1 so I'll stick with that. Thanks for the effort :)

@redfirebrooks said in Cant set resolution.. Really it is that easy ?:

i'd like to find a working out of box retrogaming system !

Well, RetroPie isn't meant to be one in every case and aspect. It's an community-driven, freely given DIY project.

That said, RP works ootb in many if not most cases. But if you happen to be one of the unlucky exceptions, you'll have to either put some time and effort into it, or move on to another system in the hope that that one won't have the same problems with your setup.

You're free to choose whatever suits your needs best, but complaining about it in every of your posts in this thread so far distracts you and everyone else who are willing to invest their spare time for your problems from actually working on a solution.

I have it on a Raspberi pi 4 with retro pie 4.6

Without any configuration necessary, RetroArch should use the current set video resolution without any issues. This looks like you have some other resolution configured somewhere ? Is this a fresh installation ?

Ok, thank you. I'll give a try with those options.

Removing the curvature removes the morié pattern completely:

Which is a shame...I really love that curving for the old school feel, especially for the 2600 where there weren't any Trinitron sets yet!

@YFZdude @mitu @dankcushions

It was the freaking port.

I connected it to the second port and booted it up, then started playing around with the config again. Lo and behold, hdmi_group=1 didn't cause a catastrophic error! The rest was cake, thanks to you guys.

Very much appreciated, thank you so much for all your help!

@goldug said in Runcommand messes up resolution for some reason:

because I hadn't changed anything, but yes, it seems there is now for some reason.

You added something, there is nothing in stock RetroPie that creates those files automatically.

@YFZdude Alright man you are the winner, I had been doing config edits all day yesterday and tried both HDMI-D ports during those edits, and at some point at the end of the night when I did the hdmi_group 1 and hdmi_mode 16 edits I did not test the cord in the primary hdmi-d slot as I had thought.
It figures the one edit I added in that actually works is the one I stopped testing both slots on.

I have the pi 4 in a case so remembering which slot was the primary was my user error.
What a nightmarish night for something so simple, thanks again to everyone in here that helped out. It runs in 1080p now.

Edit: The resolution to the problem was having the hdmi cord plugged into the primary slot (nearest the usb hub) on the pi 4. User error.

THANK YOU @dankcushions !

Your pointer was half of the solution so let me write the other half in case anyone else searches for this answer.

Setting the resolution in the retroarch Options menu did not have any effect until I also turned on "Alternate render method" in the same menu. At that point all resolution changes took immediate effect (upon leaving the retroarch UI) and now this all works perfectly.

I will write up the rest of my method to launch rom-less system soon!

Thanks again.

Note: if you implement my GPU Hard Sync tweaks from https://retropie.org.uk/forum/topic/27431/howto-major-performance-boost-on-retroarch-based-emulators you'll need to keep both shaders and bilinear filtering disabled.

I dont know what was the problem first time flashing but formatted and reflashed now its working.

This is the results of vcgencmd get_config int.
enable_dpi_lcd and display_default_lcd are set to 1.

arm_freq=1500 audio_pwm_mode=514 config_hdmi_boost=5 core_freq=500 core_freq_min=200 disable_audio_dither=1 disable_commandline_tags=2 disable_l2cache=1 display_default_lcd=1 display_hdmi_rotate=-1 display_lcd_rotate=-1 dpi_group=2 dpi_mode=87 enable_dpi_lcd=1 enable_gic=1 force_eeprom_read=1 force_pwm_open=1 framebuffer_ignore_alpha=1 framebuffer_swap=1 gpu_freq=500 gpu_freq_min=250 init_uart_clock=0x2dc6c00 mask_gpu_interrupt0=1024 mask_gpu_interrupt1=0x10000 max_framebuffers=2 over_voltage_avs=-23750 overscan_scale=1 pause_burst_frames=1 program_serial_random=1 total_mem=4096 hdmi_force_cec_address:0=65535 hdmi_force_cec_address:1=65535 hdmi_ignore_edid_audio:0=1 hdmi_pixel_freq_limit:0=0x11e1a300 hdmi_pixel_freq_limit:1=0x11e1a300

@Weatherby said in Pi4 default resolution won't work:

The Pi3 runs smoothly at 4k though, it just gets hot as hell.

Pi3 doesn't support 4k, it's probably choosing 1080p as the best display resolution.

I am not sure what the deal is with the audio not working on the HDMI1 port

That's the default. You can switch it from the Audio menu.

on arcade games in its intended resolution there is black bars at top and bottom because its on 1280x1024 when I try drop the resolution lower on launch options the game wont load up for some reason, just the sound and a black screen.

I can go into option during the game with the 1280x1024 and change the screen to fit but I have to do that for all games it's a bit annoying.

Retropie 4.6 on a raspberry pi 3B with a 128gb Card.

My guess this happens because you specifically set the resolution somewhere - either in /boot/config.txt, or in each individual RetroArch core.
EmulationStation and emulators (including RetroArch) should pick up the current resolution and run in fullscreen, without the need to set the resolution.

sure! didn't want to imply that, it just was a major roadblock for me yesterday and today and a lot of searching around just showed that a bunch of people had the same problem. the solutions with manually editing the config file sure help but it would have been just so much easier if I could have set it in the menue. not because editing the file is difficult, more like you don't think of it because everything else just works like it should (well, beside the playstation classic controller not working despite being a simple USB device) and the config tool just blanking out is confusing. honestly if the whole system wouldn't crawl around at around 10 - 15fps at 4k you wouldn't even notice the problem is there to begin with. I'll search if the problem is known at Raspbian.