490 replies to this topic

[djrino]

Try here:

 

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

 

See the DOF section - use "DOF Windows Setup Installer (MSI)".  Ignore the LEDWIZ.DLL section.

 

Hi good now i have the directory DirectOutput in c: i need to do some other step?

many many tnx for your help

[mjr]

only small problem i have is the launch button on my cab will not launch the ball in fx3 for some reason, its set as enter key and works as an enter key no problem when selecting etc in fx3 but just will not launch the ball, if i press enter on the keyboard it works fine, if i change the launch key in fx3 to my start button for example it works fine, its got me puzzled to say the least.

 

Huh, strange indeed.  Could it be that FX3 is picky about *which* Enter key is being used?  There's the normal Enter key in the main alphabetic key area, and there's the separate Enter key on the numeric keypad.  Those are actually distinct keys as far as Windows is concerned, even though both are called "Enter" and both usually have the same function in applications.  But some programs - especially games - treat the two as separate keys and let you assign different functions.  Any chance that FX3 is configured to use "Keypad Enter" and your button is mapped to "Regular Enter", or vice versa?

 

Try here:

 

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

 

See the DOF section - use "DOF Windows Setup Installer (MSI)".  Ignore the LEDWIZ.DLL section.

 

Hi good now i have the directory DirectOutput in c: i need to do some other step?

 

You should be set with DOF as far as the software goes, so you can go ahead with the rest of the DOFLinx setup you were working on.

 

DOF needs to be configured for your cab, though - you need to tell it what kind of output devices you have attached.  Here's some information on how to set that up:

 

http://mjrnet.org/pi...ide.php?sid=DOF

 

(You are using a pin cab with output devices, right?  DOF and DOFLinx are all about controlling attached devices like LEDs and solenoids.  If you don't have any of that, you actually won't have any use for DOF or DOFLinx.  If that game you downloaded is for "DOF cabs only" and absolutely won't run without DOF, you probably don't want that version of the game at all - you probably want to find the version that runs on ordinary desktop machines.)

[widget2k13]

mjr i have it mapped to the normal enter key, in fx3 i have tried in controls changing the plunger key and actually press the launch button to define that key and it puts it in as enter, its really strange 

[widget2k13]

enter button problem solved:) seems it doesn't like being the shift key lol.

 

having problem with pinsound, works perfect with the assigned buttons on cab in windows , f19 f20 shifted, but as soon as a table is launched it doesn't work, either vpx or fx3 ? 

have i done something wrong ?

[mjr]

enter button problem solved:) seems it doesn't like being the shift key lol.

 

Oh, were you using Enter as the Pinscape local shift button? 

 

That might explain it if FX was using Enter the way VP does - that is, hold down the Enter key to pull back the plunger, release the key to release the plunger.   When the button is in local shift mode, it only sends a timed pulse to the PC when you release the button.  So if FX3 was depending on you holding down the button for a couple of seconds to get the plunger pulled back far enough to release, that would never happen.

 

Note that if you really want to keep Enter as the shift button,  you can do that!  You just have to change the shift mode from "OR" to "AND" in the settings.

 

shift OR key -> default mode, where it sends the short timed pulse when you release the button

shift AND key -> sends key down/up at the same time you press the button

 

This is all explained more in the notes for that section in the setup tool.

 

 

having problem with pinsound, works perfect with the assigned buttons on cab in windows , f19 f20 shifted, but as soon as a table is launched it doesn't work, either vpx or fx3 ? 

have i done something wrong ?

 

Are you talking about PinVol?  

 

Any chance you're launching those games in Administrator mode?  PinVol can't monitor keys in the background when an Admin mode program is running, since Windows forbids that for security reasons (so that key loggers can't intercept system passwords and such).

 

If that's it, the best solution is to stop running anything in Admin mode - games should ideally never be run in Admin mode.  

 

The bad solution, which I'd recommend against, is to start running PinVol in Admin mode as well.  But you really should try to stop running the other stuff in Admin mode instead.  It'll make your life a lot easier in the long run.

[widget2k13]

Yes I think fx3 had to be run in admin mode to address a dmd issue and I always thought vpx and pinup had to run in admin mode , but if thats not the case then its easily sorted , and thank you for the help

[mjr]

Yes I think fx3 had to be run in admin mode to address a dmd issue and I always thought vpx and pinup had to run in admin mode , but if thats not the case then its easily sorted , and thank you for the help

 

If you're using dmd-ext with fx3, it *used to* require Admin mode, but that was a bug fixed in 1.7.2.  (It's also fixed in my 1.7.1 patch branch, which some people are still using because of some kind of problem with colorizing that got added in 1.7.2.)  So you should be able to solve that by updating to one of the newer dmd-ext versions.

 

VPX by itself certainly doesn't need Admin mode.  Not sure about pinup, but my guess is that there was some misunderstanding at some point where someone *thought* you had to run it in Admin mode but you really didn't.

 

Just as a rule, any time anyone says "you have to run X in Admin mode", take it with a big grain of salt - there's a lot of misinformation around here about that.  "Run it in Admin mode" somehow got onto everyone's radar as a random troubleshooting step for every type of problem.  It's in the same category as when tech support tells you to unplug your router for 60 seconds and try again - never works, but they always make you try it because it's on their script.  But Admin Mode is insidious - once you've got one thing in Admin mode, pretty soon everything else has to be in Admin mode too, because of all of the Windows security restrictions related to Admin mode processes.  So it's better not to get started down that road if you can possibly avoid it.

[widget2k13]

yes that was it 1.7.2 and colour dmd so i still use 1.7.1 for the colour dmd

 

i ran pinvol as admin and it worked, but for some reason it will not load up with windows now when in run as admin

[mjr]

yes that was it 1.7.2 and colour dmd so i still use 1.7.1 for the colour dmd

 

i ran pinvol as admin and it worked, but for some reason it will not load up with windows now when in run as admin

 

Glad that did the trick!

 

Startup launch is one of those security restrictions on Admin mode that makes Admin mode a PITA.  Windows isn't very user-friendly about it, either - if you try to launch an Admin task with a Startup shortcut, Windows just ignores you and doesn't even bother to show an error message about why.  There is a workaround, though, if you really want to keep everything in Admin mode.  You have to use Windows Task Scheduler instead of a Startup shortcut.  Create a task, add an "At log on" trigger, set the Action to "Start a program" with the PinVol program EXE as the target, and under Settings, check the box for "Run with the highest privileges".

[widget2k13]

I have took admin off everything and it all seems to be working with no issues Im so happy with it at long last , I especially love the silent mode by the press of a button thats awesome , mjr you are a genius I cant thank you enough for the work you have done.
Thank you

[mjr]

I have took admin off everything and it all seems to be working with no issues

 

Wonderful!

[DarenHawes]

Hello

 

I am having a small Problem with Teensy 3.1 and DOF.

 

This is what I am following: https://www.youtube....h?v=cMPVzsJYiMQ All the parts. I am stuck at 1:13  

 

I receive this error when trying to Test.

 

2019.03.22 15:50:25.156 Framework initialized.

2019.03.22 15:50:25.156 Have fun!

2019.03.22 15:50:25.383 EXCEPTION: TeensyStripController TeensyStripController updater thread  could not connect to the controller. Thread will quit.

2019.03.22 15:50:25.383 EXCEPTION: Thread: TeensyStripController TeensyStripController updater thread 

2019.03.22 15:50:25.383 EXCEPTION: Message: IOException --> The semaphore timeout period has expired.

2019.03.22 15:50:25.383

2019.03.22 15:50:25.383

2019.03.22 15:50:25.384 EXCEPTION: Stacktrace:    at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)

2019.03.22 15:50:25.384 EXCEPTION: Stacktrace:    at System.IO.Ports.SerialStream.EndWrite(IAsyncResult asyncResult)

2019.03.22 15:50:25.384 EXCEPTION: Stacktrace:    at System.IO.Ports.SerialStream.Write(Byte[] array, Int32 offset, Int32 count, Int32 timeout)

2019.03.22 15:50:25.384 EXCEPTION: Stacktrace:    at System.IO.Ports.SerialPort.Write(Byte[] buffer, Int32 offset, Int32 count)

2019.03.22 15:50:25.384 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.AdressableLedStrip.TeensyStripController.ConnectToController()

2019.03.22 15:50:25.384 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.OutputControllerCompleteBase.UpdaterThreadDoIt()

2019.03.22 15:50:25.384 EXCEPTION: Targetsite: Void WinIOError(Int32, System.String)

 

Here are some notes.

 

• My Teensy is on COM3 and works with Urduino.
• I have flashed the Teensy with this https://github.com/D...roller/releases
• I have Setup the INI files - See below (Where can I upload them?

 

<?xml version="1.0" encoding="utf-8"?>

<!-- This config file will set up two addressable LED strips orange on the right and blue on the left.  Each is 53 long and have the distal LED as the first in the array -->

<Cabinet xmlns:xsi="http://www.w3.org/20...chema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

  <Name>Teensytest1</Name>

  <OutputControllers>

    <TeensyStripController> 

      <Name>TeensyStripController</Name>

      <NumberOfLedsStrip1>71</NumberOfLedsStrip1>

      <NumberOfLedsStrip2>71</NumberOfLedsStrip2> 

      <NumberOfLedsStrip3>71</NumberOfLedsStrip3>

      <NumberOfLedsStrip4>71</NumberOfLedsStrip4>

      <NumberOfLedsStrip5>71</NumberOfLedsStrip5>

      <NumberOfLedsStrip6>71</NumberOfLedsStrip6>

      <NumberOfLedsStrip7>71</NumberOfLedsStrip7>

      <NumberOfLedsStrip8>71</NumberOfLedsStrip8>

      <ComPortName>COM3</ComPortName> 

    </TeensyStripController>

  </OutputControllers>

  <Toys>

    <LedStrip>

      <Name>PlayfieldRight</Name> 

      <Width>1</Width> 

      <Height>60</Height>

      <LedStripArrangement>TopDownLeftRight</LedStripArrangement> 

      <ColorOrder>GRB</ColorOrder>

      <FirstLedNumber>1</FirstLedNumber>

      <FadingCurveName>SwissLizardsLedCurve</FadingCurveName> 

      <OutputControllerName>TeensyStripController</OutputControllerName>

    </LedStrip>

    <LedWizEquivalent>

       <Name>LedWizEquivalent 30</Name>

      <Outputs>

        <LedWizEquivalentOutput>

          <OutputName>PlayfieldRight</OutputName>

          <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>

        </LedWizEquivalentOutput> 

      </Outputs>

     <LedWizNumber>30</LedWizNumber>

    </LedWizEquivalent> 

  </Toys>

 <AutoConfigEnabled>true</AutoConfigEnabled>

</Cabinet>

 

 

<?xml version="1.0" encoding="UTF-8"?>

 

<!--Global configuration for the DirectOutput framework.-->

 

<!--Saved by DirectOutput Version 3.1.6618.30526: 2018-07-31 16-41-51-->

 

-<GlobalConfig>

 

<LedWizDefaultMinCommandIntervalMs>1</LedWizDefaultMinCommandIntervalMs>

 

<LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs>

 

<LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs>

 

<IniFilesPath>C:\Pinball\DirectOutput\Config</IniFilesPath>

 

<ShapeDefintionFilePattern>C:\Pinball\DirectOutput\DirectOutputShapes.xml</ShapeDefintionFilePattern>

 

<CabinetConfigFilePattern>C:\Pinball\DirectOutput\Config\Cabinet.xml</CabinetConfigFilePattern>

 

<TableConfigFilePatterns/>

 

<EnableLogging>true</EnableLogging>

 

<ClearLogOnSessionStart>false</ClearLogOnSessionStart>

 

<LogFilePattern>C:\Pinball\DirectOutput\DirectOutput.log</LogFilePattern>

 

</GlobalConfig>

[Outhere]

No need to have this line

<!-- This config file will set up two addressable LED strips orange on the right and blue on the left.  Each is 53 long and have the distal LED as the first in the array -->

 

I don't know if this will help but I believe this is the way this should be

 

      <NumberOfLedsStrip1>60</NumberOfLedsStrip1>

      <NumberOfLedsStrip2>0</NumberOfLedsStrip2> 

      <NumberOfLedsStrip3>0</NumberOfLedsStrip3>

      <NumberOfLedsStrip4>0</NumberOfLedsStrip4>

      <NumberOfLedsStrip5>0</NumberOfLedsStrip5>

      <NumberOfLedsStrip6>0</NumberOfLedsStrip6>

      <NumberOfLedsStrip7>0</NumberOfLedsStrip7>

      <NumberOfLedsStrip8>0</NumberOfLedsStrip8>

Edited by Outhere, 22 March 2019 - 06:35 AM.

[NailBuster]

 

Startup launch is one of those security restrictions on Admin mode that makes Admin mode a PITA.  Windows isn't very user-friendly about it, either - if you try to launch an Admin task with a Startup shortcut, Windows just ignores you and doesn't even bother to show an error message about why.  There is a workaround, though, if you really want to keep everything in Admin mode.  You have to use Windows Task Scheduler instead of a Startup shortcut.  Create a task, add an "At log on" trigger, set the Action to "Start a program" with the PinVol program EXE as the target, and under Settings, check the box for "Run with the highest privileges".

 

 

another 'interesting' thing is that windows has no issue if a batchfile in win-startup folder starts an admin-exe.  So another solution is to set the exe 'as-admin' and make a batch file that simply calls it.... 

[mjr]

another 'interesting' thing is that windows has no issue if a batchfile in win-startup folder starts an admin-exe.  So another solution is to set the exe 'as-admin' and make a batch file that simply calls it.... 

 

Well, except that you'll get a UAC dialog every time the system starts.   (If you don't see a UAC dialog, perhaps you have UAC disabled on your system.  A lot of people around here do that because of all of the confusion about Admin mode, but I'd try to avoid it.)  Task Scheduler is really the right way to do this, in that Windows trusts it and lets you pre-approve the elevation at the time you create the task.

[NailBuster]

I'm seeing more cases where DOF (latest) com-object interface only working as windows-normal user.  If user runs PinUP as admin then DOF doesn't work at all.  My solution is just run as normal user but some need/want to run as admin.

 

some fixes reported by users:

 

remove DOF entries in registry and re-run registercomobject.exe as admin.  (doesn't work for all)

someone reported they fixed it by setting where the config (log?) file is located.  

 

I notice DOF makes a dof output.log in the current folder (DOF object is created in javascript).  Perhaps when ran as admin the DOF default folder is a windows system (syswow?) and that is where it fails?

I can't replicate the issue as most can run with or without admin... so im guessing as to a workaround for some.

 

just looking for ideas...

[DJRobX]

I'm seeing more cases where DOF (latest) com-object interface only working as windows-normal user.  If user runs PinUP as admin then DOF doesn't work at all.  My solution is just run as normal user but some need/want to run as admin.

 

some fixes reported by users:

 

remove DOF entries in registry and re-run registercomobject.exe as admin.  (doesn't work for all)

someone reported they fixed it by setting where the config (log?) file is located.  

 

I notice DOF makes a dof output.log in the current folder (DOF object is created in javascript).  Perhaps when ran as admin the DOF default folder is a windows system (syswow?) and that is where it fails?

I can't replicate the issue as most can run with or without admin... so im guessing as to a workaround for some.

 

just looking for ideas...

 

When it *doesn't* run for these users what is the actual result?  Is it failing to create the com object?  Is there an HRESULT code?  

Running procmon on an impacted system and watching what happens might give more clues. 

Edited by DJRobX, 28 March 2019 - 05:17 PM.

[NailBuster]

I gave a test DOF comobj utility i made to one guy to test out and report any errors/logs.   

 

update:  so user reports they get "class not registered" when trying to access DirectOutput.ComObject,   BUT same util run as normal user works fine....

Edited by NailBuster, 29 March 2019 - 02:23 PM.

[themaxx2k]

i am one of the affected users :-):
I got the following Config:
PinUpMenu.exe run as admin
VPX run as admin
DOFLinx run as admin
BAM and Future Pinball run as admin
pinvol run as admin
xpadder run as admin

Main reason for admin is that afaik BAM/FP needs this. if i turn admin off for them they stop working. And i got problems loading FP from pinupmenu when pinupmenu was not run as admin. But i will try once again to remove "run as admin" and see what happens. How can i use procmon for further investigation?

[themaxx2k]

removed admin form all parts mentioned above:

PinUpMenu working, but no DOF (probably messed during testing?)
PinVol must be admin, else no controll during Emulators
DOFLinx must be admin, else no FX3 Backglass displayed

FP/BAM must be run in compatibilitymode XP SP3, else fploader does not work
DOF / DOFLINX working everywhere else except PinUpMenu, but as mentioned, could be messed up during testing with debug / alternate registering bat (provided vor testing purpose, as mentioned a few threats above)

xpadder must be run as admin, else no keypresses in PinUpMenu (strange?!)

Thx for all who try to get this issue solved.

Edited by themaxx2k, 30 March 2019 - 05:37 AM.