vp-launch4 problem and question

[ppilot]

Okay, I know this has been covered extensively, and I know some people have reported similar sounding problems.  But I've never seen the answer posted.

If I try to launch a pinball game using vp-launch4, I get the FBI splash screen, and the only way I can get off of it is to reboot.  I've tried launching through mamewah.  I've tried going to the command line and typing 'vp-launch4 {tablename}'  I've got the executable and the vplcfgs folder in the tables subdirectory of my pinball install.  The 'default.ini' file is in the vplcfgs folder.  If I launch vp-launch4 from inside windows, I get the configuration screen with the values from the default.ini filled in.  The 'Test Launch a  Game' window has the names of my tables in it, but if I test launch I get the same result; splash screen I can't get away from.

It checks the exit key every 100 ms, so I've tried holding down the escape key to exit, nothing, I'm still stuck.  I've tried running the PinMame setup program, uninstalling visual PinMame, then re-installing.  I'm running Windows XP rev. 2.  I've got version 0.6.6028 of Visual Pinball.  The directory structure to VP-launch4 is C:\PinballPack\Visual Pinball\Tables.

I've tried this on three different computers.  I assume I'm either doing something very stupid, or vp-launch4 needs something that isn't on my computer in order to run.

That's about all I can think to tell anyone.  Also, assuming I can ever get this thing running, is there any way to remap the exit key?  I don't have a dedicated exit key on my cab.

Thanks for any help anyone can give me, this is very frustrating.

[ppilot]

Oh, and after I try to run, the vplog.txt file says

C:\pinballpack\Visual Pinball\Tables\TopSpeed.vpt with path

[ppilot]

bump, Howard, don't you have some idea?

[Howard_Casto]

I was looking into my archives and I've actually never seen this particular problem.  That's why I haven't responded yet. 

There are a couple of things to keep in mind here:

First off the version of visual pinball isn't important, but the version of visual pinmame is. You need to use the latest version as older versions had different class names and thus the wrapper can't control them. 

Also some video card manufacturers come with "window managment software"  that needs to be disabled.  Nvidia cards are notorious for this. 

Something you need to test is to make sure that visual pinball is "explorer ready".  Double-click on any vpt table from within explorer and make sure it loads properly.  If it doesn't then that's your problem right there.  It is solved by re-installing visual pinball and leaving the install program on your system while launching your first table from within explorer. 

Lastly it shouldn't be locking up.  Try alt-tab on the splash screen to see if it's a focus issue.  If so then it's just one of those odd-ball tables that sets it's own focus.  If it IS locking up then it's almost guaranteed that your problem is the problem above. 

The exit key can be remapped by passing "-keyx scancode" where, scancode is replaced with the vb scancode for your dedicated button.  It's not in the dialog because almost no one uses it. 

[ppilot]

Thank you very much for the reply.

First off the version of visual pinball isn't important, but the version of visual pinmame is. You need to use the latest version as older versions had different class names and thus the wrapper can't control them. 

I'm using version 1.52

Also some video card manufacturers come with "window managment software"  that needs to be disabled.  Nvidia cards are notorious for this. 


What would need to be disabled?  I don't have an nvidia card.


Something you need to test is to make sure that visual pinball is "explorer ready".  Double-click on any vpt table from within explorer and make sure it loads properly.  If it doesn't then that's your problem right there.  It is solved by re-installing visual pinball and leaving the install program on your system while launching your first table from within explorer. 


Which application should the .vpt files be associated with?

Again, thank you very much for your help.

[Howard_Casto]

Vpt files ARE visual pinball tables.  They need to be associated with visual pinball of course.  If they aren't, my wrapper isn't going to work, nor is any other method of launching vp tables. 

And modifying the association properties in windows won't fix it, the vp install has to do it. 

[ppilot]

Thank you for your help, Howard.  I figured out what I was doing wrong, and wanted to post about it and maybe help someone else.

Anyway, my visual pinball software was something I downloaded from http://www.pinballsim.com/ called 'pinballpack.zip'.  It contains vpinmame, visual pinball, the vbs scripts, a few tables, and a windows front end called 'visual pinball launcher'.  It works fine, but it installs everything to the same directory, and does not contain the visual pinball install program.

The package associates the .vpt files with visual pinball, but clicking on them just brings up the editor, it doesn't load the tables.  I assume this was the problem the wrapper was having.  The only install program that comes with the package is for vpinmame.  I was trying to re-install using this, and not having any luck.

Anyway, I uninstalled and deleted the package and downloaded everything seperately using the instructions found at http://www.vpforums.com/modules.php?s=&name=FAQ&myfaq=yes&id_cat=2#5.  I noticed there is an error on the instructions, in that they say 'The Table ZIP file contains a .vpt file that you unzip into the C:/VPinMAME/Tables directory' where they should say 'C:\Program Files\Visual Pinball\Tables directory.'

So anyway, it all works fine now.  Thank your for your help and for taking the time and effort to code the wrapper.

[Howard_Casto]

let this be a lesson to you.... never, EVER download emulators/sims from a thid party site.  Only use official download packages from the app's homepage. 

glad you got it working

[headkaze]

I noticed there is an error on the instructions, in that they say 'The Table ZIP file contains a .vpt file that you unzip into the C:/VPinMAME/Tables directory' where they should say 'C:\Program Files\Visual Pinball\Tables directory.'

Actually your wrong, C:\VPinMame\Tables would be the correct folder to place the tables.

[Howard_Casto]

umm no...  pinmame doesn't have any tables, it has roms, which go in c:\vpinmame\roms  by default.  tables are a visual pinball thing.

please don't "help" if you are going to give bad advice 

[headkaze]

According to the official intructions at vpforums..

[Howard_Casto]

yes, and those instructions are wrong....  your point?

[headkaze]

I'm not going to argue with someone who thinks they are right no matter what evidence your show to the contrary 

[mahuti]

Rather than quoting the instructions... try it.

[Scoobie]

First off the version of visual pinball isn't important, but the version of visual pinmame is. You need to use the latest version as older versions had different class names and thus the wrapper can't control them. 

Also some video card manufacturers come with "window management software"  that needs to be disabled.  Nvidia cards are notorious for this. 

Something you need to test is to make sure that visual pinball is "explorer ready".  Double-click on any vpt table from within explorer and make sure it loads properly.  If it doesn't then that's your problem right there.  It is solved by re-installing visual pinball and leaving the install program on your system while launching your first table from within explorer. 

Lastly it shouldn't be locking up.  Try alt-tab on the splash screen to see if it's a focus issue.  If so then it's just one of those odd-ball tables that sets it's own focus.  If it IS locking up then it's almost guaranteed that your problem is the problem above. 

The exit key can be remapped by passing "-keyx scancode" where, scancode is replaced with the vb scancode for your dedicated button.  It's not in the dialog because almost no one uses it. 

My cab went on the fritz and I've had to reinstall everything.  I'm now at the point of getting visual pinball to launch from mamewah, but am having the same issues as some in the past.

I'm able to launch vp by itself, but when using either vp-launch.exe or vp-launch4.0.exe...I too am getting stuck at the "don't do drugs" splash screen.

I checked and do have the install file and the vplcfgs folder in my visual pinball tables folder.

I also have the latest versions of both pinmame and visual pinball.  Again I'm able to launch vp and the tables, just not when using one of these wrappers.

When stuck at the splash screen, pressing alt+tab doesn't seem to do anything, so I don't think it's a focus issue.

I tried this on several tables that launch okay on their own...but I'm still getting stuck on the splash screen when using the wrappers.

I realize this has been covered before, but the only thing I've found in my searches is that people seem to fix the problem by reinstalling everything.

I've uninstalled/reinstalled all files/folders for both pinmame and vp, but am still stuck.

Any help would be most appreciated!!
Thanks.

[Howard_Casto]

Before you start with the wrapper, make sure vp is working properly.  Find a vpt file on your harddrive, right-click on it, and select play.  If starts installing crap then that was your problem.

[Scoobie]

VP works great by itself with no problems loading and playing tables.  The issue seems to be when lauched with the wrapper, using info above.  Again, same issue as others had in that I can't get past the "don't do drugs" splash screen.  I've tried the suggestions above but still no luck just yet.

Do you have any other suggestions I could try?

Thanks.

[Howard_Casto]

Just to clairfy, visual pinball can work just fine without the play function working fine.  The only way to test this is to right-click on a table and select play.  Playing it in the visual pinball program will not require the file associations that the wrapper needs and thus it is not a valid test. 

[Scoobie]

Okay, the problem seems to be that even though I have updated VP to the newest version and even tried to uninstall and reinstall VP...I get a message that my version of VP has expired and need to download the newest version.

Keep in mind this only happens when I right click a table and select "play."  If I find the program VP v.7, the tables open okay without problem.

This must be the reason I can't get the wrapper to work.  If only I knew how to fix this.

I have unistalled and reistalled VP and have redone the entire thing, step by step, twice.

Is there a way to update my version of VP without needing to re-do this all again?

Thanks for the help!

[whatisk]

Would it be that perhaps your version of VPM (rather than Visual Pinball itself) has expired?

I think the current version is 1.53

[Howard_Casto]

Okay, the problem seems to be that even though I have updated VP to the newest version and even tried to uninstall and reinstall VP...I get a message that my version of VP has expired and need to download the newest version.

Keep in mind this only happens when I right click a table and select "play."  If I find the program VP v.7, the tables open okay without problem.

This must be the reason I can't get the wrapper to work.  If only I knew how to fix this.

I have unistalled and reistalled VP and have redone the entire thing, step by step, twice.



Is there a way to update my version of VP without needing to re-do this all again?

Thanks for the help!

This is normal.  What you do is install vp and do NOT delete the installer.  Now right-click on a table to play it.  It'll complain and prompt you to automatically install some stuff.  Once it does that you are good to go.

Your issue isn't pinmame afaik because it doesn't expire. Make sure you have downloaded the latest version of visual pinball because the old versions simply don't work once they expire. 

[Scoobie]

I did this, but when I open a table, it seems to default to the older version of VP. 

Do I need to uninstall the old version, without uninstalling the program installer?  If so, how/which files am I looking for?

I currently have both an older version of VP and its files as well as VP v7.  I beleive I uninstalled the older version of VP, then installed both the VP v7 full install as well as the .exe files.

Am I better off uninstalling and deleting all VP program files and installing VP v7 full installation and .exe again?

[Howard_Casto]

Uninstall ALL VERSIONS of vp before you begin. 

you need vp 7 and vp 7 alpha

get them here and only here:

http://www.vpforums.com/modules.php?s=&name=Downloads&d_op=viewdownload&cid=1

Install alpha 7 and then install 7 over top of it.  Do NOT delete either of those installers. 



If that doesn't work then there is something wrong with your setup elsewhere which is preventing vp from installing properly. 

[Scoobie]

Okay, the main issue has been resolved.  The solution was to rename the VPinball-7alpha5 file to the same as the full install .exe file in the folder it installed to.

The tables now launch when right clicking and selecting play.

Now comes launching VP within Mamewah.  The tables launch okay, however I'm still getting the "don't do drugs" splash screen for about 5 seconds, followed by a country selection and options window.

I thought I read in a post that the splash screen only appears on the first launch of each table.  This doesn't seem to be the case.

How can I either get rid of the splash screen or at least the options window upon launching tables within Mamewah?

Thanks again!

[Howard_Casto]

You don't get rid of the splash screen.  The wrapper is saying "yes" to the "Do you legally own this rom?" question for you.  It is there to remind you that you shouldn't be stealing roms since you aren't prompted anymore. 

These options you speak of are probably specific to that table (some tables prompt you for options upon startup).  Neither visual pinball nor my wrapper have a options screen like the one you are describing.  There isn't a way to automatically launch tables that have these annoying startup options. 

[mrclean]

Ive found that if you individually open the ones you want to play in windows outside of mamewah and click on "yes" to do you originally own.. blah blah blah.. then you should never get that prompt again along with the region codes.. so basically do that to all the ones in windows and then they should run fine. I think it somehow logs that info and shouldn't re-ask you so it wont effect the wrapper.

[Howard_Casto]

Ive found that if you individually open the ones you want to play in windows outside of mamewah and click on "yes" to do you originally own.. blah blah blah.. then you should never get that prompt again along with the region codes.. so basically do that to all the ones in windows and then they should run fine. I think it somehow logs that info and shouldn't re-ask you so it wont effect the wrapper.

The wrapper handles those prompts, you aren't listening.  He's talking about region codes, which are NOT pinmame settings, they are settings of an individual visual pinball table.  And no, many of the tables that prompt you for info (there aren't many of these tables) prompt you every time and don't store the info.  What comes to my mind are those tables that ask you which romset you wish to use.  They ask you every time the table is launched.  The only way to fix it is to go into the table's script and change the code, but that is a very tricky thing for a non-programmer to do, which is why I didn't mention it. 

[lloydcom]

Thanks Howard.

I had the same problem with your wrapper.

I read this thread and remembered the association issues with VP.

I guess you need to head bang a bit before the paradigm rears its little head!

Everything works perfect now, except the winners don't do drugs disclaimer. 

Looks like I got away without seeing that!!

[Howard_Casto]

Yeah I typically don't like to place the blame on an application when a wrapper doesn't work but in the case of vp it's very true.  It is a very stubborn program to launch and get it working properly (mainly due to the bothersome expirations) and more often than not when a wrapper, any wrapper (not just mine) doesn't work with vp it is because vp is acting up. 

[Scoobie]

Thanks Howard.

I had the same problem with your wrapper.

I read this thread and remembered the association issues with VP.

I guess you need to head bang a bit before the paradigm rears its little head!

Everything works perfect now, except the winners don't do drugs disclaimer. 

Looks like I got away without seeing that!!

How did you get the "winners don't do drugs" disclaimer to NOT launch?

Howard says it's built into his wrapper, but if there's a work-around, I'd like to try it.

Thanks.

[Howard_Casto]

There isn't one, but some front-ends change the focus of a launching emu, which could cause it to get lost in the shuffle. 

[headkaze]

You could also use ShowWindow(hWnd, SW_HIDE);

[Scoobie]

You could also use ShowWindow(hWnd, SW_HIDE);

How/where would I put this?

Thanks.

[headkaze]

You could also use ShowWindow(hWnd, SW_HIDE);

How/where would I put this?

Thanks.

If you were to write a wrapper to hide that window that would be the API function to hide it. I think Howard has written a wrapper so I was really just saying that to him.

[Howard_Casto]

You could also use ShowWindow(hWnd, SW_HIDE);

How/where would I put this?

Thanks.

If you were to write a wrapper to hide that window that would be the API function to hide it. I think Howard has written a wrapper so I was really just saying that to him.

Well considering I intentionally hard-coded in the disclaimer screen, that isn't gonna happen. 

[headkaze]

You could also use ShowWindow(hWnd, SW_HIDE);

How/where would I put this?

Thanks.

If you were to write a wrapper to hide that window that would be the API function to hide it. I think Howard has written a wrapper so I was really just saying that to him.

Well considering I intentionally hard-coded in the disclaimer screen, that isn't gonna happen. 

Oh okay. I might end up writing a wrapper myself anyway, when I get around to setting up VP.

[Scoobie]

Well considering I intentionally hard-coded in the disclaimer screen, that isn't gonna happen. 

Alrighty then.