swisslizard

This isexcellent. Thanks for sharinging your knowledge.

There are several resoans why DOF is working differently. The most important reason is that DOF is just a extension/plugin to the B2S.Server. The only thing which the B2S.Server can consume are table evenets (either coming from Pinmame or from E commands in the table script). So there isn't much of a option to do things differently. Another reason is flexifility. If specific toy would be targeted in the table script, it would be very hard to start using a toy which wasn't around when the table was scripted and everybody who has a different hardware setup would run into problems (e.g. I have 10 contatcors, 5 flashers, approx 300 other rgb leds, plus some DMX effects, but most table creators have a somewhat more moderate setup). By simply processing events, DOF can easily be adjusted to different hardware setups. Another point is separation of responsibilities. With the event based system which DOF is using, the table author only has to tell DOF that a element on a table has changed its state, but he doens't need to care what should happen in terms of feedback. So that makes life a bit easier for the table authors since they dont need to care about DOF.

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

I have added your method to the DOF docu. The published docu will be updated once we have a next DOF release.

This is excellent!

Sorry, guys I cant tell you what the fix is. I've just told Herweh about the problem and he has done some small change to the B2S.Server, which seems to fix the problem. It seems that is wasn't a DOF, but a B2S.Server problem. @Randr: Yes, if you like you can add feedback to flipperless tables. No problem. You just need to put the right EM Table commands into the script of the table.

Can you please play a game of AbraCadabra and a game of Baseball and post the logs. Maybe that will help to find the reason why one table is working and the other not.

@jadflat: You will need to create a outputcontroller class for those things. This class has to implement the IOutputController interface, so DOF will recognize it as a output controller. This interface defines a few methods and properties which have to be implemented by your outputcontroller, so DOF con use it.ö Have a look at the NullOutputController class in the DirectOutput.Cab.Out namespace to get a idea what you have to do.

@jadflat: So far nothing has been developed for arfx. Just had a very quick look at their website and I guess it would be possible ti integrate a driver into DOF. Since I dont have that hardqare, I cant do that myself (cant integrate a driver without being able to test it). If someone want to try anyway, I'll be happy to help.

Finally, here is the first release of the DirectOutput framework. Far to much time has been put into coding and testing of this library, but now I believe it will work well for everyone. Since I did not like the limitations (not enough outputs) and problems (stuttering) with the legacy solution to control the outputs of my cabinet, I have created 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. The result is what I call the DirectOutput framework (DOF). If you own a pinball cabinet and want to use the DirectOutput framework, please read the paragraphs below for details. 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. 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.github.io/DirectOutput/index.html Downloads The DirectOutput framework can be downloaded from http://vpuniverse.com/forums/files/category/61-direct-output-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.com/forums/forum/118-direct-output-framework/ 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 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. 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. Source Code The source code of the DirectOutput framework is available on Github: https://github.com/DirectOutput/DirectOutput 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. Everyone who has been active during the beta testing. Everyone else who was at some stage involved in the project for their support and interest in my work. This post has been promoted to an article