46 replies to this topic

[xenonph]

I just tried it out and it adds a txt file in the nvram folder. But the Broncos Table starts with Seahawks Team. I will try Re-Initializing the Broncos Table and see if that works.

After Re-Initializing the starting Teams, it works!!

I can play both tables with same nvram file.

Will I need to include the txt files along with nvram file with all the Tables I upload?

 

 

EDIT:

 

It made its own nvram file called  NFL v1.nv and NFL v2.nv

 

Are these the nvram files I need to include with Tables I upload? Or will these be created upon table launch?

Edited by xenonph, 29 January 2016 - 03:34 AM.

[allknowing2012]

No need to include - it gets created upon startup. Its like a person settings file. The  .txt file you found might be something like highscores. Again not needed. All you need to upload are the .vpt/.vpx and .directb2s files.

[xenonph]

Well I just deleted the NFL nvram files to see if it would create. It does create but doesnt have starting team changed.

So looks like i will have to include Team nvram file with Table download, if I want the Starting Team Changes to take effect. Otherwise, both Tables start with Giants team at beginning of game.

 

Or am I missing something here?

Edited by xenonph, 29 January 2016 - 04:52 AM.

[xenonph]

Ok... I have been messing around with this for a few hours. This is how I got it to work, and I dont see any other way around it.

 

First of all...when you add NVOffset (1) to the script for table to use a seperate version of nvram, You need to have the original NFL.nv file included in there to begin with before you start new table. Otherwise it will just make it the default NFL.nv file and none of the changes take effect.(It turns NFL v1.nv into NFL.nv)

 

What I did was erased all NFL nvram files.

Started regular NFL (Stern 2001) table.

This made the initial NFL.nv file.

 

I then changed script in Seahawks Table with NVOffset (1).

I start the Seahawks Table and go into settings in the DMD and switch to Seahawks starting team.

It then initializes and makes "NFL v1.nv"

 

I then change script in Broncos Table with NVOffset (2).

I start the Broncos Table and go into settings in the DMD and switch to Broncos starting team.

It then initializes and makes "NFL v2.nv"

 

It seems all these files need to be kept together.

For instance.

If I delete NFL v1.nv out of nvram folder which is for the seahawks table, And then start Broncos Table which uses NFL v2.nv,

the Broncos Table starts with Seahawks team, like it took the place of NFL v1.nv.

Same as if I delete the first NFL.nv file. The one above takes its place.

 

So with each Table I make I will need to include the new nvram and all the preceding nvrams from earlier tables for this to work right. (WHERE YOU CAN HAVE ALL THE NFL TABLES HAVE DIFFERENT STARTING TEAM, WITHOUT OVERWRITING PREVIOUS NFL.NV FILE.)

 

So if someone downloaded my new Broncos table, and put the NFL v2.nvram, it still wouldnt work as it would be moved to default nvram position. (The line starts at NFL.nv and goes up from there)

 

Or if there is an easier way, I would like to know. Or am I missing something?

 

Otherwise I will be uploading new versions with this format. To where it wont overwrite previous versions.

 

EDIT:

 

 Not sure about this..now when I play the regular NFL table it starts with the Seahawks...This is crazy!!

Im just going to include the nvram file that changes it to specific team, and it will overwrite previous versions. So if you install the Broncos NVRAM, and start up the Seahawks Table, the starting team will be broncos.

No way around it.

Even if i save the NFL.nv and NFL v1.nv and NFLv2.nv files. and then add them like a new install, they still dont work correctly. Still have to initialize. And as soon as you initialize, the original NFL.nv file is replaced.

 

Unless I edit the script in original NFL Table to use NFL v1.nv, Then when I intitialize new tables, the original will still work maybe? I am going to mess around some more with this.

Edited by xenonph, 29 January 2016 - 08:13 AM.

[xenonph]

It worked!!!

I changed the original NFL table to NVOffset (1)

Seahawks NVOffset (2)

Broncos NVOffset (3)

 

So these are the files I need to upload with tables.

 

Seahawks Table...

 

NFL.nv  ....part of the Original NFL table Initialization. (Any NFL Tables loaded without NVRAM will use this.)

NFL v1.nv ..................Original NFL table nvram file...starting team Giants.

NFL v2.nv ..................Seahawks table nvram file.......starting team Seahawks.

 

All 3 of these files need to be placed in nvram folder for this Seahawks table to work where it starts the Seahawks Team.

(And the original NFL table stays same. Giants start)

 

Broncos Table...

 

NFL.nv  ......part of the Original NFL table Initialization. (Any NFL Tables loaded without NVRAM will use this.)

NFL v1.nv ....................Original NFL table nvram file...starting team Giants.

NFL v2.nv ....................Seahawks table nvram file.......starting team Seahawks.

NFL v3.nv ....................Broncos table nvram file..........starting team Broncos.

 

All 4 of these files need to be placed in nvram folder for the Broncos table to work where it starts the Broncos Team.

(All preceding NFL tables Start with proper Team.)

 

If you are missing just one of these nvram files the Starting team will not be changed to what you want.

 

Having this configured in this way allows you to play all 3 different NFL Pinball Tables without overwriting the others nvram.

(So no need to add the Seahawks nvram when you want to play Seahawks and Broncos tables or vice versa.)

 

I will be updating the 2 tables I have made with this configuration!!

 

So with each new NFL Table, I will be adding 1 more nvram file to the collective. So the next table will have NFL v4.nv as well as all the ones before it, in case people dont have all 4 nvram files.

Edited by xenonph, 29 January 2016 - 08:09 AM.

[xenonph]

Ok... I seem to have ran into a problem.

 

I have been using the NVRAM OFFSET command for all the NFL MODS.

 

Well the Saints table uses nvoffset (10), and apparently this will be the last table to use the nvram command as it only holds up to 10 nvram shared.

When I completed the next table (Bengals) and added number 11, it didnt work and actually caused an error in script making table not work. So I just made the Bengals table use the nvoffset (1) which was being used by the plain original NFL conversion.

 

I tried decimals and letters. Nothing worked.

So the Bengals table will be last to use the nvoffset command in script.

All the rest of the NFL Team tables will only come with the nvram that starts that specific team.

 

Unless anyone knows a way I can get around this.

 

I also tried copying the rom and adding a 1 to it, then renaming in script, but pinmame doesnt recognize. Has to be another way around this. Or am I at the end of using the nvram offset command?

 

Any suggestions would be appreciated.

[xenonph]

If I change it to 1.2 or 1.3, it still shares the same nvram as the nvram offset (1).

I cant see a way around this with out having to compile a new version of PinMAME with a NFL rom having number added to it. And seeing there is 32 NFL Teams, I will need 3 new roms. (NFL1 NFL2 NFL3)

Looks like people will only be able to have 10 NFL tables with the starting teams they like at maximum until I can find a way around this.

Edited by xenonph, 18 April 2016 - 10:55 PM.

[Carny_Priest]

You might put in a request with PinMAMEdev to up the possible count of nvram files.

[xenonph]

Thanks Carny_Priest.

Good idea, only I am not sure how to put in a request. Also after I am finished with the NFL Teams, I will be moving on to Baseball Teams Table and possibly Basketball Team tables, and they all will need more than the 10 shared nvrams capacity.

It would seem that this nvram offset command perfectly suits these particular Sports Team Tables.

I am happy with 10, but would be great to have them all start with team it was made for.

Edited by xenonph, 19 April 2016 - 12:07 AM.

[Carny_Priest]

The VPM beta thread. It is active:

 

http://www.vpforums....ic=27063&page=1

[jamos]

Also more customization if you use the alias file and name your gamenames differently with alias pointing to original rom you can position your external dmds differently per table using the same rom.

 

example i have 4 AC/DC tables. 

acd_luci,acd_170hc

acd_pwrup,acd_170hc

etc.

 

 

 

 

using offset names the tables in the nvram file with .txt on the end I think it uses the txt file to differentiate the scores etc. and settings although I have noticed credits are shared through all tables.

 

pwrup is offset 1.

Edited by jamos, 13 December 2020 - 07:27 AM.

[jamos]

Also to above why not just use a unsued rom file for nv1-10 again a diffferent version name but the rom is the latest. that way you could add 10 more teams. And do it again to add another 10.

 

For me this doesnt seem to work maybe i need to wipe out all my nv files after adding the offsets to the script. in effect resetting my tables. then try but it seems when I add coins it coulnts for all tables even with different nvoffsets. im thinking a batch script to run before and after tables loads to just back up the nvram files may just be easier sure wish nvram would just look at alias names then no offset is needed. but it doesnt seem to do that.

[jamos]

Ok got it working.

 

First I use VPMAlias file, I have to have that if you have multiple back glass for same game as I only have 2 monitors. 

acd_pwrup,acd_170hc

acd_luci,acd_170hc

acd_pv,acd_170

acd_pe,acd_170hc

acd_bib,acd_170hc

acd_ltbr,acd_170hc

twd_bigus,twd_160h

twd_alt,twd_160h

 

This allows me to place the extdmd for every alias table in different positions.

 

Then I edit each table script that shares the same ROM name. But I do not want NVoffset to pick up the alias name which it would normally and doesnt work if it does (like I said earlier NVoffset function should look at alias file first to get real rom names but it does not).

 

here is sample script where I set the real rom name call NVoffset then change it back to the Alias name.

Const cGameName = "acd_pe"

 

then in the table init section

 

   With Controller

        .GameName = "acd_170hc"

         NVOffset(3)

        .GameName = cGameName

 

I set GameName to real rom name then call the NVoffset function so it uses that name to set to 3 for copying the nvram 

then I set it back to Alias name to run the game.

 

works great and I have the advantages of the Alias name and different machine roms for the same rom version.

 

Things to note:

If using colored dmd roms you have to have a folder in your altcolor folder with the alias name.

Also if you are using DOF you need to have a alias name copy of the rom name to get dof efffects for table.

Edited by jamos, 15 December 2020 - 01:35 AM.

[Thalamus]

So, have you tested what happens if - lets say acd_bib is missing ? Is still the score for twd_alt, actually twd_alt or is it one of the others ?

[jamos]

If it is missing what do you mean?

 

It keeps track of all the scores if one is missing it just doesn't create that backup number nvram.  

You can start the tables in any order it remembers by the offset number.

What i do once I add all the Alias entries and the code in the tables is start each one arrange the external dmd  position and save then close.

I then start the first one again and add some coins. then the second and it shows 0 coins so I know its working.

 

table will give a error is it is missing from the alia file of course just like you were missing a rom.

[Thalamus]

What I mean is that if you delete one table, won't the nvram offset get skewed ? Might be that I remember wrong, I believe it is. Long time since I looked into this last. Anyway, thanks for reminding me to look into this again. I have a couple of tables I should create this for. I guess I find out myself.

Edited by Thalamus, 15 December 2020 - 05:48 PM.

[jamos]

What I mean is that if you delete one table, won't the nvram offset get skewed ? Might be that I remember wrong, I believe it is. Long time since I looked into this last. Anyway, thanks for reminding me to look into this again. I have a couple of tables I should create this for. I guess I find out myself.

no it should not you can now go to 32 offset versions. If i delete a table then I will delete the nvram offset backup for that number. 

 

I currently have 5 versions of AC-DC all work fine. If i delete one the others are still numbered correctly. if it is the one with the .txt file then I would have to change that number or just wipe out all my nvrams for that table.

 

I would say in simple terms do not play the table you are going to delete last play another version and exit or delete all your nvram backups.

 

I am using Alias with nvram backups this is kind of a hybrid way of doing two things but hey it works.

Edited by jamos, 15 December 2020 - 08:05 PM.

[jamos]

one thing to note if you use NVoffset make sure you use it on all tables that call your rom or the one that doesn't use it can mess up the nvram file.

[wiesshund]

one thing to note if you use NVoffset make sure you use it on all tables that call your rom or the one that doesn't use it can mess up the nvram file.

So, alias all tables, even the 1st one, and nvram all tables, even the 1st one?

[jamos]

 

one thing to note if you use NVoffset make sure you use it on all tables that call your rom or the one that doesn't use it can mess up the nvram file.

So, alias all tables, even the 1st one, and nvram all tables, even the 1st one?

 

Yes. And open them all up once without changing anything other than positioning the dmd then close them (do not play or add coins) we want the nvram copies to all be as if the table was new (I found also that some tables read nvram files differently so they all initially need the original rom to start with). so I have 6 AC/DC versions using 170hc all of them have alias and all have nvram set from 1 to 6 as described above. Only bitch is I have to add manually alias entries into my dof config.ini so when i update it from website tool I have to remember to cut and paste these entries first (I put them at the bottom of the config.ini so its easier to see my alias names) but this can be a good thing as I use different colored under lights etc. to distinguish each alias table. 

 

One note with the AC/DC tables I remarked out all the custom hiding of the internal dmds (I do this already with my extdmd settings) without that code remarked out I noticed occasional crashing when loading.

 

All of this Nvram coding in tables (other than placing NVoffset) could be avoided if core.vbs NVoffset function would look at Alias file first to see if the rom name is a alias but it is not coded that way and I am not changing Core.vbs as it will get overwritten on any new vpx release.

Edited by jamos, 16 December 2020 - 04:27 PM.