Jump to content



Photo
- - - - -

DOFLinx DEBUG window not showing up

DEBUG DOFLinx

  • Please log in to reply
7 replies to this topic

#1 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,805 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 04 September 2017 - 02:37 AM

DEBUG  window not showing up but if I do alt tab then shows up in the alt tab but it will not show up on the monitor this is for my desktop single monitor setup

I only have a Sainsmartt hooked to this computer

 

Attached File  doflinx.jpg   43.95KB   3 downloads

 

03-Sep-17 21:16:33.788 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
03-Sep-17 21:16:33.788 - Starting up - version 5.11
03-Sep-17 21:16:33.804 - 0 Pinscape device(s) found
03-Sep-17 21:16:33.819 - 0 LEDWiz device(s) found
03-Sep-17 21:16:33.960 - 1 FTDI (Sainsmart) device(s) found
03-Sep-17 21:16:34.103 - DOFLinx Device: 1 Initializing as FTDI (Sainsmart) #1 serial # A8008wHV
03-Sep-17 21:16:34.103 - DOFLinx device:1 FTDI (Sainsmart) setup with 8 outputs
03-Sep-17 21:16:34.103 - Reading DOFLinx.INI startup config file details
03-Sep-17 21:16:34.118 - Reading DOF config file
03-Sep-17 21:16:36.873 - Shutting down
03-Sep-17 21:16:36.889 - Program close
 

 

 

####
# The config file for DOFLinx
# A mad idea by DDH69 to have some flipper sounds, RGB display and turn buttons on when playing Pinball FX2 via Steam
# Its grown a lot since that silly start!
# Note - this works with LEDWiz, PacLed64, KL25Z, Pinscape, Ultimate I/O and Sainsmart (FTDI devices)
# 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.
#
# Output devices outputs are entered in the format of
# device (D) and output number (#) in the format D##, so controller device 1 and output 3 is "103" without the quotes, controller board 2 output 23 is "223" without quotes
####

# location of your standard DOF outut configuration file.  Keep this as the first item in the file
DIRECTOUTPUTCONFIG=E:\DirectOutput\Config\directoutputconfig.ini
PATH_FX2=E:\DirectOutput\DOFLinx games

# If you want to list the processes that will wake up DOFLinx, comment it out if you just want Pinball FX2
#PROCESSES=Pinball FX2,Future Pinball,VPinball_9_9_1,VPPhysMod5

# If you are using flag files, comment the line below out or set to 2000 as the default.
# If you need to use the Pinball FX2 grid to select games you will want this at around 30000 - I recommend not using the FX2 grid
PROCESS_TO_ACTIVE_TIME=30

# Which DOF Controller output for the flipper solenoids / contactors
L_FLIPPER_OUTPUT=107
R_FLIPPER_OUTPUT=105
# The keyboard hex code for the key that is used for each flipper from https://msdn.microso...1(v=vs.85).aspx
# Left Shift = A0, Right Shift = A1
L_FLIPPER_KEY=A0
R_FLIPPER_KEY=A1
# Just in case things go wrong (ie no keyup signal is detected, flipper held down for a long time), what is the maximum time a flipper solenoid / contactor can be in in milliseconds
MAX_FLIPPER_ON=5000
# What LEDWiz output(s) are used for RGB devices.  Just enter the Red output number.  Multiples can be entered seperated by a comma
#RGB_OUTPUT=109
# Rainbow - cycle through the colours, Random - pick a random next colour, A colour name as it appears in the DirectOutputConfig.ini file
RGB_STYLE=RANDOM
# What changes the colour?  Time - set time period, Flipper = flipper press after the RGB_TRIGGER minimum time (to stop rapid colour changes)
RGB_TRIGGER=FLIPPER
# Dependent on trigger selection the period between changes or the minimum time for change between flipper flips
RGB_MIN_TIME=1000
# The button(s) to turn on when DOFLinx starts, ie the exit button LED
#BUTTONS_ON=102 104
# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121
KEY_TO_OUTPUT=32 101 35 106 36 105
# Set a key to turn on a specific colour for your RGB.  The line below makes the Left Control (A2) and the Right Control (A3) turn my undercab RGB strip red.
# In Pinball FX2 this means when I nudge it all goes red.
#KEY_TO_COLOUR=A2 109 Red A3 109 Red
# Setting FORCE_ACTIVE=1 will cause DOFFX2 to not listen for processes and just run until you kill the process.  Handy for using it for things other than PinBall FX2
FORCE_ACTIVE=0
# If you want the program to stop when your named process stops then set this to 1.  If you want it to run in the background all the time leave it as 0
QUIT_AFTER_PROCESS=0
# Set to 1 to output the game name to the log regardless of the DEBUG flag setting.  Set to 0 to simply follow the DEBUG flag.
# Quite useful when you trying to get the FX2 window game name for setting game specific colours
OUTPUT_GAME_NAME=1

####
# Sample setup to enable the Future Pinball Link.  Edit the LINK_ items to be your ports and settings.
####
FP_ATTEMPT_LINK=1
# Use the line below if you need to extend the wait time for a FP table to load
#FP_LINK_WAIT_TIME=60000
LINK_LF=107,50,10000,255
LINK_RF=105,50,10000,255
LINK_LS=108,50,500,255
LINK_RS=106,50,500,255
LINK_ML=107,50,500,255
LINK_MC=108,50,500,255
LINK_MR=104,50,500,255
LINK_BL=103,50,500,255
LINK_BC=102,50,500,255
LINK_BR=101,50,500,255
LINK_SH=106,1000,5000,255
LINK_GR=106,750,10000,255
LINK_KN=104,120,500,255
LINK_ST=102
LINK_EB=101
LINK_CN=106,105,103
LINK_EX=104

####
# 0 = OFF (normal operation), 1 = ON - When ON a window will appear and a log file will be created in the EXE directory.
DEBUG=1



#2 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 04 September 2017 - 04:19 AM

Odd, the behaviour you describe is what I's expect with DEBUG turned off.  With DEBUG off you will see DOFLinx in Alt-Tab but it will not appear on screen.

 

Are you definitely pointing to the version of the DOFLinx.ini that you posted?  ie you don't have two INI files (one in the directoutput folder and one in a sub folder) and have edited the wrong one?

 

Ultimately you can test if all is well by sending DOFLinx a message.  Use DOFLInxMsg at a command prompt with the following ...

DOFLinxMsg DEBUG=1

 

If this makes DOFLinx pop up as visible then you've definitely got some sort of INI file issue.  Either way, the log file will record this message if it is in DEBUG mode.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#3 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,805 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 04 September 2017 - 04:37 AM

I have no sub folders and I'm starting it by double-clicking the DOFLinx.exe



#4 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 04 September 2017 - 04:47 AM

OK, send it a message and see what we get.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#5 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,805 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 04 September 2017 - 04:52 AM

command prompt

E:\DirectOutput>DOFLinxMsg DEBUG=1

This does nothing but I'm assuming I'm doing something wrong



#6 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 04 September 2017 - 06:58 AM

Looks correct, but sounds like DOFLinx didn't appear.  To test if the messages are getting through you can try "DOFLinxMsg QUIT" and DOFLinx should close - that you can't miss!

 

Back to your actual problem .... Did you have more monitors before or copy settings from a multi-monitor setup?  I'm just trying to understand if its trying to display on a non existent monitor.  I've never heard of a problem before of it not showing up!

 

In the original DEBUG.log how did you shutdown DOFLinx if you couldn't see it?


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#7 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,805 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 04 September 2017 - 02:29 PM

DOFLinxMsg QUIT  -- This works

 

In the original DEBUG.log how did you shutdown DOFLinx if you couldn't see it? -- I right clicked it on taskbar enclosed it

 

Did you have more monitors before - Yes in may of 2014

 

copy settings from a multi-monitor setup? -- no

 

In the registry it feels it should put these numbers in which makes absolutely no sense, even if I change them it goes back to this

Attached File  R-3.jpg   55.05KB   19 downloads

With these numbers it should have been showing up on your monitor

 

Update I change them again and now it appears to be working

Attached File  R-4.jpg   48.35KB   21 downloads

Thanks for your help

Can't wait to try out my addressable leds with DOFLinx....
Right now I only have them on each side of the table in my cab which has 3 screens


Edited by Outhere, 04 September 2017 - 06:10 PM.


#8 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 04 September 2017 - 10:51 PM

Nice work.  You figured out where I was heading with the monitors then :)

 

FYI - Its quite safe to delete the DOFLinx registry branch if you ever need to.  It will recreate next time.  All that is stored is the screen position (which yours went wacky for some reason) and the current status of the settings menu (if you use that)


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here





Also tagged with one or more of these keywords: DEBUG, DOFLinx