Jump to content

Search the Community

Showing results for tags 'DOF'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to the VPUniverse
    • VPU General Discussion
    • Site News & Announcements
    • The Big Bang
    • VPU Classifieds - Buy / Sell / Trade
    • Pinball Festivals, Groups & Gatherings
  • New Releases
    • B2S New Releases
    • Visual Pinball New Releases
    • Future Pinball New Releases
    • Front End & Support Files New Releases
  • PinCab/Pinball Hardware Development
    • LedWiz & Arduino Support
    • Pin2DMD
  • Digital Pinball Cabinets
    • Cabinet Discussion
    • Hybrid Builds
    • Direct Output Framework
    • B2S Development
  • Planet Visual Pinball
    • Visual Pinball General Discussion
    • Visual Pinball Support
    • Visual Pinball Development
    • Table Development and Releases
  • Planet Future Pinball
    • Future Pinball General Discussion
    • Future Pinball Support
    • Table Development and Releases
  • Artwork
    • Backglass Artwork
    • Playfield Artwork
    • DMD Colorization Project
  • Pinball Front-Ends
    • HyperPin Support
    • Pinball X Support
  • PinMAME
    • PinMAME Development
    • PinMAME Support
  • Real Pinball & Arcade Gaming Discussion
    • Real Pinball Discussion
    • Arcade Gaming Discussion
  • Other Virtual Pinball & Gaming Discussion
    • Console & PC Virtual Pinball
    • Console & PC Gaming Discussion

Categories

  • Visual Pinball - 9.x.x
    • Visual Pinball - Install & Support Files
    • Pincab Cabinet Tables (FS)
    • Hybrid View Tables (HV)
    • Desktop Tables (DT)
    • Hybrid Files
    • Visual Pinball Physics Sets
  • Visual Pinball - 10.x.x
    • Visual Pinball 10 - Install & Support Files
    • Visual Pinball 10 - Resources
    • Visual Pinball 10 - Tables
  • B2S - Backglasses
    • B2S - For Players
    • B2S - For Developers
    • Backglass Resources
  • Future Pinball
    • Future Pinball Files
    • Future Pinball Tables
  • PinMAME
    • PinMAME Roms
    • PinMAME Source
  • Direct Output Framework
  • Pinball Frontend Downloads
    • HyperPin Media Packs
    • HyperPin Support Files
    • Frontend Artwork
    • Plugins
    • Media Managers
  • HyperDMD
    • HyperDMD Files
    • HyperDMD - Fonts
    • HyperDMD - Animations
  • Development Resources
    • Table Creation Resources
  • Preview Videos
    • Visual Pinball - 1080p - (FS)
    • Future Pinball - 1080p - (FS)
    • Visual Pinball - - (DT)
    • Future Pinball - - (DT)
    • Backglass Videos
    • DMD Video
  • Cabinet Resources
    • Cabinet Plans
    • Wiring Schematics
    • Support Files
  • Table Resources
    • Playfield Resources
    • Pinball Manuals
    • Plastic Resources
    • Primitive Resources
  • Pin2DMD Files
    • Pin2DMD Documentation
    • Pin2DMD Firmware
    • Table Support Files
    • Color ROM Patches
    • ROM Frame Dumps
    • Pin2DMD Tools
    • Pin2DMD Color Palettes

Categories

  • Articles

Categories

  • Cabinet Building & Configurations
  • DMD Colorization Tutorials
  • VpinMAME
  • Installing PinMAME for SAM Emulation
  • Game Specific Tips & Tricks
  • Future Pinball
  • B2S Tutorials

Found 59 results

  1. To illuminate my game room I created 3D printed lights, designed similar to pinball bumpers/towers. Inside they have ledstrips, connected via Wifi to the pinball cabinet (avoiding cables through the room) controlled with DOF. The lamps are a combination of background light and game actions. The video shows typical animations and background lights for several games: https://www.youtube.com/watch?v=zvUSc_3gUc8 If you do not have a 3D printer, you might use purchased lamps, etc. I'm using two bumpers mounted on a plate, two of these, one each side of the room. As I could run a (hidden) cable between both I needed only one Wifi controller + power supply for both. Of course you could use one controller/power supply per lamp, if needed. To build it, you need access to a 3D printer, material need is < 1 kg ($20) Two wood plates to mount it. 1 x Wemos D1 mini (ESP8266) ($4 in China via ebay) 1 x 2 channel relais board (for Arduino) ($1 in China) 1 x 5V 15A power supply ($20) 4 x "8x5-40-LED-Matrix-WS2812-LED-5050-RGB-Full-Color-Driver-Board-For-Arduino" ($8 China) 1 x IC 74HCT245 (20 Cent) some cables, some resistors... Build the controller on a breadboard, when working you might want to solder it on a prototyping board to get it small and fit into a case. 3D files to download and print are here: https://www.thingiverse.com/thing:2781747 There are some picture how the printed part looks and how to mount the LED's as well. Here is the source for the controller. You need to download and install Arduino IDE to upload the firmware. If you never did so before, search for "wemos arduino tutorial" example: http://www.instructables.com/id/Programming-the-WeMos-Using-Arduino-SoftwareIDE/ Start with a "blink" example. When ready, open the source. Enter your Wifi data to allow it to connect. Either check your router or use the serial monitor to learn the IP address of the device (and check if Wifi connection worked). If the ledstrips, relais, power are connected correctly, it will start by enabling the relais and run a green LED through the strip. BTW, the relais are used to shutdown the power supply. The Wemos (using a Power/USB adapter, 1Ah is fine) is always connected to power. It will "wakeup" as soon you start playing pinball. Then it will power on via the relais the 5V power supply, avoiding that this thing is always connected to power and burn energy (or burn your house on failure). After 60 seconds without signal it will shutdown the power supply automatically. The controller responds to Artnet universe 1+2 for pinball. If you have an Artnet controller on your smartphone (or your smart house, such as Homematic or Siri with Homebridge), it will respond to Universe 0. The first 3 lamps represent RGB, so you can setup a background light for your room even if you don't play. Finally you need to setup DOF. The cabinet.xml is huge, as you need to define all lamps, for each color. I upload mine as example, if you use the same number of LED's, you can just copy&paste. Finally you need to setup DOF and download the directoutputconfig100.ini file. An example how from my setup is enclosed. Good luck - and much fun. Artnetpinballlamp.ino cabinet.xml
  2. 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: https://github.com/freezy/DirectOutput/tree/propinball/ProPinballSlave#configuration 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.
  3. First and most important .. Thanks for a fantastic tool that has already delivered many hours enjoyment. Until rather recently there was a table on the DOF Configtool site that was call zzz. It was very useful for creating DOF entries for tables that are not in the list. It also had a detailed candidate configuration although not made public since it was specific to my cabinet. Is it possible to restore this? The tables I was using it for are Central Park and Nova and was looking to use it again for Galaxy Play (CIC) . BTW ... The link on the DOF Configtool home page to report bugs is broken. Yes, in the scheme of things the above is really a minor issue and adding the table entries would also solve the issue. However, it would be useful to have a "Test" entry that could be used before an entry is provided (e.g. during table development). Thanks and Happy New Year.
  4. As of a few weeks back, I noticed that several of my toys, noticeably my knocker, are firing randomly while in PBX. Is that a new feature or something I should troubleshoot ? Ideally, I'd like only lights to fire... thanks.
  5. Hi, I've been stuck on something for a while now and seem to be missing a piece of the puzzle. There are tables out there that seem to have DOF feedback commands, yet are not defined in the dofconfig tool and don't include a dof mapping .xml file in the table. e.g. "Cowboy Eight Ball" from vpforums it has commands like: Const cGameName="cowboy",cCredits="Cowboy Eight Ball" and Sub S33_Hit:vpmTimer.PulseSw 33:S33.IsDropped=1:S33A.IsDropped=0:S33.TimerEnabled=1:End Sub Sub S33_Timer:S33A.TimerEnabled=0:S33A.IsDropped=1:S33.IsDropped=0:End Sub I can get the switches to fire solenoids buy assigning random incorrect table map .xml files, however they are not accurate. I'd assume either a mapping from the dofconfig tool or a specific .xml mapping file would be out there, but without either, there is no DOF working on the table. Is there something I'm missing that is preventing a large number of the VP9 tables to work correctly with DOF which have such commands? Maybe I'm just missing some history here? Thanks
  6. Version 1.01

    108 downloads

    The Grid's most awesome addressable leds make for Light Cycle ramp effects, Light Jet Cannons, Explosions and the coolest de-resolution effects you have ever seen in a real pinball cabinet! A video demonstration of this table can be seen here in my cabinet: This table has complete cabinet feedback and lighting support for the following: – 10 solenoids for flipper, slingshots, bumpers, etc.. – 5 RGB flashers – Blower Fan – Shaker – Gear motor – Strobe – Beacon – Start button – Coin button – Launch Ball button – RGB Undercab Lighting – Addressable Leds Requirements: - DOF R3 installed (for DOFLinx cabinet feedback and lighting) and addressable leds already setup and working (for MX led effects). - DOFlinx 5.20 or higher is REQUIRED, even if you don't have addressable leds. - addressable leds are NOT required to play this table, but they are HIGHLY recommended. - to use the addressable leds with this table you must have your DOF "config" files updated by using DOF Config Tool! (just like you would for Visual Pinball) To play a Future Pinball table with addressable leds support (DOFLinx MX): - update DOFLinx as per normal (must be 5.20 or higher). Make sure you copy over the new DOFLinx.vbs to "Future Pinball Scripts". - add DIRECTOUTPUTGLOBAL=c:DirectOuputConfigGLobalConfig_b2sServer.xml (assuming you have it there) to your DOFLinx.ini file. - download the awesomeness of a Future Pinball DOFLinx MX table - check DOF Config Tool to see if support for that table has been added to it yet (you will see FP tables start with "FP:") If there are no DOF commands showing for that table, its not supported yet. - "Generate" a new Config File (containing directoutputconfig30.ini in the zip) and copy the new files to your "DirectOutput Configs" folder. - play the epicness that is Future Pinball with DOFLinx cabinet feedback and addressable leds! DOFLinx 5.20+ download link: http://www.vpforums.org/index.php?app=downloads&showfile=12318 Consult the DOFLinx guide included in the download link for more information on setting up DOFLinx.
  7. Version 1.0.0

    92 downloads

    The most amazing lighting in a pinball cabinet allows for particle effects, great explosions, electrical effects, and machine gun fire, thanks to the new DOF addressable led MX support in DOFLinx 5.20! A video demonstration can be seen here in my cabinet: This table has complete cabinet feedback and lighting support for the following: – 10 solenoids for flipper, slingshots, bumpers, etc.. – 5 RGB flashers – Blower Fan – Shaker – Gear motor – Strobe – Beacon – Start button – Coin button – Launch Ball button – RGB Undercab Lighting – Addressable Leds Requirements: - DOF R3 installed (for DOFLinx cabinet feedback and lighting) and addressable leds already setup and working (for MX led effects). - DOFlinx 5.20 or higher is REQUIRED, even if you don't have addressable leds. - addressable leds are NOT required to play this table, but they are HIGHLY recommended. - to use the addressable leds with this table you must have your DOF "config" files updated by using DOF Config Tool! (just like you would for Visual Pinball) To play a Future Pinball table with addressable leds support (DOFLinx MX): - update DOFLinx as per normal (must be 5.20 or higher). Make sure you copy over the new DOFLinx.vbs to "Future Pinball Scripts". - add DIRECTOUTPUTGLOBAL=c:DirectOuputConfigGLobalConfig_b2sServer.xml (assuming you have it there) to your DOFLinx.ini file. - download the awesomeness of a Future Pinball DOFLinx MX table - check DOF Config Tool to see if support for that table has been added to it yet (you will see FP tables start with "FP:") If there are no DOF commands showing for that table, its not supported yet. - "Generate" a new Config File (containing directoutputconfig30.ini in the zip) and copy the new files to your "DirectOutput Configs" folder. - play the epicness that is Future Pinball with DOFLinx cabinet feedback and addressable leds! DOFLinx 5.20+ download link: http://www.vpforums.org/index.php?app=downloads&showfile=12318 Consult the DOFLinx guide included in the download link for more information on setting up DOFLinx.
  8. Version 1.0.0

    41 downloads

    Wipeout: DOFLinx MX Cabinet Edition Witness a modern light show in a retro theme, thanks to the new DOF addressable led MX support in DOFLinx 5.20! A video demonstration in my cabinet can be seen here: This table has the complete cabinet feedback and lighting support for the following: - 10 solenoids for flipper, slingshots, bumpers, etc.. - 5 RGB flashers - Blower Fan - Shaker - Gear motor - Strobe - Beacon - Start button - Coin button - Launch Ball button - RGB Undercab Lighting - Addressable leds Requirements: - DOF R3 installed (for DOFLinx cabinet feedback and lighting) and addressable leds already setup and working (for MX led effects). - DOFlinx 5.20 or higher is REQUIRED, even if you don't have addressable leds. - addressable leds are NOT required to play this table, but they are HIGHLY recommended. - to use the addressable leds with this table you must have your DOF "config" files updated by using DOF Config Tool! (just like you would for Visual Pinball) To play a Future Pinball table with addressable leds support (DOFLinx MX): - update DOFLinx as per normal (must be 5.20 or higher). Make sure you copy over the new DOFLinx.vbs to "Future Pinball \ Scripts". - add DIRECTOUTPUTGLOBAL=c:\DirectOuput\Config\GLobalConfig_b2sServer.xml (assuming you have it there) to your DOFLinx.ini file. - download the awesomeness of a Future Pinball DOFLinx MX table - check DOF Config Tool to see if support for that table has been added to it yet (you will see FP tables start with "FP:") If there are no DOF commands showing for that table, its not supported yet. - "Generate" a new Config File (containing directoutputconfig30.ini in the zip) and copy the new files to your "DirectOutput \ Configs" folder. - play the epicness that is Future Pinball with DOFLinx cabinet feedback and addressable leds! DOFLinx 5.20+ download link: http://www.vpforums.org/index.php?app=downloads&showfile=12318 Consult the DOFLinx guide included in the donwload link for more information on setting up DOFLinx.
  9. Version 1.0.0

    32 downloads

    Retroflair: DOFLinx MX Cabinet Edition Witness a modern light show in a retro theme, thanks to the new DOF addressable led MX support in DOFLinx 5.20! A video demonstration in my cabinet can be seen here: This table have the complete cabinet feedback and lighting support for the following: - 10 solenoids for flipper, slingshots, bumpers, etc.. - 5 RGB flashers - Blower Fan - Shaker - Gear motor - Strobe - Beacon - Start button - Coin button - Launch Ball button - RGB Undercab Lighting - Addressable leds Requirements: - DOF R3 installed (for DOFLinx cabinet feedback and lighting) and addressable leds already setup and working (for MX led effects). - DOFlinx 5.20 or higher is REQUIRED, even if you don't have addressable leds. - addressable leds are NOT required to play this table, but they are HIGHLY recommended. - to use the addressable leds with this table you must have your DOF "config" files updated by using DOF Config Tool! (just like you would for Visual Pinball) To play a Future Pinball table with addressable leds support (DOFLinx MX): - update DOFLinx as per normal (must be 5.20 or higher). Make sure you copy over the new DOFLinx.vbs to "Future Pinball \ Scripts". - add DIRECTOUTPUTGLOBAL=c:\DirectOuput\Config\GLobalConfig_b2sServer.xml (assuming you have it there) to your DOFLinx.ini file. - download the awesomeness of a Future Pinball DOFLinx MX table - check DOF Config Tool to see if support for that table has been added to it yet (you will see FP tables start with "FP:") If there are no DOF commands showing for that table, its not supported yet. - "Generate" a new Config File (containing directoutputconfig30.ini in the zip) and copy the new files to your "DirectOutput \ Configs" folder. - play the epicness that is Future Pinball with DOFLinx cabinet feedback and addressable leds! DOFLinx 5.20+ download link: http://www.vpforums.org/index.php?app=downloads&showfile=12318 Consult the DOFLinx guide included in the download link for more information on setting up DOFLinx.
  10. Version 1.0.0

    79 downloads

    Masters of the Universe: Mastered. DOFLinx MX Cabinet Edition You have the power of the ultimate light show in a pinball cabinet! This is the first Future Pinball table to use addressable leds thanks to the new DOF led MX support in DOFLinx 5.20! You have never seen a light show quite like this in a pinball cabinet! Amazing effects and animation that surround the playfield! A video demonstration can be seen here in my cabinet: This table has the complete cabinet feedback and lighting support for the following: - 10 solenoids for flipper, slingshots, bumpers, etc.. - 5 RGB flashers - Blower Fan - Shaker - Gear motor - Strobe - Beacon - Start button - Coin button - Launch Ball button - RGB Undercab Lighting - Addressable leds Requirements: - DOF R3 installed (for DOFLinx cabinet feedback and lighting) and addressable leds already setup and working (for MX led effects). - DOFlinx 5.20 or higher is REQUIRED, even if you don't have addressable leds. - addressable leds are NOT required to play this table, but they are HIGHLY recommended. - to use the addressable leds with this table you must have your DOF "config" files updated by using DOF Config Tool! (just like you would for Visual Pinball) To play a Future Pinball table with addressable leds support (DOFLinx MX): - update DOFLinx as per normal (must be 5.20 or higher). Make sure you copy over the new DOFLinx.vbs to "Future Pinball \ Scripts". - add DIRECTOUTPUTGLOBAL=c:\DirectOuput\Config\GLobalConfig_b2sServer.xml (assuming you have it there) to your DOFLinx.ini file. - download the awesomeness of a Future Pinball DOFLinx MX table - check DOF Config Tool to see if support for that table has been added to it yet (you will see FP tables start with "FP:") If there are no DOF commands showing for that table, its not supported yet. - "Generate" a new Config File (containing directoutputconfig30.ini in the zip) and copy the new files to your "DirectOutput \ Configs" folder. - play the epicness that is Future Pinball with DOFLinx cabinet feedback and addressable leds! DOFLinx 5.20+ download link: http://www.vpforums....&showfile=12318
  11. How can i get the PBX browsing feedback working with teensy leds? I have the solenoids working for left and right flipper in PBX but no leds. It seems to me that the DOF plugin is not running right in PBX, because in the B2S Screen i can not open the DOF plugin Settings. (Inside VP i can select this button.) The PinballX DOF plugin is activated in PBX. The Globalconfig_PinballX.xml and DirectOutput PinballX Plugin.dll is inside PinballX plugin directory. My DirectOutput folder is on drive F:\DirectOutput. Some people reported a non working dof if the controller id or c:\DirectOutput folder is a little bit different. Also when the XML is pointing to the right path. I have one LedWiz ID 6 and one Teensy No. 30. (directoutputconfig6.ini + directoutputconfig30.ini but no directoutputconfig.ini because i dont have a LedWiz ID1). Is this the problem? Teensy is always No. 30 with the Dof Tool. I have made the 3 RGB addressable Combos like this link: http://vpuniverse.com/forums/topic/2695-configtool-big-update-for-teensy-users/ Maybe a wrong folder or a missing INI / XML for the PBX plugin???
  12. Hi, I have DOF working well with Solienods, flashers, addressable LED Strip, and a Shaker. In certain tables like TZ and TAF, I noticed that the shaker is fired during game play, and I don't really like that effect. Ie. In TAF when "The Power" is on for the 3rd ball lock, and in TZ, when "Battling the power" . Is there somewhere I can edit/change in the config tool, that will remove the shaker from these events? Will that only effect my own tables? If theres a global change to the table, will I need to redo my settings? thanks for any help!
  13. Hi, I am using a DOF setup that is working with 10 12v solenoids. Everything seems to be working fine, then occasionally at the start of PinballX the left flipper will not fire the DOF. The PinballX receives the input as I see the screen scroll. If I try right flipper immediately afterwards it fires the solenoid, then if I try the Left Flipper it now works... and keep working. I have seen similar behavior in game. Sometimes left flipper DOF is not firing solenoid, but flipper flips, then after using the right flipper, the left one will fire. Not sure if this is co-incidence or not, but I have used different solenoids and get the same issue happening . All solenoids are connected to a 12v line of a secondary PSU in the cab. Any tips/help would be appreciated. thanks
  14. Hello everyone First of all, thanks in advance to everyone helping me with this! I've been building a Pinball Cabinet for the past few months and I am getting close to "finishing" it. If you want to check it out, use this link. My Pinball Cabinet (updates to come when everything is working) I am currently experiencing two issues with the Direct Output Framework. One shall be addressed here, the other one in this post: DOF issue #1: PWM-output on 2nd LEDWiz not working correctly I've been trying to solve these issues myself for the past few days/weeks, but failed, since I am not very experienced with DOF yet. I do not know whether these two issues are related. --- DOF issue #2: No flasher-feedback with otherwise working PinballX Plugin - The 5 flasher RGB toys (ports 1-15 on my 1st LEDWiz) do not light up when starting PinballX (with a working plugin installed) as a shell for my current user on my Windows 7 setup. - All other toys or RGB toys connected to my two LEDWiz controllers and configured in the PinballX table in the DOF Config Tool work perfectly / with the other issue mentioned above. Those are: start button, exit button, genre button, wow to play button, coin button, both flipper contactors / and with the other issue mentioned above (only 7 colors): RGB flippers, RGB magnasave Left, RGB magnasave Right and RGB undercab complex. - When running PinballX directly from desktop or any file manager (I like Total Commander) the 5 flasher RGB toys work as intended (show scrolling animation when selecting a different table in PinballX or going up/down in the menu), although the output only starts after about 5 seconds after PinballX loaded. - When running PinballX as a shell, I first have to play a Table that uses DOF in order to get the 5 Flasher RGB toys working in the PinballX frontend (exiting the table back to PinballX, not restarting PinballX). - In PinballX I have «Use DirectB2S in Front End» enabled in order to use the .b2s backglasses when scrolling tables. --- Further information on this issue and my current DOF setup. - I use this DOF R3 Beta version: DOF R3 Beta Build 5812.27024. - I use this B2S Server version: B2S Server. - I use a two identical GlobalConfig files (globalconfig_B2SServer.xml and globalconfig_PinballX.xml) and the ini-Files created by the DOF Config Tool (directoutputconfig.ini and directoutputconfig2.ini), but no Cabinet.xml or dedicated table config files. - For now I only use 2 LEDWiz, which are listed in the «My Account» tab of the DOF Config Tool. A Teensy is supposed to be added soon. --- Help required As stated above, I am not very familiar with DOF yet and don't see a way to solve this issue myself. That's why I need your help and would greatly appreciate it. I feel that this issue, and the other one mentioned above, are limiting my experience while playing my Pinball Cabinet. So, what can I do to help you guys to help me solve these issues? What additional information, logs, xml-Files, ini-Files, screenshots, videos etc. do you need? Or do you maybe already have a solution or know someone who had the same or similar issues? I'm looking forward to hearing from you guys. Thanks again in advance! --- Best regards from Switzerland fuzgi
  15. What does this mean or do? 10 Bumper Back Left
  16. DOF just got support for custom table output overrides through the <TableOverrideSettings>. Individual outputs can be globally adjusted (contactors disabled for instance), per-rom, per-table, or using wildcards (afm* for all versions of Attack from Mars). Lights or contactors can be reduced or shut off completely, overriding your configtool export settings. As always; backup your entire DirectOutputFramework - directory before toying with this ! I take no responsibility for issues, fire, damages, psychosis, insomnia etc. https://github.com/rambo3/DirectOutput/tree/ultimateio/DirectOutput/Builds Swisslizard: huge thanks for putting the project on GitHub. My cab would be dead without it. Introduction Kiwi wondered if it would be possible to turn off certain toys based on tables. No, but that's actually a great idea. So here we go! Setup Add the following to your Cabinet.xml, say just before </Cabinet> at the end of your XML, and start adjusting / removing. The example below globally turns off left and right flipper contactors. For Bad Cats turns off my overcab light, and reduces the undercab light to 50%. <TableOverrideSettings> <TableOverrideSetting> <Name>Globally disable left and right contactors</Name> <Enabled>true</Enabled> <Roms>*</Roms> <Tables>*</Tables> <TableOverrideSettingDeviceList> <TableOverrideSettingDevice> <Name>Ultimate I/O contactors</Name> <ConfigPostfixID>27</ConfigPostfixID> <Outputs>49,52</Outputs> <OutputPercent>0</OutputPercent> </TableOverrideSettingDevice> </TableOverrideSettingDeviceList> </TableOverrideSetting> <TableOverrideSetting> <Name>Bad Cats, disable or reduce undercab light</Name> <Description>Disables or reduces output percent on specific outputs for specific tables</Description> <Enabled>true</Enabled> <Roms>bcats*</Roms> <TableOverrideSettingDeviceList> <TableOverrideSettingDevice> <Name>Philips Hue projector overcab</Name> <ConfigPostfixID>70</ConfigPostfixID> <Outputs>7,8,9</Outputs> <OutputPercent>0</OutputPercent> </TableOverrideSettingDevice> <TableOverrideSettingDevice> <Name>Philips Hue undercab</Name> <ConfigPostfixID>70</ConfigPostfixID> <Outputs>10,11,12</Outputs> <OutputPercent>50</OutputPercent> </TableOverrideSettingDevice> </TableOverrideSettingDeviceList> </TableOverrideSetting> </TableOverrideSettings> Settings <TableOverrideSetting> is a mode containing a descriptive name, enabled state, comma seperated ROMs, and / or comma seperated Tables. Wildcards are supported. A single * specifies global. <Roms> specify list of ROMs without spacing, for instance: <Roms>afm*,bcats*</Roms> <Tables> specify table filenames without extension and spacing before commas, for instance: <Tables>AttackFromMars_FS_B2S,Bad Cats.VPX.v1.0</Tables> No commas in filenames, and no spacing before seperator. If there are commas in filename, use first part and add a wildcard / * at the end (AttackFromMars*). Filename are case-insensitive. <TableOverrideSettingDeviceList> contains all the devices you want to affect. <TableOverrideSettingDevice> is a single device, its outputs (according to configtool) to affect, and the output strength in percent 0-100. 0 is off. To let DOF know which device you want to control, match the ConfigPostfixID with your configtool ini file, for instance directoutputconfig27.ini with 27 being the postfixid. Debugging Check your DirectOutput.log file for details if nothing works. You should see something like: ... 2017.06.06 20.45.30.157 Debug: Setting up shape effect for area. L: 91, T: 0, W: 9, H: 30 2017.06.06 20.45.30.157 Table config loading finished: romname=afm, tablename=Attack from Marsvp91x 2017.06.06 20.45.30.157 TableOverrideSettings.activateOverrides... activeSetting[Globally disable left and right contactors]=True 2017.06.06 20.45.30.157 TableOverrideSettings.activateOverrides... activeSetting[Attack from Mars, disable flippers]=True 2017.06.06 20.45.30.157 TableOverrideSettings.activateOverrides... activeSetting[Bad Cats, disable or reduce undercab light]=False 2017.06.06 20.45.30.157 Pinball parts loaded ... Device support Currently Ultimate I/O, Teensy, and Philips Hue are fully supported. PacLed64, PacDrive have the support added in, but since I don't have those devices I can't confirm that they actually work. SainSmart USB have the support added in, but not fully testet yet. LedWiz is planned, but not sure how to add it in yet and will need to be confirmed by someone else since I don't have the thing. Fun thing Outputs can be individually affected, for instance I accidentally applied 0 OutputPercent in Bad Cats to one or two (can't remember) of the three undercab channel outputs causing a yellowish bright green instead of orange.
  17. DOF now has support for custom day and night modes through three classes: ScheduledSettings, ScheduledSettingDevice, and ScheduledSetting. This is a software approach to having lights or outputs adjusted on-the-fly during different times of the day. As always; backup your entire DirectOutputFramework - directory before toying with this ! I take no responsibility for issues, fire, damages, earthquakes etc. https://github.com/rambo3/DirectOutput/tree/ultimateio/DirectOutput/Builds Swisslizard: huge thanks for putting the project on GitHub. This project, like Philips Hue support, is not official but a side project off the original R3. Introduction As I got home from the job tired I wanted to play pincabs with less noise or brightness. I was changing the Cabinet.xml, renaming files to shut off the contactors, powering off the RGB or using alternative fade curves. At one point I started experimenting with overriding DOF output strength through Cabinet.xml and just brute force code, and eventually the XML settings got to a point that I could have full brightness on everything during the day, gradually shut off contactors, and adjust the Teensy brightness at midnight. Changes would kick in during a game and over midnight, which initially seemed like a bug where contactors would suddenly no longer "work". This is a software approach to specific devices in DOF for dynamically adjusting custom outputs, including Teensy brightness for individually adjustable RGB strips which by default are very powerful. Setup Add the following to your Cabinet.xml, say just before </Cabinet> at the end of your XML, and start adjusting / removing. The example below goes into effect 2200-0500, sets my contactor specific outputs to off, adjusts the Teensy back LED-matrix to 30%, and shuts off the SainSmart USB outputs. And it's enabled. <ScheduledSettings> <ScheduledSetting> <Name>Night Mode</Name> <Enabled>true</Enabled> <ClockStart>2200</ClockStart> <ClockEnd>0500</ClockEnd> <ScheduledSettingDeviceList> <ScheduledSettingDevice> <Name>Ultimate I/O contactors</Name> <ConfigPostfixID>27</ConfigPostfixID> <Outputs>49,50,51,52,53,54,55,56,57,58</Outputs> <OutputPercent>0</OutputPercent> </ScheduledSettingDevice> <ScheduledSettingDevice> <Name>Teensy LEDs back matrix</Name> <ConfigPostfixID>30</ConfigPostfixID> <Outputs>1</Outputs> <OutputPercent>30</OutputPercent> </ScheduledSettingDevice> <ScheduledSettingDevice> <Name>Sainsmart USB</Name> <Description>Note that the Sainsmart is a 0/1 relay array and that 0=off while 1-100 is considered on. There is no inbetween, a relay is either open or closed ("bitbang").</Description> <ConfigPostfixID>40</ConfigPostfixID> <Outputs>1,2,3,4,5,6,7,8</Outputs> <OutputPercent>0</OutputPercent> </ScheduledSettingDevice> </ScheduledSettingDeviceList> </ScheduledSetting> </ScheduledSettings> Settings <ScheduledSetting> is a mode containing start-end time of effect, enabled state, device list. You can have multiple <ScheduledSetting> objects to specify morning, daylight, evening, midnight. Times are forward-looking; typing 2050-0800 would literally mean from 2050 and until 0800 in the coming morning. <ScheduledSettingDeviceList> contains all the devices you want to affect. <ScheduledSettingDevice> is a single device, its outputs (according to configtool) to affect, and the output strength in percent 0-100. To let DOF know which device you want to control, match the ConfigPostfixID with your configtool ini file, for instance directoutputconfig27.ini with 27 being the postfixid. Passing midnight The settings have been confirmed to work passing midnight, which initially was a real problem practically and technically. There's an interesting issue here when a range passes to the next day (2300-0300 for instance), idea being schedules should be able to run all day long in real time without reboots. It's important checks are done in real time, not at DOF boot, as it probably wouldn't become active again if a pincab was online more than a day. Debugging Check your DirectOutput.log file for details if nothing works. Device support Currently Ultimate IO, SainSmart, Teensy and Philips Hue are fully supported. PacLed64, PacDrive and LedWiz have the support added in, but since I don't have those devices I can't confirm that they actually work. Note that the switches / relays like Sainsmart USB device is a 0/1 relay array and that 0=off, while 1-100 is considered on. There is no inbetween, either open or closed ("bitbang"). Gotta run real quick for work; hopefully this post doesn't have too many errors, I'll recheck after work.
  18. DOF now has support for Philips Hue through PhilipsHueController and AutoConfigurator classes. Massive thanks to arngrim for providing example libraries to start with, and support in DOF Configtool for the Hue, and the I-Pac Ultimate I/O while I'm at it. Please note, this is a fork off the original R3 by lizardking / swisslizard as I've been adding ScheduledSettings, UIO support, tweaks to the I-PAC portion of DOF etc for some time now. Check the link below, and use the latest build if you're feelin' lucky. Backup your entire DirectOutputFramework-directory before toying with this! I take no responsibility for issues, fire, damages, earthquakes etc. https://github.com/rambo3/DirectOutput/tree/ultimateio/DirectOutput/Builds Swisslizard: huge thanks for putting the project on GitHub. I love my I-PAC Ultimate I/O, and with the sources I was able to add in support for it. That is huge. Introduction The Philips Hue family consists of Zigbee / wireless controlled lights, sensors, remotes etc. using a bridge (the Philips Hue "hub"). The framework supports auto detection and configuration of these units. Philips Hue is made and sold by Philips. The class was based off PacUIO.cs, and implementation makes use of Q42.HueApi. It retains the 3-channel RGB style inputs, but converts that over to a single-channel #rrggbb hex string. Pretty much like normal RGB-bulbs in a pincab. Technically a single bridge can control about 50 lights x3 = 150 input channels (sensors are additionally ~60). Distance is covered either directly, or through ZigBee device-hopping where signal travels along devices to reach the finale device. Each device acts individually, but a LED-strip cannot have its LEDs individually controlled; the entire LED-strip acts like a single RGB device, and will light up with the same color value. Setup Before DOF can start communicating with the bridge it will need a valid key. To get a key off the bridge the Link-button on the bridge needs to be pressed, and an dof#pincab "user" needs to be registered in the bridge (whitelist) within 30 seconds. This will return a unique key (for instance "2P4R5UT6KAQcpOjFaqwLDrbikEEBsMIHY6z6Gjwg") which can then be used from that point on. The same registration on another bridge, or even the same, will create a new key and is required if you want to crossfire/SLI two hubs for reducing latency per bridge as more bulbs on the same bridge will introduce latency. To avoid duplicates / spamming the whitelist, and to avoid bugs crashing the bridge, currently this is the suggested approach for getting a key: Step 1: set static IP to bridge Get IP of the bridge. Check your phone Hue App -> Settings -> My Bridge -> Network settings. It should default to DHCP. Change this to a static IP, and make note of it, or check your router for IP. Step 2: whitelist DOF using a browser Open up the bridge API in a browser using your IP, example (replace IP with your static IP): http://10.0.1.174/debug/clip.html In the "CLIP API Debugger" it should say something like URL: "/api/1234/" with GET, PUT, POST, and DELETE-buttons. Copy&paste the following line into URL-field (not in your browser, but in the CLIP API Debugger): /api Copy&paste the following into the Message Body textfield: {"devicetype":"dof_app#pincab"} Next, walk calmly over to your bridge and press the physical Link button. You now have 30 seconds to hurry back to your browser, and press "POST"-button. Prepare for a second ride. Eventually you should get a username in the Command Response textbox, for example: "ywCNFGOagGoJYtm16Kq4PS1tkGBAd3bj1ajg7uCk". Make note of this. If you need more help, or images, see the Philips Hue API getting started tutorial with screenshots and replace the text with your own. The Name can also be adjusted. Step 3: add IP and key to Cabinet.xml Open up your Cabinet.xml, and add the following lines in the OutputControllers section, replacing the IP and key with your own: <PhilipsHueController> <Name>PhilipsHueControllerPincab</Name> <BridgeIP>10.0.1.174</BridgeIP> <BridgeKey>ywCNFGOagGoJYtm16Kq4PS1tkGBAd3bj1ajg7uCk</BridgeKey> </PhilipsHueController> Step 4: add lights using http://configtool.vpuniverse.com A bridge can handle about 50 lights. Each light will multiplex RGB (3 channels) on each send, similar to using RGB-buttons on a PacLed64 or UIO. To match your output channels to a specific light, use your Android / iOS Philips Hue app and decide which light you need to control. Each light should have a number in it, for instance "10. Hue lightstrip 1". That 10-number is the light ID. Mapped to the individual RGB-outputs in DOF Config Tool port assignments this means: ((light ID -1) * 3) + 1 = ((10 - 1) *3) + 1 = 27 +1 = 28, resulting in port 28, 29, 30 (R, G, B). If your light ID was 3, you'd map it to port 7, 8, 9. If your light ID was 1, you'd map it to port 1, 2, 3. If you want to delete the key from your bridge, open up CLIP URL again from the URL below, then enter the API-URL (replace both keys with your own, they're the same used twice), then press DELETE: http://10.0.1.174/debug/clip.html /api/ywCNFGOagGoJYtm16Kq4PS1tkGBAd3bj1ajg7uCk/config/whitelist/ywCNFGOagGoJYtm16Kq4PS1tkGBAd3bj1ajg7uCk Shutdown of lights DOF will shut down lights that have been affected, not the entire light array like an UIO or Teensy. If you have a house / apartment controlled by the same Hue bridge, it should only power down that one light or LED-strip that was affected when exiting a table. The feature was implemented as I found myself in complete darkness after quitting Attack from Mars way too often. Latency This is where things get complicated, and I try to cheat, trick and compensate for wireless issues. Signal communication is reduced as much as possible. Results will vary greatly. I'll try and detail what is going on, why, and how I tried through testing to compensate for it. Latency in milliseconds varies depending on wireless distance and signal strength, device-hopping, LED affected (R, G, or and brightness. A worst case scenario would be to adjust all RGB-channels, including brightness. A connection takes a few hundred ms (done once at init using BridgeKey and BridgeIP), and color sends per-light about 40-800ms+. Typically about 100ms. The latency becomes the DOF Philips Hue bridge refresh rate. Note that Phlips Hue does support controlling a group of lights at the same time using the same color change (not individiaully controlled); I'm not doing that right now, everything is per-bulb. The bridge will at worst case queue commands; this introduces more latency and inconsistencies (colors stuck, stuttery fades). To avoid overloading the bridge, DOF will check connection every 3s and use the last known latency as a transition time for the device to smooth out color changes much like TVs introduce frame interpolation from ~film to native panel refresh through synthesized pixel data. Color transition is a Hue API native command, and once set in motion adjust smoothly regardless of latency. The same latency (say 120ms) will become the DOF Hue refresh rate until the next connection check 3 seconds later, at which point the latency might be 300ms. If latency at any time is below 100ms, this gets reset to 100ms to avoid overloading the bridge. In practice 50ms works, 40 even, for a while. Breathing room and bridge stability has absolute priority. If any color changes occur between refreshes it gets stored locally but not actually sent to the bridge / light until the next color change. This is where colors can get stuck until the next change if latency is also high when that happens. Compensating for latency Any off-states in either R, G or B channel uses a fade the amount of current latency. Any on-states from black in either R, G or B is sent instantly without a fade to attempt to have light on as soon as technically possible. Any R, G, B changes not 0 will transition using fade time the amount of current latency. Using Hue color transitions produces smoother pulsating LAUNCH-button for instance, or color changes in general. Without it colors would change inconsistently due to latency changes of 100, 400, 200, 800ms etc while trying to set the color in a varying time span. Using Hue transitions will attempt to smooth out those changes giving the bulbs something to do while DOF is fighting latency. Practical use Start with one light. Do some testing and benchmarks, and see how far you can push it. First thing I did was crossfire / hook up two bridges and 17 devices; RGB, white, ambience, spots, two LED-strips. Then mapped them all to Undercab RGB complex in configtool. It was an interesting experience. 17 devices is 51 ports and about 6000 lumen. One bridge had 16 lights, the other 1 LED-strip. The single LED-strip was close to ~100ms and responded very well to changes, almost hiding latency completely. The other 16 lights were different; Hue will affect one light at a time when controlled individually, and in this case it took about 2 seconds for all lights to light up one by one. For undercab light, it wasn't bad, and the whole apartment flashed vividly, including the bedroom. I then tried mapping all lights to left (red) and right (blue) flipper. Due to the quick changes, the lights could not keep up. Some commands were ignored as they were issued turn off commands before having a chance to light up. Splitting the lights between the two bridges would have reduced latency, but the Hue API does have support for groups. This increases latency, but will attempt to sync and set all lights simultaneously instead of gradually for each command. Start with 1, take it from there. arngrim suggested undercab light. It's a very good match with one of the newer +1000 lumen LED-strips. Debugging Check your DirectOutput.log file for details if nothing works. It should say PhilipsHueController for those specific commands, whether connection was made, whether your IP and key was read of Cabinet.xml, and connection status so you can check your actual latency to the bridge after a game. Wear and tear The bulbs are not cheap. They will break a whole lot quicker being controlled like flashers. Use common sense. I take no responsibility for broken hardware, damages, risks, downtime, pissed off better halfs etc. Example Config.xml attached, with some extra bonuses. Cabinet.xml pincab_dofhue_20170529_1.mp4
  19. File Name: Scarface DOF (JPSalas)(2013)(Arngrim mod)(1.0)(FS)(vp9.15) File Submitter: jpsalas File Submitted: 03 Nov 2013 File Category: Original Creations Permission to Mod: Contact Author First.VP Version: v9.15 Here is the DOF version of Scarface! The requirements to run it: A cabinet, a ledwiz DOF software installed http://vpuniverse.com/index.php/index.html/_/articles/vparticles/direct-output-articles/directoutput-framework-announcement-r32 The ledwiz configuration is available here http://vpuniverse.com/ledwiz/login.php once you configured your account to use DOF instead of Legacy ledcontrol, on your account tab of configtool, retrieve the ini files and enjoy it Click here to download this file
  20. Hello, I have an idea about adding a new feature for my pinball machine. I will get a professional printed Bezel for the Backglass (Screen) with my own design. Thus I want to put some LEDs behind the Bezel to illuminate it like some real machines do (some with effects). For this I need some more custom output channels of DOF (in my case 4 custom non RGB outputs). Is it possible to add some more? If yes - how? Could this be a feature for the DOF Config Tool? Adding a flexible number of Custom (Single/RGB) Outputs with a naming option? Thank you very much! Greetings, BlackZero
  21. Heyah! I found out about Virtual Pinball Cabinets about 3 years ago. I am currently building one and want to share my experience, because this forum and its members helped a lot! So, there will be lots of information and pictures upcoming soon! I hope to inspire others to build a cabinet. And I want help out other members by answering questions about my project and by giving advice. Two pictures for starter: - First project picture (March 2015) - Current state of interior (August 2016)
  22. File Name: Trigon 2.0 DOF version File Submitter: arngrim File Submitted: 01 Sep 2014 File Category: Original Creations Permission to Mod: YesVP Version: v9.9.0 - DX9 Added DOF mapping in the script and needs to be combined with DOF ini version 1318 at least Added 2 digits to the backglass to go upper than 10.000.000 Moved non mech sounds to backglass output for users with 2 sound systems, the others are not affected Added option to disable mech sounds line 17 of trigon_engine.vps ' dofS constant removes the mech sounds, redundant with DOF and noisy toys Const dofS = 1 Click here to download this file
  23. Hello everyone First of all, thanks in advance to everyone helping me with this! I've been building a Pinball Cabinet for the past few months and I am getting close to "finishing" it. If you want to check it out, use this link. My Pinball Cabinet (updates to come when everything is working) I am currently experiencing two issues with the Direct Output Framework. One shall be addressed here, the other one in this post: DOF issue #2: No flasher-feedback with otherwise working PinballX plugin I've been trying to solve these issues myself for the past few days/weeks, but failed, since I am not very experienced with DOF yet. I do not know whether these two issues are related. --- DOF issue #1: PWM-output on 2nd LEDWiz not working correctly - All RGB toys connected to a 2nd LEDWiz do not output in the full color spectrum. Only 7 colors are possible (red, lime/green, blue, yellow, cyan, magenta, white). It seems that the LEDs three channels are either «ON» or «OFF» and that the PWM/intensity settings are not handled properly by my current DOF setup. - DOF toys affected on the 2nd LEDWiz: RGB flippers (ports 5,6,7), RGB magnasave left (ports 10,11,12), RGB magnasave right (ports, 13,14,15), RGB undercab complex (ports 25,26,27). Those are all RGB toys connected to the 2nd LEDWiz. - When triggered by other software tools (LEDWiz software by GGG, LEDBlinky) all of the above outputs/ports behave normally. When adjusting intensities with those tools, single output colors are dimmable. And using multiple outputs/ports with different intensities results in a wider color spectrum. This is why I believe that my issue is related to my DOF setup or DOF itself and not to my LEDWiz controllers or related hardware (Zebsboards). - RGB toys connected to the 1st LEDWiz are not affected by this issue and light in full color spectrum. Those toys are: 5 flasher outside left throughout 5 flasher outside right. Ports used: 1-15. - When adjusting the «Custom Brigthness» setting in the DOF Config Tool in the Ports assignment tab, the brightness of all my RGB toys adjust properly, but still only with 7 colors for those on the 2nd LEDWiz. --- Further information on this issue and my current DOF setup. - I use this DOF R3 Beta version: DOF R3 Beta Build 5812.27024. As far as I remember, I already had this issue when using DOF R2. - I use this B2S Server version: B2S Server. - I use a two identical GlobalConfig files (globalconfig_B2SServer.xml and globalconfig_PinballX.xml) and the ini-Files created by the DOF Config Tool (directoutputconfig.ini and directoutputconfig2.ini), but no Cabinet.xml or dedicated table config files. - For now I only use 2 LEDWiz, which are listed in the «My Account» tab of the DOF Config Tool. A Teensy is supposed to be added soon. --- Help required As stated above, I am not very familiar with DOF yet and don't see a way to solve this issue myself. That's why I need your help and would greatly appreciate it. I feel that this issue, and the other one mentioned above, are limiting my experience while playing my Pinball Cabinet. So, what can I do to help you guys to help me solve these issues? What additional information, logs, xml-Files, ini-Files, screenshots, videos etc. do you need? Or do you maybe already have a solution or know someone who had the same or similar issues? I'm looking forward to hearing from you guys. Thanks again in advance! --- Best regards from Switzerland fuzgi --- 1st Edit: I just figured out that when I use DirectOutputConfigTester.exe at least the under cab complex RGB toy changes its color (within the full spectrum) when enabling / pulsing different table effects.
  24. Hello, I hope there isn't a general feedback threat for DOF Table Configs - otherwise please append my threat there I am using 5 Flasher and 2 WS2811 Stripes for "PF Back Flasher MX" simultaneous. I noticed that changing tables at PinballX the light direction of the 5 flashers are opposed to the light direction of the "PF Back Flasher MX". Is this intended? Further more: At 5 Flashers the "5 Flasher Left" and "5 Flasher Center" are always flashing both together. Is this intended? Thank you very much! Greetings, BlackZero Edit: I found the solution for my 2nd request. "5 Flasher Left" should have this value for single operation: "$PBXWheelLeft White 80 W80 L2/$PBXWheelRight White 80 W240 L3/$PBXWheelPageRight|$PBXWheelPageLeft White 400 5 L4". I will try to submit this to public. Edit2: Also an easy task to change 5 Flasher direction ^^
  25. Hi Guys, We have a big update for users who have ledstrips controllers like Teensy or similar Currently, you had to use ini files provided from outside the configtool, this is over now, ALL tables have now ledstrips configs fo it in the configtool About the changes in the site itself, this is how the port assignment looks like now: We have now custom brightness for ledstrip toys, flasher toys, Strobe toy and Strobe MX toys, consolidated into that page now The Ledstrips variables section let you define the position of each variable used in the ledstrip toys, the shape of the emulated flasher, these configurations will affect all table configs So if you had lots of custom ledstrip configs in the configtool, if you want to revert all configs for one toy to public, to use these ledstrip variables, i added a button on the stats page where you can do that for a specific toy,, you select it, press on the revert button and it will do the job I don't have ledstrip on my cab myself, so I wanna thanks a lot Randr, Swisslizard and Gech who created the configs, helped in testing, finding bugs and suggest on improving the features
×