Jump to content



Photo
- - - - -

HELP. DOF NOT WORKING ON MOST ORIGINALS

ORIGINALS DOF NOT WORKING

  • Please log in to reply
63 replies to this topic

#1 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 03 April 2025 - 12:05 AM

OK, here we go. I have a problem with DOF and I cannot figure out how to fix it.

The problem is I cannot get DOF to work on about a third of the Original Tables I have installed.

I am currently running:

Visual Pinball: 10.8 rev 2015 (6163503) 64 bit

Vpinmame: 3.5 ver 1.42

B2S: v2.1.3.327

DOF: v3.0

FlexDMD: v1.9.1.0

 

I will list the tables and maybe someone can narrow down the problem.

 

Original Tables that work with DOF.

Blood Machines,  Diablo,  GOTGalaxy,  Halloween 1978-1981,  Happy Potter,  IT,  Jaws,  Deadpool,  Minions,  Predator,  Rambo,  Red Sonja, SOAnarchy,  Southpark, Speed Racer,  The Goonies,  Terminator Salvation,  The Magnificent Seven,  TNA,  Tron Legacy,  Wizard Of OZ.

 

Original Tables not working with DOF:

Hip Hop,  John Wick, Jumanji,  Need For Speed,  Pirates Life,  Resident Evil,  Streets Of Rage,  Swamp Thing,  Terminator 1,  The Exorcist.

One other table also has no DOF. Terminator 2 G5K v1.25, however version 1.1d is working with DOF.

Any help on this one would be greatly appreciated



#2 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 09 April 2025 - 08:37 PM

Hmmm. Nothing. No suggestions. Damn.



#3 fhjui

fhjui

    Enthusiast

  • Members
  • PipPipPip
  • 374 posts
  • Location:Germany

  • Flag: Germany

  • Favorite Pinball: especially EM tables

Posted 09 April 2025 - 09:42 PM

I had read your thread but don't have the one solution to fix that. But...

whats this DOF 3.0 version? That's not the correct one. You have to install the recent R3++ version 3.2 from mjr. The recent version has a combined installation of 32bit and 64bit component. No more frickeling to configure the 64bit part.

http://mjrnet.org/pi...ll-updates.html


Edited by fhjui, 09 April 2025 - 09:42 PM.

My documentation for installing vpin software with PinUpsystem (Baller installer): https://mega.nz/fold...wAXZlOEMQGbdutQ

Files and PDF-docu in the subdir "Installation vPin-Software with Baller-Installer"


#4 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 16 April 2025 - 03:35 AM

OK. Thanks. I'll check out later after work



#5 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 17 April 2025 - 03:39 AM

So i downloaded the 32 and 64 20250329 files,

Neither of them will install. Tried all types of directory paths.

I obviously have something wrong with my setup. this is the error I'm receiving

FEATURE TRYING TO USE ON NETWORK RESOURCE IS UNAVAILABLE.

ENTER AN ALTERNATE PATHT TO FOLDER CONTAINING THE INSTALLATION PACKAGE DOF INSTALL FILE - DIRECT OUTPUT RELEASE 20240901

 

My Directoutput directory is straight under C:



#6 fhjui

fhjui

    Enthusiast

  • Members
  • PipPipPip
  • 374 posts
  • Location:Germany

  • Flag: Germany

  • Favorite Pinball: especially EM tables

Posted 17 April 2025 - 08:18 AM

Hmm, a bit of a challenge.

I suspect you previously installed DOF from a network drive.

My tip: never install software from a network drive; it's better to copy the installation files to a separate directory on C:\ (e.g., C:\Software), so nothing can get lost.

The Windows installer saves this source directory, and if it's no longer there, or if the file has been moved or deleted, errors like this one can occur.

Many MSI packages—if the programmer has provided it—offer the option to "repair" the software, uninstall it, or add or remove features. The MSI file is still required for this.

But to isolate the error, I would suggest to run the DOF installation of one of the packages with logging parameters.

  • Open the command prompt with "Win+R", type cmd, press enter
  • assuming the psi package is in your download dir. ,then run the MSI package manually: msiexec /i "DirectOutput-mjr-x64-release-20241105.msi" /L*V "DOF64.log"
    here as an example for the 64bit version.
  • Then post the log file here, and we'll take a look.

My documentation for installing vpin software with PinUpsystem (Baller installer): https://mega.nz/fold...wAXZlOEMQGbdutQ

Files and PDF-docu in the subdir "Installation vPin-Software with Baller-Installer"


#7 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 17 April 2025 - 08:28 PM

Ok. As soon as I read your answer it struck me. I partitioned my drive and stored backup files on it.

I found the file it was looking for, pointed to that file when it asked, and it seems to have installed with no errors.

I will now try the no dof tables and see if they are now working.

Will let you know.

OH. AND THANKS so much.

I'd shout you a beer if you were in Australia.



#8 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 17 April 2025 - 09:01 PM

I ran the above cmd, this is the log file it produced:

 

 

Windows ® Installer. V 5.0.22621.3880 
 
msiexec /Option <Required Parameter> [Optional Parameter]
 
Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]
 
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
 
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.


#9 fhjui

fhjui

    Enthusiast

  • Members
  • PipPipPip
  • 374 posts
  • Location:Germany

  • Flag: Germany

  • Favorite Pinball: especially EM tables

Posted 17 April 2025 - 10:06 PM

there must be something wrong with the parameters you have entered.

check the parameter, there is no space between  /L*V, the "i" paramter is necessary because windows installer must know what to do with the package.

Would suggest to copy the msi file into a new directory, create a batch file with this command, add pause at the end, run cmd and run this batch file.

example for 64bit version:

msiexec /i "DirectOutput-mjr-x64-release-20250329.msi" /L*V "DOF64.log"
pause

 

I have tested exactly the command from above, works flawless.

But please use the recent DOF version from mjr, DirectOutput-mjr-x64-release-20250329.msi. The version I mentioned above is beta.


My documentation for installing vpin software with PinUpsystem (Baller installer): https://mega.nz/fold...wAXZlOEMQGbdutQ

Files and PDF-docu in the subdir "Installation vPin-Software with Baller-Installer"


#10 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 17 April 2025 - 11:41 PM

I copied the 20250329 msi file to the root directory c: then ran the above. It then came up with Change(greyed out), Repair or Remove. I chose Repair and that seemed to work OK.

I then tried a couple the tables again that currently have no DOF working, john wick and pirates life.

However it is still the same, DOF isn't working.



#11 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 19 April 2025 - 10:43 PM

Just wondering if there is anything else I could try.

Thanks



#12 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,807 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 19 April 2025 - 11:48 PM

Post a Log from one that works and one not


Edited by Outhere, 19 April 2025 - 11:55 PM.


#13 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 20 April 2025 - 03:48 AM

Might seem a bit stupid.

But where are the table log files located?



#14 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,807 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 20 April 2025 - 05:08 AM

Might seem a bit stupid.

But where are the table log files located?

DirectOutput.log in the DirectOutput folder



#15 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 20 April 2025 - 11:14 PM

.


Edited by brarnienim00, 21 April 2025 - 05:41 AM.


#16 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,807 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 21 April 2025 - 03:36 AM

Delete the one Above and post one log from a working game and one from a non working game.
-

When posting large items like a LOG or ini files And Code

After you paste - highlight it, Then click on this symbol above <> then post



#17 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 21 April 2025 - 06:23 AM

2025.04.21 16:00:18.428 Failed: 123
2025.04.21 16:00:18.428 Warning: Cant parse the trigger part 123 of the ledcontrol table config setting 123.
2025.04.21 16:00:18.428 EXCEPTION: Could not parse setting 123 in column data E102/123.
2025.04.21 16:00:18.428 EXCEPTION: Thread: 
2025.04.21 16:00:18.428 EXCEPTION: Message: Exception --> Cant parse the part 123 of the ledcontrol table config setting 123.
2025.04.21 16:00:18.428 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2025.04.21 16:00:18.428 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2025.04.21 16:00:18.428 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2025.04.21 16:00:18.428 Warning: Previous exceptions occurred in the line willywonka,0,0,0,0,0,0,E101,0,0,0,0,0,E102/123 of the ledcontrol file
2025.04.21 16:00:18.548 Loading LedControl file C:\DIRECTOUTPUT\directoutputconfig51.ini
2025.04.21 16:00:18.548 Min DOF Version is 0.8 for file directoutputconfig51.ini
2025.04.21 16:00:18.548 Resolving Tables Variables (C:\DIRECTOUTPUT\directoutputconfig51.ini)
2025.04.21 16:00:18.548 Resolving Global Variables (C:\DIRECTOUTPUT\directoutputconfig51.ini)
2025.04.21 16:00:18.673 2 directoutputconfig.ini or ledcontrol.ini files loaded.
2025.04.21 16:00:18.674 Config for RomName mm_109c exists in LedControl data. Updating cabinet and config.
2025.04.21 16:00:18.676 Table config loading finished: romname=mm_109c, tablename=MedievalMadness_Upgrade(Real_Final)
2025.04.21 16:00:18.676 Pinball parts loaded
2025.04.21 16:00:18.676 Starting processes
2025.04.21 16:00:18.676 Initializing cabinet
2025.04.21 16:00:18.676 Debug: Initializing output controllers
2025.04.21 16:00:18.677 Pinscape Pinscape Controller 01 initialized and updater thread started.
2025.04.21 16:00:18.677 Debug: Initializing LedWiz Nr. 08
2025.04.21 16:00:18.677 Pinscape Pinscape Controller 01 updater thread  started.
2025.04.21 16:00:18.677 Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2025.04.21 16:00:18.677 LedWiz Nr. 08 initialized and updater thread initialized.
2025.04.21 16:00:18.677 Debug: Output controllers initialized
2025.04.21 16:00:18.677 Updater thread for LedWiz 08 started.
2025.04.21 16:00:18.677 Cabinet initialized
2025.04.21 16:00:18.679 Loading shape definition file: C:\DIRECTOUTPUT\DirectOutputShapes.xml
2025.04.21 16:00:18.686 Framework initialized.
2025.04.21 16:00:18.686 Have fun! :)
2025.04.21 16:01:47.114 Finishing framework
2025.04.21 16:01:47.114 Finishing cabinet
2025.04.21 16:01:47.114 Debug: Finishing output controllers
2025.04.21 16:01:47.116 Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2025.04.21 16:01:47.117 Pinscape Pinscape Controller 01 finished and updater thread stopped.
2025.04.21 16:01:47.117 Debug: Finishing LedWiz Nr. 08
2025.04.21 16:01:47.117 Updater thread for LedWiz 08 terminated.
2025.04.21 16:01:47.119 LedWiz Nr. 08 finished and updater thread stopped.
2025.04.21 16:01:47.119 Debug: Output controllers finished
2025.04.21 16:01:47.119 Cabinet finished
2025.04.21 16:01:47.119 DirectOutput framework finished.
2025.04.21 16:01:47.119 Bye and thanks for using!
2025.04.21 16:00:18.428	Failed: 123
2025.04.21 16:00:18.428	Warning: Cant parse the trigger part 123 of the ledcontrol table config setting 123.
2025.04.21 16:00:18.428	EXCEPTION: Could not parse setting 123 in column data E102/123.
2025.04.21 16:00:18.428	EXCEPTION: Thread: 
2025.04.21 16:00:18.428	EXCEPTION: Message: Exception --> Cant parse the part 123 of the ledcontrol table config setting 123.
2025.04.21 16:00:18.428	EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2025.04.21 16:00:18.428	EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2025.04.21 16:00:18.428	EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2025.04.21 16:00:18.428	Warning: Previous exceptions occurred in the line willywonka,0,0,0,0,0,0,E101,0,0,0,0,0,E102/123 of the ledcontrol file
2025.04.21 16:00:18.548	Loading LedControl file C:\DIRECTOUTPUT\directoutputconfig51.ini
2025.04.21 16:00:18.548	Min DOF Version is 0.8 for file directoutputconfig51.ini
2025.04.21 16:00:18.548	Resolving Tables Variables (C:\DIRECTOUTPUT\directoutputconfig51.ini)
2025.04.21 16:00:18.548	Resolving Global Variables (C:\DIRECTOUTPUT\directoutputconfig51.ini)
2025.04.21 16:00:18.673	2 directoutputconfig.ini or ledcontrol.ini files loaded.
2025.04.21 16:00:18.674	Config for RomName mm_109c exists in LedControl data. Updating cabinet and config.
2025.04.21 16:00:18.676	Table config loading finished: romname=mm_109c, tablename=MedievalMadness_Upgrade(Real_Final)
2025.04.21 16:00:18.676	Pinball parts loaded
2025.04.21 16:00:18.676	Starting processes
2025.04.21 16:00:18.676	Initializing cabinet
2025.04.21 16:00:18.676	Debug: Initializing output controllers
2025.04.21 16:00:18.677	Pinscape Pinscape Controller 01 initialized and updater thread started.
2025.04.21 16:00:18.677	Debug: Initializing LedWiz Nr. 08
2025.04.21 16:00:18.677	Pinscape Pinscape Controller 01 updater thread  started.
2025.04.21 16:00:18.677	Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2025.04.21 16:00:18.677	LedWiz Nr. 08 initialized and updater thread initialized.
2025.04.21 16:00:18.677	Debug: Output controllers initialized
2025.04.21 16:00:18.677	Updater thread for LedWiz 08 started.
2025.04.21 16:00:18.677	Cabinet initialized
2025.04.21 16:00:18.679	Loading shape definition file: C:\DIRECTOUTPUT\DirectOutputShapes.xml
2025.04.21 16:00:18.686	Framework initialized.
2025.04.21 16:00:18.686	Have fun! :)
2025.04.21 16:01:47.114	Finishing framework
2025.04.21 16:01:47.114	Finishing cabinet
2025.04.21 16:01:47.114	Debug: Finishing output controllers
2025.04.21 16:01:47.116	Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2025.04.21 16:01:47.117	Pinscape Pinscape Controller 01 finished and updater thread stopped.
2025.04.21 16:01:47.117	Debug: Finishing LedWiz Nr. 08
2025.04.21 16:01:47.117	Updater thread for LedWiz 08 terminated.
2025.04.21 16:01:47.119	LedWiz Nr. 08 finished and updater thread stopped.
2025.04.21 16:01:47.119	Debug: Output controllers finished
2025.04.21 16:01:47.119	Cabinet finished
2025.04.21 16:01:47.119	DirectOutput framework finished.
2025.04.21 16:01:47.119	Bye and thanks for using!

MEDIEVAL MADNESS - WORKING



#18 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 21 April 2025 - 06:59 AM

2025.04.21 16:51:48.240 Failed: 123
2025.04.21 16:51:48.240 Warning: Cant parse the trigger part 123 of the ledcontrol table config setting 123.
2025.04.21 16:51:48.241 EXCEPTION: Could not parse setting 123 in column data E102/123.
2025.04.21 16:51:48.241 EXCEPTION: Thread: 
2025.04.21 16:51:48.241 EXCEPTION: Message: Exception --> Cant parse the part 123 of the ledcontrol table config setting 123.
2025.04.21 16:51:48.241 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2025.04.21 16:51:48.241 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2025.04.21 16:51:48.241 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2025.04.21 16:51:48.241 Warning: Previous exceptions occurred in the line willywonka,0,0,0,0,0,0,E101,0,0,0,0,0,E102/123 of the ledcontrol file
2025.04.21 16:51:48.376 Loading LedControl file C:\DIRECTOUTPUT\directoutputconfig51.ini
2025.04.21 16:51:48.384 Min DOF Version is 0.8 for file directoutputconfig51.ini
2025.04.21 16:51:48.384 Resolving Tables Variables (C:\DIRECTOUTPUT\directoutputconfig51.ini)
2025.04.21 16:51:48.384 Resolving Global Variables (C:\DIRECTOUTPUT\directoutputconfig51.ini)
2025.04.21 16:51:48.515 2 directoutputconfig.ini or ledcontrol.ini files loaded.
2025.04.21 16:51:48.518 Config for RomName t2_l8 exists in LedControl data. Updating cabinet and config.
2025.04.21 16:51:48.547 Table config loading finished: romname=t2_l8, tablename=Terminator 2 (Williams 1991) g5k 1.25
2025.04.21 16:51:48.548 Pinball parts loaded
2025.04.21 16:51:48.548 Starting processes
2025.04.21 16:51:48.549 Initializing cabinet
2025.04.21 16:51:48.549 Debug: Initializing output controllers
2025.04.21 16:51:48.550 Pinscape Pinscape Controller 01 initialized and updater thread started.
2025.04.21 16:51:48.550 Debug: Initializing LedWiz Nr. 08
2025.04.21 16:51:48.551 Pinscape Pinscape Controller 01 updater thread  started.
2025.04.21 16:51:48.551 Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2025.04.21 16:51:48.551 LedWiz Nr. 08 initialized and updater thread initialized.
2025.04.21 16:51:48.551 Debug: Output controllers initialized
2025.04.21 16:51:48.552 Updater thread for LedWiz 08 started.
2025.04.21 16:51:48.554 Cabinet initialized
2025.04.21 16:51:48.559 Loading shape definition file: C:\DIRECTOUTPUT\DirectOutputShapes.xml
2025.04.21 16:51:48.621 Framework initialized.
2025.04.21 16:51:48.621 Have fun! :)
2025.04.21 16:53:51.533 Finishing framework
2025.04.21 16:53:51.535 Finishing cabinet
2025.04.21 16:53:51.536 Debug: Finishing output controllers
2025.04.21 16:53:51.538 Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2025.04.21 16:53:51.538 Pinscape Pinscape Controller 01 finished and updater thread stopped.
2025.04.21 16:53:51.538 Debug: Finishing LedWiz Nr. 08
2025.04.21 16:53:51.538 Updater thread for LedWiz 08 terminated.
2025.04.21 16:53:51.542 LedWiz Nr. 08 finished and updater thread stopped.
2025.04.21 16:53:51.542 Debug: Output controllers finished
2025.04.21 16:53:51.542 Cabinet finished
2025.04.21 16:53:51.542 DirectOutput framework finished.
2025.04.21 16:53:51.542 Bye and thanks for using!
2025.04.21 16:51:48.240	Failed: 123
2025.04.21 16:51:48.240	Warning: Cant parse the trigger part 123 of the ledcontrol table config setting 123.
2025.04.21 16:51:48.241	EXCEPTION: Could not parse setting 123 in column data E102/123.
2025.04.21 16:51:48.241	EXCEPTION: Thread: 
2025.04.21 16:51:48.241	EXCEPTION: Message: Exception --> Cant parse the part 123 of the ledcontrol table config setting 123.
2025.04.21 16:51:48.241	EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2025.04.21 16:51:48.241	EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2025.04.21 16:51:48.241	EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2025.04.21 16:51:48.241	Warning: Previous exceptions occurred in the line willywonka,0,0,0,0,0,0,E101,0,0,0,0,0,E102/123 of the ledcontrol file
2025.04.21 16:51:48.376	Loading LedControl file C:\DIRECTOUTPUT\directoutputconfig51.ini
2025.04.21 16:51:48.384	Min DOF Version is 0.8 for file directoutputconfig51.ini
2025.04.21 16:51:48.384	Resolving Tables Variables (C:\DIRECTOUTPUT\directoutputconfig51.ini)
2025.04.21 16:51:48.384	Resolving Global Variables (C:\DIRECTOUTPUT\directoutputconfig51.ini)
2025.04.21 16:51:48.515	2 directoutputconfig.ini or ledcontrol.ini files loaded.
2025.04.21 16:51:48.518	Config for RomName t2_l8 exists in LedControl data. Updating cabinet and config.
2025.04.21 16:51:48.547	Table config loading finished: romname=t2_l8, tablename=Terminator 2 (Williams 1991) g5k 1.25
2025.04.21 16:51:48.548	Pinball parts loaded
2025.04.21 16:51:48.548	Starting processes
2025.04.21 16:51:48.549	Initializing cabinet
2025.04.21 16:51:48.549	Debug: Initializing output controllers
2025.04.21 16:51:48.550	Pinscape Pinscape Controller 01 initialized and updater thread started.
2025.04.21 16:51:48.550	Debug: Initializing LedWiz Nr. 08
2025.04.21 16:51:48.551	Pinscape Pinscape Controller 01 updater thread  started.
2025.04.21 16:51:48.551	Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2025.04.21 16:51:48.551	LedWiz Nr. 08 initialized and updater thread initialized.
2025.04.21 16:51:48.551	Debug: Output controllers initialized
2025.04.21 16:51:48.552	Updater thread for LedWiz 08 started.
2025.04.21 16:51:48.554	Cabinet initialized
2025.04.21 16:51:48.559	Loading shape definition file: C:\DIRECTOUTPUT\DirectOutputShapes.xml
2025.04.21 16:51:48.621	Framework initialized.
2025.04.21 16:51:48.621	Have fun! :)
2025.04.21 16:53:51.533	Finishing framework
2025.04.21 16:53:51.535	Finishing cabinet
2025.04.21 16:53:51.536	Debug: Finishing output controllers
2025.04.21 16:53:51.538	Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2025.04.21 16:53:51.538	Pinscape Pinscape Controller 01 finished and updater thread stopped.
2025.04.21 16:53:51.538	Debug: Finishing LedWiz Nr. 08
2025.04.21 16:53:51.538	Updater thread for LedWiz 08 terminated.
2025.04.21 16:53:51.542	LedWiz Nr. 08 finished and updater thread stopped.
2025.04.21 16:53:51.542	Debug: Output controllers finished
2025.04.21 16:53:51.542	Cabinet finished
2025.04.21 16:53:51.542	DirectOutput framework finished.
2025.04.21 16:53:51.542	Bye and thanks for using!

TERMINATOR 2 - ONLY SLINGSHOT BUMPERS WORKING. (Flippers not, Rumbler not)


Edited by brarnienim00, 21 April 2025 - 07:00 AM.


#19 brarnienim00

brarnienim00

    Hobbyist

  • Members
  • PipPip
  • 45 posts

  • Flag: Australia

  • Favorite Pinball: attack from mars

Posted 21 April 2025 - 07:26 AM

I tried 3 original tables with DOF not working. The directoutput.log doesn't update when run the tables. Tried John Wick, The Exorcist and Pirates Life.

Maybe I'm doing something wrong!



#20 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,807 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 21 April 2025 - 03:28 PM

Post your GlobalConfig_B2SServer.xml File
And you said the Log file was in your Tables Folder?







Also tagged with one or more of these keywords: ORIGINALS, DOF NOT WORKING