Hi,
usually I use a CVT resolution for AO486, but I also have an ini with a lot of custom video modes, e.g. for real dos resolution, Jazz Jackrabbit ect.
Did not use them for some time now, but today I tried and nothing is working anymore... I always get "out of sync". I'm using a VGA-Monitor with an HDMI to VGA-Converter (always did). Does anyone can give me a hint what's wrong here? I would very much appreciate it.
Here is my ini:
I have an older version of MiSterFPGA on an SD-Card, where the ini is still working like it should: Wonderful DOS-Mode.
I tried older Versions of AO486, but it seems not related to the core itself... anything else I can test?
I did recheck the DOS-mode line again and it seems right to me:
[ao486]
video_mode=720,15,108,46,400,13,2,34,27983,0,1 ; 720x400@70.1Hz@31.48kHz DOS Text
direct_video=0 ; use the scaler
vsync_adjust=2 ; set to 2 above
vscale_mode=1 ; set to 0 above
video_info=5 ; show resolution information for X seconds
hdmi_limited=2 ; 1 - use limited (16..235) color range over HDMI
; 2 - use limited (16..255) color range over HDMI, for VGA converters.
Total Horizontal Pixels:
720 + 15 + 108 + 46 = 889
Total Vertical Lines:
400 + 13 + 2 + 34 = 449
Pixel Clock: 27.983 MHz = 27,983,000 Hz
HSync frequency:
27,983,000/889 = 31.47kHz
VSync frequency
31.47kHz/449= 70.1Hz
Still have no idea why nowadays this results in 26,9khz 60hz.... 
Sorry, no hint, more of a you as well!?
My setup is running a direct_video HDMI -> 15kHz CRT monitor, and it was working fine about a two years ago. But now I can't get it to sync.
I've been going through the old AO486 to TV thread testing each modeline, with no luck, and I distinctly remember that at least 2-3 of them were working before..
edit
That's one sweet beige VGA screen you've got there btw 
OK, I guess the culprit somehow is MisterDB9. I have an Antonia Villena Mister and a "normal" one. Usually I use the DB9 version. I took two new SD cards and reinstalled Mister from scratch on both of the devices.
Result: On the "normal" distribution, AO486 resolutions are working fine as they should. On the DB9 fork, it is not working and shows the above mentioned wrong refresh rate.
Does anyone have an idea who might be interested in this issue? I would do more testing if I knew what files might be responsible for this. The AO486 core seems not to be the problem because I tried older ones with the same bad result.
Thanks.
I just double checked and swapped the SD-cards. Normal distribution to DB9 MiSter and DB9 SD to "normal" MiSter. The error moves with the SD-Card. So my conclusion is, it must be a DB9-Distribution bug. Still I have no idea what to do with this conclusion...