Leaderboard

hey to everyone here nice to meet you all, cant wait to play some of those old classics that i used to play in the pub when i was younger

A little bit hacky, but more progress on the MfmeTools Extractor. Usually when right-clicking the left side of the layout to pull up the Properties window, we land straight on the first component (the background). This isn't always the case though, sometimes there might be a component like a checkbox there. So we must get back to the first component... I've added a large 'dummy test' lamp on the left of this Andy Capp layout I'm testing with, so we can test getting back to the first component. Here is the new window scraping code getting its first use, watching the component number change while clicking left, until it sees it has successfully reached the first component:

I’ve had the streak on a 02 £4.80 Grand National. It does seem anything v04 £6 don’t have the same profile, likely due to the enriched period being outlawed. I’m still going to keep at these and make the line wins free, shame about those forced streaks as it was one of the pitfalls of doing the lines, giving it an element of jeopardy Still it’s kind of fun to experience the trick on the games we don’t have early software for. J

Nice to see you are feeling up to carrying on with this, I only wish I knew what you’re going on about way above my head . We do all appreciate the hard work and commitment you put into this .

A small tech update on this project I have the general custom window scraping written (so it can grab the RGB value of specific pixels from the various MFME windows). Currently working on integrating that functional scraping code into MFME Tools - the first use of which will be to simply scrape the component number from the properties window (so we can 'rewind' back to component #1 after getting into Properties - this is how I found it best to do under the Arcade Sim Layout Scraper). The plan is that this custom scraping code, whilst also being complete independent of Unity (MFME Tools is written in C# as a Windows executable), will also provide missing stability, as the scraping system I used under Unity to drive Arcade Sim and also the layout extraction, had a tendency to crash! So hopefully when this is fully developed, I can leave it with a massive batch of DX layouts, and it will not crash even after many hours of extracting... Commits are all here for those interested in the code, this is all open source: https://github.com/johnparker007/Oasis/commits/main/