Everly

[Everly]

I had some time yesterday to do some more troubleshooting on my cabinet and try to figure out this problem.  What I found is interesting but sadly I don’t think it will result in a solution.  One thing that has been emphasized is the need to completely exit BAM (not just closing the table and opening another in the same BAM session)  I don’t know what possessed me to do this but here is the sequence.

I open BAM and load and launch F-14 (DMD stays blank)

I exit the table but leave BAM open and the table loaded in the editor then relaunch (DMD now shows the PUPScreen#1 video and Overlays as expected)

At this point if I load any other table the DMD will work so long as I close the table but leave BAM up and open the new table in that same session.  This also seems to work with the Jaws table but will not work with RetroFlair or Death Star Assault.  After the initial launch of F-14 or Jaws when the DMD stays blank, as long as that session of BAM stays open, the DMD will work on all my PinEvent tables.  However on RetroFlair and Death Star Assault I have white rectangles on the playfield. (big one on DSA where the X-Wing usually sits and the left side of the apron and the stream over the Ms. Pacman sign on RetroFlair)  Those rectangles will only go away if I completely close BAM and launch a new session, which then makes the DMD no longer work.

Hopefully that info provides an Ah-HA! moment for someone so we can figure out what is going on.

I tried disabling the PUPStream in the PinEvent Settings but that had no affect on these issues.  Thanks in advance for any help anyone can offer.

You need to login in order to like this post: click here

[Everly]

TerryRed wrote:

Did you set your pupdmddrivertype = 1 for Real DMD in PinEvent_Settings.vbs ?

You should have PUP Stream disabled until you have everything working correctly (as it can cause problems for some ppl)

Don’t enable Custom Settings in the table script, as it’s not needed (normally, unless one table needs a different pupdmd setting)). All the settings in PinEvent_Setting.vbs are used by default for all tables.

Based on the DEBUG output… you seem to have all PinEvent options set correctly (yay that debug worked and helped).

So the only other problem left is pupdmdcontrol or dmddevice.ini not setup right or working (since PinEvent is all setup and running correctly). Can’t help you much with PinDMD3, but I know its common for people to have problems with it… but it does work.

If you can’t get your real DMD working for whatever reason…. then you have another option.

Set pupdmddrivertype = 2 (FullDMD), and use either the “FullDMD on Backglass” pup-pack option (for a 16×9 backglass monitor), or use the “AIO” pup-pack option (for square / 4×3 / 5×4 monitors). Then you can use FP Intercept for your real DMD to display FP’s DMD (since pupdmd is not using the real DMD).

Yes, my PUPDMDDriver is set to 1 in my Pinevent Settings.vbs

I will try disabling the PUP Streams and see if that changes anything

Yes, the Use Custom Settings is set to false in the table script

I’ll look into changing the driver type and report back on any changes it causes.  The only other piece of troubleshooting information I can offer is that on the Retrofire table I am getting the PupOverlay 1 displaying on my DMD but not the video for PupScreen 1.  I will double check next time I have some pinball time and confirm the script settings for both tables are the same and report back.

You need to login in order to like this post: click here

[Everly]

Alright, I have been working on this for about 4 months now and haven’t found a solution.

PROBLEM : I cannot get my Real PinDMD V3 to display the video and overlays from PupScreen1 from PinEvent Tables.

I am running Windows 10 on a 2 screen setup (Playfield and Backglass) with the PinDMD V3

In my Pinevent Setting ini file I have my Cabinet Setting (Option #2) with all of the variables set to True except useFP Sounds is set to false and Night Mode is set to 2.  I’ve spent the most time working on the F14 Tomcat table.  In that script I have the PinEvent Profile setting set to 2 and the Use Custom Settings set to False.

PUPSCREEN1 is set to 512 x 128 for the 4:1 Ratio

Popper Doctor will mirror the TEST DMD image correctly.  FX3 tables show on the DMD and Non-PinEvent Future Pinball tables (such as Major Frenchy’s Mod of Pink Floyd) show on my DMD as well.

I have selected the Option #1 Real DMD for the PUP Pack.

When I run the table in Debug Mode (F9) the following information is displayed…

PinEvent 1.4 – by TerryRed: June 2020

PinEvent_Variables.vbs 1.4 loaded

PinEvent_Settings.vbs 1.4 loaded

PinEvent – Cabinet Profile

PUPDMD Default = 1 REAL DMD

PinEvent_Control.vbs 1.4 loaded

PUPDMD = 1 REAL DMD

Start DOF

Start PUP

PinEvent_PUPDMD.vbs 1.4 loaded

BAM Version: 317

PuP Plugin has started

PS-BackBox_AIO disabled, or PUPOVERLAY not detected

PuP Stream-FullDMD-using PUPSCREEN5

PuP Stream-Backglass-using PUPSCREEN2

PuP Stream-Apron Left-using PUPSCREEN5

PuP Stream-Apron Right-using PUPSCREEN2

PuP Stream-PF_Screen-using PUPSCREEN5

 

From the readout it appears the PUPDMD is set correctly in the table and should match the PUP Pack I’ve selected for a REAL DMD.

If I Alt-Tab I can see PUPSCREEN1 running with the video of the fighter jet over the water and I see PUP Overlays 1 also active but neither are being displayed on the PinDMD v3.  This is all being done manually outside of a front end launch as is recommended.

You need to login in order to like this post: click here

[Everly]

@dazz – Sorry it took me so long to reply to this.  I did get it working.  The general tab you posted looks about right.  Here are my opening and closing scripts.  As you can see they could used cleaned up as there are a number of REMark lines.

rem PC GAMES.
rem - for PC Games, you need to specify what each game "TITLE" is called in the "Custom Launch Parameter" in "Games Manager" for every PC Game.
rem -[CUSTOM1] is the "Custom Launch Parameter" in "Games Manager" for your selected game.

START "" "[STARTDIR]Launch\VPXSTARTER.exe" 5 1 5 “nowindow”

cd "c:\Pinball\MyBingoPrograms"
START "" /min "LaunchBingoGameRoom.exe" "[GAMENAME]"

rem LAUNCH PC GAMES. This will launch your PC game using either a shorcut (lnk) or a BAT file, depending on what you setup in the emulator settings.

rem START /WAIT "" "[GAMEFULLNAME]"

Closing

START "" "C:\PinUPSystem\Launch\PUPCLOSER.EXE"

In terms of the DOF Linx setup, the only line I adjusted in my ini file was under MISC SETTINGS to include LaunchBingoGameRoom

######## MISC SETTINGS ########

# The list of processes that can activate DOFLinx, such as Pinball FX3, Future Pinball, etc.

PROCESSES=Pinball FX3,Pinball FX2,Future Pinball,mamelayplus,LaunchBingoGameRoom

I’ll be more responsive moving forward, I know what it is like to have a problem and how appreciative I am that Nailbuster, TerryRed, and Major Frenchy have been willing to help me thru it so I’m happy to finally be on the helping end.

You need to login in order to like this post: click here

[Everly]

OK, you guys are NOT going to believe this.  So in my efforts to get PinEvent up and running on my cabinet, one of the things I did was update my DOF Config files even though I had just got them refreshed about 2 weeks ago.  That was what happened.

Looking through the DOFLinx log I saw it referencing the ROM FP_PinkFloyd.  I remembered a previous post from Terry that Amgrim was going to add files to the DOF Config Tool and it clicked in my mind that the ROM it is reading is probably from my directoutputconfig30.ini file.  So I opened it up and scrolled down to that section and saw this..

fp_multipede,0,0,0,0,0,0,0,0,0
fp_noes_slam_ultimate,0,0,0,0,0,0,0,0,0
fp_noes_ult_pro,0,0,0,0,0,0,0,0,0
fp_oblivion,0,0,0,0,0,0,0,0,0
fp_paragon,0,0,0,0,0,0,0,0,0
fp_phantom_ultimate,0,0,0,0,0,0,0,0,0
fp_pinevent,0,0,0,0,0,0,0,0,0
fp_poc,0,0,0,0,0,0,0,0,0
fp_reelitin,0,0,0,0,0,0,0,0,0

So…where is the Pink Floyd table?  I went on to the DOF Config site and looked up the table and all of the MX codes are there.  So I generated another config file and this time FP_PinkFloyd is in the list with the associated codes.  So I dropped it into my folder and launched the table and my lights are back.

So for some reason when I got my config file on 5/3 and again today the FP_PinkFloyd table was in the list but when I generated a file yesterday it wasn’t there and I have been beating my head against the wall trying to figure out what I did that caused my MX effects to disappear and for some reason I just had a corrupted/incomplete config file I was working off of.

I still have the issue of my flipper feedbacks firing constantly only on FP tables now, but Night Mode is a bit of a solution for that and PinEvent runs them perfectly, and that was really the reason I was working to get FP up on my cabinet.  Looking forward to Death Star Assault.  Thanks everyone for the help and I hope I was able to document what I ran into to help anyone else that is having similar issues.

You need to login in order to like this post: click here

[Everly]

TerryRed wrote:

DOFlinx is a completely different thing to PinEvent. The tables won’t give you any info. You need to run DOFLinx in it’s own DEBUG mode, which is enabled in the doflinx.ini

Yeah, I thought about that later and checked my DofLinx.log.  I had it set to Debug=2 earlier so I was capturing info.  From looking at the log it certainly appears I am establishing a link.

15-May-20 19:59:59.237 – DOF Linx for Pinball Emulators – DOFLinx by DDH69
15-May-20 19:59:59.362 – Starting up – version 7.14
15-May-20 19:59:59.362 – For support come and visit the community here http://www.vpforums.org/index.php?showforum=104
15-May-20 19:59:59.362 – Pre-Reading DOFLinx.INI startup config file details
15-May-20 20:00:00.128 – DEBUG enabled with showing of window False
15-May-20 20:00:10.841 – Found Teensy controller named ‘LEDStripController’
15-May-20 20:00:11.099 – Joystick # 1 detected : 32 buttons Z-Axis
15-May-20 20:00:11.317 – DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
15-May-20 20:00:11.317 – DOFLinx device:1 Pinscape setup with 65 outputs
15-May-20 20:00:11.359 – DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0
15-May-20 20:00:11.359 – DOFLinx device:2 LEDWiz setup with 32 outputs
15-May-20 20:00:11.374 – Reading DOFLinx.INI startup config file details
15-May-20 20:00:11.374 – Turning DEBUG off
15-May-20 20:00:11.374 – DEBUG enabled with showing of window False
15-May-20 20:00:11.374 – Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig30.ini
15-May-20 20:00:11.565 – Turning on checking for nudge during basic keybaord checking
15-May-20 20:00:12.610 – Set Debug Privilege = Set OK
15-May-20 20:00:14.716 – DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
15-May-20 20:00:14.719 – DOFLinx device:1 Pinscape setup with 65 outputs
15-May-20 20:00:14.720 – DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0
15-May-20 20:00:14.722 – DOFLinx device:2 LEDWiz setup with 32 outputs
15-May-20 20:00:20.079 – Found valid process name of ‘Future Pinball’
15-May-20 20:00:20.203 – Setting Future Pinball process ID to :5728
15-May-20 20:00:22.258 – Activated by process name : ‘Future Pinball’
15-May-20 20:00:22.263 – Named process detected and startup commenced
15-May-20 20:00:22.264 – 64 bit OS detected
15-May-20 20:00:22.819 – FP full name=C:\Pinball\Future Pinball\Future Pinball.exe Size=28547584 bytes, Dated 12/31/2010 12:23:32 PM
15-May-20 20:00:22.957 – Starting scan of FP process for DOFLinx code
15-May-20 20:00:44.001 – Starting scan of FP process for DOFLinx code
15-May-20 20:00:45.001 – Starting scan of FP process for DOFLinx code
15-May-20 20:00:46.000 – Starting scan of FP process for DOFLinx code
15-May-20 20:00:47.000 – Starting scan of FP process for DOFLinx code
15-May-20 20:00:50.001 – Starting scan of FP process for DOFLinx code
15-May-20 20:00:52.002 – Starting scan of FP process for DOFLinx code
15-May-20 20:00:58.001 – Starting scan of FP process for DOFLinx code
15-May-20 20:01:00.001 – Starting scan of FP process for DOFLinx code
15-May-20 20:01:03.002 – Starting scan of FP process for DOFLinx code
15-May-20 20:01:07.001 – Starting scan of FP process for DOFLinx code
15-May-20 20:01:09.806 – FP table running DOFLinx code found and link established
15-May-20 20:01:12.293 – Using full colour palette
15-May-20 20:01:12.295 – 122 colours added to the palette
15-May-20 20:01:12.317 – Loading DOF ‘Pinball’ with ROM=’FP_RETROFLAIR’
15-May-20 20:01:53.538 – Link is turning on device #8 for 50 milliseconds
15-May-20 20:01:53.541 – Link is turning on device #10 for 50 milliseconds
15-May-20 20:01:53.557 – Link is turning on device #4 for 50 milliseconds
15-May-20 20:01:53.601 – Link is turning off device #8
15-May-20 20:01:53.603 – Link is turning off device #10
15-May-20 20:01:53.616 – Link is turning off device #4
15-May-20 20:01:54.818 – Link is turning on device #2 for 50 milliseconds
15-May-20 20:01:54.882 – Link is turning off device #2
15-May-20 20:01:57.896 – Link is turning on device #2 for 10000 milliseconds
15-May-20 20:01:58.132 – Link is turning off device #2

The Pink Floyd table provides a similar log file that indicates a link is established and it is reading from a ROM associated with that table.

You need to login in order to like this post: click here

[Everly]

TerryRed wrote:

If DOFLinx is not able to make a LINK with a FP table that has DOFLinx support… then it will fallback to its “key to output” functions. This means that any FP table will make your flipper solenoids go off EVERYTIME you press the flipper button, no matter what is happening.

So you may not have doflinx making a proper connection to the FP Link for the table, and its just triggering your flipper solenoids on each button press.

DOFLinx works completely different than PinEvent. DOFLinx needs to use a workaround to open communication to FP. If that isn’t working the DOFLinx commands in the table won’t do anything for DOF.

PinEevent tables access and use DOF directly the same way VPX does (actually more direct than VPX tables normally do).

I’ll add more clarification to the guide. It says you “may” need to adjust UAC for DOF. This is true… in that UAC, Admin access all are part of the same problem. Sadly I can’t say one setting is right or wrong because everyone’s install and setup could have been done differently for DOF.. and that affects all of this. Luckily pup works fine for most as long as they didn’t mess with any pup files. :)

I have suspected that my DOF wasn’t completely correct on some tables, but it appears to be more than just the Key to Output.  For example, on the DofLinx version of RetroFlair when I hit the spinner on the left side my right flipper contactor engages for every revolution.  I notice that the LEDs in my buttons also flash in sync with it.  Almost like it is firing every output I have, but it is happening off of the spinner while I’m not pushing any buttons.  The PinEvent version doesn’t do that.  The bumper field triggers my mid field solenoids, the slingshots trigger those solenoids and I only hear my flipper contactors when I press my flipper buttons.

So I completely agree that I am not establishing a link with DOFLinx on these other tables.  I was experiencing similar performance with my FX3 tables.  After registering the Com Object file as Administrator I placed a couple of those tables and now they seem to be running more accurately.

Which brings me back to the fact that I must not being linking to DOFLinx with these FP tables, but I am getting MX effects that are accurately based on the events of the FP tables (bumpers, slingshots, launch ball effects)  So what can I check to try to figure out where my break is?  The Debugging code you put in PinEvent was very helpful as we could quickly see I didn’t have a connection to DOF.  I ran the DofLinx tables in Debug but didn’t see anything helpful.

You need to login in order to like this post: click here

[Everly]

Alright…made some major headway and I wanted to share what I think as going on.

Some time ago I had gone into UAC and set it to the lowest setting figuring that would prevent complications, but in the last part of that link to Nailbuster’s wiki I noticed this comment, “Everyone thinks that turning off UAC just shuts off some prompts, but it actually shuts down the whole system service that allows the desktop shell to elevate selected processes.” 

So even when you select files to run as an Administrator if this system is disabled it doesn’t really run that way.  So when I was running one of the few things that needs to be run As Admin (the RegisterComObject file) I really wasn’t.  I raised my UAC to the next lowest setting and ran the file.  It appeared to run the same way it normally does but now I have MX effects not only on the RetoFlair table but I got them back when I’m in the Pinup Menu front end.  It doesn’t appear that any of these programs need to be run As Admin, I just needed to actually run the RegisterComObject as Admin.

PinEvent now has access to DOF and in Debug I see Start DOF and Start PUP, so I am set to move into the next phase of setting up a PinEvent emulator in Pinup Menu so I can automatically pause DofLinx when I launch this table from my Front End.

This is the one oddball thing that I haven’t resolved yet.  Shortly before I started into wrestling with PinEvent I installed MajorFrenchy’s DofLinx MOD of the Pink Floyd table.  It plays great and I LOVED the MX effects.  For some reason in all of this I have lost the MX effects of this table.  I still have them on the DofLinx version of RetroFlair and Knight Rider, so I can’t figure out what happened there.  I also noticed that the DofLinx version of RetroFlair seems to fire my flipper contactors when almost anything happens whereas the PinEvent version is much more accurate.  The slingshots and bumpers activate the correct solenoids in PinEvent.  The Pink Floyd table still fires my feedbacks, but just like the DL RetroFlair my right flipper contactor is almost always firing to the point I often just press my Night Mode button to quiet it down.

Not sure if that last piece of info is a clue to what is happening or not.

You need to login in order to like this post: click here

[Everly]

TerryRed wrote:

Not sure if you have been here or tried this:

http://www.nailbuster.com/wikipinup/doku.php?id=dof_registry&s%5B%5D=dof

Yes, I went thru all of those steps back when I was trying to get my MX effects working when I was in my Front End just because I thought they would be nice.  But I went thru and verified everything.  The last step was to actually raise the slider in User Access Control up as that has solved the issue for some people and I did that and then went back and checked running things AS ADMIN and NOT AS ADMIN but no dice so far.

You need to login in order to like this post: click here

[Everly]

Thank you for helping work through this Terry.  I’ve been doing all of this with DofLinx not running and launching BAM and the table directly, not thru my front end.  I’ve gone through and confirmed that FP, BAM, and all other programs are NOT running as Admin.  I then followed the steps you gave.

• be sure FuturePinball.exe is NOT Run as Admin (Confirmed it is NOT ADMIN)
• set FPloader.exe to NOT Run as Admin (Confirmed it is NOT ADMIN)
• be sure the PinEvent vbs files are not blocked by Windows (I use 7-Zip and then looked at the properties on each and the “Unblock” button was not shown)
• be sure the COM Extensions file is not blocked by Windows (Didn’t see the “Unblock” button.  I do see COM Extension in the Plugin section within BAM.  The only option that is shown the security level which I have set to “Same as VPX Don’t Care”)
• disable all DOF and PUP options in PinEvent_Settings.vbs for the mode you are trying to use (Desktop, Cabinet/Arcade mode, VR) if the table now runs fine with DOF and all PUP features disabled… then PinEvent vbs files are working! (I adjusted my Profile #2 so that everything was false and the table loaded)
• now try enabling either DOF or PUP options (all pup features on or off together). Only one or the other!
  see what DEBUG window tells you to help narrow it down if you can get one or the other working on their own, that is good (I set my PUP options to true and the table loaded and the videos all played as expected.  In the Debug window I saw the line “START PUP”  When I only had DOF set to true I had no videos and the line in the Debug window said “DOF not Installed or Detected”.  When I had them all set to true I had the videos and the same line about DOF not Installed)
• you may need to Run FPLoader.exe as ADMIN or NOT as Admin. Try both. (Tried it but was the same)
• its possible that either DOF or PUP will work with Admin set one way, but the other may not
  if that is the case… then some of your pup files may be set to Run as Admin (and should NOT be Run as Admin) or your DOF install may be restricting access to FP because of security / admin issues
  ideally… nothing on your system should need to be Run as Admin at all so it all works nicely together (I also checked my UAC setting and it is set to the lowest possible setting.  Not sure how else to set it to help)

I also tried the parallel install that Coreduo had success with it didn’t work for me.  I still have DOF and MX effects working on the DofLinx version of the Retro table so that is good.  Not sure why I lost the MX effects on the Pink Floyd table, I still have the feedback on that, although almost every bumper wants to activate the flipper contactors and not the associated solenoid.  But one problem at a time.

So we know the PinEvent is working as it activate the videos, it just doesn’t have access to DOF and it appears that Pinup Menu doesn’t either for some reason.

You need to login in order to like this post: click here

[Everly]

coreduo0099 wrote:

I’ve got the 3 monitor setup PUP working fine with my 16:9 full lcd dmd and both this and halloween. They look great, just like your videos.

However my DOF does not work. I believe I’ve downloaded/updated everything. All of you previous FP MX/DOF tables work great with my MX/DOF setup.. including the prior Retroflair with MX/DOF. But when I launch the tables in F9 debug, FP says DOF is not installed/detected.

I’ve validated all checklist items but to no avail.

Any other ideas/suggestions out there?

I’ve done the following:

verified DOFLinux 7.14 and in debug see that it is paused by front end.

verified my directoutputconfig.ini has the proper ‘rom’ mappings

re-run RegisterDirectOutputComObject.exe

no UAC, verified bam plugin is there at lowest security

Run FPLoader as admin (always have)

no other futuredmd or the like running

EVERY PUP pack and DOF for FX2, FX3, FP game all work.

This is my exact situation.  I’ve tried reinstalling the R++ DOF Setup, re-registering the Com Objects, running FPLoader as Admin and not as Admin, and changing the script as Terry suggested.  When I modified the PinEvent_Control.vbs as indicated I started getting Mediation Errors on table start up.  When I changed it back I was still getting the errors somehow.  I also noticed I no longer have MX Lights on the Pink Floyd table that MajorFrenchy released, although I have solenoid feedback on it.

I saw in the Jaws table Coreduo did a parallel install in a different directory and got it working so I will try that as well.  Side note for me is that I have also had DOF giving me issues in PinupMenu.  When I run my front end I haven’t had my MX Effects for several months.  I’ve tried Popper Doctor but haven’t been able to make any headway.  Terry is confident that “something” is blocking access to DOF in certain situations and that is a theory that fits the facts, but I would LOVE to get this figured out because I do like the Retro table PinEvent features and if I could combined the DOFLinx effects for it (which are still working ironically) that would be epic.  And I know Death Star Assault is coming….nuff said.  So if anyone has some insight I’m all ears.

You need to login in order to like this post: click here

[Everly]

I told you to try running the FP BG in windowed to help narrow down what is happening… not as a solution to fix the problem.

(Whoa..flash back to 2nd grade when the teacher yelled at me)

I went into the Registry and changed the Second Monitor Height and Width to 1200 and 1920 and that got me where I wanted to be.  Now the BG fills the second screen as I hoped.  Thank you for the guidance.

I was also able to get my PinDMDv3 to display the DMD from Future Pinball tables, so that is a plus.  Now moving on to installing and testing the PinEvent files.

You need to login in order to like this post: click here

[Everly]

Thank you for the direction.  I see the affect that has but it isn’t want we are wanting.  I did notice that when I uncheck Full Screen the resolution is set to a landscape configuration (which my monitor is).  So I went with 1028×728 and that gave me a window of the right proportions in the center of the screen but I couldn’t resize it any larger.  In the BAM menu if I tried to scale it higher the picture would just start getting larger than the window but wouldn’t make the window any larger.

I also noticed that when I clicked Full Screen all of the resolution options I could choose from would be in a portrait configuration, like 728×1028 smaller number was always first.  I can change to the largest resolution but it is staying in portrait configuration and it won’t fill a landscape oriented monitor.

If any screen captures would help please let me know.

You need to login in order to like this post: click here

[Everly]

Just updating, I’ve reinstalled the Grander Unifier R++ for DOF but I’m getting the same results.  I have no antivirus running and use 7-zip so nothing should be blocked.  DOF is set to = true in the ini file.  I’m sort of like you, there isn’t much to it, so when it doesn’t work I’m not sure where else to look.

DOF works fine with tables, just not when in Pinup Menu, which is just my addressable LED strips.  I don’t know if the fact that Doctor doesn’t respond to any DOF ON Events when the DOF Driver type is Popper DOF is telling us something or not.

I’ve done everything in the wiki regarding the DirectOutput.ComObject.

You need to login in order to like this post: click here

[Everly]

I have, here is what I see.

In Popper Doctor the DOF Driver Type is Popper dof and the Dof Rom is pinupmenu. When I press Start DOF the log says Starting DOF, then DOF After INIT. No matter what I put in the DOF Element and Send DOF On nothing happens. If I change DOF Driver Type to DOFDirect I get an error message when I try to start it saying “The system cannot find the file specified, ProgID; DirectOutput.ComObject” When I press Stop DOF I get a message saying “Invalid variant operation” I’ve gone into the registry and tried working with the settings as indicated in your wiki but so far I haven’t figured out what the problem is. Hopefully, like the display needing set to Active and Update, you know another place I should look.

You need to login in order to like this post: click here

[Everly]

YES!!!!!!  Thank you so much David!  I have been trying to work that out for several months.  You and I actually talked about that when you were helping me work out the issue I had launching and exiting the Bingo tables.  Now I can really get my cabinet set up with a smooth selection process that gives a great end user experience.  Now I just need to figure out why DOF isn’t working when I’m in Pinup Menu.

Thanks again.

You need to login in order to like this post: click here

[Everly]

Ok, I have got the PUP Packs working again.  As near as I could tell it was the dll file.  The only way I can get PUP Packs and the newer PUPDMDcontrol.exe methods to work is to stay with the Dmddevice.dll file dated 12/24/16 in my PinDMD3 folder within Vpinmame.  The Devicedmd.dll in the root of vpinmame is dated 7/3/18.  I completely agree that moving dll files around is the best way to messing things up, but in my system this was the only thing I could get to work correctly.

I updated to DOFLinx 7.0A and that resolved a new problem I had where my addressable led strips and the backglass in Pinball FX3 were not working at all.  Now when I load a FX3 table I have the BG and the Lighting feedback I had lost.  So I am now down to the last issue of the LED strips not working within Pinup Menu.  I used to have some feedback with those lights as I scrolled through the tables but now I don’t, not sure why.  The DOFLinx update to 7.0A didn’t reinstate that feature but I’m not sure why.

In Popper Doctor the DOF Driver Type is Popper dof and the Dof Rom is pinupmenu.  When I press Start DOF the log says Starting DOF, then DOF After INIT.  No matter what I put in the DOF Element and Send DOF On nothing happens.  If I change DOF Driver Type to DOFDirect I get an error message when I try to start it saying “The system cannot find the file specified, ProgID; DirectOutput.ComObject”  When I press Stop DOF I get a message saying “Invalid variant operation”  I’ve gone into the registry and tried working with the settings as indicated on Nailbuster’s wiki but so far I haven’t figured out what the problem is.  So if anyone has an idea or has run into this and solved it, please let me know.

You need to login in order to like this post: click here

[Everly]

Just an update on the MK1.  I made a flash video that I’m using on my back glass when I’m in the Front End.  My friend’s design for the decals were great and I got them printed and applied last weekend.

You need to login in order to like this post: click here

[Everly]

TerryRed wrote:

I would reinstall dmdext 1.71 files, as the AIO may have replaced it with one that may not work correctly.

dmdext-v1.7.1-x86.zip

https://github.com/freezy/dmd-extensions/releases/tag/v1.7.1

Also, recheck your dmddevice.ini to be sure that it wasn’t replaced from the AIO and be sure that it has PUP enabled.

That is a possibility.  I’ve learned that the dmdevice.dll creates a problem with my cabinet.  When I installed the teensy board to control my LED strips my PinDMDV3 failed to work.  I would get a PinDMD3 not found error.  The solution I stumbled across was the dmdevice.dll.  I had to overwrite the one that had been updated back to one dated in Dec of 2016.  When I did that the DMD and the Teensy would cooperate and everything would work.  I have confirmed that dmdevice.dll is the 2016 version and my pindmd3 and addressables work, but no PUP Packs will work and no DOF from within Pinup Menu.

The dll in the link you provided will overwrite the dmdevice.dll and will introduce the conflict between my dmd and teensy, but I’m curious to see if the PUP Packs will then begin to work again.  If that is the case, then I just need to figure out where to put the 2016 dll and where to place the 2018 dll to get everything to operate correctly.

I have confirmed that my dmdevice.ini does have Pup Enabled set to true, but I’ll overwrite that ini with the one from Freezy 1.71 if I see it has a different modified date and see if that takes care of the issue.

You need to login in order to like this post: click here

[Everly]

Gwen wrote:

If you recently installed any Terminate-Stay-Resident software (something that stays in memory) it could be conflicting. I had issues with a Discord client that got installed with a game once.

I haven’t installed anything other than the all in one installer for vpx 10.6.  The more I think about it I believe the two issues are unrelated.  Something is causing my PUP packs to not run (as I don’t have a puplog in my vpinmame) and some other issue is causing dof to not work while in Pinup Menu.

I’ve followed all of the steps in Nailbusters videos and everything seems set correctly.  Just not sure what I’m missing.

You need to login in order to like this post: click here

[Author]

Posts