Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Search the Community

Showing results for tags 'DirectOutput'.



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
  • VPUniverse.com Online Virtual Pinball League
    • League Discussion
  • New Releases
    • B2S New Releases
    • Visual Pinball New Releases
    • Future Pinball New Releases
    • Front End & Support Files New Releases
  • Digital Pinball Cabinets
    • Cabinet Builds
    • Cabinet Discussion
    • PinCab/Pinball Hardware Development
  • Pin2DMD Forums
    • Pin2DMD General Discussion
    • Pin2DMD DMD Colorization Works in Progress
    • Pin2DMD Research & Ideas
  • Planet Visual Pinball
    • Visual Pinball Support
    • Visual Pinball General Discussion
    • Visual Pinball Development
  • Planet Future Pinball
    • Future Pinball General Discussion
    • Future Pinball Support
  • Artwork
    • Backglass Artwork
    • Playfield Artwork
  • Pinball Front-Ends
    • HyperPin Support
    • Pinball X Support
    • Pinup Popper
  • PinMAME
    • PinMAME Development
    • PinMAME Support
  • Real Pinball & Arcade Gaming Discussion
    • Real Pinball Discussion
    • Arcade Gaming Discussion
  • Table Development and Releases
    • Works in Progress
    • Table Requests
  • Table Development and Releases
    • Works in Progress
    • Table Requests
    • Resources
  • Direct Output Framework
    • Direct Output Announcements
    • Direct Output General Discussion
    • Direct Output Support
  • B2S Development
    • B2S Development Support
  • Console & PC Virtual Pinball
    • Other Virtual Pinball & Gaming Discussion
    • Pinball Arcade
    • Console & PC Gaming Discussion
    • ProPinball

Categories

  • Backglass Downloads
    • B2S - For Players
    • B2S - For Developers
    • Animated Backglasses
    • Backglass Resources
  • PinMAME
    • PinMAME Source
    • PinMAME Roms
    • ROM Colorizations
  • Visual Pinball
    • VPU Patching System
    • Visual Pinball - 10.x.x
    • Visual Pinball - 9.x.x
  • Pin2DMD Files
    • Pin2DMD Documentation
    • Pin2DMD Firmware
    • Table Support Files
    • ROM Frame Dumps
    • Pin2DMD Tools
    • Pin2DMD Color Palettes
  • Future Pinball
    • Future Pinball Files
    • Future Pinball Tables
  • Direct Output Framework
  • Pinball Frontend Downloads
    • HyperPin Support Files
    • Frontend Artwork
    • Plugins
    • Media Managers
  • Development Resources
    • Table Resources
    • Table Creation Resources
    • Cabinet Resources

Product Groups

There are no results to display.

Categories

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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 12 results

  1. Hello and thnakyou for any help in advance. I am having trouble getting doflinx to launch. i suspect i havent configured it correctly. I have VPX installed and working fine with B2S backglass. I have a arduino mega flashed with LWclone that works fine with led blinky. Here is how I installed and configured directoutput/doflinx: - extracted DirectOutput_R3Beta_Build_5812.27024.zip to c:\DirectOutput\ - extracted DOFLinx V6.22.zip to c:\DirectOutput - unblocked all .dll and .exe files in c:\DirectOutput\ - set all .exe files to run as admin - made shortcut to c:\DirectOutput\ in c:\visual pinball\tables\plugins\ - deleted line 'LoadScript("ledcontrol.vbs"):Err.Clear' in c:\visual pinball\scripts\core.vbs - copied DOFLinx-FX3 B2S Backglass only-No toys.ini from sample inis folder to c:\DirectOutput\and renamed to DOFLinx.ini - went to http://configtool.vpuniverse.com - set 1 ledwiz device with start button on port 1 and launch button on port 2. didnt touch any other settings - generated config files - copyed directoutput.ini to C:\DirectOuput\ - copied tablemappings.xml to C:\DirectOutput\config\ - copied example cabinet config from https://directoutput.github.io/DirectOutput/cabinetconfig.html into new file c:\DirectOuput\config\cabinet.xml - ran global config editor - set ini files path to C:\DirectOutput\config\ - set cabinet config to C:\DirectOutput\config\cabinet.xml - saved global config file to C:\DirectOutput\config\GlobalConfiguration_b2SServer.xml - opened DOFLinx.ini - changed PATH_B2S_SERVER=C:\VP\Tables\ to PATH_B2S_SERVER=C:\visual pinball\Tables\ - opened vpx and loaded table - right clicked backglass. enabled plugins when i launch doflinx.exe i get a .net popup with an error, (photo attached). I am helping someone can point me in the right direction, cheers.
  2. Hi folks Please read the following points before asking for help with DOF issues: General As always RTFM! I know, reading manuals is maybe not the most interesting thing to do, but it often helps!DOF R2 Documentation: http://directoutput.github.io/DirectOutput/ Latest DOF WIP Documentation: http://pinball.weilenmann.net/docu/DirectOutputWIP/index.html In particular please make sure you read the pages on Installation and Configuration, Cabinet Configuration, Built in Toys, Built in Output Controllers. They contain a lot of sample xml structures which you can use for your own configs and there are explanations on most settings as well. Last but not least, here is a tutorial on the XML basics: http://www.w3schools.com/xml/default.asp DOF Installation Problems If DOF doesnt work, please check if it is installed correctly. Here are a few things to do: Double check your installation Instructions are on http://directoutput.github.io/DirectOutput/installation.html Make sure you really follow these instructions step by step. Check if DOF is visible for the B2S.Server Go to the B2S.Server settings screen and click the plugin settings button. This will open a new window, which should list DOF. If DOF is not visible there, check if DOF is in the right place (as explained in the installation instructions) and if the right B2S.Server instance is called (see next paragraph). Check B2S.Server installation(s) If the B2S.Server is working (backglass visible), but DOF is not visible in the settings window, your problem is probably that you have more than one B2S.Server instance on your machine and that VP calls a different B2S.Server instance than the one you think it is calling. Visual Pinball doesnt find the B2S.Server by its location in the filesystem (it is actually not relevant where you install the B2S.Server). Instead VP is looking up the B2S.Sever by its COM object name (that is the Createobject("B2S.Server") thing in the table scripts). This name is resolved by the system using a bunch of registry lookups, which will finally return the path to the B2S.Server dll file. If this path doesnt point to the B2S.Server which has DOF configured as its plugin, DOF will not be called. To fix this, try to reregister the B2S.Server instance for which you have installed DOF. Dont register any other B2S.Server instances on your machine. As a general rule of thumb, there is no reason to have more than one B2S.Server installation one a machine. IMHO it is bet to get rid of all duplicate installations if you have any. Unblock the files This is another typical installation problem, depending on how you put the DOF files into their installation dir, windows thinks that they might be dangerous (becaus you have downloaded them) and will block access to the files. This will stop DOF from working. Check if all DOF files are unblocked. Details can as usual be found here: http://directoutput.github.io/DirectOutput/installation.html#installation_unblockauc Enable Logging / Create a Global Config file For installations which only use a ledwiz or some other automatically detected controllers a global config file is not mandatory. However, if you have problems with your installation you should create a global config file, so you can enable the logging function of DOF. Instruction for global configs are overe here: http://directoutput.github.io/DirectOutput/globalconfig2.html Cabinet Configuration problems Most problems with config xml files are caused by a bad file structure resp. So before calling for help, please make sure your file contains valid XML. To check this open your xml file in Firefox, Chrome or even Internet Explorer. All those browsers are able to show properly structured xml in a nicely formatted fashion and even allow to expand and collapse parts of the file. If there are structural problems present, the browsers will not show the nicely formated structure and a error message (more or less helpful) is displayed. Use a tool which knows about XML to edit your files (plain text editors usually dont know xml by heart). There are quite a few XML editors available on the internet (I'm using Microsofts Visual Studio, but that is a full development IDE). These editors will help you to produce valid xml structures and typically they will also produce nicely formated files (which makes them much easier to read). Try to reduce the number of potential problems. E.g. if you try to extend your cabinet config for ledstrips and a Teensy controller get rid of everything you dont need to get that new stuff running (remove all ledwiz configs, all ledwizequivalent toys whiche are not related to the teens controller and so on) or start a new config file from scratch. This will make it much easier to detected the cause of a config problem. Once you have your new toys working or fixed the problem you can put all the other stuff back in place. If you still have trouble with your config files, please upload them to dropbox, Google drive or any other service you like and post the links instead of the file content! Dont post lengthy XML structures to the forums directly. It is much easier to just download a file and open it in a suitable xml editor instead of scrolling through long xml structures which are in many cases no even formated nicely. Posting help requests Dont ask for help using PMs Everybody should be able to learn from problems that occured earlier. For this reason I kindly request, that ask for help in the forums instead of private messages. Create your own thread Create your own thread with a decriptive name (e.g. Pinballwizard Ledstrip Config Problems) instead of reusing/hijacking another thread. It much simpler to keep track of things if they are in their own place. Threads where problems of several users are dicussed are becomming hard to follow pretty fast and it is more benefitial to concentrate on the actual problem solving than on trying to keep track of several different topics in one thread. Only reuse another thread if you have exactly the same problem as the one described in the thread first. "DOF is not working" is probably not the same problem for you as for someone else. Explain what you have tried Please explain in detail what you have tried already and what the outcome was. This will make it much easier to narrow down the possible causes of problems and will save us a lot of questions. Dont post lengthy file content It is much easier to just download a file and open it in a suitable tool, than to scroll through many pages of data in the forums. Therefore, please upload anything thats more than just a bunch of line to dropbox, google drive, one drive or any other service you like and post the link instead of the file content. If uploading several files or putting serveral file in one zip file, please give them a meaningfull name (Screenshot{Number}.jpg isnt a helpful name, B2SServerPluginSettings.jpg would be a good name). Be patient Everyone who is trying to help is only doing this a a hobby and we all got real life jobs and other duties as well. Therefore answers do sometimes take a bit longer. Nagging will not improve response times! Thanks and all the best Tom / Swisslizard
  3. Hello, I am in need of some help with DOF! I tested out my LEDWiz and all outputs are (pretty much) working, so I know that this is not a hardware issue with the LEDWiz. I am wondering if I don't have the "correct" ledwiz for my configuration? Any help is greatly appreciated. I am chopping at the bit to get this thing up and running...yes, it is a new install; I probably should have said that. Below is my log of DOF. Also, my DOF is running and active in the backglass server when I run my visual pinball tables. Thanks, Chris --------------------------------------------------------------------------------- 2015.08.23 21:55:24.086 DirectOutput Logger initialized 2015.08.23 21:55:24.086 DirectOutput Version 0.8.5307.1702 as of 2014.07.13 00:56 2015.08.23 21:55:24.086 Global config loaded from: C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml 2015.08.23 21:55:24.086 Loading Pinball parts 2015.08.23 21:55:24.086 Loading cabinet 2015.08.23 21:55:24.086 No cabinet config file loaded. Will use AutoConfig. 2015.08.23 21:55:24.086 Cabinet auto configuration started 2015.08.23 21:55:24.195 EXCEPTION: Could not init LedWiz 2015.08.23 21:55:24.195 EXCEPTION: Thread: 2015.08.23 21:55:24.195 EXCEPTION: Message: Unable to load DLL 'LEDWiz': The specified module could not be found. (Exception from HRESULT: 0x8007007E) 2015.08.23 21:55:24.195 EXCEPTION: Stacktrace: at DirectOutput.Cab.Out.LW.LedWiz.LWZ_SET_NOTIFY(MulticastDelegate notifyProc, UInt32 list) 2015.08.23 21:55:24.195 EXCEPTION: Stacktrace: at DirectOutput.Cab.Out.LW.LedWiz.StartupLedWiz() 2015.08.23 21:55:24.195 EXCEPTION: Targetsite: Void LWZ_SET_NOTIFY(System.MulticastDelegate, UInt32) 2015.08.23 21:55:24.195 EXCEPTION: A exception occured during auto configuration for output controller(s) of type LedWizAutoConfigurator. 2015.08.23 21:55:24.195 EXCEPTION: Thread: 2015.08.23 21:55:24.195 EXCEPTION: Message: Could not init LedWiz 2015.08.23 21:55:24.195 EXCEPTION: Stacktrace: at DirectOutput.Cab.Out.LW.LedWiz.StartupLedWiz() 2015.08.23 21:55:24.195 EXCEPTION: Stacktrace: at DirectOutput.Cab.Out.LW.LedWiz..ctor() 2015.08.23 21:55:24.195 EXCEPTION: Stacktrace: at DirectOutput.Cab.Out.LW.LedWiz.GetLedwizNumbers() 2015.08.23 21:55:24.195 EXCEPTION: Stacktrace: at DirectOutput.Cab.Out.LW.LedWizAutoConfigurator.AutoConfig(Cabinet Cabinet) 2015.08.23 21:55:24.195 EXCEPTION: Stacktrace: at DirectOutput.Cab.Cabinet.AutoConfig() 2015.08.23 21:55:24.195 EXCEPTION: Targetsite: Void StartupLedWiz() 2015.08.23 21:55:24.195 EXCEPTION: InnerException 1: Unable to load DLL 'LEDWiz': The specified module could not be found. (Exception from HRESULT: 0x8007007E) 2015.08.23 21:55:24.195 Cabinet auto configuration finished 2015.08.23 21:55:24.195 Cabinet loaded 2015.08.23 21:55:24.195 Loading table config 2015.08.23 21:55:24.195 Warning: No table config file found. Will try to load config from LedControl file(s). 2015.08.23 21:55:24.195 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName ACDC 2015.08.23 21:55:24.211 Loading LedControl file C:\Program Files (x86)\Visual Pinball\Tables\directoutputconfig.ini 2015.08.23 21:55:24.491 1 directoutputconfig.ini or ledcontrol.ini files loaded. 2015.08.23 21:55:24.491 Config for RomName ACDC exists in LedControl data. Updating cabinet and config. 2015.08.23 21:55:24.507 Table config loading finished 2015.08.23 21:55:24.507 Pinball parts loaded 2015.08.23 21:55:24.507 Starting processes 2015.08.23 21:55:24.507 Initializing cabinet 2015.08.23 21:55:24.523 Cabinet initialized 2015.08.23 21:55:24.523 Framework initialized. 2015.08.23 21:55:24.523 Have fun! 2015.08.23 22:00:21.222 Finishing framework 2015.08.23 22:00:21.232 Finishing cabinet 2015.08.23 22:00:21.232 Cabinet finished 2015.08.23 22:00:21.232 DirectOutput framework finished. 2015.08.23 22:00:21.232 Bye and thanks for using!
  4. I have DOF working with one ledwiz and one SainSmart 8-channel. I would like to add 2 more SainSmart 8-channel to the setup. I have tried to edit the cabinet xml and cant get it right. I will uplaod what I have at this time. I have only tried to get one more working at this time thinking if I get it to work the next one will be easy. If somone could help that would realy be awsome. Thanks Rich Cabinet.xml
  5. Hi I have One ledwiz and one sainsmart. I have directoutput working and ledwiz not the sainsmart. I don't have a cabinet xml and don't know how the make one. I go to the web sight with the config tool and it makes two ini files. I will attach the files and my DOF Log. I think I am running in legacy mode because it looks like it is running off the ini files. Thanks Rich directoutputconfig(4).zip
  6. Version V0.8.5307.01702

    4,865 downloads

    During the past few month a lot of new things have been added to the DirectOutput framework (DOF). Since most of my new ideas have been integrated by now it is time for a second release (R2). Watch the following video to see some of the new features, in particular the addressable ledstrips, in action: While I have been busy with the DOF extension Arngrim has added a lot of new functionality to the config tool, so the new functionality can be configured through the config tool. The config tool also got a new name and logo, but it still resides in its old location. Please be sure to read the following paragraphs for download and update instructions. Keep (virtual) pinball alive and all the best! Swisslizard / Tom Upgrading your installation To upgrade your DOF installtion just download DOF R2 and copy all the files in the package to the directoy where you have installed DOF and say yes if you are prompted to overwrite files. For new DOF installtions, please consult the documentation. Important note: DOF R2 uses a new global config structure. So if you use a global config file, please create a new global config file using the global config editor in the package. If DOF does not work for you, be sure to unblock the DLL and EXE files. Sometimes windows tends to block downloaded files. For instructions read: http://directoutput.github.io/DirectOutput/installation.html#installation_unblockauc Documentation The documentation of the framework is available on GitHub. It contains a lot of information on the installation, architecture and the configuration of the framework, as well as the fully documented object model. The pages about the installation and supported hardware might be a interesting starting point. http://directoutput....tput/index.html Support & Forum If you have questions about the framework (please read the docu first) or want to discuss something, please visit the support forum. http://vpuniverse.co...tput-framework/ Source Code The source code of the DirectOutput framework is available on Github: https://github.com/D...ut/DirectOutput
  7. File Name: DirectOutput framework R2 File Submitter: swisslizard File Submitted: 13 Jul 2014 File Category: Direct Output Framework During the past few month a lot of new things have been added to the DirectOutput framework (DOF). Since most of my new ideas have been integrated by now it is time for a second release (R2). Watch the following video to see some of the new features, in particular the addressable ledstrips, in action: While I have been busy with the DOF extension Arngrim has added a lot of new functionality to the config tool, so the new functionality can be configured through the config tool. The config tool also got a new name and logo, but it still resides in its old location. Please be sure to read the following paragraphs for download and update instructions. Keep (virtual) pinball alive and all the best! Swisslizard / Tom Upgrading your installation To upgrade your DOF installtion just download DOF R2 and copy all the files in the package to the directoy where you have installed DOF and say yes if you are prompted to overwrite files. For new DOF installtions, please consult the documentation. Important note: DOF R2 uses a new global config structure. So if you use a global config file, please create a new global config file using the global config editor in the package. If DOF does not work for you, be sure to unblock the DLL and EXE files. Sometimes windows tends to block downloaded files. For instructions read: http://directoutput.github.io/DirectOutput/installation.html#installation_unblockauc Documentation The documentation of the framework is available on GitHub. It contains a lot of information on the installation, architecture and the configuration of the framework, as well as the fully documented object model. The pages about the installation and supported hardware might be a interesting starting point. http://directoutput....tput/index.html Support & Forum If you have questions about the framework (please read the docu first) or want to discuss something, please visit the support forum. http://vpuniverse.co...tput-framework/ Source Code The source code of the DirectOutput framework is available on Github: https://github.com/D...ut/DirectOutput Click here to download this file
  8. During the past few month a lot of new things have been added to the DirectOutput framework (DOF). Since most of my new ideas have been integrated by now it is time for a second release (R2). What is new in DOF R2: Support for Sainsmart and other FT245R based controllers Pacled64 problems fixed Support for a controller for WS2811 based ledstrips. SMD version of the controller should be ready in a few weeks. LedWiz uses now the whole value range from 0 to 49 (instead of only 48 before) Better toy objects for Shaker and GearMotor. New settings for MinPower, MaxPower, KickstartPower and KickStartDuration. LedStrip toy which allows for the support of addressable ledstrips The toy support simple strips, but also two dimensional arrays of ledstrips. RGBAToyGroup and AnalogAlphaToyGroup toys support the grouping of RGB toys (e.g. RGBLeds) resp. AnalogAlpha toys (e.g. single color lamps) in arrays, so they can be controlled be the same effects as the ledstrips. Most toys do now support fading curves (either predefined curves or your own curves can be used) to fine tune the fading behaviour for the toys (Docu still pending) New general use effects (e.g. ValueInvertEffect) have been added. Special effects for LedStrips and toy groups, including a bitmap animation effect, have been added (Check out the video). Loads of new config options for the config ini files are available as well. Colors in ini files can now also be specified as hex colors (#ff0000 for red) in addition hex colors can be used directly in the effect configs. Conditions for effect triggering in ini files, e.g. (S48<>0 and S49=0) will only trigger the effect of solenoid 48 is active and solenoid 49 is inactive. Lists of table elements can also be used to trigger effects, e.g. S48|S49 will trigger the effect if either solenoid 48 or 49 is activated. ini Files do now support variables on global and table level (Sorry, docu not yet written).. A update notification has been added, which will ask you to update DOF if you are using ini files which require a new DOF version to support all settings. The global config system has been changed to make it a bit easier to understand. There is even a small tool to edit your global configs: GlobalConfigEditor.exe Many small changes behind the scenes and some bugs fixed as well. Watch the following video to see some of the new features, in particular the addressable ledstrips, in action: While I have been busy with the DOF extension Arngrim has added a lot of new functionality to the config tool, so the new functionality can be configured through the config tool. The config tool also got a new name and logo, but it still resides in its old location. Please be sure to read the following paragraphs for download and update instructions. Keep (virtual) pinball alive and all the best! Swisslizard / Tom Upgrading your installation To upgrade your DOF installtion just download DOF R2 and copy all the files in the package to the directoy where you have installed DOF and say yes if you are prompted to overwrite files. For new DOF installtions, please consult the documentation. Important note: DOF R2 uses a new global config structure. So if you use a global config file, please create a new global config file using the global config editor in the package. Documentation The documentation of the framework is available on GitHub. It contains a lot of information on the installation, architecture and the configuration of the framework, as well as the fully documented object model. The pages about the installation and supported hardware might be a interesting starting point. http://directoutput....tput/index.html Downloads The DirectOutput framework R2 can be downloaded from http://vpuniverse.co...tput-framework/ Support & Forum If you have questions about the framework (please read the docu first) or want to discuss something, please visit the support forum. http://vpuniverse.co...tput-framework/ Source Code The source code of the DirectOutput framework is available on Github: https://github.com/D...ut/DirectOutput
  9. After months of development, I more than happy to announce the DirectOutput framework for virtual pinball cabinets. Since I did not like the limitations (not enough outputs) and problems (stuttering) with the current ledontrol.vbs solution to control the outputs of my cabinet, I have started to implement a completely new system to control output hardware connected to virtual pinball cabinets. During the past months the project has grown quite a bit larger than expected and more and more options have been added. A lot of testing has been done by a group of alpha testers and myself as well. The result is what I call the DirectOutput framework (DOF). Since DOF has proved to be pretty stable during the alpha testing period, beta testing starts today. For this phase of the project, it would be great to have a few more people joining for beta testing. Please read the paragraphs below for more information. Keep (virtual) pinball alive and all the best! Swisslizard / Tom What you get Key features of the DirectOutput framework: Support of up to 16 LedWiz and 4 Pacled64 units (including a mix of them). Support of Art-net/DMX. Multithreaded to ensure optimal performance and avoid stuttering issues. Integration with B2S.Server. Support for EM tables. Loads of new config options. Extendable through scripting. Extendable object oriented architecture. Coded in C#. Fully documented code. More new developements: Since DOF can support more than one output controller, Degoor has extended his great LedWiz config tool with new functionality to allow the configuration of more than one output controller. Arngrim has reviewed most of the configs in the config tool. The config tool will also support a 10 contactor setup in addition already existing 8 contactor setup. Configuration DOF supports two different configuration schemes: Natively the framework uses XML files to store its configurations. The XML based configs allow you to configure every aspect and option of the framework. The config files allow for all config option, maximum flexibility, but they do also add some addition complexity. Ledcontrol.ini files like the ones used for the legacy ledcontrol.vbs solution can be used for the configuration as well. Together with the auto config features for some of the supported hardware, they will allow for a configuration with very little effort. If more than one LedWiz and/or PacLed64 is in use, several Ledcontrol.ini files can be used for the configuration. Due to the limitations of ledcontrol files, not all options and aspects of the framework can be configured. Supported hardware Currently DOF is supporting the following hardware: LEDWiz from GroovyGameGear The use of up to 16 LedWiz units is supported by the framework. DOF can even detect and configure LedWiz units automatically. PacLed64 from Ultimarc Up to 4 PacLed64 units can be used. PacLed64 units can be detected and configured automatically. Art-Net / DMX Art-Net and DMX are standards used to control light effects. On the market you can find tons of DMX controlled light effects ranging from small and cheap to very big and expensive. Planed hardware support: PacDrive from Ultimarc Driver for addressable RGB led stripes (WS2811/WS2812 based stripes). Support for other hardware (e.g. some home grown Arduino or Raspberry Pi based controller) is easy to implement. Therefore the number of supported controllers will likely grow over time. Documentation The preliminary documentation of the framework is already available on GitHub. It contains a lot of information on the installation, architecture and the configuration of the framework, as well as the fully documented object model. The pages about the installation and supported hardware might be a interesting starting point. http://directoutput.github.io/DirectOutput/index.html How it is working The DirectOutput framework is working as a plugin for Herwehs great B2S.Server. This means that every table using the B2S.Server can use the DirectOutput framework as well, usually without any changes to the table script. For more information on the B2S.Server plugin interface have a look at http://directoutput.github.io/B2SServerPluginInterface/ and for some sample plugin code you can go to http://directoutput.github.io/B2SServerSamplePlugin/ Since the outside interface of DOF is quite simple (currently only 3 methods), the implementation of interfaces to other pinball simulations should be easy. Sample code for a plugin host supporting DOF has already been developed and can be provided on request. Downloads Sorry, public downloads are not yet available. At this time the software is only accessible for the testers, but it will become available for everyone once beta testing has been completed. Support & Forum If you have questions about the framework (please read the docu first) or want to discuss something, please visit the support forum. http://vpuniverse.com/forums/forum/118-direct-output-framework/ Source Code As soon as the project is released for everyone, the source code for the framework will be published on GitHub and everybody is invited to download, change and extend the code. Testers wanted A good amount of testing has already been done by a group of very helpful enthusiasts and myself. Now, we would like to invite a few more people for the beta testing phase. If you want to participate in the testing you should at least have some basic idea how VP, Pinmame and B2S.Server interact, know a little bit about table scripting and you should be willing to read some documentation and follow the relevant discussions. If you are interested to help testing, please send my a PM. Please include your email address in the PM, so I can enable access to the Google drive containing the files for the testers. Since I can only work with a limited number of people at the same time (still need to manage the whole thing somehow), only a limited number of testers will be able to join initially. Thanks When developing software, coding is only a part of the work. Testing, doing configurations and encouraging the coder take a lot of time as well. Therefore I want to thank the following enthusiasts: Herweh for adding a plugin interface to his B2S.Server and enduringing my everlasting requests for changes and features. Arngrim for being the first to board the train and start testing, constantly finding bugs and most of all redoing and enhancing the configs in the LedControl config tool. Bent98 for testing and tryinging to help to mange the project somehow. Degoor for extending his Ledwiz config tool. Bill55, SirCheddar and Slydog for testing. Everyone else who was at some stage involved in the project for their support and interest in my work.
  10. Hello everyone There are now more than enough people doing beta testing for DOF. Since I still need to manage the testing, doing bugfixes and further developement, I will not accept any further requests for participation in the beta testing. Exceptions will only be made for pinheads having a cabinet with at least 2 output controllers (e.g. 2 ledwiz or a mix of ledwiz and pacled64). If testing progresses as well as it did so far, there will be a first public version in a few weeks. All the best Tom
  11. Hi guys I've been working hard lately to put a lot of new functionality into DOF. Arngrim has helped me a lot with the preliminary testing. So, please download the new DOF version from the google drive (B2S.Server remains the same), install it (just copy it over the old installation) and play a few games. If you want you can also try to configure some of the new features. Let me know if there are any issues. Here is a list of important changes: Layer support Effects and toys for RGBLeds and analog ouputs are now using layers to allow for more control of the resulting output. olors resp. Values in a layer do also have a alpha/transparency channel which will allow us to blend the colors/values in the layers. If a bottom layer is blue and top is a semi transparent red, you will get some mix of both. If one of the two blinks you get changing colors. The following picture might give you a clearer idea how the layer with their alpha channels work: This will work with any number of layers. Layers are also supported in LedControl files. For analog outputs (e.g. lamps or gear motors) the behaviour is the same as explained above. Whats different is that analog output do only have one value and a alpha channel, compared to RGBLeds which have 3 values and a alpha channel. New LedControl Config options The way how the ledcontrol file loader configures DOF has been changed completely (thats the biggest change apart from the layers). Instead of using special code to execute the effects defined in the ledcontrol file, DOF is now using native DOF effect classes. This does also allow for easy conversion of ledcontrol config to xml configs (A converter is in the works). New config options: M{Duration} specifies a minimum duration for the effect (e.g. S48 M5000). W{Duration} specifies a delay before the effect is triggered (e.g. S48 Red W250). Color settings in ledcontrol files can now have four parts. In addition to red, green and blue, you can also specify a optional alpha value (e.g. RedTransparent=48,0,0,24). If the alpha part is missing, DOF assumes that colors ,where at least one component is not 0, have a alpha value of 255, color 0,0,0 (black) will have a alpha value of 0. Instead of using named colors, the colors can now also be specified directly in the ledcontrol setting (e.g. S48 #ff0000 for fully opaque red or S38 #00ff0080 for transparent green). Note: These direct color definitions have a range of 0-255, not 0-48 like other ledcontrol settings). F{Duration} is used to define fading for the values/colors of a effect (e.g. S48 Red F500). In addition it is possible to use FUDuration} and FD{Duration} to specify separate durations for fading up and down. Try things like S48 Red/S48 Blue Blink F250 for some nice changing color effect. Ledcontrol settings do use layer. The first setting in a column goes into layer 1, second setting in layer 2 and so on. The default layer number can be overriden by specifying L{LayerNr} (e.g. S38 Red L3). Apart from these new settings all other settings should work as they always did. These new settings allow for many new, cool effects. Try things like S48 Red/S48 Blue Blink F250. LedControl file names To avoid confusion with the legacy ledcontrol.ini files, DOF does now support directoutputconfig.ini as the file name as well. In addition it does also support new names for the section in the files: [Colors DOF] works instead of [Colors LedWiz] [Config DOF] works instead of [Config outs] These changes will allow to use config files for DOF, which cant be read by the legacy ledcontrol.vbs which makes sure that ledcontrol.vbs wont use wrong files by mistake. Deegor will update the config tool soon to use the new names. The old filenames (ledcontrol.ini) and section names do still work as well. Cabinet config file The serialization process for output controllers has changed. It is not necessary anymore the specify the outputs in the cabinet.xml. If DOF exports a cabinet files it will also ommit the outputs. I hope this makes creating cabinet config files a bit easier. As before, if you only use ledwiz units you dont need a cabinet config file. Autodetection will detect and configure the ledwiz units automatically. Documentation Do to the new effects, toys, layer support and changes in the cabinet config file save process the docu is now really outdated for these areas. I working on the update, but that is will take a little while (Will not be able to do a lot of DOF work for the next 2.5 weeks). Com object You will probably not need this now, but the com object allows to embed DOF into almost any scripting language you can imagine. This means that there is now a easy interface to integrate DOF into almost any application. There is also a small exe to register the com object. More There are also loads of changes behind the scenes. More error handling, extended timer functionality and much more. All the best Swisslizard / Tom
  12. If you want to do more configs in DOF than just using autodetection and ledcontrol files, the first thing you will need is a global config file. This file tells the framework where to look for which data. There is a special page in the docu on the global config file: http://directoutput.github.io/DirectOutput/globalconfig.html Here is the content of the global config I'm mostly using (it is also attached so you can easily download it): <?xml version="1.0" encoding="utf-8"?> <!--Global configuration for the DirectOutput framework.--> <GlobalConfig> <LedControlIniFiles /> <CabinetConfigFilePatterns> <FilePattern>{GlobalConfigDir}\cabinet.xml</FilePattern> </CabinetConfigFilePatterns> <CabinetScriptFilePatterns></CabinetScriptFilePatterns> <TableScriptFilePatterns></TableScriptFilePatterns> <TableConfigFilePatterns> <FilePattern>{GlobalConfigDir}\{TableName}.xml</FilePattern> </TableConfigFilePatterns> <EnableLogging>true</EnableLogging> <LogFilePattern>{DllDir}\DirectOutput.log</LogFilePattern> <GlobalScriptFilePatterns /> </GlobalConfig> This global config file tell the DirectOutput framework to look for a cabinet config file in the config dir (subdirectory called config in the install dir of DOF) and for table configs named like TableName.xml in the table dir. It does also turn on the logfile in DOF, which will be written to the install dir of DOF. All these paths can point somewhere else if you prefer other locations for your files. If no table or cabinet config file can be found in the specified location, the framework will try to find a table config in the ledcontrol files and use autoconfig for the cabinet configuration. This is also the reason why DOF will even work if no configs, apart from a ledcontrol file are present. This global config file does not contain definitions for ledcontrol files. This means that the framework will automatically start to look for ledcontrol files named ledcontrol.ini, ledcontrool2.ini and so on. If yo8u prefer other names for your ledcontrol files or want to assign specific numbers to them, you can list those files in the LedControlIniFiles section of the file. All the best Tom GlobalConfig_B2SServer.xml
×
×
  • Create New...