| Megadrive overclock [message #4722] |
Sat, 24 December 2016 10:57  |
|
In new build (updated cpu core):
max_md_timestamp = Main68K.timestamp * 7;
removing *7 - caused drop fps. Only if I decreased timings in new m68k " / 2", then it's not cause drop fps. But can I get more overclock?
|
|
| Re: Megadrive overclock [message #4723 is a reply to message #4722 ] |
Sat, 24 December 2016 23:38  |
|
|
What do you mean by "drop fps"?
|
|
| Re: Megadrive overclock [message #4724 is a reply to message #4723 ] |
Sat, 24 December 2016 23:57 |
|
fps:
34
17
17
only removing *7.
Attachment: snapshot1.png
(Size: 752.41KB, Downloaded 182 time(s))
|
|
| Re: Megadrive overclock [message #4725 is a reply to message #4724 ] |
Sun, 25 December 2016 01:07 |
|
|
What sort of CPU are you using?
|
|
| Re: Megadrive overclock [message #4726 is a reply to message #4725 ] |
Sun, 25 December 2016 01:55 |
|
System:
AMD x4 Athlon 3.4 GHZ
Nvidia gt 640
Overclock worked good until m68k update.
FPS dropped also on other PC's with other specifications.
Looks like z80 and m68k desync...
|
|
| Re: Megadrive overclock [message #4727 is a reply to message #4726 ] |
Sun, 25 December 2016 03:09 |
|
|
What exact commands are you running to compile; e.g. "configure" and "make", and any parameters/environment variables passed to them?
|
|
| Re: Megadrive overclock [message #4728 is a reply to message #4727 ] |
Sun, 25 December 2016 03:15 |
|
$ ./configure --host=i686-w64-mingw32 CC=i686-w64-mingw32-gcc CXX=i686-w64-mingw32-g++ CPPFLAGS="-D_LFS64_LARGEFILE=1" SDL_CONFIG=/usr/i686-w64-mingw32/sys-root/i686-w64-mingw32/bin/sdl-config
make -j5
|
|
| Re: Megadrive overclock [message #4729 is a reply to message #4728 ] |
Sun, 25 December 2016 03:28 |
|
|
Is the attached custom overclocked build(with the * 7 removed) any faster than the build you made?
|
|
| Re: Megadrive overclock [message #4730 is a reply to message #4729 ] |
Sun, 25 December 2016 03:52 |
|
Benchmark tests are same. Only fps different. In your build is okay - 60fps.
completed config.log
Attachment: config.log
(Size: 474.74KB, Downloaded 151 time(s))
|
|
| Re: Megadrive overclock [message #4731 is a reply to message #4730 ] |
Sun, 25 December 2016 05:50 |
|
|
Is your mingw toolchain using sjlj or dwarf2 exception handling? The former is known to be slower, though I'm not sure if it could explain the poor performance you're getting in this case.
|
|
| Re: Megadrive overclock [message #4732 is a reply to message #4731 ] |
Sun, 25 December 2016 06:27 |
|
libgcc_s_sjlj-1.dll
If you mean this
|
|
| Re: Megadrive overclock [message #4736 is a reply to message #4732 ] |
Sun, 25 December 2016 14:53 |
|
If that DLL is used by the executable you compile, then yes.
Somewhat related: https://wiki.qt.io/Mingw-64-bit#Exception_handling:_SJLJ.2C_DWARF.2C_and_SEH
Official 32-bit Windows Mednafen builds use DWARF/dw2, and the 64-bit Windows builds use SEH.
|
|
| Re: Megadrive overclock [message #4738 is a reply to message #4736 ] |
Mon, 26 December 2016 11:38 |
|
|
Compiled with msys2 on windows. Now 60 fps. Thank you! Interesting, but with overclock my CPU loaded to 50℅. And your overclocked build load cpu same.
[Updated on: Mon, 26 December 2016 22:41]
|
|
Members 
Search 
Help 
Register 
Login 
Home 
Attachment: mednafen-0.9.39.2-mdoverclock-win32.zip
]