Main » Emulation » Final preparation complete! XTREME OCD » New reply
    Alert
    You are about to bump an old thread. This is usually a very bad idea. Please think about what you are about to do before you press the Post button.
    New reply
    Post help

    Presentation

    [b]…[/b] — bold type
    [i]…[/i] — italic
    [u]…[/u] — underlined
    [s]…[/s] — strikethrough
    [code]…[/code] — code block
    [spoiler]…[/spoiler] — spoiler block
    [spoiler=…]…[/spoiler]
    [source]…[/source] — colorcoded block, assuming C#
    [source=…]…[/source] — colorcoded block, specific language[which?]
    [abbr=…]…[/abbr] — abbreviation
    [color=…]…[/color] — set text color
    [jest]…[/jest] — you're kidding
    [sarcasm]…[/sarcasm] — you're not kidding

    Links

    [img]http://…[/img] — insert image
    [url]http://…[/url]
    [url=http://…]…[/url]
    >>… — link to post by ID
    [user=##] — link to user's profile by ID

    Quotations

    [quote]…[/quote] — untitled quote
    [quote=…]…[/quote] — "Posted by …"
    [quote="…" id="…"]…[/quote] — ""Post by …" with link by post ID

    Embeds

    [youtube]…[/youtube] — video ID only please
    Thread review
    RokkumanX @Screwtape

    I solved the problem, in my Super Famicom.bml I specified the region to 
    region:   SNS-XJ


    It should be 
    region:   SNS-XJ-USA


    This little piece of information helped me solve the problem:


    The region field is mandatory, and is used by higan to determine the regional hardware and TV frequency variants used for proper emulation. When game serial numbers are present that include the regional information within them, these values are used. In the simple example above, the region ends in -JPN, which indicates the game is from Japan, and uses the NTSC standard. In the complex example, -USA obviously implies the game is from the US. If the game serials are not known, the value will be up to the emulated system's requirements.


    Thanks for all your help though! It looks like higan v106r52 is my choice for Super Famicom/Super NES emulation now.
    Screwtape I'm not familiar with the specific higan revisions you're talking about, but 'region' is usually an option in the "Load Game..." dialog, in the bottom left. It's possible that byuu reworked how region detection worked at some point and you picked a revision where region detection happened to be broken.

    In general, if you want to be sure everything works as intended, you should be using official releases (higan v106, bsnes v107.3) rather than WIPs.

    > Everything in the .bml files is correct, there is nothing I could change?

    The game's manifest.bml describes what's unique about a particular game, boards.bml describes what's unique about a particular board, but "region" is a property of the base console.
    RokkumanX Damn, and I don't see any options in this particular version of higan to change region either.

    Every game I have besides Star Fox 2 boots, what is bsnes doing different than higan? I don't see an option in bsnes but it boots there just fine.

    Everything in the .bml files is correct, there is nothing I could change?

    Not that Star Fox 2 is a "super" game I care about but still it would be nice if every of the 24 games I have boot instead of 23.

    I must continue to investigate.
    CaptainJistuce
    Posted by RokkumanX
    OK, this is really weird.

    Star Fox 2 (USA) works great in bsnes v107.1 but in higan v106.52 I'm getting this message:

    This game pack is not designed for your SUPER FAMICOM or Super NES


    I don't even know how this could happen, am I missing something here?
    Sounds like it is booting the game in PAL mode and it is angry.

    Games can detect the frame rate, and some will use that to enforce regional lockouts on people with lockout bypass devices or modifications.
    RokkumanX OK, this is really weird.

    Star Fox 2 (USA) works great in bsnes v107.1 but in higan v106.52 I'm getting this message:

    This game pack is not designed for your SUPER FAMICOM or Super NES


    I don't even know how this could happen, am I missing something here?
    RokkumanX I'm using pre-built higan binaries from the GitLab Jobs page.
    I would gladly use higan v106r85 but the Blur and Color options is broken, something I need I'm afraid.

    higan v106r52 seems quite stable, I haven't had an issue yet and it's as barbone as it gets for my taste (I like clean and simple emulator GUI's)

    However nothing is written in stone, the heavy ground work is done and now starts the work with what version to use.

    I rather not using anything latest of higan, I'm no rocket scientist but those versions is way to complex for me to use. I don't understand a thing of how to run games on them.
    Screwtape Were you building higan/bsnes from source, or downloading pre-built binaries? If you're building from source, be aware that often higan and bsnes are built from the same source-code, and which one gets built by default often depends on what byuu happened to be working on at the time. In particular, v106r85 builds bsnes by default, which would account for why it "had the similar looks like bsnes". To be sure you're building higan, you need to say:

    make target=higan
    Also note that bsnes v107 is forked from on higan v106r85 so they should be similar emulation-wise. r85 was just before byuu started rebuilding the higan UI, which was very experimental for quite a while, so if you want something newer than r85, you probably want to use the latest version (or the latest version of bsnes).

    Looking at the changelog, it seems the last SNES-related change before r85 was r66 which I think fixes a problem with save-states for games that use the SPC7110 chip; everything between those two seems to be MSX/WonderSwan/NGP emulation. There's other minor SNES-related changes in the revisions before r66, too.
    RokkumanX So I've spent some unhealthy time pulling this off but this is the end result of dozens of hours (researching, testing and making)

    Super Famicom.bml



    boards.bml



    Everything here is customized to utter perfection, every game I dumped have the same exact board as the physical cartridge in my shelves.

    I even splitted the boards in the boards.bml so every board is it's own "unique" board. The SHVC-1L5B is a good example of that because it's SHVC-1L5B-(11,20) in the original boards.bml whereas it's SHVC-1L5B-02 SHVC-1L5B-11 and SHVC-1L5B-20 in mine.

    The contents in Super Famicom.bml and boards.bml is sorted perfectly accordingly to my OCD standards, I'm a sick puppy.

    So the question now is what version of higan to use? Well I made quite a few tests and reached to this conclusion.

    Most of the newer versions with the drastically reworked UI don't seem to boot anything no matter how many times I import my games, the complexity of higan is astounding to say the least.

    I worked my way down and found out that v106r85 had the similar looks like bsnes, only problem there were that the Blur and Color options did absolutely nothing so that ruled out the possibility with those versions.

    Worked my way even lower and hit the sweet spot between v106r52 - v106r44
    It looked decent enough, my games worked and most importantly the Blur and Color options worked correctly.

    It's such a joy to look in the Manifest Viewer now when everything looks so clean.

    There is absolutely no way I'm going through all of this again so either v106r52 or v106r44 have to do, Super Famicom emulation in higan is pretty much perfect since way back right?
      Main » Emulation » Final preparation complete! XTREME OCD » New reply
      Powered by AcmlmBoard XD, version 2.2.5-Lambda
      By Kawa, Arisotura, Nadia, et al
      AcmlmBoard © Jean-François Lapointe
      Page rendered in 0.099 seconds with 21 MySQL queries.
      This does not actually go there and I regret nothing.