54 replies to this topic

[billmcse]

Couple dumb, basic questions...assuming no bells and whistles aka "no toys"

 

or verifications....so the batch file can go as a shorcut on my desktop and include disabledof=yes along with the exe for pinball fx3

 

Then configure the ini file....where does the ini file go? And other than those steps, what am I missing?
 

[DDH69]

Yes you have the command line correct.

The ini file can be placed anywhere if you use another command line parameter that I can't quite remember th he synta of while away for Easter. You will find this quite early in the guide whete all command line parameters are explained. Alternatively the default for the ini file is the Windows startup folder where DOFLinx starts.

[billmcse]

Got it. Is that sufficient to have those things in Windows startup and then run FX3 manually?

[DDH69]

Got it. Is that sufficient to have those things in Windows startup and then run FX3 manually?

This should allow you to have DOFLinx running in the background and activate when FX3 is started.

[billmcse]

Ok, will give it a try. What does FP have to do with any of this? Just curious, trying to understand how all the pieces tie together

Does ANYONE who is using just doflinx and FX3, no-toys, mind posting up your batch file at startup? Still not working and a working batch file with correct syntax, parameters,etc would help me a ton.

[billmcse]

Not working for me 

 

Here's what I have in my startup - C:\DirectOutput\DOFlinx.exe DISABLEDOF=YES DEBUG = 1 "PATH_INI=C:\DirectOutput\DOFLINX_ini\"

 

Here's my doflinx.ini file 

 

####

# The config file for DOFLinx to achieve B2S backglasses only with Pinball FX3

# 

# IMPORTANT - when used just for backglasses with FX3 and no output devices with toys, you must add this command line options for DOFLinx, DISABLEDOF=YES

#

# Edit this file as you see fit, lines that start with a hash (#) or are blank are not processed.  This blurb and comments can be cut out if you want.

####

 

# Point to your directoutputconfig.ini file.  Your file may have a number, ie directoutputconfig20.ini

# You can point to any of your directoutputconfig.ini files, but only one

# Keep this as the first pararameter to process in your INI file.  The order past ths point is not relevant

 

DIRECTOUTPUTCONFIG=c:\DirectOutput\config\directoutputconfig.ini

 

# The location of the .FX3 game specific files included with the DOFLinx release package

# Ensure your path has a \ on the end of it

 

PATH_FX3=C:\DirectOutput\DOFLinx_FX3\

 

# The path to where you keep all of the .directb2s files that you've downloaded for use with FX3

# Ensure your path has a \ on the end of it

 

PATH_FX3_B2S=C:\DirectOutput\DOFLinx_FX3\B2S\

 

# This is the folder where B2SServer.exe can be found on your system

 

PATH_B2S_SERVER=C:\Visual Pinball\Tables\

 

# The list of processes that can activate DOFLinx, in this case, just Pinball FX3

 

PROCESSES=Pinball FX3

 

# An over-ride to the default setting given this is just being used with Pinball FX3, not FX2, FP or other systems that may require the default delay

 

PROCESS_TO_ACTIVE_TIME=1

[DDH69]

Looks li kje you have spaces in between DEBUG, the = sign and 1. On a command line for Windows a space separayes parameters so this will fail.

Ypu might find it easier to remove DEBUG=1 f rrom the command line and add it as a line in your ini file.

[billmcse]

Ok I took out the spaces. If a log is created, what is it called?

[DDH69]

Ok I took out the spaces. If a log is created, what is it called?

DOFLinx.log created in the same folder as DOFLinx.exe

[billmcse]

No DOFLINX.log file anywhere on the machine. Possible reasons it's not being created? Removed the spaces from the line above

Edited by billmcse, 21 April 2019 - 01:24 PM.

[DDH69]

Did you move it I to your DOFLinx.ini file as suggested? If so, then you either have a syntax error on that line or are not pointing to that ini file.

[billmcse]

That's kind of what I'm looking for....I don't see a problem with the startup as C:\DirectOutput\DOFlinx.exe DISABLEDOF=YES DEBUG=1 PATH_INI=C:\DirectOutput\DOFLINX_ini\

 

The doflinx.ini file is posted above AND I added the debug=1 line in there too.

[DDH69]

Have you managed to find the LOG file yet?  A LOG file is created regardless of the DEBUG= setting, it just doesn't contain much.  You really need to find this file (should be in the same folder as DOFLinx.exe).  With the DEBUG=1 setting it will contain details of anything that we need to pay attention to.

[billmcse]

Well that's what's confusing here. Everyone tells me that a log file should be generated. I chose This PC, did a search for doflinx.log and then dof*.log with no results. 

 

My command line reads like this - 

 

C:\DirectOutput\DOFlinx.exe DISABLEDOF=YES PATH_INI=C:\DirectOutput\DOFLINX_ini\ DEBUG=1

 

 

Looked in the same folder where doflinx and the doflinx.in is, not there either

 

Does anything above look incorrect?

[DDH69]

If you are not generating the file DOFLinx.LOG then you are not starting the application DOFLInx.EXE.  One of the first, basic and essential actions the program does is create / open this file.

 

My suggestions;

1) I repeat my recommendation to remove the DEBUG=1 from the command line and only have it in the DOFLinx.INI file

2) Open a command prompt

3) Change directory to C:\Directoutput (cd \ DirectOutput)

4) Check if you have a DOFLInx.LOG file (dir *.LOG)

5) If you do - yay you've found it, but delete it anyway so its clear, then abort this list and resume as per previous now that you know where the LOG file is  (del DOFLinx.LOG)

6) Run DOFLinx.EXE directly from the command line (DOFLinx)

7) Check if you have a log file (dir *.log)  If you do, then you are not running the command line you thought to start the program.  If you do not have one, then there must have been an on screen error about you not having write permission to this area of your own C: drive - fix that

[randr]

I must say this has came a long way since I first tried this in what 2013? 2015? I’m not a huge fan of fx2/3 but wow does having feedback make a huge difference.
Thanks so much for keeping this going it’s truly amazing work.

[billmcse]

Ok DDH69 - I followed steps 1-4 and there is no log file. 

 

I then followed the remaining steps and ran doflinx.exe from the command line and AGAIN no log file exists. Not sure why??
 

 No errors appear regarding permissions and I am an admin on the box

 

If no other thoughts maybe I will remove and reinstall. What version should I use?
 

Edited by billmcse, 24 April 2019 - 08:03 PM.

[billmcse]

Ok after installing and replacing the existing files for direcoutput and using 6.70 of doflinx I was able to generate a doflinx.log - it is below :

 

C:\DirectOutput>type doflinx.log

24-Apr-19 16:19:51.893 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

24-Apr-19 16:19:51.908 - Starting up - version 6.70

24-Apr-19 16:19:51.914 - For support come and visit the community here http://www.vpforums....p?showforum=104

24-Apr-19 16:19:51.923 - Pre-Reading DOFLinx.INI startup config file details

24-Apr-19 16:19:51.980 - 0 Pinscape device(s) found

24-Apr-19 16:19:51.994 - 0 LEDWiz device(s) found

24-Apr-19 16:19:52.001 - 0 FTDI (Sainsmart) device(s) found

24-Apr-19 16:19:52.011 - 0 PacLED64 device(s) found

24-Apr-19 16:19:52.026 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!

24-Apr-19 16:19:52.033 - Reading DOFLinx.INI startup config file details

 

C:\DirectOutput>

[DDH69]

Great news and congratulations on the progress.

 

Now its time to run DOFLinx from your shortcut so that it points to your INI file and gets the DISABLEDOF argument.  Given that you have DEBUG=1 in your INI file, DOFLinx will continue to log everything not just the startup as per your log above.

 

Once you have things starting up OK from your shortcut, then run FX3, start a game, launch a ball, do a couple of flipper presses and quit FX3.  We should then have a good log file to look at.  Post the log file and a description of what has worked and not worked.

[billmcse]

I'm getting an unhandled exception error now from .net framework