DJRobX

VIP Class
  • Content count

    412
  • Joined

  • Last visited

  • Days Won

    42

DJRobX last won the day on January 23

DJRobX had the most liked content!

2 Followers

About DJRobX

  • Rank
    Advanced Member
  • Birthday 11/13/1974

Profile Information

  • Gender
    Male
  • Location
    Valencia, CA

Recent Profile Visitors

537 profile views
  1. So I found out what was going on with the "No DMD device driver found" error I was seeing. I found that I am not able to load DMDDevice.dll if the table script loads VPinMame.Controller directly, it would only work through B2S.Server. The LoadLibraryEx call in VPM currently limits the DLL search to only the specified folder. So it would find the DMDDevice.dll, but then it couldn't locate a DLL it depended on (mscoree.dll). If loading through B2S, it - also being a .NET dll - loads this DLL first, so it bypasses the issue. Changing the LoadLibraryEx line to: hModule = LoadLibraryEx(filename,NULL,LOAD_LIBRARY_SEARCH_DLL_LOAD_DIR | LOAD_LIBRARY_SEARCH_DEFAULT_DIRS); appears to take care of it and allows me to load VPM directly with the external DMD working. I committed the fix to Carny's repo.
  2. Need more details. Plunger has nothing to do with VPM. . When you say the plunger doesn't work what do you mean exactly? Is the ball in the shooter lane but you can't launch it? Do you have a mechanical plunger? If so what type? If NOT you may have a game controller plugged in that VP thinks is a plunger.
  3. @freezy If you add: this.ShowActivated = false; to the VirtualDMD() constructor in VirtualDMD.xaml.cs, it stops the focus problems
  4. Note that HyperPin+FPlaunch doesn't currently support VPX. You have to rename VPX's to VPTs. There's a file called VPExeTables.txt that you can use to tell FPLaunch which version of VP to use for a VPX file. If you're new to virtual pinball you might consider PinballX instead. It's newer, more supported, and easier to set up.
  5. Do you have the latest FPLaunch installed? I think FPLaunch has its own log also.
  6. Some people have reported minor performance issues with that build. It works fine for me though. If it's working for you, do feel free to keep using it as it appears to fix the crashing bug. It's otherwise based on the latest code. Once VPX dev gets around to starting the 1..3 cycle you can switch to theirs as it will also have a similar fix in place.
  7. I'm really glad you reported the crashing problem. It was just obscure enough that I would have assumed my cab was unstable or something like that. And having to play Metallica LE so much trying to reproduce it really sucked. I'll have to keep testing this update to make sure there are no other bugs ...
  8. That super-slow frames slowdown with non-JIT LE tables is an IRQ timing problem. Once that happens the LE lights/GI will stop also. TWD LE is the most sensitive to it. It's because the non-JIT code doesn't check for IRQ events as frequently and the serial interface freezes. That's the reason I spent so much time debugging MJR's the JIT implementation to make it work for SAM - checking to see if an IRQ triggered after every memory write slows things way down. JIT was the only way to keep acceptable performance while emulating the serial port.
  9. If I load Avatar (avr_110) from VPX, I get "No DMD device driver found". Doesn't matter if there's a PAL file or not. It's the only table that does this, I can switch to a different table and it loads fine. No log is generated. Same happens on two machines. Weird... *Edit* has something to do with the way the VPM controller is loaded. If I force ccontroller to 3 (B2S) instead of trying to use ccontroller.txt, it loads OK. Still weird, but now I know how to work around that. Does anyone else have focus problems? I never really noticed this because I was mostly using VPX tables in true fullscreen, but VP9 tables load and the virtual DMD is stealing focus. I have to alt-tab to the table to play them.
  10. 8GB Should be plenty. I just tried FGY color. Works fine with JIT on on both my cab and my laptop. JIT does use more memory than non-JIT, but if you have over 4GB it shouldn't be an issue. If you guys are using anti-virus make sure that your Visual PInball folder is excluded. Also if you can grab the crash.txt (it'll be in your tables folder) and share the contents of that it may be helpful.
  11. I'll try FG, I haven't gotten to that one yet. I'm not sure what's going on with your TWD, my Cleland LE ROM works fine with JIT + pal file. Which modified ROM are you using? Jesper - How much RAM does your pinball machine have?
  12. Don't have a way to test anything other than your virtual DMD driver, but I would think it almost has to be on the VPM side. I am looking into it.
  13. A-ha! You're right. My cab had a VPM from around the same time as the official VPM release. I ran it with a fresh build and now the palette is correct. So now just have the segmented display issue mentioned in the previous post. Thanks!
  14. It's strictly a memory thing, as long as you have more than 4gb of memory you really shouldn't be running into crashes post reboot. Share the crash.txt file and maybe that will give me more of a hint as to what's going on. I noticed something else weird about Freezy's virtual DMDDevice. More recent updates have segmented displays showing dotted output now, however, these result in strange MAME behavior. I noticed it on Taxi first, the Taxi ROM sometimes screeches and beeps particularly if you delete the NVRam file. The game sometimes starts and works OK though, if you get past that. Then I tried some early 80's pins like Mata Hari... The ROM would seem to crash and restart over and over, the game wasn't playable. Just switching from ShowPinDMD=0 and ShowWinDMD=1 makes everything go back to normal. It only seems to be a problem for games with segmented output, all the dot matrix games seem to work beautifully. So it seems like something really bad is happening for segmented output. I can't imagine what would have THAT effect though!
  15. Yep, the one in that zip of Lucky's palette files. The other colors (red & blue) are coming through. Its just the score that's in orange, which I"m pretty sure is coming from VPM default. I used to have a brighter color set for VPM default, before I flushed back to default values, and that showed through at least with the old DLL. TWD LE with Cleland audio works fine for me, with Lucky's Pin2dmd.pal. It has a white->yellow->brownish palette that looks pretty nice. Haven't seen any crashes, but do remember that the TWD table is very sensitive to memory fragmentation issues.