The first thing I have to say is well done on the docs because pyprocgame manual is not good compared to this already. It was a steep curve having been new to Python, at times very confusing , even though the simplest thing is staring you in the face half the time.

I was racking my brains for ages learning that in 2 months on/off. It's definitely not good for the people that don't have the time I had to do that.

While I'm no way near a master at python/pyprocgame I have & can finish a whole tables rules now, which is enough for me, that's all I really wanted. Basically to jump in, do this, do that, use pre made modules (which I do a lot of), currently sort of not possible unless you're prepared to put the hours in to try & fully understand it all. Looking back it hasn't been all that bad but the time it's taken is.

Can/will you use some more advanced gfx libraries/hooks that can be used out of the box?

Let's see the price and let's see if it comes with a 8x8 switch matrix. The P-ROC bits I need for the whole custom game I have going is $942.82.

Unfortunately this is a problem, there is no real "dummies guide" to follow. There's not really a good base like they're trying to achieve here.

There is no step by step to make you feel comfortable to learn it. Instead you have to ask questions, you have to search, you have to pester people, you have to go through existing code, which half the time felt like spaghetti to me unless the main code is mainly in one file like JD.

I'm making it out to be the impossible? it wasn't so bad in the end and it's actually pretty easy once you start to click, but not sure it was realized how much of a curve it could be and expect you to dedicate a lot of time developing the same old things that should be standard, instead of developing rules & your game.

Did no-one set you up for VP yet? :/

I thought you wanted to run pyprocgame with VP.

Love it. Just give me at least 64 switches that doesn't cost the same price as one p3-roc board and I'm going FAST.

With the VP thing, surely you can use Micheal's existing edited bridge?

I know it's early but would like to know if I could use all these modes I've written for pyprocgame to use with a fast. It's not too much trouble anyway I suppose , it could all be re written as you're using Python here too.

Nice.

I think he has his own for that...

Well, this is something I'm going to have to admit that I obviously never truly understood. Why it's not clear to me I still don't know, is it just "easier" to use a few switch boards than direct off original p-roc?

This basically cuts £140 off my estimate for 64 switch.

Don't take this the wrong way mate but it's taken you 2-3 years, maybe more and you've had to resort to building off a pre-made table.

I know you wouldn't of spent all of that time learning it. It's just an fine example of how difficult it could be without proper docs/walkthrough/clear code base.

Portable pins, could be onto something there...

Very nice! Great idea, thanks for sharing pics. What's the length?

If you went P3-Roc, 4 switch boards, 2x power driver, 8x8 lamp. = $815, an added power supply bumps up a bit maybe. You may not even need all that , you may not need 2 power drivers and you don't need to have the extra switch boards.

Probably what also has happened there was converting from my currency back again, so apologies for the confusion, but is close enough. You can see that's where the ghost $2.82 has come from.

Wouldn't take it to heart, you wanted a discount at one point. The only real "bashing" has come from people that haven't used it & have wanted/tried to.

Save yourself a bit of typing just doing, self.game.score(100)

Aaron, have you made or is there a thread for all FAST questions? Not trying to say , "get your own thread". I'm interested to know whether you will support Data East , Sys 11 out of box?

Presuming a yes on the sys 11, because of FH.

Thanks, I see, some just used sys 11 sound. Had to deal with the A/C before. Blatantly trying to get away with not giving you $

Felt the same way with pyprocgame where I should've done some noobie guides as I was learning. Just couldn't be bothered in the end, I feel that most people must've felt the same way. But anyway, saying that, it may be a decent idea to work on a table and video document it as I go.

Well, what you've just mentioned there would be good for me at some point.

I've been learning all pyprocgame/python through VP & desktop cmd running the main() on each mode.

Finished a game and about 20% through the next one. That first game would need going over again if it was to go on the real table though. Only because of the relay stuff on DEast, I wouldn't trust it to work 100%, even though it "should" work, timings etc.

I was trying to say I'd create guides for pyprocgame for others so they don't have to go through hassle of searching for answers, deciphering. Drifting away from MPF again now though, I would use both.