[INFO] DOF 2 et Configtool 2

Salut les gars,

Ces deux merveilleurs outils qui nous permettent d'avoir du force feedback dans nos pincab sont updatés, nouvelle version

Voici les changements de DOF

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.
  
•  LedStriptoy 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 fromhttp://www.vpforums....s&showfile=9737
 
 
Source Code
 
The source code of the DirectOutput framework is available on Github:https://github.com/D...ut/DirectOutput



Et voici les changements de configtool de moi   , et un petit tuto, sorry c'est en anglais


Hello Guys,
 
As you may have seen, DOF R2 is out since yesterday, it has been prepared in coordination with the extension of the Config Tool that can use new functionalities of DOF R2, with a lot of changes, some visible for end users, a lot of for admins to manage a lot of key elements used in the tool, and a redesign of the data model.
 
Basically, the new Config Tool is multi controller based, you can currently have a maximum of
 
16 Ledwiz
1 Pacdrive
4 Pacled
4 Ledstrip board (made by Swisslizard) for adressable ledstrips (these have a lot of new effects around, check the DOF manual for details)
10 SainSmart
16 Artnet controllers
 
configurable in the same time on the tool, and manageable by DOF as well.
 
To be able to do that, in DOF and configtool we have defined numbers of devices so DOF can easily know what device is used
 
Like Ledwiz can have directoutput.ini from 1 to 16
Pacdrive is ini 19
Sainwmart from 40 to 49
Artnet is from 100 to 116
 
We can add as many as controllers thanks to the controller management tools by admin.
 
Let's have a review of all the current and new functionalities of the tool.
 
HOME
 
at the home page, you can find the latest DOF, latest B2S.Server and a DOF package ready which can be useful for newcomers
***these files will be updated tonight
 

 
 
MY ACCOUNT
 
1* The API Key, for those who don't know what is the usage, this is used by the excellent tool of Zarquon, which allows you to download latest ini files without the need to log into the website, essential!
 
check here : http://vpuniverse.com/forums/topic/332-ledwiz-configtool-downloader/
 
you can put the bat file at the start of Windows in your cab for example
 
2* You can define the number of the devices you have, most of you will have one ledwiz but who knows in 6 months
 
3* An option to define the brightness of the flashers (only), on request by users that have their flashers too bright, we can now diminish the intensity, without altering the colorr, FF is the more bright, 00 is off, you need to be near 00 to see a big difference
 
4* Allows you to not generate nofeedback files, when you download ini files you have directoutputconfig.ini and directouptutconfignofeedback.ini
this nofeedback shuts down the noisy toys that you defined on your setup, there are not used as such, because we will need an update from the frontend and dof to use them, so they can deactivated (they are by default)
 
5* You need to define Directoutput framework to benefit for all the DOF options and config files, or you will be stuck with legacy configs, outdated, not optimized, missing a LOT of tables, i know that quite some users are still in Legacy...
 

 
PORT ASSIGNMENT
 
1* So, you will see all your devices on the device frame, with the ini file that will be generated, and the number associated
 
2* Devices have a custom range of outputs, from 1 to 512, depending on how the admins have defined the controller of the tool, but don't worry, if you can see 512 outputs for Artnet, the ini files will only create the necessary outputs based on the higher output number configured for your device. In this example, the directoutputconfig 100 ini will have only 11 outputs on each rom lines, like
 
bighit,0,0,0,0,0,0,0,0,0,0,0
 
3* That is not new but you can define the shaker min and max intensity, so if you define I36 as max and I12 as min, I8 in the files will become I12 and I48 will become I36
 
4* Same as 3* but remove the fadings, which is very cool to not stop the fan brutally, if your hardware setup can handle it
 
5* This option can define the effect of contactors when they are triggered for a target or a drop target, like i set up my latest configs at s** 300 I32 for targets and s** 150 I40 for drop targets, you can now define the settings yourself, if you don't want any cange of intensity or duration, leave it to 60 and 48 for both.
My recommandation is 300 32 for target and 180 40 for drop target
 
it will appear like this in your ini files at the top
 
[Variables DOF]
 
t = 180 I40
dt = 300 I32
 
*** Database needs to be adapted tonight, no config is using these variables for the moment, and it will be only valid for the configs stamped DOF Revision 1.7




 
TABLE CONFIG
 
1* the table details have additional info, the history of the table configs
 
2* table variables are available, this is useful for DOF specialists, it allows you to define a table variable that can be replaced when the ini file is used by DOF
 
this is visible like this in the ini file on top of the script
 
[TableVariables]
 
simpprtf,Test=(S48=1)/Test2={(S46=1/S22 <> 0)}
twenty4,test3=(S21=1)
antar2,test3=(S21=1)
 







 
Bottom of the table config
 
the table colors, to easily see how the color looks and by clicking on a color, it will paste the color name where the cursor was, if you were on a output line on the left, quite useful imho
 

 
And you can see in the new ini files that all these color are hexadecimal
 
[Colors DOF]
 
White=#FFFFFFFF
Red=#FF0000FF
Lime=#00FF00FF
Blue=#0000FFFF
Yellow=#FFFF00FF
Cyan=#00FFFFFF
Magenta=#FF00FFFF
Silver=#C0C0C0FF
Gray=#808080FF
Brown=#800000FF
Olive=#808080FF
Green=#008000FF
Purple=#800080FF
Teal=#008080FF
Navy=#000080FF
Dark_red=#8B0000FF
Black=#000000FF
Firebrick=#B22222FF
Crimson=#DC143CFF
Tomato=#FF6347FF
Coral=#FFFFEFFF
Indian_red=#CD5C5CFF
Light_coral=#F08080FF
Dark_salmon=#E9967AFF
Salmon=#FA8072FF
Light_salmon=#FFA07AFF
Orange_red=#FF4500FF
Dark_orange=#FF8C00FF
Orange=#FFA500FF
Gold=#FFD700FF
Dark_golden_rod=#B8860BFF
Golden_rod=#DAA520FF
Pale_golden_rod=#EEE8AAFF
Dark_khaki=#BDB76BFF
Khaki=#F0E68CFF
Yellow_green=#9ACD32FF
Dark_olive_green=#556B2FFF
Olive_drab=#6B8E23FF
Lawn_green=#7CFC00FF
Chart_reuse=#7FFF00FF
Green_yellow=#ADFF2FFF
Dark_green=#006400FF
Forest_green=#228B22FF
Lime_green=#32CD32FF
Light_green=#90EE90FF
Pale_green=#98FB98FF
Dark_sea_green=#8FBC8FFF
Medium_spring_green=#00FA9AFF
Spring_green=#00FF7FFF
Sea_green=#2E8B57FF
Medium_aqua_marine=#66CDAAFF
Medium_sea_green=#3CB371FF
Light_sea_green=#20B2AAFF
Dark_slate_gray=#2F4F4FFF
Dark_cyan=#008B8BFF
Aqua=#00FFFFFF
Light_cyan=#E0FFFFFF
Dark_turquoise=#00CED1FF
Turquoise=#40E0D0FF
Medium_turquoise=#48D1CCFF
Pale_turquoise=#AFEEEEFF
Aqua_marine=#7FFFD4FF
Powder_blue=#B0E0E6FF
Cadet_blue=#5F9EA0FF
Steel_blue=#4682B4FF
Corn_flower_blue=#6495EDFF
Deep_sky_blue=#00BFFFFF
Dodger_blue=#1E90FFFF
Light_blue=#ADD8E6FF
Sky_blue=#87CEEBFF
Light_sky_blue=#87CEFAFF
Midnight_blue=#191970FF
Dark_blue=#00008BFF
Medium_blue=#0000CDFF
Royal_blue=#4169E1FF
Blue_violet=#8A2BE2FF
Indigo=#4B0082FF
Dark_slate_blue=#483D8BFF
Slate_blue=#6A5ACDFF
Medium_slate_blue=#7B68EEFF
Medium_purple=#9370DBFF
Dark_magenta=#8B008BFF
Dark_violet=#9400D3FF
Dark_orchid=#9932CCFF
Medium_orchid=#BA55D3FF
Thistle=#D8BFD8FF
Plum=#DDA0DDFF
Violet=#EE82EEFF
Orchid=#DA70D6FF
Medium_violet_red=#C71585FF
Pale_violet_red=#DB7094FF
Deep_pink=#FF1493FF
Light_pink=#FFB6C1FF
Pink=#FFC0CBFF
Antique_white=#FAEBD7FF
Beige=#F5F5DCFF
Bisque=#FFE4C4FF
Corn_silk=#FFF8DCFF
Lemon_chiffon=#FFFACDFF
Light_golden_rod=#FAFAD2FF
Light_yellow=#FFFFE0FF
Saddle_brown=#8B4513FF
Sienna=#A0522DFF
Chocolate=#D2691EFF
Peru=#CD853FFF
Sandy_brown=#F4A460FF
Burly_wood=#DEB887FF
Tan=#D2B48CFF
Rosy_brown=#BC8F8FFF
Moccasin=#FFE4B5FF
Navajo_white=#FFDEADFF
Peach_puff=#FFDAB9FF
Misty_rose=#FFE4E1FF
Lavender_blush=#FFF0F5FF
Linen=#FAF0E6FF
Papaya_whip=#FFEFD5FF
Slate_gray=#708090FF
Light_slate_gray=#778899FF
Light_steel_blue=#B0C4DEFF
Lavender=#E6E6FAFF
Dim_gray=#696969FF
Dark_gray=#A9A9A9FF
 
 
 
STATS
 
you want to know if a toy is used a lot? for which tables? i made it for you
 

 
 
I think I didn't forgot anything, just that the moment you generate new files with the DOF Config Tool, you MUST have DOF R2 installed, or it won't work good and you will have a big popup on your backglass screen saying you need to update your DOF
 
Enjoy " />" />" />

Merci arngrim.
Je déplace ton topic dans les tutos.

Merci

j'ai bien galéré pendant 2h ce matin, concours de circonstance, le nouveau dof est sortit et je bidouillais pour faire deux dossiers pour vp et physimod, comme j'ai le .bat qui fait les mise à jour tout seul d'un coup plus rien ne marchais, le hasard c'est fou..... bon j'ai pensé au tout nouveau dof juste avant que je vois ce post, trop fort.

je comprends pas ton problème, enfin les ini files doivent être dans le même dossier que b2s.server, meme si tu as deux dossiers tables, c'est là ou b2s.server est qui est le plus important

si je ne mets pas les ini dans le 2eme dossier ça ne fonctionne pas.

strange, moi ça fonctionne, montre ton dof xml, celui qui est dans le dossier le plus loin dans la hiérarchie, me souviens plus du nom

Salut Anrgrim,

Depuis la mise à jour du DOF hier soir ... je n'ai plus de forcefeedback ni de gestion des leds sur toutes mes tables ... c'est chiant !!!

Je pense avoir fait tout comme il faut en suivant ton tuto ... et rien à faire !!!

Des pistes ou des idées ???

Merci pour ta réponse !

tu as recréé un GlobalConfig_B2SServer.xml avec GlobalConfigEditor.exe?

arngrim a écrit:

tu as recréé un GlobalConfig_B2SServer.xml avec GlobalConfigEditor.exe?

Oui bien sûr ... et à priori toutes les DLL sont enregistrées !

active log et balance ici pour voir

arngrim a écrit:

active log et balance ici pour voir

Et tu fais çà comment ??  

c'est une option quand tu créés le xml avec l'éditeur, tu dois spécifier le chemin par exemple

ok arngrim ...

je vais essayer et je reviens vers toi

Faudra m'expliqué lol c hard

Bon alors les gars ... à ma grande surprise ... tout fonctionne ce soir alors que je n'ai rien fait (si ce n'est générer à nouveau le global truc pour activer le log !!!)

Donc rien compris mais tout roule ... donc c'est l'essentiel !!!

merci Arngrim pour le super boulot que tu fais la-dessus !!!

A+

t sur t'avais généré un nouveau fichier avant d'activer les logs?

content que ça marche

comme le l'ai dit ici sur le fofo il y a peu il faut refaire un generat config et tout rentre dans l'ordre

Je viens de test la cyclone physique mod 5 avec le DOF2 et franchement ça pète ^^
Du beau boulot.

Chaque table devrait spécifier à l'avenir sa version de DOF dans le script?

je parle de ces lignes là:

Citation :

'*DOF method for rom controller tables by Arngrim********************
'*************************use Tabletype rom or em********************
'*******Use DOF 1**, 1 to activate a ledwiz output*******************
'*******Use DOF 1**, 0 to deactivate a ledwiz output*****************
'*******Use DOF 1**, 2 to pulse a ledwiz output**********************
Sub DOF(dofevent, dofstate)   
    If cController=3 Then
        If dofstate = 2 Then
            Controller.B2SSetData dofevent, 1:Controller.B2SSetData dofevent, 0
        Else
            Controller.B2SSetData dofevent, dofstate
        End If
    End If
End Sub

non c'est seulement pour les tables originales et celles avec rom qui nécessitent de splitter des switches parce qu'elles partagent plusieurs éléments du playfield à la fois, ou bien quand on peut associer le gear motor d'une meilleure façon par le script que par le solenoid correspondant

z'avez vu ça?

hehe ça claque la vidéo

et une autre   

sympa les animations des vidéos,   il touche bien sa bille le père Arngrim, de la banque, il va passer au cinéma, moi je vous, le dis, le septième art, a qu' à bien se tenir !!

c pas moi qui les ai faits, d'autres obt fait ça par surprise pour nous rendre hommage, mais c'est vrai que ceux qui n'ont pas de force feedback ne connaissent pas cette grosse contribution pour vp de ma part

arngrim a écrit:

c pas moi qui les ai faits, d'autres obt fait ça par surprise pour nous rendre hommage, mais c'est vrai que ceux qui n'ont pas de force feedback ne connaissent pas cette grosse contribution pour vp de ma part

Je ne le connais pas encore ce coté de la force feedback, mais je te dit merci d'avance pour tout ton taf. Merci Arngrim et merci a tes compères.