Jump to content

New release: v1.10.2


freezy

Recommended Posts

  • 2 weeks later...

Thanks for all your work on giving us the new driver for our VP 

I am having issues with the new version I'd like to share.

Now I know I even run a newer version of your .dll but same was with 1.10.2.

Problem description:
with faster frames display looks blurry.

Test situation:
Freezy 1.10.3.2
Real pin2DMD  Firmware 4.31 ST32 hardware

Table: Tales of the A.N.
colorization : found here on VPU, latest 2.01 version by NetzZwerg 

What I think happens:
visable with faster frames I see that the new frame is being written on_top of the existing one resulting in a double, blurry picture.

Although very much visable during gameplay it is very easy to see with TOTAN when you have a ball drain and the machine starts counting the points.
With that counting it displays the new value on the DMD but as it does not clear the previouw frame there are 2 values being displayed together.
When the counting stops then finally the display is ok.

I did not make a picture of the counting process but here is a picture from an in-game situation.

When reverting to Freezy 1.8.0 with the same file everything is ok and very much sharp.

Happens to more tables, same problem but especially the counting when draining the ball as described is easy to reproduce.

Hope this helps, thanks!



TOTAN_display.jpg.ace43c8d82fe1dbe866b4eec8c49e309.jpg

Link to comment
Share on other sites

1) virtual DMD will not colorize with the real color files.   It does colorize making use of the 4 defined colors in the F1 menu but not make use of the color_files from NetzZwerg .

If I run both pin2dmd and virtual dmd the real dmd is colorized ok but the virtual is not. However...although not right colorized picture is perfect, not messy

2) using your 4.31 .dll  is the same problem when tested show little more messy.

Link to comment
Share on other sites

Could it be that the program where the authors do the colorization changed for 64 colors and that that output causes these double not_in_time frames?

And then it's a combination op the new .dll with that output that causes the blur.

Also : it occurs on multiple color_files from different authors.

As said: The older freezy version (1.8)  with the new 64 color .pal / .vni works fine so unless there is an update on this I'll stick to that.

Thanks for the support.

Link to comment
Share on other sites

1 minute ago, lucky1 said:

Freezy 1.8 does not support 64 colors, so I wonder how it could work fine  ?


it works fine regarding the issue I reported....so 1.8 is not blurry/double images.

Of course it does not support 64 colors....

Link to comment
Share on other sites

  • Content Provider

I just tested the TOTAN colorization on my VPIN and could not recognize any of the issues you described.

Neither on the pin2dmd nor or the virtual DMD.

I think there is another problem. Did you also update your pinmame version ?

Link to comment
Share on other sites

Thank you for your time and effort to test it.

Checked pinmame: all fine.

But:  

I managed to get the virtual display working in full 64 color.

Here the problem of the double frames (as I see it) does not occur, everything perfect on virtual DMD.

This means afaiks that all software, pinmame, vpx, drivers for the pin2dmd as well as all colorization is perfectly fine.

The error is -somewhere- on the link output PC -> STM32 -> Pin2dmd.
Also updated FW to 4.35 but result the same.

Could it be that the STM32, being one of the first releases, is not capable of handling the frames?  Did you test it with a STM32?

Thanks

Link to comment
Share on other sites

  • Content Provider
6 hours ago, Joppnl said:

Could it be that the STM32, being one of the first releases, is not capable of handling the frames?  Did you test it with a STM32?

 

Actually I did test with a STM32F4 Discovery board. I guess your problem is on the USB side. Make sure you have a dedicated USB port which is not shared with any other device. 

Link to comment
Share on other sites

Good!

So that means that the hw should be capable of doing the 64C thing.

Now....I think I 've found something.

The pin2dmd has it's own USB port nevertheless changed to other USB port(s), no result.
Changed different cables...no result.

However....when disconnecting the pin2dmd USB cable I could see that the led's on the magna-flipperbuttons went out....

Reconnecting the USB for the pin2dmd made them on  so....

I guess that there is a ground problem do to a bad connection and/or broken wire so therefore the current from other hooked up things like the magnabutton led's find it's way by the ground of the usb cable causing interference with the USB data for the pin2dmd.

When I build the VP I had the magna buttons before the pin2dmd so the design is ok but I have to search for a loose wire or not so bolt on screw or a broken wire especially the ones which deliver ground.

Might be a nasty thing to find but can do and will find and see then if the pin2dmd on 64 colors work correctly.

Thanks for your suggestion that brought me to this point

Link to comment
Share on other sites

Did a lot of testing last days and think I can reproduce the problem now....

1st: what I said about that ground wire: true, did repair it but did not change the problem of the 'double frames'. (with double frames I mean 2 rapidly changing images-in-1 like the end of ball count on TOTAN)

This is what I found out:

I have several USB connections: mouse/kb of course, but also pin2dmd, an external soundcard for SSF and MJR's pinscape.

When running the 64 color .dll with ONLY the kb/mouse and pin2dmd everything is perfect but...

When connecting one of the other devices (either the soundcard or the pinscape) or both the 'double frames' problem occurs.

This occurs both on Freezy's .dll and on the (latest)  pin2dmd .dll (last one also running ok with mentioned USBdevices not attached).

The pin2dmd is directly connected to an on-board USB port (no share with others) and all other devices also have there own usb-port.

Changing the pin2dmd to an othe usb-port does not change behaviour.

When reverting to 16 color then all is fine (with 16 colors..yes...) but no double frames and all devices connected.

So...my guess is that the new 64 color driver is conflicting with the other USB drivers (but I am no specialist, just thinking about the logic I see on the test) causing the 'double frames'.

For now I will revert to 16 color driver as I hope (??) that new 64 color .pal/,vni files are downwards compatible (is this true?)

Thnks

Link to comment
Share on other sites

  • Content Provider

You don´t have enough bandwidth for the 64 color frames on your USB bus. They are bigger then 16 color frames.

Even if you have a dedicated port I guess your ports are all running on the same internal bus. Please check your hardware

documentation about that. Adding a 10$ USB PCIe card to your system should solve your problems.

 

1 hour ago, Joppnl said:

that new 64 color .pal/,vni files are downwards compatible (is this true?)

 

No !

Link to comment
Share on other sites

Have a MSI Mortar B450M MB with 2 x USB 3.1 (Gen2) + 6 x USB 3.1 (Gen1) + 6 x USB 2.0   so I guess at least 3 different busses....

I'm sure I did try different combinations but will put pin2dmd alone on fastest 3.1 gen2 port and other HW on other ports, will re-install MB USBdrivers and see what happens. 


Are 64 C files downwards compatible?

Link to comment
Share on other sites

im updated to the newest freezy 1.10.2 and I get tons of doubling of letters etc. like the real dmd posted above except im using a lcd full dmd.  

 

Where do we find the files from lucky that everone is talking about? A search or google doesn't bring anything up .  And if we put his .dll into our vpinmame folder does it overwrite our freezy setup? or can they both work side by side with no issues.

 

Also besides the installing of luckys files and where they go, what settings are we supposed to set our lcd full dmd too? I'm not talking about when you hit f1, im talking about when you right click on the dmd and click on the bottom custom settings option.  this brings up a whole page where you can adjust fonts , dot size etc.  is there a certain setting it should be set to on the bottom photo? my jurassic park looks amazing now, but batman , champions pub, you can't even read the words anymore. 

 

 

 

Capture12.thumb.PNG.be65157570594ec8de33afb8134a017b.PNG

 

Link to comment
Share on other sites

17 hours ago, outhere said:

Lucky1's file will only work with a Real Pin2DMD

Thank you for the response. What about the second part? Is there a general settings we should set our real dmd to? 128x 32, 128 x32 color , 192x 64? 

 

Im almost positive i had a colorized version of Champ. Pub, but now it looks like a mess. I downloaded what im pretty sure was for the full dmd version, but i get the doubling of the letters like was posted above by someone else. 

Link to comment
Share on other sites

  • 3 weeks later...

I have problem with position saving. If I do right click and select save position for romname it isn't added to dmddevice.ini file anymore. All previously added positions for roms were stored there but it stopped working...

If I do it by hand the position are properly read from the ini, but can't do right click and save position for particular game anymore. Any clues?

Link to comment
Share on other sites

Is ... useregistry = false set under [global] ?

 

Always. If you got problems, providing good information about your problem, ie - putting the dmddevice.ini up on pastebin or something "made" for code sharing helps. Just paste the link to it and I would not have to ask what your value is.

Link to comment
Share on other sites

5 hours ago, Thalamus said:

Is ... useregistry = false set under [global] ?

 

Always. If you got problems, providing good information about your problem, ie - putting the dmddevice.ini up on pastebin or something "made" for code sharing helps. Just paste the link to it and I would not have to ask what your value is.

Here is my dmdDevice.ini: https://pastebin.com/G5X99KQJ

Link to comment
Share on other sites

6 hours ago, Thalamus said:

Is ... useregistry = false set under [global] ?

 

Always. If you got problems, providing good information about your problem, ie - putting the dmddevice.ini up on pastebin or something "made" for code sharing helps. Just paste the link to it and I would not have to ask what your value is.

Here is my dmdDevice.ini: https://pastebin.com/G5X99KQJ

 

Wanted also add that this worked in version 1.9 for sure... I've been able to save position for particular rom and it was showing up in the ini file as a new section

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...