Jump to content


Supporting Member
  • Content Count

  • Joined

  • Last visited

  • Days Won


slippifishi last won the day on October 7 2020

slippifishi had the most liked content!

Community Reputation

501 Excellent


About slippifishi

  • Rank
    Advanced Member

Profile Information

  • Location
  • Interests

Recent Profile Visitors

1,859 profile views
  1. slippifishi


  2. Is it just an editor limitation? I do have a GB here and I have wondered about pulling the ColorDMD out so I can try having a go myself, it's all a bit pink and purple and I would love to give it some polish, though I'm not sure how easily Ican convert my desktop pin2dmd into something I can use with the machine. I looked very briefly - spent like 1 minute - looking at pinball browser, but I don't think it would provide the same freedoms to colour as the approach I am used to using the editor
  3. SOME credit dot states are covered in some areas, but probably only whole numbers. Freeplay should be working everywhere, but freeplayDOT definitely won't. The easy solution - fix your dot! "easy" The harder solution - get me some specific rom dumps. I was using VPX (and Wob) to generate my dumps, and capturing all the dot states was not so easy. If you are willing and able to do some rom dumping then I can add some triggers, but please note that there is a little bit more than just 1 frame needed; as the score is displayed, if no switches are hit then eventually the bottom o
  4. You might also try generating a small raw dump at https://playfield.dev/ - these definitely work with the editor and might help pin down if it's something related to the dumping process you are using. There are some instructions on the github page https://github.com/neophob/wpc-emu
  5. The forum and download sections here are probably your best bet, you can also try @Audiofreaks site http://pin-display.ch which will let you contact some of the artists directly. @dzorbas also maintains a listing of finished projects at https://sites.google.com/view/pin2dmd/colour-files though almost all the links will bring you back here
  6. I have personally never used the "create key frame after cutting" action, but you can use the bookmark list to easily go back to the start of that scene later by selecting it from the drop down - the bookmark name will track the name you give the scene. I think this is better, often you may cut a scene for colouring and not actually know how it will be triggered yet - maybe a single trigger aligned with the start? Or maybe it will have to be cut up; either way it will be easier to manage that cut up (if needed) if there isn't already an existing trigger associated to that first frame. Also, wh
  7. Nope, this is EXACTLY how I did my first working project. Once you get that static title screen working, that's when the bug bites...
  8. I think the raw files are literally the raw bytes of frame data; the text files are a textual representation of the same data, but this takes up more space. Hence the TXT files can become massive, and that is why they are gzipped. I come from a virtual development platform, so things are definitely different in that respect and I have never used my pin2dmd to dump the frames so can't answer your question on how to stop dumping, but I will say this... I prefer the TXT format. I can manually edit the text dumps and cut and patch a file together with hard to find scenes that I maybe see
  9. Just use the raw file raw! No zipping needed!
  10. You are correct that the same project sources generate the output for both virtual and real pinball. Most, if not all, of the authors of the projects you describe are willing and able to create the files for real pinball, they just ask for a donation up front - you have to contact them either by posting in the forum thread, or through PM, or using a site like pin-display.ch to reach out to them. These projects do take a significant amount of time, if they are done properly - literally hundreds of hours of sometimes monotonous, occasionally boring, always challenging and often frustrating
  11. @lucky1 I'm afraid I didn't look at LCM mode yet; the video mode in Getaway is so complex, I think I want to try it on a simpler scene before I try anything quite that hectic, but there might be something in my next project I can try it with. @sprudeldudel I tried running the L-2 rom in VPX but I am not experiencing any noticeable problems in those scenes, though I appreciate VPX is no substitute for the real thing ? I also checked against the Nov 2019 sources and I am using the same triggers/didn't retrigger those scenes (though both were recoloured/touched up). I will admit that the tri
  12. Sorry lucky - as soon as I posted that I realised you were probably the wrong person but figure you might be interested. I raised a new issue on freezy github. I have just uploaded some new files - sources, VPIN and REAL - to fix the following: No more hitchhiker ghost hair on ball 1 lock sequence Match sequence cop car palette adjusted Freezy 1.8.0 compatible (all replace sequence scenes have at least 2 frames) Have fun! VPIN FILES: https://drive.google.com/drive/folders/1SG6htoGkxMJ7UzaJNafeHpOICk9A0-Ob?usp=sharing REAL PIN FILES: https://drive.google
  13. Hah OK, I have figured it out - @lucky1 FYI! I downloaded freezy 1.8.0 and was experiencing the same crash on the title screen. The title screen was using a "Replace Sequence" scene 1 frame long - I used "Replace Sequence" as I intended it as a backup in the event the chequered flag transition didn't fire because of any timing issues with the triggers/hashes. I tried deleting the trigger and the attract sequence would run until the Williams logo - again, another 1 frame "Replace Sequence" scene. DMDDeviceLog showed "System.NullReferenceException: Object reference not set to an instance of
  14. Ahhh if the ghost hair and mismatched cop are the worst you can find, then I was successful! I have made a note and will try and sort those out when I'm fixing the above vpin issues, will drop a note here when done.
  15. OK at a guess you are using Freezy's DLL and this is a result of me using some scene types that aren't supported - that title screen is one of the few places I used them. Lucky had mentioned this a few pages back in this thread, but I didn't think that restriction applied to the types I used (ColorMask Sequence and Replace Sequence) as these just feel like extensions of the other main types. My VPIN cab with pindmd3 isn't running at the minute so I have just been testing on a pin2dmd running lucky's DLL - perhaps I will adjust my testing approach. As such, the VPIN files I posted above sh
  • Create New...