Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Joppnl

Members
  • Content Count

    137
  • Joined

  • Last visited

  • Days Won

    1

Joppnl last won the day on October 12 2017

Joppnl had the most liked content!

Community Reputation

17 Good

About Joppnl

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Update: changing the driver to libusb-win32 does work for normal dmd images and also the pinUP packs work but you will loose xDMD functionality. The better solution is to change the version of the used WIN driver. When connecting a pin2dmd to a fresh Win10 system it installs a driver version V10.x which does NOT work with Freezy's .dll With the Zadig tool you can downgrade it to V6.x which works fine and you don't loose xDMD functionality. When changing the driver be sure that after you pressed some buttons in the left and right box are the same (V6.x) (in this image I didn't press the button but after I pressed the big button it didn't change either, had to go into that option menu of the big right box by pressing the small arrow on the right and choose the downgrade/install option)
  2. OK...found it: with help from Jens Leiensetter who gave the solution: with the Zadig tool you need to install the libusb-win32 driver, I did use an other one which worked great but not in conjunction with Freezy's .dll Thanks for your help,
  3. Well.... tried everything I can think of but...no luck. Did: - use your .ini file - reïnstalled .net 4.5.2 as suggested by Freezy: PC says I have newer version, abort - reïnstalled C++ by Freezy's link - updated pin2dmd to 2.67 I guess ultradmd is working as that-table-not-to-be-mentioned works fine..... Out of options now.....
  4. Thank you outhere....lot of new options, will give these a try, will report later.
  5. Hello, as I'm installing PUPplayer I need to install the Freezy drivers for PIN2DMD and I really can't get it to work (just standard use, directly run from VPX, not talking about pinup pack or so at this moment) Some more info: I am on firmware 2.60 and with the normal pin2dmd .dll everything works fine, also full color etc. PC Win10. When using Freezy's 1.71 (x86) I do copy all that files into the pinmame dir (make sure they are all unblocked). Change the ini file to enable pup packs. now: I do get a virtual dmd on my table screen (makes sense, it is enabled in the .ini file) but the pin2dmd does not work. Pin2dmd is enabled in the ini as are some others (this is default). When I disable the virtual dmd and the other real-dmd's (except pin2dmd) then it also does not work at all. Pup is working fine with Freezy's .dll but it is not working fine with the original pin2dmd.dll (although with that dll I do have pin2dmd working. Any suggestions to get it work? Is it possible to get it to work with Freezy .dll? (and yes: 'use external dll is active (otherwise with the normal .dll pin2dmd wouldn't work as well) Thanks in advance! DmdDevice.ini
  6. Thank you for this beautiful table, also having a lock problem: when shooting into the lock (see green arrowed line in picture) ball won't return. Very sometimes I get a ball back on that red wire on the left but most times it does not. 2nd: ball was quicker then the kicker on the left outlane (see yellow line) so the ball got into the drain and never returned. I do think I did hear the kicker so I guess it was registered by the switch (it all goes very quick) but it was just to late to do so and never got it back 3r: what is that red small light on the PF (blue line). Thanks!
  7. We don't say it e-ve-ry time but.. thank you for your on-going work on this. One of the essential VP files...where would we be without it?? (nowhere...) And DJRobX...did try it on Jack-Bot...works excellent, thank you! (and also for all the other workt you do)
  8. This looks amazing good! And...don't know why...also plays better.....😁😁 Thank you for your great work!
  9. Thank you very much for your colorization on this pin! Looks great already 😂 Thanks! ! 👍👍👍
  10. It was the file coming from the 2.55 version of the pin2dmd git-hub section (my pin2dmd firmware is 2.55) Also tried it with the latest 2.58 version (both firmware and .dll) but same effect. When I do the new install I will use the standard pin2dmd dmddevice.dll which comes with the all-in 1 installer but what I do not know is with what firmware version is corresponds... therefore I did use the dmd file from the corresponding firmware version. Is there any benefit of using Freezy with a pin2dmd display?
  11. Mmmm....from memory: All the xx30 rev's did have the crash error. What I experienced with the latest rev 4738 that it runs with the color enabled the first time but not the 2nd time (as described above). I do not know if that was the case as well with older xx30 rev's but I am sure that the xx20 rev's did not have this problem. But now...after the Freezy test-install pinmame crashes immediately even the first time (even with the xx20 versions) and I couldn't get it back to work so now I'm totally installing a complete new build including WinX and VPX...... What I will do: install a fresh WinX and a fresh VPX first without any additions like DOF or Lucky's dll or whatsoever and build it up from there and test every step and see at what time it is going wrong. (if the new build has the same problem). Will report back but can take a while as I'm not at my cab for the next 3,5 weeks but will come back to you, thank you for the support!
  12. Thanks for testing. I did not have freezy's extention as I am told that it has no benefit when you use a pin2dmd-display. Nevertheless I installed it, but I couldn't get the real pin2dmd to work, only the virtual dmd which was looking 'freezy's ' (other pixel-shape) so that worked. I did check the freezy's ini file to see if the pin2dmd was enabled but it was enabled by default. Then I wanted to revert back to the working standard situation and...now nothing works at all anymore. Time to do a total Windos X and VPX install......
  13. Wow...thank you guys for your help and the update. As I don't want to waste this thread (more then I already did) I started a new thread in the general tab, see 'rev4638 2nd start problems' in 'Pinmame development' thanks!
  14. **note** this thread is a continu from the official beta 3.2 thread as I didn't want to spoil it more with my findings and questions.** Reason for my postings in the official thread was that pinmame startin with the xx30 rev's and further on are having the problem that pinmame fully crashes when starting a rom. No warning, no sings...crash. This only happens when the external pin2dmd is active. Disabeling it and having the virtual display will run the rom's fine (so it's not a rom issue). Now....about this 4638 version (thanks guys for your help and very fast response) Something weird but I can reproduce the error now. Ok...here it is: after copying the new .dll into pinmame dir and running pinmame/test my test-rom works out very well. (TZ94CH) Pressing start gives the note in pinmame that it is running and the pin2dmd shows the TZ graphics. But.....running a 2nd time the rom (press stop and directly start) is impossible: a direct hard crash of pinmame back to Win10. Starting pinmame again and running the test won't help: a direct crash. Now....rebooting the PC (soft reboot is fine) and starting pinmame / test : everything fine the 1st time but 2nd time the same. And now something more interesting: For this TZ94CH rom I enabled the color option in the F3 game menu. I do not have full color for it but a nice white graphics to a black background . pal file (see attachment). When I rename the TZ94CH alt color directory (where the pal file is in) to a weird name so that pinmame can not find it and I restart pinmame/test: Everyting is fine! The color option in the game menu is still on but, as it can not find the directory it will display some kind of orange colors but stopping and running and stopping and running...everything is fine. So it seems to be a combination of using a .pal file and running pinmame a second time. ** Edit: tested an other ROM-with-pal-file (term3) : same problem: after reboot first time ok, 2nd time crash, only reboot will help. Thanks again so far! pin2dmd.pal
×
×
  • Create New...