|
Post by elmer on Dec 11, 2021 20:05:39 GMT
|
|
|
Post by turboxray on Dec 11, 2021 20:27:51 GMT
Yeah, that's MrJ. He had some experience with porting mednafen to other platforms. He's doing some pcedev and was trying to get some things added to mednafen - that's the repo he put up for adding development features.
|
|
|
Post by elmer on Dec 11, 2021 20:33:15 GMT
Cool ... I can't find that name in the members list I take it that he doesn't hang out here then?
Do you have any idea of what he's trying to add to mednafen?
|
|
|
Post by dshadoff on Dec 11, 2021 20:56:00 GMT
He's looking to fix various aspects of the emulation, which is really showing itself to be sub-optimal these days.
I've been talking with him on Artemio's discord, and I was thinking of layering on your happyeyes debug fixes, as well as a few of my own... are you interested in doing the same ?
|
|
|
Post by dshadoff on Dec 11, 2021 21:00:07 GMT
By the way, he was encouraging using the "issues" log to post items which need to be fixed, kind of a "TODO" list.
|
|
mrzonk
What's a PC Engine?
Posts: 3
|
Post by mrzonk on Dec 12, 2021 0:08:19 GMT
Hi everyone, yes, that's me trying to see if we can move Mednafen forward collectively (if even a little) in support of the PCE Dev community at large.
I was looking into doing some minor 240pSuite updates when making a dedicated SGFX version when I just ran into wall after wall trying to do some testing with Mednafen as-is. So thoughts I'd document a train-of-thought doc for people looking to do the same simple PCE Dev work like me from scratch.
Having ported and supported Mednafen over on other portable platforms like iOS and tvOS, I thought I'd give this new pceDev16 GH Repo a shot and see if others were supportive and think it would help the community at large.
Nice to meet everyone here!
|
|
|
Post by ccovell on Dec 12, 2021 7:43:38 GMT
Hey, since we're on the topic of HappyEyes Mednafen, these hacks make the font in the hex viewer smaller to fit more pages of data on-screen. This doesn't make my eyes as happy as the larger hex view font in the old Mednafens. Is there a way to configure all of these?
|
|
|
Post by elmer on Dec 12, 2021 16:10:23 GMT
Mednafen hard-codes most of these values in the source itself, and so it's not really "configurable" as such. In the case of the memory debugger, it was actually using a smaller font than the one in "happyeyes", but the display is so small (in pixel terms) that it triggers mednafen's code to double the screen output ... which then makes the font larger on the users screen, but with lower resolution (which looks terribly cheesy to me). "happyeyes" just uses the same font size as the disassembly text, on the theory that if it's large-enough to read on that screen, then it's large-enough to read on the memory debugger screen. From the practical standpoint of how do you get the old memory screen back, but still use the other "happyeyes" features that you want ... this is one of the reasons that I decided to make the project as a bunch of "feature" patches instead of a repository of the mednafen source. If you take a look at the "mednafen-1.27.1-expand-watch.patch" and remove (or tweak) the individual patches that you want to apply, then you can change the memory screen how you wish ... assuming that you then use the script to build mednafen, which has unfortunately got a lot harder with v1.27.1! <EDIT> Honestly, we're not getting any younger ... there is a good argument to be made for using a larger font on *all* of the debugger screens. "happeyes" uses a 6x9 or 6x13 font instead of mednafen's tiny 5x7 font, but there are larger fonts available if we start using a 1024x768 debug display instead of 800x600 (happyeyes) or 640x480 (mednafen).
|
|
|
Post by dshadoff on Dec 12, 2021 17:34:34 GMT
I suppose this is a function of how large your screen is... I've been debugging on desktops and large-screened laptops... ...But I seem to recall that it was also a function of the resolution of the screen itself, in terms of what the multiplier is for scaling the output.
That is to say, the first time I used elmer's adjustments, the debugging screen only covered about 60% of the total area, until I made some adjustments to output scaling. I don't recall the details at the moment, but I may be able to look into this again.
What is the resolution of the screen you're using ?
(Or maybe I just selected a different font for the display, which filled out the screen better...)
|
|
|
Post by dshadoff on Dec 12, 2021 22:02:41 GMT
Following up on this, the happyeyes changed the default resolution on screen from 640x480 to 800x600 (at least for my old version).
I ended up using these settings for my specific circumstances (a MacBook Pro using Mednafen in windowed mode under Linux in a VM):
pce.debugger.disfontsize 6x12
pce.shader none pce.special none pce.stretch 0 pce.videoip 0
pce.xscale 8.50 pce.xscalefs 1.000000 pce.yscale 8.50 pce.yscalefs 1.000000
I have a vague memory of making the transparency more opaque as well, though I'm not sure if that's code or settings.
If your screen is perhaps more like 1024 or 1280 vertical, then 800x600 won't end up as a nice multiplier... I don't have any problems resizing for a larger display area in such a case.
|
|