Recent Posts

.

Have some new left overs I would like to sell.

First up is a custom mame arcade machine backlit style marquee.

New Backlit Printed Custom Arcade Mame Marquee 26-3/4 X 7-11/16

Nice quality backlit marquee, I ended up going with a different art set is all, item is still new and flawless Asking $28 shipped or best offer.

Hard drive failure? Maybe clean connectors on HD?

Hello
I do not understand really how to diassemblly and add the new iron into the clutch
May do you have any picture to see it better ?
Thanks in advance!!

Sorry, no pictures... this is already a pain to do, let alone document it... but if you are at this point of rebuilding the clutch... you likely already know this thing.

again, if you are at the point of needing to disassemble and rebuild this clutch... you already know how to disassemble it. This isn't a casual maintenance instruction set. This is the last-ditch repair instruction. This instruction includes information other threads on the subject lack... concrete information. None of the other threads about this contain any concrete information.

The pure number of threads I discovered out there where someone posts about trying to find or fix the MPC's and there has been replies like "oh yeah, i got ALL the stuff and i'm gonna rebuild it... i just don't have the time" is ridiculous and tantamount to school aged children saying "I can _______ , I just don't want to"

gettin real tired of feeding bots and algorithms. Utilize the concrete information and your concrete will work fabulously.

also, my current favorite interest is throwing broken tools into the algorithm and seeing how the information is indiscriminately absorbed and inserted without any rational thoughts.

 
Awesomesauce Danny!

Hello

I found another issue, related to the font size.

with groovymame277 the text is unreadable in the menu. (readable in the mame 277 non patched)

searching into the patch file, I found in the file src/frontend/mame/ui/ui.cpp
this change :
    float const one_to_one_line_height = float(raw_font_pixel_height) / target_pixel_height;
 
    // determine the scale factor
-   float scale_factor = target_font_height() * scale / one_to_one_line_height;
+   float scale_factor = std::min(target_pixel_height / float(raw_font_pixel_height) / options().font_rows(),
+                        target_pixel_width / float(raw_font_pixel_height) / options().font_rows());
 
    // if our font is small-ish, do integral scaling
    if (raw_font_pixel_height < 24)



I think the expression target_pixel_width / float(raw_font_pixel_height) / options().font_rows()
should probably be target_pixel_width / float(raw_font_pixel_width) / options().font_rows()

but I guess the get_font()->pixel_width() doesn't exist....

I removed this change, and the font size is readable again...

I attached a path file includng the correction.

I am now flying this on my own. So far I've put around 9 hours on it on my own. Mechanic put an hour or so on it initially, and several hours with me. So there's about ten hours minimum left before we can submit the test paperwork to make the plane fully registered.

So you can now tell people you know a test pilot 😁

It will only allow me to upload one more photo. If I try to do more it tells me that my photos felt security check. So I can't upload the rest to show you the board. You'll have to just accept what I was able to give.

I currently have three motherboards that are doing the exact same thing. Status one light stays illuminated while status 2 flashes. I've noticed that U53 seems to be resetting with the status to life. I just received an oscilloscope and I have a logic probe. My voltage is good. I just have no idea where to begin with trying to get this thing working. I'm attaching all the photos that I have of it. I do have a compact flash card with the correct game files so I can put that up when the time comes.

I find it kind of strange that I can have three of these that are doing the exact same thing. The chip at U14 is getting warm but I can touch it and leave my finger there without burning. 

There is no know bug for Rabbids, when using correct dumps and when everything is set up as it should
But there are a lot of ways to have it not working, or partially working because of the number of different pre-patched files existing on various dumps (and sometimes not compatible)

I can't say anything in your case, not untill you can share a demulshooter debug file to check some details
See here:
https://github.com/argonlefou/DemulShooter/wiki/Debugging#step-3