37 replies to this topic

[Conehead]

I have other aliases using the same syntax and they're working ok.

 

SimpHorror, simpprty

SimpParty, simpprty

Batman66, flash_l1

Smokey, flash_l1

Beatles, seawitfp

Abba, seawitfp

PlayboyBally, playboyb

RockDiner, playboyb

EvilDead2, ironmaid

BluesBros, ironmaid

AddamsMovie, taf_l7

AddamsTV, taf_l7

[Outhere]

Try the game without using the aliases and see if it works

[gtxjoe]

Alias names are the problem. You modified the rom name in the table and it no longer matches anything in the DOF config site so DOF does not know you are playing Addams Family

Try using alias name that start with the real rom name. I.e. taf_l7_puppack

Edited by gtxjoe, 30 April 2021 - 12:06 PM.

[Conehead]

Ok, that did the trick.  I changed the alias names to:

 

taf_l7AddamsMovie, taf_l7

taf_l7AddamsTV, taf_l7

 

And now both tables work with DOF.  Thank you!!  

[wiesshund]

 

Ok, that did the trick.  I changed the alias names to:

 

taf_l7AddamsMovie, taf_l7

taf_l7AddamsTV, taf_l7

 

And now both tables work with DOF.  Thank you!!  

 

 

well, now we know it definitely pays attention to alias names

 

good to know actually, that could come in handy later as a diagnostic trick

[wiesshund]

So question

Is there a generic DOF config in all that stuff?

one that simple contains all of the possible channels, in a default configuration

 

like this list of events, with some kind of default values for pulse duration etc?

'E101 Left flipper
'E102 Right flipper
'E103 Slingshot left
'E104 Slingshot right
'E105 Bumper back left
'E106 Bumper back center
'E107 Bumper back right
'E108 Bumper Left
'E109 Bumper center
'E110 Bumper right
'E111 Knocker
'E112 Shaker
'E113 Gear motor
'E114 Red flashers
'E115 Green flashers
'E116 Blue flashers
'E117 Beacons
'E118 Fan
'E119 Strobes
'E120 Red undercab
'E122 Green undercab
'E123 Blue undercab
'E124 Bell
'E125 Hell ball motor
'E126 Hell ball Green 
'E127 Hell ball Red 
'E128 Hell ball Blue
'E129 Chime 1
'E130 Chime 2
'E131 Chime 3

[arngrim]

The id you use in the configtool will depend on the id used in the script of the respective table, and not all tables are (hopefully) the same

Sent from my SM-G970F using Tapatalk

[wiesshund]

The id you use in the configtool will depend on the id used in the script of the respective table, and not all tables are (hopefully) the same

Sent from my SM-G970F using Tapatalk

 

Ok, your probably going to pull your hair out here, but humor me

 

Say i have 20 tables, not presently supported in dof config

 

Could one not make an ini entry

 

GenConfig, E101, E102, E103, etc etc

 

and then take said tables, and hand code them for DOF as you would an EM anyways

 

and if table used a ROM then alias the rom as GenConfig_romname,romname

and if table was Romless, change cGamename to GenConfig_tablename

 

and then, all 10 table would use the generic DOF config?

 

Now i realize you may run across some situations where you have to adjust something, modify a duration or what not
but seems you could copy the genconfig, make the required modifications and put it in as some appropriate name?

 

I know you said not all tables are hopefully the same, but kind of a lot are
i could take almost all of my EM tables, and run them on the same setup, and they would be prefect
some may use more toys than others, some have 2 bumpers some 3 etc but i dont think DOF will care if you dont use something.

 

and same goes for unsupported roms where for what ever reason, the rom itself just doesnt play nice

you could dof the table as if an EM
Cause bumper kicker flipper slingshot is still a bumper kicker flipper and a slingshot

[Outhere]

For Rom tables it's easier to use Solenoids numbers - Those would be very hard to have one generic set up
You could easily have one table set up on the DOF website for multiple games for Em or Originals
Just keep adding more E numbers so Only things that match in the games would use the same number
-
But since we have multiple people working with DOF as far as setting them up it would be a disaster

Edited by Outhere, 02 May 2021 - 01:05 AM.

[wiesshund]

For Rom tables it's easier to use Solenoids numbers - Those would be very hard to have one generic set up
 

except when the table has no switch solenoid or lamp for the events one might wish to use

[arngrim]

The constants for all em are the flippers, a drain, not all of them have 2 slingshots, 3 bumpers, 3 upper lanes, 4 down lanes, not all of them have a knocker, some of them have targets, drop targets.

And it really depends what ids are used in the scripts, so when i dof an original or em, i fill the script and the dof config at the same time, most of the cases there are no ids in the scripts of the authors

Sent from my SM-G970F using Tapatalk

[wiesshund]

The constants for all em are the flippers, a drain, not all of them have 2 slingshots, 3 bumpers, 3 upper lanes, 4 down lanes, not all of them have a knocker, some of them have targets, drop targets.

And it really depends what ids are used in the scripts, so when i dof an original or em, i fill the script and the dof config at the same time, most of the cases there are no ids in the scripts of the authors

Sent from my SM-G970F using Tapatalk

 

Some of them have no sling shots, some have 1 slingshot some have more than 2 sling shots, heck schuss has 6

but if table 1 has none and table 2 has 1 and table 3 has 4 of them
as long as all 4 tables use the same events list, it wont matter if table 1 never has a slingshot event, and wont matter that table 2 only has one slingshot being used, nor should it matter that table 3 is using 4 of them

since they are all 3 using the same exact list of events, just some of them are not making use of said events.

At least, it would seem that way?

[arngrim]

Some of them have slingshots in the middle of the playfield, bumpers at the bottom but the most important is how the table scripts are filled with ids, which in most of the cases, there are none.
So the point to have a generic config would not give advantages, if there is a rom missing, ask me to add it in the configtool, and me or somebody else can do a proper config respectively of the table/rom

Sent from my SM-G970F using Tapatalk

[wiesshund]

Some of them have slingshots in the middle of the playfield, bumpers at the bottom but the most important is how the table scripts are filled with ids, which in most of the cases, there are none.
So the point to have a generic config would not give advantages, if there is a rom missing, ask me to add it in the configtool, and me or somebody else can do a proper config respectively of the table/rom

Sent from my SM-G970F using Tapatalk

 

Does not seem any one understands what i am asking

[arngrim]

I don't see an interest to have a generic config that needs to be adjusted for each table afterwards.
Check the inlanes, i put the color respective the color surrounding the inlane, rgb undercab matches the color of the real cab, rgb flippers matches a secondary color of the table.
i try to have a great feedback experience so all tables are different, personally i wouldn't want to give a not that good feedback to a table

Sent from my SM-G970F using Tapatalk

[wiesshund]

Never mind, you are not understanding

[TerryRed]

Yes, you could make one "generic" big dof config that has standardized Exxx triggers for all major devices. Then use that one config for multiple EM tables, etc.

 

This was my original plan when I started creating PinEvent for my own releases (having a standard for Exxx triggers to use)... and while I basically do just that, in the end I always end up creating a more table specific config anyway (the tables I update are not very similar). Since I have my own DOF Config Creator Sheet (with a PinEvent specific version for myself using my own standard), its not worth using a singular big config for everything I do (which is more than just simple DOF). It actually end up being more work, as it's easier for me to create the "exact" effects and lighting I want.

 

For things like solenoids, sure you can add every combination of Exxx you could ever want to use for a "standard", as these are just on / off / pulse and don't require specific timed durations. For more complex lighting and effects, you will always want more properly "timed" effects.

 

For "basic" table like EMs, there's not really much to get to fancy about (but you can if you wanted to)... however in the end, everyone pretty much always wants each table to have their own config. If that uses the same Exxx triggers for 90% of them, that's fine... but using "one" config for all of them probably won't be a good idea.

[foodie]

dof sucks for me been trying to work out for 4 weeks what im doing wrong folled so may youtube videos the problem is all my files seem to be what i thort was in the right  place when i scroll the menu ect all my dof lighting works great  but when i go to load a table thaey turn off for loading so far so good but when the table loads and i start to play nothing all lights gone im at a loss did a format on my pc and installed baller staller seems a big mistake ,might have to go back to a old system of dof and vpx .please help i possible