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

Dazz

Administrators
  • Content Count

    1,296
  • Joined

  • Last visited

  • Days Won

    99

Everything posted by Dazz

  1. Dazz

    Where have all the roms gone?

    The ROM's section is back up. Gottlieb ROM's have been removed. We did not get a C&D like VPF may have, but I removed them as I don't want to deal with it.
  2. Dazz

    Hi everyone

    ROM downloads are disabled for right now.
  3. Ok, so I've never actually completed a VP build before so take this thread with a grain of salt.... If anyone else is working on this feel free to continue with your build as I'm not making any promises to complete this. I'm going to work on this as much as I can, but I'm not an artist nor a coder, so no promises. If anyone would like to work with me on this, particularly with coding and lighting please let me know. I started building this yesterday so I'm not that far along yet.
  4. I've been trying to get PROC running for a while now. Took a break from it, but trying to get back to it. I just did a fresh un-install and re-install of PROC using the new installer. Everything appeared to have run fine without error. I do run VP from another drive (D:) other than my C: drive. Tables are all on D: drive. Error when running CCC via VP. Error running Evil Dead.
  5. Dazz

    SAMBuild3.2 beta thread

    Thanks. Someone was able to send it to me... Now running into the same thing with Shrek, World Poker and Wheel of Fortune. I'm not sure what changed, but my roms for these games were working... Now when I check them in PinMAME they say Actual = 0 meaning the filesize in the zip is 0 bytes.
  6. Dazz

    SAMBuild3.2 beta thread

    Has there been any changes with Family Guy lately? Been trying to run fg_1200af but getting terminated. I've tried everything I can think of and keep getting same termination error. Even downloaded new rom from Stern and tries, getting same error. Rom name inside of zip matches what PinMAME is expecting.
  7. I decided to fire up Pinball Browser and start messing around with doing my first colorization. Decided to tackle the Stern logo first. Deleted the pinball image, drew in Slimer and slimed the logo. I know it's not much, but it's a start to learning how to do this.
  8. I received a message from the owners of ColorDMD regarding the use of dumps from ColorDMD for use in Pin2DMD colorization. It was determined long ago that we would not support anything that infringes on ColorDMD. So far they have been really polite regarding our projects. Please; lets not poke the bear any further.
  9. I have friends that are building real CCC machines and I'd like to have it in VP. Has anyone gotten PROC and VP to live together nicely? If so do we have a Cactus Canyon Continued build?
  10. Dazz

    DMD Extensions v1.7.0 released

    Well, it seems that a full disk format and re-install of Win10, VP, VPM, etc seems to have done the trick. Thanks guys.
  11. Dazz

    DMD Extensions v1.7.0 released

    I think over the years something may have gotten corrupted... I'm just going to backup my main drive, do a complete format of the OS drive and do a fresh install of everything.
  12. Dazz

    DMD Extensions v1.7.0 released

    Yes, all test are done directly on the cabinet. It's currently 100f out and I'd be sweating balls out in the garage. Only using network to grab screen captures and verify file locations. There is no log being created in Visual Pinball, Visual Pinball/Tables, VPinMAME.
  13. Dazz

    DMD Extensions v1.7.0 released

    D:\Visual Pinball D:\Visual Pinball\Tables D:\VPinMAME D:\VPinMAME\VPinMAME.dll D:\VPinMAME\DmdDevice.dll D:\VPinMAME\DmdDevice.ini My Pin2DMD works fine using v2.55 and the supplied dll from Lucky's GIT. I can drop Lucky's dll right into my PinMAME folder, overwrite whatever dll is there and the DMD will work fine. If I drop in any of Freezy's dlls (1.6 or 1.7) they do not work and I've never been able to get them to work in the past. If I run PinMAME Setup.exe, Test a game, ex 24, Start, i see both the PinMAME DMD and Freezy's Virtual DMD, but it closes almost immediately. If I launch a VP table from VPX (any version), the virtual dmd loads and immediately closes and VPX stops responding/freezes/crashes w/no error. PinMAME folder Visual Pinball folder
  14. Dazz

    DMD Extensions v1.7.0 released

    Am I the only one that runs a multiple drive/partition setup? I have my OS on C drive, and VP/VPM, etc on D. I haven't tested yet, but it could be possible that Freezy's DLL isn't working for me as I have it and VP/VPM on my D drive instead of C?
  15. Dazz

    DMD Extensions v1.7.0 released

    No log is being created...
  16. Dazz

    DMD Extensions v1.7.0 released

    dmddevice.ini is posted above. I don't recall which driver I'm using, but I think it's winusb... I'll have to check in the morning.
  17. Dazz

    DMD Extensions v1.7.0 released

    I was looking for the log earlier, but it looks like a log isn't being created. I am not running from a protected folder and have tried via Pinmame Setup and VP. There is nothing with dmddevice on my C (Windows) drive. D:\VPinMAME > <target name="console" xsi:type="ColoredConsole" useDefaultRowHighlightingRules="false" layout="${pad:padding=4:inner=[${threadid}]} ${date} ${pad:padding=5:inner=${level:uppercase=true}} | ${message} ${exception:format=ToString}"> <highlight-row condition="level == LogLevel.Trace" foregroundColor="DarkGray" /> <highlight-row condition="level == LogLevel.Debug" foregroundColor="DarkGray" /> <highlight-row condition="level == LogLevel.Info" foregroundColor="Gray" /> <highlight-row condition="level == LogLevel.Warn" foregroundColor="Yellow" /> <highlight-row condition="level == LogLevel.Error" foregroundColor="Red" /> <highlight-row condition="level == LogLevel.Fatal" foregroundColor="Magenta" /> </target> <target xsi:type="File" name="file" fileName="DmdDevice.log" layout="${pad:padding=4:inner=[${threadid}]} ${date} ${pad:padding=5:inner=${level:uppercase=true}} | ${message} ${exception:format=ToString}" replaceFileContentsOnEachWrite="false" deleteOldFileOnStartup="true"/> </targets> <rules> <logger name="" minlevel="info" writeTo="console" /> <logger name="" minlevel="info" writeTo="file" /> </rules> </nlog>
  18. Dazz

    DMD Extensions v1.7.0 released

    This is what my ini has: > [global] ; how to downscale SEGA 192x64 pixel games to smaller displays: fit, fill or stretch resize = fit ; flips the image horizontally fliphorizontally = false ; flips the image vertically flipvertically = false ; enable or disable frame-by-frame colorization (inactive in VPX bundle) colorize = true ; a DMD that renders with nice dots on a computer monitor [virtualdmd] enabled = true ; virtual dmd stays on top of all other windows stayontop = true ; hide the resize grip hidegrip = false ; ignore the aspect ratio of the rendered dots when resizing ignorear = false ; use VPM's registry values when positioning the virtual dmd useregistry = false ; x-axis of the window position left = 0 ; y-axis of the window position top = 0 ; width of the dmd in monitor pixels width = 1024 ; height of the dmd in monitor pixels height = 256 ; scale the dot size (set to 0.8 for same size as pre-1.6.0) dotsize = 1.0 [pindmd1] ; if false, doesn't bother looking for a pinDMD1 enabled = false [pindmd2] ; if false, doesn't bother looking for a pinDMD2 enabled = false [pindmd3] ; if false, doesn't bother looking for a pinDMD3 enabled = false ; COM port, e.g. COM3 port = [pin2dmd] ; if false, doesn't bother looking for a PIN2DMD enabled = true [browserstream] ; if enabled, stream to your browser in your LAN enabled = false port = 9090 [vpdbstream] ; if enabled, stream DMD to https://test.vpdb.io/live enabled = false endpoint = https://api-test.vpdb.io/ [video] ; if enabled, writes frames to an .avi file enabled = false ; path to folder or .avi file. if folder, gamename.avi is used. path = [pinup] ; if enabled, send frames to PinUP. enabled = true When running Freezy's 1.7.0 DLL the game will load, virtual DMD will show (pin2dmd display is black), but then VPM crashes and VP exits completely. If I simply replace Freezy's DLL with the dmddevice.dll from the Pin2DMD github and everything works fine. I've ensured that I'm running Pin2DMD v2.55 firmware also tried v2.50. Ensured that PinMAME is updated, SAM dll is updated, VPX 10.5, etc. I do have the dmddevice.dll also in. The dll needs to be in these folders in order for these games to work. D:\Visual Pinball\XDMD D:\Visual Pinball\VPinSPA
  19. Dazz

    DMD Extensions v1.7.0 released

    The only dmddevice.dlls I have are these. None of which are on my OS drive.
  20. Dazz

    DMD Extensions v1.7.0 released

    PinMAME games will not display on my Pin2DMD when using Freezy's DLL.
  21. Dazz

    DMD Extensions v1.7.0 released

    I seem to have an issue with Freezy's DLL displaying PinMAME on Pin2DMD. This happened with previous versions as well, but figured I'd try to update to 1.7.0. I'm currently using Pin2DMD firmware 2.55.
  22. I've been trying to get PinUp Player to work, but it crashes PinMAME when using the dmddevice.dll that is supposed to be unified. I've narrowed the crashing down to using the most recent Pin2DMD firmware v2.51 with the unified dmddevice.dll from PinUP. I guess I could downgrade firmware, but don't really want to loose the more enhanced color options.
  23. You use the .spk from Stern and then have to extract the image.bin from it. This is the only frame I've done so far... I'm using Pinball Browser right now. So, I'm not quite sure what any of this means yet. I haven't had to create/use a new palette, but it looks like I will need one for the next scene.
  24. Yeah, after clicking out of the R6043 error the code runs and the game/dmd load. I'll try running Ninuzzu again to see if it will help. Ok, I was able to fix it... had to remove a path from my windows environment.
  25. I went through and un-installed the install from Ninuzzu. Installed using Horsey method, got errors and unable to launch CCC... Overwrote install with Ninuzzu's and able to run CCC and ED, but I get the R6034 error. According to mjocean this error should have been resolved with an updated register_vpcom that was dated 01.28.17.
×