356 replies to this topic

[jasonsmith]

jasonsmith, did you check the readme how to change the font size and the position of the background image?

 

Clearly I failed to do that LOL. Sorry man. 

 

EDIT: Wow, that is awesome. I can't believe I didn't see the added settings at the bottom, I even looked at the file. 

Edited by jasonsmith, 23 April 2013 - 04:24 PM.

[ppsalzar]

Hello Fuzzle and all,

 

I am following very interested your development due to my Win7_64 installation, but since I am a newbie to VP I would still need a little hint on getting alle the puzzle together.

 

I understand that PS   is just a front end to allow me to select a table via a graphic interface.

 

PS then forwards parameters to FPlaunch which actually does the job of launching and closing all the many elements:

 

   VP , selected table, backglasses and animations  in various versions ( UVP, directb2s, B2s, ledwiz )

 

now my question:   how to set up VP scripts to  correctly set up a directb2s and B2S versions. 

I get it to work directly out of VP but not in combination with FPlaunch / PS. 

 

Is there anybody that can direct me to a thread or tutorial where I find the neccesarry details ?

I read that  FPlaunch wip 10 is the version to use.

Static Backglasses work perfect so far.  B2S tables also work but don't close.  directb2s i did not try yet

 

 

ppsalzar

Edited by ppsalzar, 23 April 2013 - 07:13 PM.

[open6l]

Do you have the latest FPLaunch installed? It's a separate install file. Latest version is 1.295 WIP 10

 

Hello Fuzzle and all,

 

I am following very interested your development due to my Win7_64 installation, but since I am a newbie to VP I would still need a little hint on getting alle the puzzle together.

 

I understand that PS   is just a front end to allow me to select a table via a graphic interface.

 

PS then forwards parameters to FPlaunch which actually does the job of launching and closing all the many elements:

 

   VP , selected table, backglasses and animations  in various versions ( UVP, directb2s, B2s, ledwiz )

 

now my question:   how to set up VP scripts to  correctly set up a directb2s and B2S versions. 

I get it to work directly out of VP but not in combination with FPlaunch / PS. 

 

Is there anybody that can direct me to a thread or tutorial where I find the neccesarry details ?

I read that  FPlaunch wip 10 is the version to use.

Static Backglasses work perfect so far.  B2S tables also work but don't close.  directb2s i did not try yet

 

 

ppsalzar

[fuzzel]

now my question:   how to set up VP scripts to  correctly set up a directb2s and B2S versions. 
I get it to work directly out of VP but not in combination with FPlaunch / PS. 
 
Is there anybody that can direct me to a thread or tutorial where I find the neccesarry details ?
I read that  FPlaunch wip 10 is the version to use.
Static Backglasses work perfect so far.  B2S tables also work but don't close.  directb2s i did not try yet
ppsalzar

did you register the db2s server first? you have run the register tool just once, after that you replace VPinMAME.Controller into
B2S.Server in the table script and finally you should use the same filename for the vpt and direct2bs file.

[jasonsmith]

Is there an attract mode or something similar in the works fuzzel? I tend to abandon my cab during the day, a different table showing up usually catches my attention and begs me to play it.

[fuzzel]

If I run it as admin I still get the same result:[img]http://i36.tinypic.com/2di22p3.jpg[/img]

hmm i don't have clue what's your problem there, i will release an update tomorrow where you can activate a debug mode which gives some error messages if images couldn't be losded, perhaps this will issolate your problem

Is there an attract mode or something similar in the works fuzzel? I tend to abandon my cab during the day, a different table showing up usually catches my attention and begs me to play it.

hehe I was thinking about that for some time now. I wasn't very happy with the attract mode in Hyperpin, because after some timeit selects a random table but I wanted to play the last table again, or the table next to it and had to search for it again. But maybe scrolling through the tables isn't a bad idea. What about a feature that you have to press let's say the start button to selectthe randomly showed table but every other button would jump back to the last played one?

[jasonsmith]

I think we should preserve the launching of a table with the enter key or the launch ball button just to keep things simple. I see what you're saying though and I agree that getting to the last played table is important, especially if it's your goal for the day or week or whatever. Often I'll be on the other side of the house and see the backglass of a table I haven't played in a while and I run over to launch the table. I like the random attract method as it digs deeper into the library of tables. If it's just scrolling say alphabetically then it may take hours to get through the whole library depending on time limits. 

 

1. How about your idea but backwards, say the start button becomes the "return" button while in table view mode and takes you back to the last played table and the launch button launches whatever is in front of you at the time. I think that is more consistent with what were all doing now. 

 

or

 

2. Maybe both flipper buttons on at the same time take you back to the last played table and everything else stays the same. Both flipper buttons are already associated to alternate functions within some roms, it seems natural that doing that in a front end would do something as well.

 

or

 

3. Would it be possible to show the last played table in the exit menu that we can just launch from wherever we happen to be without even going to it? If not in the exit menu maybe as the first highlight on the filter screen.   

 

 

I think I like #2 the best. 

[knucklehd]

I just wanted to say that this program is freaking awesome, I had just about given up hope and lost interest in my cab because of hyperpin slowness. (win 7 64, 3 monitor on ati 6870) if i unplug hdmi/dp adaptor from my tv prob seems to go away, but I'm not going back to two monitors.

 

Anyway, this is so fast it's hard to believe.

Initial problem when I started with ver 161, is that I don't use future tables yet, so i had a default profile in the folder and pinselect kept giving me weird errors. it took a few to figure it out.

I wonder since new version uses hyperpin settings.ini does it look at whether or not futurepin is true or false? Could save someone some grief in the future.

Keep up the great work this is really nice, and you can tell it will keep getting better and better.

 

Last thing i noticed it doesnt seem to always run ledclear.bat I notice my buttons still on after exit sometimes. Could be my setup.

 

Thanks again for your time and continued efforts on this project Sir(s).

Ken

[jasonsmith]

I can confirm that ledclear.bat isn't always being run as well. I have a shortcut on my desktop for that reason. 

[evilantal]

Hmmm... it seems I'm missing some setting

 

The table image + wheel is always displayed on my backglass leaving my playfield monitor empty. I've put the files in my Hyperpin directory. Hyperpin is working correctly, so I assumed (as it is using Hyperpin's settings) PinSelect would be displayed in the same way.

 

What am I missing?

[hotdp]

Sounds great with the "debug mode".

Any ETA on source release?

[fuzzel]

I hope I can release the messy code this weekend

[hotdp]

@fuzzel, I know how it feels. I am sure it is not as bad as you say ;-) Will it contain any comments?

I hope this project will involve and contain videos and stuff like that and be awesome.

[fuzzel]

Well the code could be much more structured. I started this project for my own and threw in more and more options/features.
I have already added some comments but don't expect too much.
Regarding video, this seems to be a really tough part. Basicly it's not a problem to play a video but to do the overlay with other graphics and support .f4v video files seems more or less impossible without using Flash.
I tried a lot possibilities playing videos but all options weren't really applicable.
Perhaps someone with more .NET experience can implement video support in the future, but up to now I won't add video support.

@evilantal, sounds like PS thinks your playfield is the 'Secondary' monitor.
The normal setup is as follows:
Playfield_Monitor = Primary
Backglass_Monitor = Secondary

Be sure that your playfield screen is the main screen (under Windows display no one) and the backglass screen is the second screen (under Windows display no two).

[pocketpal]

The table image + wheel is always displayed on my backglass leaving my playfield monitor empty. I've put the files in my Hyperpin directory. Hyperpin is working correctly, so I assumed (as it is using Hyperpin's settings) PinSelect would be displayed in the same way.

 

I finally gave PinSelect a go last night after reading about for several days, but I ran into this same problem.  The backglass image would appear on my backglass monitor for a split-second, and then the playfield image would display over it, with nothing but my Windows wallpaper on the playfield monitor.

 

@evilantal, sounds like PS thinks your playfield is the 'Secondary' monitor.
The normal setup is as follows:
Playfield_Monitor = Primary
Backglass_Monitor = Secondary

Be sure that your playfield screen is the main screen (under Windows display no one) and the backglass screen is the second screen (under Windows display no two).

 

I looked at these lines of my settings file and, based on the instructions in the readme file for PinSelect, decided maybe PinSelect was expecting a '0' for primary and a '1' for secondary.  When I changed those values, suddenly I got an image on both monitors!  They were, however, switched:  the playfield image was on the backglass monitor, while the backglass image was on the playfield monitor.  I thought to myself, "No problem!  I'll just switch them in the settings!"  For some reason, though, doing so made absolutely no difference; they were still switched.  It was getting late, so I gave up and went to bed.

 

My playfield monitor is definitely set as the primary (no. 1) display in windows,  The only thing I can think of that might be different than other setups is that I moved the taskbar to the backglass monitor, and I also regularly move windows that I'm working with over to it as well, so I don't have to cock my head sideways to be able to tell what I'm doing.

[The Loafer]

I think the task bar has to be set to the playfield, someone brought up such as issue with Hyperpin or fplaunch not that long ago. Try setting it to the playfield and see if it works.

[pocketpal]

Ok, I took the opportunity to mess with it a little more while I was home for lunch.

 

I think the task bar has to be set to the playfield, someone brought up such as issue with Hyperpin or fplaunch not that long ago. Try setting it to the playfield and see if it works.

 

I moved the taskbar back to display 1 (and double-checked that my playfield is, in fact, display 1), and tried the settings several different ways again, but still got the same results as before.

 

On a whim, I tried moving the explorer window from which I was launching PinSelect from monitor 2 over to screen 1, ran it, and LO AND BEHOLD... it was different -- not right, but different:  my playfield image was where it belonged, but now I had no backglass image!  I tried the different settings again, and then I was right back to where I was before.  This was puzzling me, but strange as it may seem, I figured out that it must depend on which screen my mouse pointer is located when I launch PinSelect!  If my cursor is on the playfield display, then that's where both images go, and if it's on the backglass monitor, then that's where the images will display.  Or something along those lines... I had to hightail it back to work, so I didn't get to do any further diagnoses.

 

Any more ideas?

 

EDIT:  I should mention that it doesn't seem to make a lick of difference what the Primary and Secondary settings are, as long as they're numbers.  The words "Primary" and "Secondary," however, cause both images to be on the backglass.

Edited by pocketpal, 24 April 2013 - 07:32 PM.

[fuzzel]

oh yeah...I was about to release v1.8 but I guess I will first fix this screen bug before releasing a new version...stay tuned!

[fuzzel]

Ok, I took the opportunity to mess with it a little more while I was home for lunch.

 

I think the task bar has to be set to the playfield, someone brought up such as issue with Hyperpin or fplaunch not that long ago. Try setting it to the playfield and see if it works.

 

I moved the taskbar back to display 1 (and double-checked that my playfield is, in fact, display 1), and tried the settings several different ways again, but still got the same results as before.

 

On a whim, I tried moving the explorer window from which I was launching PinSelect from monitor 2 over to screen 1, ran it, and LO AND BEHOLD... it was different -- not right, but different:  my playfield image was where it belonged, but now I had no backglass image!  I tried the different settings again, and then I was right back to where I was before.  This was puzzling me, but strange as it may seem, I figured out that it must depend on which screen my mouse pointer is located when I launch PinSelect!  If my cursor is on the playfield display, then that's where both images go, and if it's on the backglass monitor, then that's where the images will display.  Or something along those lines... I had to hightail it back to work, so I didn't get to do any further diagnoses.

 

Any more ideas?

 

EDIT:  I should mention that it doesn't seem to make a lick of difference what the Primary and Secondary settings are, as long as they're numbers.  The words "Primary" and "Secondary," however, cause both images to be on the backglass.

 

It should work if your primary monitor (playfield) is the one which holds the 'main' desktop including the taskbar all other monitors should be only an extension to the desktop. E.g. if you have a three monitor setup screen1 is you main desktop with taskbar (playfield), screen2 (backglass) extends screen1 and finaly screen3 (DMD) extends screen2.

So if you start PinSelect from screen1 it should work, well at least it works on my cab and on my desktop in that way

 

On a second thought I'm going to release v1.8 now, and you can try it. I'll try to find a better way detecting primary/secondary screen and make a bug fix version asap...

ok checkout post#1 for v1.8.

 

It introduces a simple attract mode together with the possibility to launch the last played table from the exit screen (thx jasonsmith for the nice idea )

Edited by fuzzel, 24 April 2013 - 09:55 PM.

[jasonsmith]

RE 1.8

 

Fuzzel I'm getting a bunch of errors on start, after clicking through them I get a blank screen with just the wheel and no games. Here's what I'm seeing, I get about 6-8 of them for different games from both FP and VP. 

 

 

EDIT: I think starting this rewrote my settings file paths...

I fixed my paths and all is well. For some reason they were changed.

 

 

New one... 

 

Loading the last played table from the menu didn't load the last played tables backglass, it loaded the backglass that the wheel was currently sitting on. 

Edited by jasonsmith, 24 April 2013 - 10:18 PM.