ericharbison

> Funny, I was about to post about a similar issue. I don't remember this happening with Model 3, I'd have to double check. But this happens with MAME, I've...

I took a look at the code. Looks like SuperModel 3 and MAME use the same code in the FFB plugin. I haven't setup FFB in MAME yet, but will...

I think I figured it out. I changed the exit code in MAMESupermodel.cpp to this: static int __stdcall ExitHook(UINT uExitCode) { //TerminateProcess(GetCurrentProcess(), 0); MH_DisableHook(MH_ALL_HOOKS); Sleep(1300); ExitProcess(0); return 0; } I...

I think I need to give up. I seems like it has something to do with not freeing the MAME.dll library on exit or possibly something else on exit. I...

I think I have it officially working. In the MAMESupermodel.cpp file I changed: First I moved the HWND hWnd; outside of the WinMain() function so that I could access it...

Let me do a little more testing first on different machines.

I found some oddities on another machine. This code listed below seemed to do better. if (StopConstant == 255) { MotionFalse = true; triggers->Constant(constants->DIRECTION_FROM_LEFT, 0); triggers->Constant(constants->DIRECTION_FROM_RIGHT, 0); StopConstant = 0;...

I don't think renaming the files does anything. When I have some time I want to see if I can fix the WndProc destroy. It doesnt appear to be running...

Im rewriting the ffb code to not use the mame dll directly. Im getting closer to finishing.

I think I finally have it working. I made extensive code changes to the MAMESupermodel code to separate out the MAME dll from the code. I got that working but...