53 replies to this topic

[DDH69]

Just loaded V7.13 to sort out the AUTO_MX=1 issue.

 

Have fun.

[denetor]

¿There is a problem with the link?. I can´t reach the file download.

[DDH69]

¿There is a problem with the link?. I can´t reach the file download.

 

I just used it and it seems fine.  Is there a specific error you are getting?  Is it just this download or others on the site?

[denetor]

 

¿There is a problem with the link?. I can´t reach the file download.

 

I just used it and it seems fine.  Is there a specific error you are getting?  Is it just this download or others on the site?

 

It appear the message " sorry you don´t have permission for that!", when i try to download it.

¿It is necesary a special permission to download this file?,  i don´t have problem with any other download

Edited by denetor, 21 March 2020 - 09:33 AM.

[DDH69]

No special permission required.  The file may not have been released by Admin for download yet.  Perhaps try again later.

[denetor]

No special permission required.  The file may not have been released by Admin for download yet.  Perhaps try again later.

Ok, thank you, i´ll try later.

[Polyphemus]

Same problem here

[fR33Styler]

The link works now (i wrote the admin) 

 

 

Hi DDH69,

 

sorry for delay... the topic "live with corona on this planet" re-designs everything.

 

Just for the protocol:

 

(my problem) was the 'launch lane effect' which runs on MX Right Effect coused by AUTO_MX=1 issue.

Fixed/works with V7.13.

 

Thx again for your support for the community and stay healthy! 

 

Greetz

 

BTW: i updated all 100 FX2/FX3 tables at the config tool... and submited for public consideration with Added RGB/MX Flippers/Magnasave, Undercab FX. Feel free to try, with your new RGB Buttons

[DDH69]

 

BTW: i updated all 100 FX2/FX3 tables at the config tool... and submited for public consideration with Added RGB/MX Flippers/Magnasave, Undercab FX. Feel free to try, with your new RGB Buttons

 

 

That is very BAD, please DO NOT do this.  Please reverse this ASAP.  Trying to have the DOF ROM compete with DOFLinx in controlling the output devices will break things for a lot of people.

 

I RECOMMEND PEOPLE STOP THEIR AUTO DOWNLOAD OF DIRECTOUTPUTCONFIG FILES UNTIL THIS IS REVERSED.

Edited by DDH69, 21 March 2020 - 10:31 PM.

[fR33Styler]

oh ok... i can do this and "reccomend" the changes again and delete things before... but to save a correction loop.... from which entries to you talk exactly to remove:

 

[LynnInDenver]

oh ok... i can do this and "reccomend" the changes again and delete things before... but to save a correction loop.... from which entries to you talk exactly to remove:

If i had to guess... RGB/MX Flippers, RGB/MX Magnasaves and all the Undercab FX that you added the past 2-3 weeks. Basically every single thing you've been adding in to the FX3 tables.

 

Note that I'm personally not directly affected - I don't have RGB flipper/magnasave buttons, no MX, and no undercab FX. Nor am I autoupdating. But I do happen to have update emails turned on, so I was seeing the summary of the changes you were making.

[DDH69]

 

oh ok... i can do this and "reccomend" the changes again and delete things before... but to save a correction loop.... from which entries to you talk exactly to remove:

If i had to guess... RGB/MX Flippers, RGB/MX Magnasaves and all the Undercab FX that you added the past 2-3 weeks. Basically every single thing you've been adding in to the FX3 tables.

 

Note that I'm personally not directly affected - I don't have RGB flipper/magnasave buttons, no MX, and no undercab FX. Nor am I autoupdating. But I do happen to have update emails turned on, so I was seeing the summary of the changes you were making.

 

 

Correct.  All of these things create conflicts over devices that DOFLinx is set to control via configuration that should be made there.  Its the sort of conflict that you experienced with the magna save buttons previously.  This will manifest differently for various people based on their devices.  For example DOFLinx drives the RGB devices based on events in FX3 tables, setting the ROM for that table to have commands for RGB items will directly conflict with that.

 

If you do want configuration for yourself that differs from what can be supported generically then add them to your "candidate config" and generate your own DirectOutputConfig set of files.  Your desired setup may well support what you have attempted to do, and you may be happy with the result - if so great, go for it, just in your own setup.

 

If you want to 

[fR33Styler]

I´ve done it (deleted entries, saved and submitted) for all tables the change was already accepted.

(I check this the next days and if there are "older submits" in the pipeline which come online... i´ll fix them too).

 

Done 

Edited by fR33Styler, 23 March 2020 - 07:55 PM.

[DDH69]

I´ve done it (deleted entries, saved and submitted) for all tables the change was already accepted.

(I check this the next days and if there are "older submits" in the pipeline which come online... i´ll fix them too).

 

Done 

 

Thank you