Recent Posts

This is unrelated to arcades but during my time on this forum I have read several threads that lead me to believe that someone on here might be able to help me out.

I use a CAD/CAM program called Alphacam at work to fabricate stone countertops. It has VBA integrated that allows us to create macros to automate the repetitive aspects of the job. We have an extensive automation system setup.

There was one item left out of the API for the version of Alphacam we have. The ability to read the state of the autosnap function from the VBA API, or a way to force autosnap into a known state (either on or off). The only thing we can do is toggle it (if it’s on, it turns off, and vice versa) but without being able to tell its current state we don’t know when to toggle.

I currently have an ugly hack in place to detect its state so we can decide to issue the toggle command to put it into the state we want but i’m looking for something better.

There are multiple thread here about hacking programs to get the state of features in game finding memory locations to rwad to add controls or force feedback, etc.

Would it be possible to write a small command line program to find the memory location that stores the autosnap state in alphacam and return a value when the program exits? I have the ability to run such a prpgram from our alphacam macros and import the value it returns. This would be a good solution it it could work.

How would I go about this? Any assistance appreciated.

Okay I think I know what you are saying. What is a wall wart by the way? Do you mean the wall plug?

If it can't dim that is fine. Just being able to turn it on/off would be great.

BUMP
I found second Big Blue (I'm too lazy to take a new photo)
So now I am offering 2 big blue knobs for 1 black one if anyone is interested!

I can't understand the need of setting on the fly an EDID for modeswitching. That is almost absurd : you need to trigger a read of the EDID at OS level. This is slow, has got a massive impact on the OS. So why ?

Price reduced to $150. I hate to toss this in the trash.

One thing to note - not sure if you can place it on it's screen to transport? It doesn't have supports to protect the backside. Maybe you can seatbelt it in upright, too.

Why not use the geometry tool with switchres?

I am happy to see they are selling another variant here:

OK ... so far I figured out:

-The gun tracking backwards was due to the "TOP" logo not being set or the camera being rotated in the wrong orientation - got that all sorted.
-The tracking is still pretty jumpy - going to work on getting more IR light out of these LEDs ... or maybe I guess I need diff LEDs/diff resistor ... setup ... (using 37 ohm 0.5w)
-Looks like I had to have the trigger wired up to make it through this menu (for some reason I though I could use CTRL on keyb or something ...)

Hello,

First Gun4IR build - I am currently hitting an issue after attaching the Camera.
When I go through calibration I'm unable to make it through due to error:

The 4 IR points must be detected in the camera preview:


In the image we can see that there are 3 points detected ... but if I back up further I can see all 4 ... but I still can't do calibration.

I thought at first, this was due to the IR LEDs not being bright enough - but all LEDs were emitting light fine - I then went as far as to bridge one of them in each cluster to make the other two brighter, as I thought maybe the IR LEDs perhaps were not bright enough ... I'm not thinking this is it though (please let me know of your thoughts though).

I've gone through testing here and made a video to share, please take a look - the one strange thing: It's hard to see but: near the end you can see that the tracking of the mouse picked up in the OS, despite jumping around quite a bit, seems to be tracking backwards when moving the gun left to right .... I thought I must have a wire backwards but checked the wiring diagram (pdf and videos) and I seem to have it correct.  I've even taken out my 2nd camera (for my second gun) and wired that one up and my issue is identical.

Thoughts on what I'm likely doing wrong?

other than trying random things like "0000" "1111" "1234" there was no default code... JVL had no code originally so someone put one on there.

you'll have to reset the system to clear out the code...as it's stored in the IO board. you'll have to remove the battery on it to clear the memory in it (difficult in this machine, as it's soldered in place.)... then boot it up and reset or reinstall the software to original state to totally clear it out and start fresh.

there is a good chance your IO board is going to need the battery replaced anyway... now is a good time to do it.

that said, if someone who owned this machine had megatouch machines too, they may have reused the code from that to keep them the same...the code for those is "4123" and older ones "4777"

if you do manage to get in, you can clear out the code, or change it to something you will remeber.