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

grunger106

Members
  • Content Count

    47
  • Joined

  • Last visited

Everything posted by grunger106

  1. I knew I'd had this issue before and then fixed it, and I remember doing this a few years ago pretty sure you linked your VPF post on a thread on MB Mystery solved. Thanks!!
  2. To be clear from my testing I see the following: Table + Script - Latest from VPU (2.0) PROC+Assets from 01/2018 Result: 3 balls where there should be(Certainly in Gold Mine MB + Last Call) Running the script to download the latest assets on another PC then copying and dropping those in place of \CactusCanyon in the gamecode folder, results in 2 balls in GoldMine and 1 ball in last call. Perhaps I need to update Python itself? (When I was taking about PROC previously I meant Python)
  3. The only thing I've not investigated is the version of PROC The one I'm running will be a similar era to my working game code, does that need updating along with the newer assets? How do you check the PROC version? If I can help test anything when real-life allows the time just shoot me a message
  4. Ok, I've done a little testing. Tried @luvthatapex's table with the same result, so it's not the table. I then reverted my gamecode to what I had before (dated 01/2018) and I now have 3 ball multiballs, but I guess with older assets
  5. @luvthatapex I've tried that script on the table/proc setup I've got and I have and don't see the same result. I'm 97% I had this working at some point, I'd be interested to try the actual table you have rather than just the script It was a few years back, so my memory is pretty hazy, but I'm sure this was an issue and then it got solved.... I did update my tables to the ones here from what I had, and the file sizes were slightly different as I recall, I assumed I was going from the one I had to the latest but it may be I went backwards..... Edit: nope - I restored my previous one from backup and same behaviour, I'll try reverting my proc gamecode tomorrow....
  6. Definitely seeing this behaviour GMM - 2 ball, it seems to know that - it ejects two balls, but if you loose one you then get the restart prompt, so it is aware there are two and not assuming there are three Not sure if this is normal but when trying to light the locks the goldmine moves back down again after a period of time where as in normal CC I'm pretty sure it stays up after the first hit (but this could be a feature in CCC) Last Call - just one ball ejected.
  7. Pretty sure I'm seeing this too and I've been down a similar path - I'm 90% sure last call was a two ball before I updated the code a few weeks back and I'm pretty sure it's one ball after dropping the new assets in. I do have my original install (the whole P-ROC structure) saved as was though, so I can certainly check what I had when it was working and what I've got now in terms of timestamps. I'll check it out later and get back to you.....
  8. No problems as far as I know, no errors on startup - pretty sure its Python 2.7, so maybe I did this later than I thought, 2018 seems like a long time ago now! As my cab isn't connected to any network, and was feeling lazy about digging out a long enough cable and getting at the NIC I had a read through the batch file and I can see what it does, so I thought I'd see if I could get the assets on one machine and then shunt them over to the cab on a flashdrive What I actually did in the end was run the install CCC batch on my workstation let it grab the assets and then moved that folder over to my cab, backed up the user-settings yaml, renamed the existing game directory, dropped in the new one downloaded and dropped my settings file back over the top. And yep I noticed the new script in your description, so I replaced the current scripts on both tables with that (setting the PROC flag obviously on CCC) All seems to be working fine One further question, is there any way to get 100% coverage of the DMD monitor - I've got it positioned on the DMD monitor (3 screen cab) and the x/y set so its in the middle with a pixel size of 9, which is as good as I could ever get, but the result is it pretty much fills the x axis, but there is a gap above and below it If I increase the pixel size it over hangs in the x axis. I've seen people where they do seem to have the DMD fully used, but they may be using Pin2DMD and a real DMD of course.
  9. Yeah would have been the first one Ninuzzu released way back when, I've updated the table since, but not the code. I'll grab 3.4 and run the batch Thanks
  10. I've had CCC working happily for a few years now and it works great, what do I need to do to just update the assets/code (I'm assuming i don't need to upgrade the PROC instance?) Just grab the 3.4 package re-run the Install CCC batch file?
  11. Is there somewhere to watch the progress? FS is the only VP9/PM5 table I have left, love the game
  12. Anyone else notice chattering flippers on the newest BOP with this release?
  13. Found the source of my stutter - The table overrides the VSync options to off by default. Changed that to -1 so it respects the global settings in VPX and now its a smooth as butter, Edit: I'm talking about MET LE by the way!
  14. Just had a crash to desktop playing fren's Met Pro.... first time ever had it crash in play Shooting a right orbit if that's of any help
  15. Had a few games on this - looks awesome. No crashes, but the ball movement is slightly jerky when rolling down the playfield and I have very high CPU usage in comparison to other tables. 90%+ load on this, and less than 40% on Fren's orginial version Tried the PM DB2S and the Pro to see if that made any difference Looks like there is a ball in a kicker under the apron? (I saw while the flashers were going off on multiball start) Specs: i3 (Sandybridge Gen) 3.1Ghz 8GB RAM GTX 760 2GB SSD running VPX 10.2.1, VPM 2.8 (B02) and B2S 1.6.02
  16. Out of interest how many bugs are we looking at.... I'm sure the foundation will be solid as it's one of yours! I've been meaning to actually have a play with VPX building and thought one of these might be a good starting point to look at? Taking on a full table would be too much, be looking at a semi-working one might be better (Or maybe I'm wrong?)
  17. I've checked I'm on the latest (Dec) VPinMame, which I wasn't but am now - but that's not made any difference. The top post behaves exactly the same in the VPX release, so that's 100% a ROM based issue (or 'feature') as you said For the testing of the ROM emulation speed I was going to try a few older ROMs, but I can't find any of the earlier ROMS? MET_164 is on here and on Sternpinball.com, but a search of the downloads here doesn't show anything older? Or I am I being blind?
  18. Cool - makes sense The grave markers are a pain to test - that mode is a bastard to start with the best will in the world! You might be right about the ROM being out of sync actually - I do rememeber thinking the ROM reaction to sparky hits seemed a bit delayed (not the model shaking - just the ROM callout) and I bet the sparky multiball magnet is on for longer than the grave marker one. Would also explain why a really slow orbit shot allows the sparky post work correctly like you say Question is can I do anything about it? I'm using the current ROM from stern's site and re-packed as normal, wonder if its just the new ROM (IIRC the table was built around one of the older ROMs?) Pretty sure I'm on the lastest PinMAME, but I'll double check that. Machine is i3 3.3Ghz/8GB/660, so I would suspect an emulation issue rather than a lack of raw grunt Anyone else noticing this?
  19. Hey Vette Awesome table, I've put in a load of games over the last week. Few issues I've noticed (and some of them could be as designed!) A shot to the captive balls seems to 9/10 bounce into the snake (after hitting the balls) Quite often a direct shot into the snake bounces out - like there is a post in its mouth (is there?) Orbit shots appear to be blocked by the post behind sparky (unless the shot is really slow up the left orbit - then it seems to drop) so all the left orbits bounce back and all the right orbits end up in the pops. It does drop OK if you go for the super skill shot though. (Is this by design now? - maybe they've changed the code - never played 161 on a real machine) This also happens on the VPX table by Fren, so it looks ROM based? After completeing the grave markers the magnet doesn't seem to energize and start the mode? (All graves down and hit the cross a couple of times, arrow flashing but it doesn't seem to register the hit) However, I have slightly altered the Y scale of the table as I have a 16:10 screen - am I likely to have screwed some of this up by making that change? Great table though ​
  20. Wish you'd asked yesterday! - I had my head inside a Spiderman for the better part of 2 hours yesterday afternoon...... But I'm not with the machine any longer - its back on site.​
  21. Me too - dealing with ramps, and how the script/rom calls are linked would be my next questions
  22. Thanks AL - I'll give that a try Also - I've followed 85Vetts instructions and managed to get my first light lined up - I now have a totally unjustified sense of pride! Thank you for writing such clear instructions
  23. DJRobX explained the ROM was firing the post up and down at the same time and suggested using a 'latch' He posted a code extract in the other thread, but I'm not quite sure what do with it! Also I'm pretty sure Groni posted this one with permission to mod, so if there is one with working mini-playfield lights I'd love a copy, and I think it would be OK to upload here?
  24. @KoolyWiz I have, but I'm not in front of it right now. I just upped the Y scaling slightly though, plays fine.
×
×
  • Create New...