buzz880

This was great. I Have all my videos created, hopefully this will reduce my attract mode issues simply by having everything 100% on the same Codec. I was thinking though I should have used a codec that is native to windows 8.1 so I can get rid of Shark 007 completely. SO that might be the next step if I have more issues. Thanks!

Sadly my problem has returned! I stand by my original solution as that was a repeatable issue with the LED Plugin the way I had it configured. AS of last night I am getting the same error as before only nothing has changed with the Ledwiz setup. I have made other big changes though: - Installed Zeb's Digital Plunger with Analog Nudge - tried disabling it in Device Manager and deselecting it in VPinball settings and still get the same error so I don't think thats the cause (Also cleared all Joystick Controls in PinballX). - I did experiment with using pinmame inside the frontend, I gave up on that and put it back how it was config-wise. SO I do not know why any time I try something different I have to go back to the drawing board on this error though I am glad at least one other person has seen it.

Interesting. I'm actually trying running PINMAME inside the PINBALLX Frontend right now but I can't seem to get it to scale right so maybe yours is the answer. I'll try it later. Thanks!

Update: I'm not quite ready to say it is totally resolved but it is significantly improved, here is why: - I Figured it was Codecs so I downloaded a freeware called Mediainfo - When I looked at all my video files in MediaInfo, 15 or so of my DMD Videos reveal themselves to be AVI, even though the extension was MP4. These will play in PinballX just fine if I run them alone but it seems like when combined with PF and BG eventually things get wonky. - I took those files out of the directory and am now 3-4 hours without a complete lockup or crash. I do think it still hangs briefly a little here or there but that is nothing compared to what was happening. So fingers crossed for now. Also, if anyone knows a good freeware to re-encode these DMD video files, let me know? I tried Super and a couple others but even on HQ settings I'm getting a much lower quality result. Thanks!

Solved! (For Realz this time). After BOP crashed just now I realized there was some documentation in there that outlined what the script that keeps crashing actually does. *DOF method for rom controller tables by Arngrim********************'*************************use Tabletype rom or em********************'*******Use DOF 1**, 1 to activate a ledwiz output*******************'*******Use DOF 1**, 0 to deactivate a ledwiz output*****************'*******Use DOF 1**, 2 to pulse a ledwiz output**********************Sub DOF(dofevent, dofstate) If cController=3 ThenIf dofstate = 2 ThenController.B2SSetData dofevent, 1:Controller.B2SSetData dofevent, 0ElseController.B2SSetData dofevent, dofstateEnd IfEnd IfSomething about this reminded me of the PinballX LED Plugin works so I disabled the LED Plugin and Voila! Problem solved. I liked the way I had the LED Plugin working so I will go back in later and see if maybe it was just an issue with how I configured it but at least I know what I'm dealing with going forward. As a bonus, I had implemented a few performance tweaks when I was stuck in DB2S standard mode and they didn't do enough to make me happy then but now that I am back in EXE mode things are the best they've ever been performance-wise. Good-Night!

I have the same issue with Cirqus Voltaire and Apollo 13 (Most recent tables). Essentially the identical thing. Completely unplayable. So what These and MM have in common is they all rumble the shaker for effect (I do not have a gear motor). MM when you hit the castle gate, Apollo 13 immediately when the table launches because it moves the rocket... CV when you hit the trigger the ringmaster. It is these events where it crashed with the exact error I show in my first post. So I assume the problem will also exist in a bunch of other tables also. If someone can explain to me why this is an issue only when I launch with PinballX and only if the Backglass is in EXE mode I would really appreciate it. Otherwise it shall be back to Hyperpin because I am completely stumped on this one... Even if someone out there has NO issues with these tables launched in PinballX, let me know, I can probably learn something.

I know I've had the issue with other tables as well but here is the one I have spent the most time trying to get working (It is my favorite): Medieval-Madness_NightMod_LoadedWeapon_1.1 http://www.vpforums.org/index.php?app=downloads&showfile=10157 Here is one of the db2s files I have tried - I've tried a couple versions the result is the same. http://www.vpforums.org/index.php?app=downloads&showfile=9332 So if anyone knows what Pinballx is doing that is different than what happens when I simply launch the table directly, or via Hyperpin, that would be a big help. I do not want to give up running tables like this with backglass in EXE mode because of the performance advantage. Thanks!

Thanks I did try that, same result. Works in STANDARD mode not in EXE Mode.... unless I launch from outside of PinballX in which case it works perfectly. Unfortunately table performance is perfect in EXE mode but not in Standard. I should mention I had at least one other table with the same issue I just don't recall which. Its weird because some work in EXE Mode, some don't. There is another thread on here where a guy had a similar issue related to the gear motor... when I get the error in MM its right after the castle is hit so if I had a Gear Motor it would run when the drawbridge opens so I tried his script changes last night, no result. I don't have a Gear Motor and have not enabled it in my directoutput.ini file but I tried his fix anyway - no improvement. I redownloaded the table and am back to the beginning after that.

Hi this is a follow up to an issue I had that I thought was resolved. (Thread now locked entitled Crash: Index Out of Range) I was getting an Index Out of Range crash, particularly in the Loaded Weapon 1.1 Medieval Madness Nightmod as soon as I hit the castle. I fixed it and thought it was good but realize because the fix required me to NOT run the DB2S in EXE mode I am taking a significant performance hit. Is there any reason I cannot reliably use EXE mode when launching this table from PinballX and is there a workaround? It is 100% fine launched from Hyperpin or directly. Most other tables seem fine either way. Thanks.

This is where I started. There is nothing in event viewer that I see. Its a fresh Windows 8.1 install on a dedicated machine and I've been careful about what I let schedule itself. The thing is it doesn't seem to happen if I use the PinballX default DMD video exclusively so that would tend to rule out other processes being a factor I think.

Sorry was at work when I posted that. Here are the ini and log files attached. log.txt PinballX.ini

I've seen others with similar, but not identical, problems though I have not seen a fix that works for me. Even if someone can give me a starting direction I'd appreciate it, at the moment I am thinking it is Codec related. That said, I have the same issue with both Shark007 and Windows 8.1 standard Codecs. The only difference between Shark and standard Codecs is I do get a crash with an error more often with the Shark ones, whereas the standard package Hangs without error more often. I'd say the failure rate by one means or the other is about the same. I have Backglass, DMD and Table Videos all running. It seems to be fine if I remove all DMD videos except the PinballX default one. If I use my full DMD collection it might go 10 minutes, even 30 minutes before it hangs or errors. When it hangs it is totally non-responsive. Sometimes it comes back in 4 or 5 minutes, sometimes it does not. At first I thought it was a corrupt video file so each time I would remove the last video accessed. This did not seem to improve the outright failure rate. It certainly does not happen on the same video every time. PinballX 1.95 Windows 8.1 x64. Thanks!

***Edit: I re-downloaded the table and changed the ROM to 109b from 109c that I was using before and I can no longer recreate the issue. So for now it seems to be resolved though I'm not sure what I actually did to fix it. *** This example is Medieval Madness (Physmod, Nightmod), The first time I hit the Castle I get the error. Table plays fine if not launched through PinballX. I read somewhere on this forum I should not run the DB2S in "EXE Mode" so I switched that off, no difference. Error is: Line 70: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: Index Line 70 reads: Controller.B2SSetData dofevent, 1:Controller.B2SSetData dofevent, 0 Log and ini are attached Thanks! log.txt PinballX.ini