Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. Thank you for your support. Tom Speirs

Patreon

supermario0523

Basic Member
  • Posts

    13
  • Joined

  • Last visited

supermario0523's Achievements

Advanced Member

Advanced Member (2/5)

0

Reputation

  1. This EXACTLY did it! I didn't re-install, but I did remove every key and value in the registry referring to DOFConfig, and re-registered... and VOILA! Thank you so much!
  2. Hey Tom- I tried re-running the RegisterComComponent as admin again, and tried your ZIP replacing my files (adjusting the xml's appropriately) and still no luck. I did this week, however, switch all my toys to run of relays connected to the LEDWiz, so the LED plugin manager can knock my toys as desired... just obviously no Teensy action.
  3. Hey Tom- Sorry, yes I have disabled DOF in this run of log to isolate that addressable LED issue, and doing the run with Pin2DMD support to alleviate that issue... I will re-enable DOF plugin to generate that log tonight for your viewing
  4. So, Tom- I tried installing with Pin2DMD support and copied the DMDDevice.dll from the VPinMAME folder, and it worked on the first try... the Teensy was not being interfered with and a table would load properly. I don't know what I bugged up after that, but this was the only time I got it to work. Now with this solution, the table loading will crash pinballx. I looked at the log of events before the crash, and nothing is really showing any errors. I tried going int he PBX folder and deleting every DMD file except for XDMD, and everything seems happy now. Addressable LEDs work when tables launch, DOF works on tables (still not on PBX), and we are on 3.13... very strange
  5. I could give that a shot. Would this quirk be new to DOF R3++? I was able to get it good on my laptop a few months back
  6. Hey Tom, I'll give it a try when I get home tonight Also, not sure if this is related... My teensy flashes like it's receiving data immediately upon PBX 3.12 boot (even with DOF plugin disabled), and subsequently launches tables locks out the teensy... But only that. The rest of DOF works. This is not an issue when I load direct from VPX. I tried rolling back to PBX 3.0 and that solution remedies the problem Thanks
  7. Attached below Thanks! PinballX DirectOutput Plugin.log log.txt PinballX.ini
  8. I just tried a full, clean install of *everything*, even uninstalling DOF and VPX... no changes. It still gives me the "ERROR" message described above. Tried rolling back to even 2.50 PBX, then tried PBX 3.12 from this morning... same error
  9. Hi all- I have gotten a new cpu build for pinball, and a month or so ago copied all my table files over after doing a fresh install of pinballx and vpx. Since the project has been an upgrade as well as adding new things like DOF Linx, it's taken me a while to get to setting up PinballX DOF. VPX DOF and FX3 DOFLinx work great now. But I can't get PinballX DOF to work. I reinstalled R3++ DOF, copied over the PinballX Plugin to the plugins folder, and in the plugin manager, the state says "Error! DirectOutput framework not found. Make sure the DOF com object is registered.". This is not the case when looking at the config test within the directoutput folder itself. I'm not sure which files would be helpful (I did read the sticky), but I have attached the log from the PBX folder, as well as the 2 globalconfig files from my DirectOutput config folder. I'm hoping I overlooked something, but I am dotting my i's and crossing my t's, comparing to the file structure from my old build, and I see no reason why I should be having this issue. Please let me know if there are ay additional files or further info I can provide. Thanks! log.txt GlobalConfig_B2SServer.xml GlobalConfig_PinballX.xml
×
×
  • Create New...