356 replies to this topic

[jasonsmith]

1.5 is awesome fuzzel. Thanks for all the updates. The wheel is much quicker now, I like that a lot. The backglass is much quicker too, actually it's now faster than the table image for me LOL. 

 

On VP tables only I'm getting the taskbar on a table exit. 

[fuzzel]

You're welcome...if you like 1.5 let's see how you will like 1.6 I have to make some tests and will release it later

Regardings your taskbar issue: I can't reproduce that on my cab. PinSelect hides the taskbar on startup so it could be some FPLaunch issue on your system?!

Edited by fuzzel, 16 April 2013 - 08:13 PM.

[jasonsmith]

Sorry that was my fault, I forgot to change the HP settings back to pinselect.exe 

 

Now that I have been using this more and more I've noticed that PS has made most of my ledwiz induced micro stutter go away in VP. I was getting it quite bad as I have a weak PC but this has almost made it completely go away, on a few tables so far anyway. Great News!!

Edited by jasonsmith, 16 April 2013 - 08:33 PM.

[chepas]

Actually Jason I'm not surprised by that. Sometimes VP tables will run better without HP in background, depending on how demanding the table is.

[bent98]

Does this help Win XP performance as well?

[fuzzel]

bent89: can't tell you that, but because PinSelect needs much less memory than HP it could be faster on WinXP as well.

 

Btw: check post #1 I've updated v1.6

[open6l]

Thanks for the offset fix - works perfectly now! This gets better and better with each release.

[open6l]

hmm - bar texture isn't displaying anymore for me.

 

edit: works if I rename it from ps_barTexture.png to just barTexture.png.

Edited by open6l, 16 April 2013 - 10:42 PM.

[fuzzel]

ups thanks open6l. PinSelect updated to 1.61

[nebrunner]

Fuzzel thanks for your work on this. For you guys who have dived in and are trying this out now in beta form, have you seen any focus issues or are they completely fixed?

[jasonsmith]

As long as you change the hyperpin exe line in the HP Settings ini file all is well focus wise. The focus is actually better due to the less overhead I guess. Just right now if you're going back and forth between this and HP you have to keep changing that line and sometimes you may forget 

 

Although the wheel speed was greatly increased it's still much slower to move around than HP because you can't "spin" the wheel and catch the table as it fly's by. Letter jumping and filtering is required to move about quickly. Now I only have 216 tables loaded so I'm kinda in the middle where scrolling through the tables isn't a big deal unless it's slow. Those with 500+ tables are probably filtering and letter jumping anyway as it would be next week before they got to Z. 

 

Table picker idea:

 

How about a Rolodex card stack type thing? Each card could have 3 or 5 tables on it. You can use the nudge buttons to rotate the back card to the front and then the flipper buttons to go left or right to high-lite the table you want. The cards could be stacked so you can see maybe half of the card below with a total of 3 cards visible including the card in focus. This way you can flip through 3 tables at a time and possibly see 9 tables in a go. A long press on something could still letter jump as well. 

 

Sorry for the crude drawing

 

Edited by jasonsmith, 17 April 2013 - 04:25 PM.

[fuzzel]

Nice idea, but wouldn't it hide too much from the playfield of the current table? I could shrink the icons a little bit more, but depending on how detailed the icons are designed it could be hard to identify tables?!

Another way could be to completely remove the playfield images and just show icons...

I would like to add more 'animation' to the wheel or implement some 'fly-by' style like HP has but all this isn't really working in GDI+ though So the whole drawing is more or less limited to static images especially

if you want to have some smooth animation. PinSelect wasn't designed for those features. I just did some simple and fast frontend for selecting tables on my cab. Now the project is public I understand that there are

others who want to replace HP but have a lot of tables to manage.

Perhaps I have to redo PinSelect with a graphics framework based on DirectX/OpenGL but all frameworks I could find don't have multiple monitor support. So if someone has an idea here, please step in

[jasonsmith]

I understand fuzzel, thanks for entertaining it anyway. I think like many I'm just a slightly frustrated Win7 HP user who was wishing it was more efficient. When playing a table in HP it feels like pulling a trailer with the brakes on. In this case all is smooth and fast. 

 

I certainly didn't wish for you to completely rethink how you're doing things, I know jack about building programs so I have no idea what frameworks mean or the implications of my suggestions. 

[fuzzel]

Hmm ok back to the drawingboard again ...but that will take some time for sure. As long as I don't have another idea you have to live with it

Edited by fuzzel, 17 April 2013 - 10:12 PM.

[Slydog43]

I'm working on my own version I call MyPinCab, its very similar to yours, but I think it is much faster.  I do use a SQLServer Database to drive the whole thing though.  I have a manager part that allow import/export of Hyperpin Databases.  I use it on my pincab since I needed someway to manage all my files.  It has some verification stuff so I know what files are missing and are extra (HyperPin acts weird when extra files are in the directories).  It doesn't use GDI so I think the speed is awesome.  It has a long way to go, but I hope to show off stuff by the end of the weekend.  I hope you don't mind me posting this here fuzzel.

[fuzzel]

That's cool. How do you render the images?

[blur]

I see that move to next table is done on key up

 

it would be better if wheels are rotated on key down (only wheels, pf and bg can be black), and then on key up - pf and bg are drawn? (like in hyperpin)

 

Is there a way to load keys from hyperpin's settings.ini?

[fuzzel]

Blur, you're right. I use a timer for detecting how long a key is pressed, and after the timeout I jump to the next letter. I thought about the same on how to handle the drawing, but

doing it that way you can't jump to the next letter anymore by pressing the flipper button for some seconds. Perhaps it's better to leave the letter jump option to extra buttons instead

of long pressing the flipper buttons? What you think about that?

 

PinSelect doesn't support the Settings.ini format, you have to define the keys in the PinSelect.exe.config file.

[chepas]

Sorry, should of tried this before as it only took 1 minute to download, install.

 

I'm finding your config a bit bohemium, haha. Especialy key values. Is there any reason why you didn't want to read the keys which are setup in the hyperpin.ini?

Is there a way to load keys from hyperpin's settings.ini?

 

Beat me to it

[fuzzel]

Yep the reason is simple: laziness With C# there is a very fast and easy way to handle your application configuration. Supporting the HP settings.ini file would mean to parse the textfile

and handle all formating problems you can run into. Of course it's not impossible but just annoying to implement