131 replies to this topic

[darthwhat]

Can someone post what there ini looks like that has color styles saved for alphanumeric dmd besides the default?

[bmheyob]

Pls disregard my prior post, I wrote it in the wrong forum.

Edited by bmheyob, 10 May 2020 - 07:05 PM.

[darthwhat]

@Freezy

I figured out a way to save the color style name without having to type it.  C&P instead.

[freezy]

Sorry @darthwhat for not replying earlier, but I'm glad you've found a workaround. Ctrl+Ving the new name into the combobox works, but not typing directly?

[darthwhat]

Sorry @darthwhat for not replying earlier, but I'm glad you've found a workaround. Ctrl+Ving the new name into the combobox works, but not typing directly?

No worries, and that's correct cant type it in, I have type it on notepad, copy/paste that into the color style UI default entry and then save and it saves the profile in the ini

[Jeffrey Spender]

Just a little something to think about:

Did you all know you need to have the dotNet framework 4.5.2?
I've spent 2 days just trying to figure out why it would not work. (i know i'm a bit slow)
I don't have my Cab connected to the internet, so it was a lot of reading, looking at youtube and then going downstairs to the Machine.

 

My VpinMame kept crashing, i did not know the how/why. I did everything the video's told me.
Then i tried to execute the DmdExt.exe directy and Windows gave me this error message about not having the dotNetFX 4.5.2.

So maybe someone else here, having problems check on that.

[freezy]

To be fair, the first thing in the install instructions after installing, is test. Also the compatibility section explicitly mentions .NET.

[darthwhat]

@freezy
Another issue Im having that might be freezy related. Maybe you can see if you can replicate it. But I have this one table that the dmd flickers on. The table is like the slimer table but not available anymore if you catch my drift. The rom file is a unzipped folder that goes in the vpinmame folder and not in the ROMs folder. Its literally the only table Im having this flickering dmd on and it worked before installing the new freezy. Any ideas by chance?

EDIT: I confirmed with a few others on a couple FB groups and they are having the same problem with this particular table.

Edited by darthwhat, 13 May 2020 - 12:39 AM.

[Outhere]

@freezy
Another issue Im having that might be freezy related. Maybe you can see if you can replicate it. But I have this one table that the dmd flickers on. The table is like the slimer table but not available anymore if you catch my drift. The rom file is a unzipped folder that goes in the vpinmame folder and not in the ROMs folder. Its literally the only table Im having this flickering dmd on and it worked before installing the new freezy. Any ideas by chance?

Same here
 

[LoadedWeapon]

Yea and it was fine on 1.7.3

[freezy]

You guys all have PIN2DMDs? And it works with the virtual DMD? And probably using altcolor too?

 

EDIT: The best is to comment here if you can reproduce. Firstly it would be interesting to know if that happens with coloring disabled. Secondly, please check if the virtual DMD works fine, so we know it's a driver issue.

Edited by freezy, 13 May 2020 - 08:25 AM.

[vothar]

@freezy
Another issue Im having that might be freezy related. Maybe you can see if you can replicate it. But I have this one table that the dmd flickers on. The table is like the slimer table but not available anymore if you catch my drift. The rom file is a unzipped folder that goes in the vpinmame folder and not in the ROMs folder. Its literally the only table Im having this flickering dmd on and it worked before installing the new freezy. Any ideas by chance?

EDIT: I confirmed with a few others on a couple FB groups and they are having the same problem with this particular table.

i just installed this *table that you didn't named* 2 weeks ago and got this problem of flickering on my virtualDMD (with altcolor).... even with 1.7.3...  (even more strange, the problem of flickering didn't  appear if i juste test and start the rom), the problem was solved using 1.71 dll in the vpinspa directory

Edited by vothar, 13 May 2020 - 03:32 PM.

[freezy]

@vothar, so 1.7.1 doesn't flicker, but 1.7.3 does?

[vothar]

@freezy

 

yes... (it doesn't flicker if you test the rom in vpinspa, the special version of vpiname included with the table, but it flicker when you play in vpx)

 

i just found something weird with 1.8.1 (from r7 to r16)...

 

all the version 1.8 didn't like AT ALL the color rom of Who dunnit ( https://www.pincabpa...rsion-fr#188724 )

you can begin a game , but in less than 2 minutes of play , VPX crash to death depending of the scene on the dmd. no problem with 1.7.3

Edited by vothar, 13 May 2020 - 08:00 PM.

[freezy]

Hmm, could you create a GitHub issue about that one please? Provide a log, and if possible the palette or a direct link to it so I can reproduce.

 

And guys, in general, don't just take the lastest CI build. Those are usually from branches that aren't stable. r16 has like 900 line changes that aren't tested at all. So please get the official release, and CI builds only if you know what you're doing.

[Outhere]

On a LCD

I.71  --  Good
1.73 and 1.8  Bad   ---  Flickers the whole time I play the game from start to the and

[Roadblock]

 

Is there a tweak or setting I can get Baywatch and Frankenstien DMDs to look better ?

 

I must admit that I haven't retested this, but there shouldn't have been any changes. Will test and fix if necessary, thanks for the report!

 

 

I found old post:

Does it work in 1.8 ? can we alter the look of the dmd?

 

I haven't merged that branch yet, mainly because I've noticed performance issues. It works fine if there aren't many active dots like scores, but if over 50% of the display is lit, it starts stuttering. Will need to see if there are hacks to make it faster, re-write it as a shader, or just merge it as-is.

 

 

OK did some testing last night.

My PinDMD1 works with Visual PinMAME 2.7 (Standalone DLL, PinDMD1) 2.7

I've tried VPinMame 2.8, 2.8b, 2.9, 3.0, 3.1, 3.2, 3.3 they either crash or they update the DMD slowly

 

That's weird indeed. Maybe @toxie has an idea what changed after 2.7 that could cause this effect?

 

Hi Freezy,

I haven't heard from @toxie bit I did some more testing.
I installed Future Pinball and BAM.
Future Pinball works with my PinDMD1 without any lag using FP-Intercept.
FP-Intercept uses ftd2xx.dll and OpenGL32.dll to drive the DMD.
VPinMame stopped using those drivers/library files when it started using DmdDevice.dll (VPM 2.7 was the last version that worked properly).

There must be someone else out there still using a PinDMDv1. Please let me know how yours works. Please share your solution.

Thanks, Roadblock
 

[CyclonePF]

Help.

 

I installed DMD Extensions 1.8 tonight and upgraded my DMD firmware. Everything was looking and working great for a while, but some how during testing / configuring stuff tonight I've messed up something and I can't figure out how to fix it. What I am now seeing whenever I launch any table is that small alphanumeric display windows show up on the playfield (on top of the actual playfield). These are similar to the windows shown in the picture in the first post of Freezy's Hi-res alphanumeric rending with dmdext (https://www.vpforums...showtopic=41291). And automatic entries in my DmdDevice.ini get appended at the end of the file. For example, after launchingthe Pinbot table, the alphanumeric windows immediately show up on the playfield, and the following entries get appended to my DmdDevice.ini file:

 

[pb_l5]

alphanumeric pos.0.left = 520

alphanumeric pos.0.top = 520

alphanumeric pos.0.height = 120

alphanumeric pos.1.left = 26

alphanumeric pos.1.top = 26

alphanumeric pos.1.height = 120

alphanumeric pos.2.left = 52

alphanumeric pos.2.top = 52

alphanumeric pos.2.height = 120

alphanumeric pos.3.left = 78

alphanumeric pos.3.top = 78

alphanumeric pos.3.height = 120

alphanumeric pos.4.left = 104

alphanumeric pos.4.top = 104

alphanumeric pos.4.height = 120

alphanumeric pos.5.left = 130

alphanumeric pos.5.top = 130

alphanumeric pos.5.height = 120

 

Removing these entries doesn't fix it. The next time I play the game the entries get recreated and the alhphanumeric windows appear on top of the playfield again.

 

Does anyone know what I may have done and how I can fix it?

 

CyclonePF

[Outhere]

Add this to the INI File

[alphanumeric]
enabled = false

[CyclonePF]

Thanks Outhere. That fixed my issue.