Jump to content



Photo
- - - - -

RGB's stay on


  • Please log in to reply
50 replies to this topic

#41 dramaone

dramaone

    Enthusiast

  • Members
  • PipPipPip
  • 108 posts

  • Flag: United Kingdom

  • Favorite Pinball: star wars

Posted 16 October 2017 - 07:34 AM

All good advice from my friends above.

 

If you want to make more use of the strobe you can either;

a) edit the FX2 files and add it to trigger whenever you want, or;

b) given the limited number of feedback devices you have comment out the "LINK_SR= line and set your strobe port to a the LINK device used for one of the bumpers in FX2, ie LINK_BC=102,100,2000,255

 

The strobe toy is not used a lot on FX2 tables.  Given your setup, if you want more strobe, I'd go with b) above so that the strobe goes off every time you hit the bumper (most tables have 3) set to the centre bumper.

Yes agreed, all help is welcome and with everybody's setups being bespoke even down to what PC or hardware toys you buy sometimes you do have to try a few things.

Your idea sounds good for both what Id like and to test to see if they are working due to the frequency of what they would trigger.

Will test later today.

 

Thanks again



#42 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,807 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 16 October 2017 - 01:53 PM

You can Use the same Port number on 2 or 3 items



#43 dramaone

dramaone

    Enthusiast

  • Members
  • PipPipPip
  • 108 posts

  • Flag: United Kingdom

  • Favorite Pinball: star wars

Posted 24 October 2017 - 07:30 AM

Making good progress and decided to install an additional 2 flashers so ive the traditional 5 now which gives a much better appreciation of the light feedback sequences.

Ive made the strobe trigger off various areas of the table.

 

Are there any known issues with sainsmart boards? , the solenoids always are stable however the strobe can somethings stop working in games but is run off the same relay board as the solenoids.

A doflinx reset fixes this.



#44 DDH69

DDH69

    Pinball Wizard

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

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 24 October 2017 - 07:35 AM

Only one I'm aware of it, SainSmart (anything FTDI) has a driver issue where it really only likes one program communicating with it at once.  As such, DOFLinx closes the connection in between uses, whereas with all other output devices it does not need to do this.


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

#45 dramaone

dramaone

    Enthusiast

  • Members
  • PipPipPip
  • 108 posts

  • Flag: United Kingdom

  • Favorite Pinball: star wars

Posted 24 October 2017 - 09:26 AM

Yea that must have been what Id read. It doesn't appear to be that issue though.

Ill have to give it more attention later.

 

Just a quickie - with debug set as 1 my understanding was that you get a text file produced and the console appears on launch which allows fake emulation and scrolling updates.

The console has stopped appearing. 

 

Have i missed doing something or am I just having a brain fart?



#46 DDH69

DDH69

    Pinball Wizard

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

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 24 October 2017 - 11:58 AM

If you have DEBUG=1 in your INI and are getting the DEBUG.LOG produced with lots of info, then if you have been changing screens around (physically or logically) it is possible to confuse DOFLinx's saved settings for screen location.  These are held in the registry (exact path in the guide - sorry I don't have it in front of me currently).  You can simply delte the DOFLinx registry keys (or entire branch), it will recreate.


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

#47 dramaone

dramaone

    Enthusiast

  • Members
  • PipPipPip
  • 108 posts

  • Flag: United Kingdom

  • Favorite Pinball: star wars

Posted 26 October 2017 - 07:17 AM

Making good progress and decided to install an additional 2 flashers so ive the traditional 5 now which gives a much better appreciation of the light feedback sequences.

Ive made the strobe trigger off various areas of the table.

 

Are there any known issues with sainsmart boards? , the solenoids always are stable however the strobe can somethings stop working in games but is run off the same relay board as the solenoids.

A doflinx reset fixes this.

Ok I ( think ) this is happening. Initially when pinballfx2 games are launched all feedback is working and game specific scripts working fine.

 

Then at some point or when changing games it seems to go back to almost a default  script, with basic lighting rather than games specific.

Sort of basic RGB lighting and strobe only flashing on ball launch/start.

 

If I quit doflinx and restart is works fine again.



#48 DDH69

DDH69

    Pinball Wizard

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

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 26 October 2017 - 07:25 AM

Produce and post a log file when the problem occurs and give a full account of the problem that was the log is showing.


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

#49 dramaone

dramaone

    Enthusiast

  • Members
  • PipPipPip
  • 108 posts

  • Flag: United Kingdom

  • Favorite Pinball: star wars

Posted 26 October 2017 - 07:33 AM

Will do. Cheers



#50 dramaone

dramaone

    Enthusiast

  • Members
  • PipPipPip
  • 108 posts

  • Flag: United Kingdom

  • Favorite Pinball: star wars

Posted 26 October 2017 - 03:17 PM

If you have DEBUG=1 in your INI and are getting the DEBUG.LOG produced with lots of info, then if you have been changing screens around (physically or logically) it is possible to confuse DOFLinx's saved settings for screen location.  These are held in the registry (exact path in the guide - sorry I don't have it in front of me currently).  You can simply delte the DOFLinx registry keys (or entire branch), it will recreate.

Thanks is working now. Deleted the registry keys and then had to turn debug to 0 and run doflinx, and then change to 1 and run doflinx before the console would show, incase anybody else comes across the same thing.



#51 dramaone

dramaone

    Enthusiast

  • Members
  • PipPipPip
  • 108 posts

  • Flag: United Kingdom

  • Favorite Pinball: star wars

Posted 31 October 2017 - 12:19 PM

Thanks for all the help.

 

All is working as I intended and its just amazing!

My last hurdle was that Pinballfx2 if used in isolation and therefore launching from the grid would correctly load config files for the first game selected however would then stop and not select a 

new config file when a new game was chosen.

I resorted back to launching FX2 from PinballX and all feedback config files are working sweet as!

 

I've now moved onto installing Future Pinball to gather some classic tables and in conjunction with BAM ( after following a nice guide from Terry - thanks )

works fantastic.

I thought BAM was all about using head tracking to view the table as 3d but its so cool how is allows you to shape and config Future Pinball tables.

I'm interested in tinkering with the 3d tracking aspect using my sons xbox one kinect although Im guessing this requires much more computing power, graphics card, cpu, ram etc.

Can anybody confirm this? It was not detailed clearly on the BAM site.

 

 

I intend to gather my overall learnings and post in one thread as although there is a general method for this hobby everybody has specific systems that require some degree of bespoke or

where to buy parts from etc depending where you live in the world.


Edited by dramaone, 31 October 2017 - 12:20 PM.