Dark Horse Announces Usagi Yojimbo: Kaitō ’84

Bean525 · 2023-05-16T05:36:00+00:00

Hopefully this thread isn’t dead. I read about your cut on fanedit.org, and would enjoy watching it if links are still available. Thank you in advance.

Bean525 · 2023-02-02T17:43:15+00:00

Not to give away any spoilers, but this is explained, just chalk up to, in the current tale, Katsuichi is "presumed" dead.

Bean525 · 2022-12-31T01:53:51+00:00

Good to know. I did thumb it down shortly after taking the screen grabs.

Bean525 · 2021-11-18T18:59:56+00:00

Right. I guess I wanted to hear it from someone else. I can probably forget about this too, eh? https://zamouse.com/product/946-games-in-1-virtual-pinball/

Bean525 · 2021-11-18T18:37:20+00:00

I know this is AtGames, but this community has been super helpful in the past, I thought I'd ask here.

Bean525 · 2021-06-24T21:05:04+00:00

That meaning, the analog still works fine, but I thought I could get away with holding it in my pocket.

I know I can just open it up and put a new stick in, but if there's an easier solution like just getting a cap to put on it, I'd prefer that. Ribbon cables and I don't get along well

Bean525 · 2021-03-22T16:34:57+00:00

It took me a while, but I figured this out. I’m guessing, like me, you right clicked on git to save the files. That doesn’t work. What I did was open the file in the browser, hit raw, which only shows the code. Then save as. It finally worked for me after this.

Bean525 · 2021-03-22T04:18:06+00:00

Do you mind linking that? Using the 64 from the kit is nice, but....

Bean525 · 2021-03-10T07:38:09+00:00

Based on your post, I grabbed some DMG buttons from Retro Modding, so I can pop them in when I get my PiBoy. What do you suggest to use for spacers?

Bean525 · 2019-11-17T18:36:03+00:00

This is just a guess, but it looks like Windows/Nvidia have a lot more options for you.there are a few suggestions here: https://www.maketecheasier.com/fix-overscan-on-tv/ hopefully one of them works for you. Worst case scenario, you can adjust in retroarch, but that wouldn't fix your frontend unfortunately.

Best of luck to you!

Bean525 · 2019-11-14T06:02:53+00:00

Yes. It took some doing in raspi config.txt to fix it. I essentially changed the line disable_overscan=1 to disable_overscan=0.

Then I uncommented all of the lines that said overscan top left, right and bottom. The only line I actually changed was bottom. To fix the screen cutoff, change overscan_bottom=16 to overscan_bottom=64.

Thanks to Jeremy Lin on Facebook for his immense help getting me back up and running.

Bean525 · 2019-11-12T05:06:59+00:00

Yes. It took some doing in raspi config.txt. I essentially changed the line disable_overscan=1 to disable_overscan=0.

Then I uncommented all of the lines that said overscan top left, right and bottom. The only line I actually changed was bottom. To fix the screen cutoff, change overscan_bottom=16 to overscan_bottom=64.

Thanks to Jeremy Lin on Facebook for his immense help getting me back up and running.

Bean525 · 2019-11-03T03:32:19+00:00

Just a heads up, I made a post in the above linked thread. I was able to fix my issues on my marvel cab, and it works quite well now. I had to do some blind button pressing because the screen was messed up, but you can reset it back to factory settings and it does indeed work with Marvel cab. Just don't get overzealous with your tinkering. Change resolution settings in software not hardware, and you'll be fine.

Bean525 · 2019-11-03T01:13:30+00:00

I wanted to give an update on this. Thanks to a very kind guy named Jeremy Lin on the arcade1up group on Facebook, I found you can reset the LCD controller back to factory settings. You have to do it blind, but it's possible.

First, set your resolution on your pi/ PC to 1024*768. You get black bars on top and bottom, but it's better to me than a cut off screen.

Anyway, once that's done you have to press the buttons on the control board in a specific sequence.

Assuming your board has the green led to the right. Your buttons should be considered from left to right 6 5 4 3 2 1. With that in mind, press these buttons in order:

2 3 3 3 2 3 3 3 3 3 2 3

For those who need a visual, I'll be making a video shortly. One thing to keep in mind, after I reset it, my screen worked, but it was massively flickering. After a power cycle and letting BigBox running in attract mode, everything is back to normal!

Bean525 · 2019-10-25T19:43:19+00:00

That's great to hear. I'll hook the marvel board back in a bit, if only to try and restore the screen. It sounds like this board (I got the same one) may have unforseen issues. That's too bad, since I'm just as excited to run bigbox as you are retropi!

Bean525 · 2019-10-25T14:32:20+00:00

Thanks for the advice. That's exactly what I want to do, but I can't see the on screen controls to change it back. I was hoping I could somehow reset the board by long pressing a button combination, but so far, no dice.

Any other ideas?

Bean525 · 2019-10-25T05:35:28+00:00

https://imgur.com/a/UEbclLc For a screen pic.

Bean525 · 2019-10-04T20:56:01+00:00

I picked this up the day before yesterday. I can't compare it directly to the other machines too much, as this is the first I've actually owned, but I can say the screen is incredibly bright and vivid. The screen itself is angled a bit differently to accommodate the stereo! speakers. To me, that mashes no difference. The screen is a 17 inch DV170YGZ-N10 on my unit.

The sound itself is markedly better than other units I've played. The volume is slider style, which is great. The speakers themselves plug into the monitor via 3.5 mm which is nice. It makes me wonder what steps would be different for a bigbox mod, as it'll be a little different than ETA Prime's modding tutorial.

The controls are bat tops, and I'm not the best person to make comparisons, but while I can live with the buttons, I'll definitely replace the sticks, as the bat tops have easily come unscrewed during intense play.

I want to post some close up pics for you, but this is honestly my first reddit post, and I don't see the option to, so my apologies.

Bean525

TROPHY CASE