Jump to content

rablack97

VIP Class
  • Content count

    39
  • Joined

  • Last visited

  • Days Won

    2

rablack97 last won the day on August 17 2016

rablack97 had the most liked content!

About rablack97

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

531 profile views
  1. Shrek and POTC colorized patches no longer work

    The issue i had was that the 3.1 did not like the patched color rom, these 2 games can only be colorized with pin2dmd hardware. It would crash the vpinmame test or just load the tables and then freeze, with an error.
  2. Shrek and POTC colorized patches no longer work

    no i did all of that. is that pin2dmd? are you using freezy's dmddevice.dll? did you check the other colorization tables.....metllica, acdc, mustang, avengers, start trek etc
  3. Shrek and POTC colorized patches no longer work

    Yeah i tried a few versions and narrowed it down to 3.1 being the culprit. in testing the vpinmame.dlls would either work with those 2 tables and break others or viceversa. Latest Freezy and latest 3.0 works fine. I took Carny's advice and tested 3.1 but rolled back to 3.0.
  4. Shrek and POTC colorized patches no longer work

    Figured it out, shrek and and POTC don't work with the 3.1 beta, I went back to the lastest 3.0 Sam and all color roms work as expected now.
  5. Shrek and POTC colorized patches no longer work, updated to Freezy's 1. 71. I am on latest Sam build and using djrobs, sam.vbs. Anybody else experiencing this, crashed the table in vpx and in vpinmame
  6. Pin2Dmd Colorprism V2.0 Firmware

    yes i copied over everything, its working now, it took about 3 tries before the key registered, i had to hit the reset button and then click pin2dmd.exe. Thanks Lucky....
  7. Pin2Dmd Colorprism V2.0 Firmware

    Hello Lucky updgraded to 2 .55 and the key doesnt work anymore, i keep getting an error say firmware not supported please upgrade.
  8. Feature request for the tool

    any update on getting the FP tables entered into the database?
  9. Feature request for the tool

    The DOF works, but it doesn't pick up the attract effect unless the rom matches up, Maybe it has something to do with the $pinballx area, trn by itself doesn't work, but when i change to trn_174h in the file it works.
  10. Feature request for the tool

    Yes the format of the rom name does not matter, as this is just the link to the table name. For the attract effect it seems that the table name from the PBX is what is used to match the table name in the INI. I tested the Gremlins line, and it does work, I have Gremlins as the table name in PBX, and it still recognized FP Gremlins as the correct table. As long as there is a specific word match in the title seems to work, if it needs to be specific, I can just add FP to the title in the PBX game manager. Tron also needs an alternate rom trn_174h trn is not working unless i update the file to say trn_174h
  11. Feature request for the tool

    Thank you for your consideration Arngrim Ok for future pinball, the table names have to matchup up in the tablemappings.xml and the future pinball.xml in Pinball X. For example, I think Gremlins is only on Future pinball, so to get the addressable led attract effect to work, I added the table to the tablemappings.xml <Mapping> <TableName>Gremlins</TableName> <RomName>disco</RomName> </Mapping> Tablename matches description in PBX FP xml <game name="GREMLINS PHYS 2_5(DOFlinx)"> <description>Gremlins</description> <rom></rom> <manufacturer></manufacturer> <year></year> <type></type> <hidedmd>True</hidedmd> <hidebackglass>True</hidebackglass> <enabled>True</enabled> <rating>0</rating> I then just picked a VP table that had the effects already in place and put that as the rom name for Gremlins $disco Yellow AL0 AW34 FU200 FD150 SHPDiamondPulse L3 The nice thing about this you could makeup your rom naming conventions such as FP-GREM. The key is the user would have to match their description in PBX with your table name. Would look something like this Here is a short list to start with, these games are not in your current list, which im assuming means they weren't ported over to VP. Aliens Legacy Batman Joker Edition Blue Vs Pink Bubble Bobble Gremlins Jaws Knight Rider Masters of the Universe RetroFlair Sonic the HedgeHog The Goonies
  12. Feature request for the tool

    Hello Arngrim, Sorry I meant to say mtl_164, 168 doesnt exist. There is nothing wrong with the rom. Some users have better luck using prior roms rather than the most recent. In this case the 170 rom causes metallica to freeze up and it doesnt play well. mtl_164 plays perfectly for me. So if you are able to create custom table configs in our profiles, there should be an option, possibly a free text field, where you can add the name of the specific rom that you are using so the tool uses that name in the ini files. Another request would be a section for future pinball addressable led support for pinballX, This would allow users to insert the attract effects for each table. Today users can't use the up to date table mapping without manual manipulation. The tool also wiped out custom future pinball entries for the attract effects in the config30 file. I would think, all that would be needed is table name, table short name (equivalent to rom name as FP does not use roms) and the PF back PBX MX. Thanks for any consideration to these suggestions.
  13. Feature request for the tool

    I tried 170 and it was causing me issues 168 seemed to work the best. So a rom name override feature isn't possible by profile? Sent from my SM-G920P using Tapatalk
  14. Feature request for the tool

    I thought the same, but for instance like metallica the 2 options are mtl_170h and hc i think, i'm using the mtl 168 rom, If i leave 170h in the table mapping and the config files nothing works, but when i manually change it all to 168 then everything works. So my thoughts were thats its looking for exact rom name matches. Also if what you say is true, the prefix for the metallica rom is the same yet there are 2 options. The tool generates the config files with these exact rom names not just mtl and the DOF does not work, Changing the file to reflect the mtl_168 rom fixes the problem, which is why i wondered if a naming override is possible so the tool creates the specified rom name for that user profile.
  15. Not sure if this is possible but, can you add a field to override the rom name, for instance, circus voltaire, if i am using cv_20h the DOF table is hardcoded to cv. So i have physically change the rom name so the configs match up. I notice some games have a drop down for other rom options. For those that don't have it an override field would be cool. That way the new name will show in your config files.
×