VIP Class
  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by freezy

  1. Hi all, I'm posting this because I'm kind of short of time and I think 95% of the work has been done. As you might know, Barnstorm lately added support for third-party executables to be called with Timeshock that allow for adding real DMD and force feedback support. With the former done with DMD extensions, I've spent some time interfacing DOF with the force feedback part. Tom was so nice to release the latest sources of DOF, so my fork basically compiles to an executable you can throw into the Pro Pinball installation folder and tell Pro Pinball to use it for sending force feedback info to. What signals are sent you can see here: Now, I'm wondering how to configure this. As far as I understood there are two ways of mapping the input signals to the output hardware. Is this all done in the XML? Are the .ini files only for VP ROMs? If any DOF configuration expert owning Pro Pinball wants to give it a try, I can post a (completely untested) binary of the executable. Cheers! EDIT: Yeah I'll read the doc when I get to it.
  2. No, everything should work, it's just that there is no table config in the DOF Config tool for Timeshock right now, and what I've put as config to test my setup were just the solenoids. The config is read from directoutput,ini in the Timeshock folder. @arngrim let me know when you have set up Steam!
  3. That's kind of you, but if you want to support me then I'd prefer supporting the good guys that actually need funding like the EFF.
  4. Yeah you need to place directoutput.ini in the same folder as DOFSlave.exe (i.e. in the Pro Pinball folder). Note that this completely ignores your current DOF installation. The whole DOF is compiled into DOFSlave.exe and reads the config file from the path where it's executed.
  5. Okay so I've got something working. Just drop these files into the Pro Pinball folder (try %PROGRAMFILES(X86)%\Steam\SteamLibrary\steamapps\common\Pro Pinball Ultra), then in Steam right-click on Pro Pinball Ultra, Properties, Launch Options and put "q m2 fDOFSlave". Make sure you use the 64-bit version of Pro Pinball (e.g. on a 64-bit OS). The included DOFSlave.exe is a complete DOF build which will read DOF config from the folder's directoutputconfig.ini (example file included). I've got solenoids working, but not the flashers, although that's probably due to my missing DOF config skills. Can anyone put a decent table config for Timeshock into the DOF Config Tool? Who would have those skills? The available signals sent to DOF are documented here.
  6. It's a fun topic, I'll address this after the next dmdext release!
  7. Sorry to reply to late. I've added support for reading the DMD position from VPM's registry, so if you have positioned the DMD in VPM, dmdext's DLL will be able to reuse those values. Will be in the next release coming up the next few days.
  8. Glad you have it running and sorry I didn't respond earlier, @DJRobX Do you have any idea how I could fix crashes with JIT turned off? It seems in this case the crash isn't originating from dmddevice.dll but from VPM itself. Any way we can debug this?
  9. It's still on the list but I didn't have any time for anything the last months, so go figure. I'll try to get into it the next week(s) though.
  10. Nope, not yet, it skipped down to position #4 of my ongoing projects, so it might take a while. Not forgotten though!
  11. Yeah that should be doable quickly. I'll take care of it next time I switch projects.
  12. Cheers and thanks for you patience!
  13. Fixed the last crashes (thanks sliderpoint). Get the update here. Season for new features is open again.
  14. Yeah the whole externalization happened thanks to Lucky1/PIN2DMD.
  15. Those folders contain the DLLs for native external DMD support written in C. If you have a PIN2DMD you won't even be needing dmdext's DmdDevice.DLL because Lucky1 already added support for everything in there. In order for the DLL to be actually used, you need to check "Use external DMD" in VPM's game options. I'd suggest having a try with dmddevice.dll from the PIN2DMD folder. If that works, you'll know it's a problem with dmdext's DmdDevice.dll. Then I'll need a log to tell you more.
  16. For those of you who didn't update the latest build I've posted here, it's now an official (bugfix) release: @Andypc: The "alwaysontop" parameter sets the window's Topmost property to true. That's a .NET thing. There might be better more reliable methods do achieve that. Feel free to open an issue at GitHub and I'll have a look at it when I have time.
  17. Is it the Direct2BS backglass or Hyperpin's background that stays on top?
  18. Oh, right. I thought that was included in Windows 7. Sorry, my bad, I'll add a note to the install instructions. Thanks @Thalamus!
  19. Really bad luck, huh. What bitness is your Windows?
  20. Yes, you can override the position on a per-game basis. See GitHub page. I don't have any particular idea about the capturing problem. It's kind of ironic though, given dmdext is based on screen capturing. Does OBS Studio have an API for input sources? If so, it probably wouldn't be very difficult to just create another output source for dmdext that sends data directly to OBS studio...
  21. I'm still pretty sure you're using an old version. I'll publish a new official release soon to get rid of that doubt. When using the exe, the log is what's displayed in your console.
  22. I've tested this. If it doesn't work I'll need your exact command plus the log.
  23. Sorry I was kind of slow these last weeks, but happy to see your issues resolved. And thanks for reporting your solutions, otherwise people would have spent time trying to resolve them in vain. EDIT: I'm posting this here as well: For those having crashes (probably quite a few), try this new build:
  24. There is a post-build script that copies DmdDevice.dll to the VPM folder, you probably need to update it: Right-click on the PinMameDevice project, Properties, Build Events and under Post-build update the folder 3 times. Maybe try putting the .dll into SysWOW64 instead of the VPM folder, otherwise I'll need a log, please.
  25. New version here! I've added two new things for you guys to test: 1. In DmdDevice.ini, add: [browserstream] enabled = true port = 9000 Want to check the score of junior's game in the basement? Open a browser and connect to the IP of your cab port 9000 (or whatever you put). It'll stream the DMD live to your browser. 2. In DmdDevice.ini, add: [vpdbstream] enabled = true Then open in a browser and run a game. You might even see someone else playing. There were some other fixes and additions as well, e.g. you can now override settings per game in the .ini, like positioning the virtual DMD slightly differently depending on its resolution and backglass. More details in the changelog and README.