83 replies to this topic

[GordonJames]

 

If I have a 64 bit pc why would i download something that's meant for a 32 bit pc?, IE x86? The person who uploaded the tutorial i folowed specifically said that if you have a 64 bit pc you download and install the x64 bit versions of the dmd software, and if you have a 32 bit pc you download the x86. I'm utterly effing confused now. So I just spent a whole day trying to get this to work and the instructions I duplicated three times over are wrong and counter intuitive?

 

 

 

Simple

 

Your PC and OS bitness means jack and squat.

 

If you run 32bit VPX, then you use 32bit vpinmame and 32bit freezys DMD extensions

 

If you run 64bit VPX then you run 64 bit vpinmame and freezys DMD extentions
And you accept the fact that some stern and williams ROMs may crash or go out of sync due to no working a9jit in 64bit vpinmame presently.

And yes, you can actually run both side by side

 

you put freezys files in the vpinmame folder

 

in vpinmame folder you make an altcolor folder

in alt color folder you make folders with the same names as the rom's zip file
in that folder you put the .vni and .pal file
All .pal and .vni files are named p i n 2 d m d (without all the spaces)

 

.crs color files i dont think the file name matters, only the folder name

 

.pac files, you will have to ask luck1 as those only work in his crap mess

they dont work in freezys, and wont cause he told freezy to piss off basically.

 

run setup.exe or setup64.exe from vpinmame folder

click test
find rom and select

click game settings

check use external dll

uncheck show dmd

check colorize

click OK

click start button

 

DMD window should appear
and if color files are good, rom should have color.

 

Stern roms are different, you need a .pal file
and you have to patch the ROM itself.

 

yep, the tutorial i posted advised all of that but also wrongly advised to use x86 for "a 32 bit system". He should have said 32 bit vpinmame. Specifics are important. I downloaded the x86 versions after i read this thread and bam, worked immediately like it should have.

 

Now I have a new issue to resolve. When I start up these tables with color DMD files the editor stays visible on my monitor after the table loads. I have to manually click the screen with my mouse to remove it every single time now even after saving the table and re booting my pc. Anyone know how to fix this?

 
 

Edited by GordonJames, 08 August 2023 - 06:07 AM.

[wiesshund]

what are your launch args?

how are you launching the tables?

[GordonJames]

what are your launch args?

how are you launching the tables?

I don't know what "launch args" are. Remember, I'm a noob. I am launching the tables three different ways and all result in the editor still on screen after these color DMD tables launch. All other tables launch normally.

 

1. I launch vpx tables by double clicking on a folder shortcut on my desktop of the VPX tables folder in my Visual Pinball folder on my single C drive. Then I select a random table, type the first two or three letters of the desired table i want to launch on my keyboard, search by eye till i find the appropriate table and i double click on the vpx file for that table. The vpx editor pops up, the vpin mame box pops up and the table starts in desktop mode without the editor or the vpinmame box visible. Totally normal behavior like Future Pinball acted when i used that.

 

2. I also have a shortcut on my desktop of the vpx exe in my visual pinball folder on my C drive. I double click this and the editor pops up with no table loaded into it. It also pops up a window that is a link to my vpx table folders. When i want to go into the script without starting the table first, or make changes to any other settings before launching a table i will close the pop up link to my vpx tables folder and click the editor, then file, then open, browse to a table, double click on it and it loads in the editor without launching the table in full screen ready to play. This way i can make changes first before I choose to open the table by pressing F5.

 

3. i can simply not close that window that pops up when i double click on the vpx exe shortcut and simply start a table that way. But i never do. I use the number 1 or number 2 options to open tables exclusively. 1 for quick table launch or 2 when i want to make changes to the script or other settings etc first before opening a table full screen.
 

Edited by GordonJames, 08 August 2023 - 02:53 PM.

[wiesshund]

Hmm, at the moment i am at a loss as to why the editor comes into focus.

 

Normally that only happens of the table incurs an error, and of course the editor shows an error message.

 

If you hit F1 while the offending ROM's table is running, is cabinet mode checked in vpinmame settings?