8 replies to this topic

[Swisslizard]

Hi

 

There seem to be some users which have problems with the Pacled64 and DOF. Since the Pacled seems to work fine in my cab, I wonder if there other users which use Pacled and DOF successfully or if everybody has problems. Need to find out if there is a problem in the Pacled implementation of DOF or not.

 

Please let me have your feedback regading your experiences with Pacled64 and DOF.

 

Thanks!

Edited by Swisslizard, 20 November 2015 - 11:25 AM.

[blashyrk]

I'm wiring up my pacled64, if I run into any problems I'll let you know

[zebulon]

The only issues I've heard of are the occasional locked on outputs upon exiting tables.

 

I created a simple fix that you run in pinballx after a table exits (much like the ledwiz clear utility that Darkfall created).

 

You can download it from http://www.zebsboard...s/17/pacfix.zip

[Swisslizard]

Well, outputs which stay on when DOF exits are a known problem and not related to the pacled. As far as I can tell this happens since VP doesnt seem to quit properly sometimes and rather kind of crrashes during the exit. In such a situation DOF cant turn off the outputs.

[arngrim]

i plan to install the pacled on my cab in december, during my next holidays, i'll be able to do a lot of tests

[robertms]

Swisslizard, first of many thanks for all your brilliant work on DOF, you've helped people like me to transform technically a video game into a tactile and addictive eperience that rivals real pinball machines. I'm also running the Pacled64/DOF setup on my cab without any issues. Then again I'm using Zeb's excellent output kit and a booster board so maybe that's why I haven't ran into any issues. You can check out my cab setup by clicking the link in my signature below.

[Swisslizard]

I've been digging through the code and the SDK docu of the Pacled quite a while this evening.

 

In the end I realized that there was something important missing. The Pacled has a global fade speed register. All commands you send to the pacled to set some outputs to a value are using this fadespeed. Since DOF handles all fading on its own, it is important that the feedspeed is set to 0 before the first ouput command is sent. The problem was that exactly this fadespeed command was missing in the code, which resulted in a somewhat strange behaviour of the outputs. I'm still surprised that it took so long untill it became really clear that there was a problem.

 

Anyhow, this is fixed now. Will provide a new DOF R3 preview soon (as soon as I have fixed some other bugs which I have introduced recently).

[lizard]

Looks like a good find, i will have to dust off the pacled and try it again. 

[Swisslizard]

Check out the beta for DOF R3: http://www.vpforums....=33080&p=325757