[RESOLVED] Problems running db2s in EXE Mode

[buzz880]

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.

[jaharr01]

try uninstalling and reinstalling the table. If you change the name sometimes you get that error. Some are more finicky than others. Also check and make sure you changed the controller from Vpmame to b2s

[buzz880]

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.

[buzz880]

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!

[buzz880]

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.

[buzz880]

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 Then

If dofstate = 2 Then

Controller.B2SSetData dofevent, 1:Controller.B2SSetData dofevent, 0

Else

Controller.B2SSetData dofevent, dofstate

End If

End If

Something 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!

[tthurman]

Based on the view to response ratio, your problem seems to have been pretty unique. That or others simply haven't had the misfortune to stumble upon it as of yet, and so it's great that you figured it out.

Your persistence paid off for sure, congrats!