Jump to content

Do Release 2 Beta V 0.8 Build 5285.37539 Feedback


Recommended Posts

  • Replies 149
  • Created
  • Last Reply

Late to the party but downloaded the beta just a minute ago (thx swissliziard) and will check it out later :) 

the readme and wip docu is really interesting i will enjoy playing around with some things.

Link to comment
Share on other sites

Got the beta up and running on my cab and everything seems to be working great!  Just for reference, I'm running a LEDwiz and an 8 port Sainsmart device.  A have a few questions though:

 

- for the Sainsmart device the new config tool named the control file ledcontrol40.ini   Any reason for the 40?  Not a big deal, but I had to change my global and cabinet config files to number the LEDwiz 40 instead of 2 to get it to work.  Just curious more than anything else.

 

- A general question about DOF configs.  If there is a config setup for a table in the tool, does that mean that there is a corresponding DOF enabled table file out there somewhere, or are there some that haven't been officially released yet?  For instance, I put the EM Big Brave on my cab and even though there is a config, the file I'm using doesn't seem to have DOF enabled.

 

Thanks to Swisslizard and arngrim for all of your work on DOF.  You've spoiled me to the point that it feels odd playing a table that doesn't have DOF!

Link to comment
Share on other sites

  • Content Provider

all the defined numbers are choosen in a way that you don't need to configure them in cabinet.xml, dof naturally launched first sainsmart with ini40, second with ini41, same goes for other controllers ans the choosen numbers.

about dof configs, not sure if i understand the question, do you have dof running with tables like champion pub for example?

for em table like big brave, you need the modded table that goes with it, don't know if it has been public somewhere, if you can't find it let me know

Link to comment
Share on other sites

all the defined numbers are choosen in a way that you don't need to configure them in cabinet.xml, dof naturally launched first sainsmart with ini40, second with ini41, same goes for other controllers ans the choosen numbers.

 

Hmmm, I must not have my config set up the preferred way then.  I tried to go without a config.xml, but couldn't get the Sainsmart to be found.  Like I said, it's not a big deal at all now that I tweaked my setup to expect the sainsmart file to be named ledcontrol40.ini 

 

about dof configs, not sure if i understand the question, do you have dof running with tables like champion pub for example? for em table like big brave, you need the modded table that goes with it, don't know if it has been public somewhere, if you can't find it let me know

 

Yes, DOF is running fine for all ROM controlled tables.  Sorry the question wasn't clear.  I was just wondering if there are modded EM tables out there for each of the EMs that have a configuration set up in the tool.  In the case of Big Brave, I couldn't find the modded table so I was wondering if one actually existed but from your response I guess it does and I just didn't know where to look?

Link to comment
Share on other sites

  • Content Provider

Quick explanation:

For the Sainsmart and compatible devices a cabinet config file is mandatory. Compared to the ledwiz or the devices from Ultimarc, the Sainsmart has no identifier which can be used the assign some kind of fixed number to it, but such a number is required for automatic configuration (otherwise DOF doesn't know which file to use for the config). Since the Sainsmart has only a serial of the USB interface chip, this mapping has to happen in the cabinet config file.

Link to comment
Share on other sites

The Advanced DOF tool is a completely separate program.  It contains greater customizations than the current LEDWiz Config tool.   It is also open to anyone from the DOF team who wants to share it, but there is no magic in it.  Arngim has already implemented the dimming in the current tool it seems.

Link to comment
Share on other sites

Hi, today i had some time to look into it a bit deeper an after creating a global + cabinet config i got the most things running.

The dimming works like a charm with the new fading curves :) thx for that 

Now i only got a few errors in the log but i think it´s because i use the "old config tool" ini files

eg something like this. i think when the new dof2 config tool is out and i can use the files these errors will go away.

 

2014.07.08 16:32:59.685 Warning: No DOF version information found in file C:\VisualPinball\Tables\directoutputconfig.ini.

2014.07.08 16:32:59.705 Warning: Cant parse the part Green of the ledcontrol table config setting S20 BlueS21 Green

 

 

 

The Advanced DOF tool is a completely separate program.  It contains greater customizations than the current LEDWiz Config tool.   It is also open to anyone from the DOF team who wants to share it, but there is no magic in it.  Arngim has already implemented the dimming in the current tool it seems.

 

yes seems so :) and for your tool i poorly can´t get it to run on my cab. there´s an error msg saying that the Microsoft.ACE.OLEDB.12.0 provider is not registred to my computer. seems like i´m missing something but i don´t want to install unnecessary thngs on my cab so i will test i again in an VM image

Link to comment
Share on other sites

The Advanced DOF Config tool requires that your PC can read MS Access databases.

 

The documentation  file included gives a link to the required download.

 

For any further question, maybe head over to the Advanced release thread so it doesn't;t muddy the waters here.

Link to comment
Share on other sites

i can't locate the S20 BlueS21 Green, can you tell me which table you try to run to have that?

or better, give me your ini file

as i thought these errors are gone when using the new beta ini :) with the new ini the upper mentioned probs are gone but i got a new one ^^

 

now when i start a table eg 24 it looks like this

 

2014.07.09 13:17:05.260 Loading LedControl file C:\VisualPinball\Tables\directoutputconfig.ini

2014.07.09 13:17:05.325 Warning: Cant parse the part I48W19 of the ledcontrol table config setting W18 60 I48W19 60 I48
2014.07.09 13:17:05.325 EXCEPTION: Could not parse setting W18 60 I48W19 60 I48 in column data S10/S12/S13 60/S21 60/W17 60 I48/W18 60 I48W19 60 I48.
2014.07.09 13:17:05.325 EXCEPTION: Thread: 
2014.07.09 13:17:05.325 EXCEPTION: Message: Cant parse the part I48W19 of the ledcontrol table config setting W18 60 I48W19 60 I48
2014.07.09 13:17:05.340 EXCEPTION: Stacktrace:    bei DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2014.07.09 13:17:05.340 EXCEPTION: Stacktrace:    bei DirectOutput.LedControl.Loader.TableConfigSetting..ctor(String SettingData)
2014.07.09 13:17:05.340 EXCEPTION: Stacktrace:    bei DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2014.07.09 13:17:05.340 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2014.07.09 13:17:05.340 Warning: Previous exceptions occured in the line gprix,S30 Orange f100/W57 Cyan f200,S9 White/S17 Red/W33 Red/W44 Yellow/W45 Yellow/W58 Red f200,S11 Blue/S32 White f100/W36 Yellow 300/W43 Yellow,S10 Red/S18 Red/W17 Green 300/W18 Magenta 300/W19 Blue 300/W42 Red/W61 Red f200,S19 Green/S31 Orange f100/W60 Cyan f200,0,S7/S48,S1/S2/S7/S46,S17,S18,S8/S9/S22/S27 200/S28 200/W44 60 I48/W45 60 I48,S11/W36 60 I48/W43 60 I48,S10/S12/S13 60/S21 60/W17 60 I48/W18 60 I48W19 60 I48,S3/S5/S6,L80 m550 Blink fu500 fd600,0,W40 600 I32/W38 600 I32,0,0,0,0 of the ledcontrol file
2014.07.09 13:17:05.450 1 directoutputconfig.ini or ledcontrol.ini files loaded.

 

seems like in the gprix line is an error somewhere. if i remove the gprix line manually in the .ini file no errors will come in the log

 

2014.07.09 13:28:01.371 Loading LedControl file C:\VisualPinball\Tables\directoutputconfig.ini

2014.07.09 13:28:01.541 1 directoutputconfig.ini or ledcontrol.ini files loaded.
2014.07.09 13:28:01.541 Config for RomName twenty4_150 exists in LedControl data. Updating cabinet and config.
2014.07.09 13:28:01.571 Table config loading finished
2014.07.09 13:28:01.571 Pinball parts loaded
2014.07.09 13:28:01.571 Starting processes
2014.07.09 13:28:01.571 Initializing cabinet
2014.07.09 13:28:01.576 LedWiz Nr. 01 initialized and updater thread initialized.
2014.07.09 13:28:01.576 Updater thread for LedWiz 01 started.
2014.07.09 13:28:01.576 Cabinet initialized
2014.07.09 13:28:01.596 Framework initialized.
2014.07.09 13:28:01.596 Have fun! :)

 

But that´s the only error for now. I will continue testing for now with the RGB Undercab Complex and some new colors :)

thx for all again and if you need my config files let me know i can upload them then :)

 

EDIT:

Found the bug in the 8 Bumper Right Line in the Tool

now the line looks so (which causes an error in the log)

 

S10/S12/S13 60/S21 60/W17 @t@/W18 @t@W19 @t@

and when i put the missing / in it works without error in log

 

S10/S12/S13 60/S21 60/W17 @t@/W18 @t@/W19 @t@

I submitted the change in the new tool so you can take a look at it.

 

 

greetz dup3d

Link to comment
Share on other sites

  • Content Provider

I dont think the random knocker isusue has any relation to zebs hardware. Its either a DOF problem or a issue in the ledwiz driver or in the ledwiz itself.

 

Will try to find some time to dig into the ledwiz part of the DOF code again.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
  • Create New...