MiSTer FPGA Forum

I've made a fork for the template and pull requested it. I've also forked the Genesis core, including an rbf of my latest version of that. Haven't put a pull request there, not sure if I should.

Anyways, I've done what I can. Hopefully it gets approved.

Interesting. Do you think you could do the same with the ao486 core? Resolution switching while adhering to Resolution and AR would be cool. I'm not really familiar with the ao486 core, not having used it before today, but I downloaded a freedos vhd and did a build of the ao486 core with the changes in it. Unfortunately it doesn't seem to do anyth...

I’ve also got a 2.4ghz M30 that I’m using for MiSTer, the type that plugs in to an actual mega drive. I think that it’s not possible to map the shoulder buttons and c and z separately on mine because the signal needs to be compatible with the original hardware. I think it can be done when plugged in via cable rather than wireless. Not sure if the U...

I have this same device (well, the V3), and I cannot for the life of me get it working. I’ve taken ioev’s .ko file (which is for V1 but marx said worked for them with a v3) and put it in lib/modules/4.19.0-socfpga-r1 and have rtl8188eufw.bin in lib/firmware/rtlwifi. I’ve edited wpa_supplicant to have the id and password, and removed the underscore ...

Can someone please specify the custom aspect ratios that are needed to get full integer scaling with a 6:5 pixel aspect ratio on NES, Genesis, and SNES? I see 64:45 posted above - is that value correct (I've seen 64:49 posted other places), and does it apply to SNES and Genesis also? Thanks. I recently posted a build of the Genesis core with a men...

So there would be no need for aspect ratio settings if one wanted perfect pixel mapping? Also, this will theoretically work for games that change resolutions during game play? I think I remember Vay for Mega-CD changes resolution for battles. Depends what you mean by perfect pixel mapping. If you mean 1:1 pixel aspect ratio, you can do that alread...

Yes to the first, not necessarily to the second. This doesn’t do anything to the vertical scaling, but since you can already set the MiSTer for integer vertical scaling this does allow both. The aspect ratio of the whole image will not necessarily be “perfect” because integer scaling limits your choice of aspect ratios since you upscale in large st...

I've made a mega drive build of this - I just copied the changes from sys_top.v and ascal.vhd into the genesis core sys directory and added a menu option for it in genesis.sv, I didn't spend a lot of time thinking about whether it would work. Fortunately it does seem to work, at least at first glance. It's here. I haven't had much time for testing,...

Would this solution also allow for integer horizontal scaling with aspect-correct vertical scaling (which usually will result in a border)? This doesn’t do anything to the vertical scaling, so it won’t make that easier but it won’t stop it either. I think you’d have to turn vertical integer scaling off and use the vertical border adjust to get the...

I went with an option in the OSD partly because I knew how to make one already and partly because for testing it was better to be able to turn it on and off and switch between narrow and wide on the fly rather than having to edit mister.ini and reboot every time. If the option were changed to be in the the ini file then I think it would be possible...

LamerDeluxe wrote: ↑Wed Feb 10, 2021 12:30 pmIt is a lot of hassle though. An option to set horizontal integer scaling, or for both directions, would be much easier.

I may have some good news for you.

There's been a fair bit of talk lately about using custom aspect ratios with vscale_mode 1 to get integer scaling both horizontally and vertically. This works, but it's a bit of a nuisance. I've had a fiddle with the SMS core and implemented automatic horizontal integer scaling as an OSD option which can be set to round the scaling multiple to the ...

In my experience this depends on a lot of different factors. If you are using the stock power supply from the DE10-Nano and a usb hub addon board you will often run into an issue where you are undervolting something among these. That can cause issues. Is this a common problem? I recently switched from a cheap unpowered external hub to the daughter...

t9999clint wrote: ↑Tue Jan 05, 2021 5:27 pmwhy the MiSTer isn't detecting the controllers on the retrode2.

Bit of a late response here, but I was able to use a mega drive controller on MiSTer through my retrode2, so it is possible. I think I just plugged it in and used the define function in the OSD, no particular tricks to get it going.

Integer pixels should avoid shimmer whatever shape they are, so long as every pixel in the image is made up of the same number of screen pixels, as you say. Shimmer as I understand it is caused by image pixels changing size as they move across the screen. Regarding your new screen, what video mode are you using? The amount of vertical scaling will ...

Good outcome! I was only thinking of digital displays rather than CRTs, but if it works that’s good. I think more stuff gets done by the TV in the back porch than the front, so if there were problems it might make sense to take a few pixels away from the front porch and put them in the back (maybe 2048, 30, 44, 78). Is it necessary to have so much ...

The pixel_clock of video_mode=8 runs at 148.5. I calculated the minimum required pixel clock for 2048x960 to be 138.2547 mhz. So it seems the pixel clock is indeed not the cause in this scenario (or I'm calculating the required frequency wrongly). I think you’re right if you’re looking to have the MiSTer output 2048x960, the problem is that unless...

I guess I’ve been wrong about 2048 being a hard limit for the mister’s horizontal resolution. Whoops. I think I’m starting to get my head around this pixel clock thing, but it’s still pretty confusing. From the MiSTer GitHub, video.cpp, the full details of mode 8 are: { { 1920, 88, 44, 148, 1080, 4, 5, 36 }, 148.5 }, //8 As I understand it, the mea...

I'm still struggling to understand the workings of the pixel clock, but I think this boils down to resolution. I set up a couple of very wide custom aspect ratios for my SMS core and gave them a shot running on video mode 8 (1920x1080). At 1080p the SMS's vertical resolution of 192 is multiplied five times to 960. 28:15 - this works out to 1792x960...

I haven’t tried this, but I think you could get horizontal only integer scaling by setting a ratio of (integer upscale):(vertical resolution set by video mode), because the default scaler behaviour is to fill the screen vertically. For example, if you’re running a 256x240 core on 1080p, you could set 1280:1080 for a five times horizontal integer up...

I think the issue is that mode 12 is a 4:3 aspect ratio at 1440p, so it’s not that 1440p isn’t supported, it’s that wider aspect ratios that give horizontal resolutions above 1920 won’t fit. Apparently horizontal resolutions above 2048 aren’t supported by the MiSTer at all. I think the same issue would apply for mode 13, which is 2048x1536, also 4:3.

Thanks for the explanation. I’ve always kind of just gone off what looks right to me or tried to figure it out from images of original hardware running through CRTs.

I don’t have a screen capable of 1440 so I can’t test anything, but I notice that on integer scaling at that resolution 32:21 should give a resolution of 2048x1344. According to this post 2048 is the maximum mister can put out horizontally, so maybe it’s to do with running so close to the edge? Actually, looking at mister.ini, video mode 12 gives 1...

Genesis has a separate setting for 320 and 256 resolution aspect ratios, doesn't it? I think only the main setting has custom ratios though. Regarding the SMS, changing the aspect ratio makes no difference to the vertical resolution on my system. I have what appear to me to be consistent square pixels on the default setting, and I can get 6:5 pixel...

Can you explain further the relevance of the pixel clock? Are you just using it to figure out what the aspect ratio would be on a CRT and so what the target aspect ratio should be for upscaling on HDMI?

I think whether these figures give perfect pixels depends on the resolution used. At 1080p, a core with an internal resolution of 240 will be scaled 4x to 960 vertical pixels. If you use the NES example of 256x240, setting the aspect ratio to 5:3 will give a horizontal resolution of 1600 (five times one third of the vertical resolution, so 960/3 = ...

I think the only way to force it to 4:3 if your TV doesn’t have an option for it is to have the mister output at the full resolution of your TV (presumably 2560x1440?) and set the core’s aspect ratio to 4:3. Then the image sent to the TV will be 16:9, but the active area in it will be 4:3. But, according to this post , you can’t set it above a hori...

I fired this up on my region-modded PAL Mega Drive, I found there was slowdown on the Bridge running at both 50 and 60Hz, but I think it was worse at 60. The first hornet caused noticeable slowdown on NTSC but only a little if any on PAL. The falling bridge caused slowdown either way.

I basically did it this way because this is the way I could figure out how to do it, so I'm not opposed to having separate aspect ratio settings for the two horizontal resolutions (can you have separate custom aspect ratios for the different resolutions, though?). That said, I do feel this is an accurate way to approach the original hardware since ...

It shouldn’t do. The point of this is to provide a consistent resolution, so the aspect ratio doesn’t need to change. There is the question of what the correct aspect ratio is - a 1:1 pixel aspect ratio gives a 4:3 screen aspect ratio. This sounds right for old screens, but the SMS usually ran with borders above and below, so the actual aspect rati...