149 replies to this topic

[Herweh]

Edit: Hmmm...just had a thought. Herweh, do you know if .net framework can cause issues? I just read another thread where someone has mentioned there system was smooth until they loaded the .net. Now, it works for me in everything else, but i wonder if there could be something with this i need to look into?? I do not know enough about it to know direction..

 

Sorry, don't think so, Rosve's backglasses are using .NET 4.0 too.

Have you tried the EXE mode? This is technically so close to Rosve's EXE backglasses.

[maceman]

Okay, for the EXE mode, am i doing this correct?

 

I go to the Menu and there is a square button box to the right that i press that says "exe mode" or whatever (not at the cab currently).

 

Then i press save, then i close and exit vp and reload. Same thing.

 

I just tried F14 as a good candidate as Roger's works for me, but the new one does not work.

Thanx for the help Herweh, I know this can be frustrating especially when you've worked so hard, but if you can get me up and running and am sure it will elp alot going forard in helping others

Cheers,

Maceman

 

EDIT: One other thing.. I am at the cab with HH loaded. What is weird i think is that in the S Menu, when i press turn off LED's it works. But anything else(like turn off lights) does not work, and after i save and reboot back in, it is all back, nothing is saving it seems.

Edited by maceman, 12 February 2013 - 10:03 PM.

[Herweh]

Thanx for the help Herweh, I know this can be frustrating especially when you've worked so hard, but if you can get me up and running and am sure it will elp alot going forard in helping others

Cheers,

Maceman

 

Yeah, it's really frustrating with all that different Windows issues. All this sounds like the 16bit/32bit color depth problem. Are you 100% sure you have set the backglass monitor to 32bit color depth in the OS settings?

[maceman]

I am 100% sure that both the windows graphic options say 32 bit and your S Menu when i click on monitors reports both display 1 and 2 are both 32 bit.

 

Cheers,

Maceman

 

I kinda hope in a weird way someone else has this issue so i can work with them to find a solution. How can i confirm that that EXE button on/off is working for me?

[Herweh]

I kinda hope in a weird way someone else has this issue so i can work with them to find a solution. How can i confirm that that EXE button on/off is working for me?

 

Open the taskmanager and get into the running processes (not tasks) tab. When you see the process 'B2SBackglassServerEXE.exe' you are running in EXE mode.

[bob78954]

Dammit..Just when I thought I had it all figured out...

 

lol

[ICPjuggla]

Okay, well I un-installed everything to start over!

Here is what's going on I followed the directions to a T, I click on the B2SBackglassServerRegisterApp and it prompts me to run as administrator. (I'm running XP witch it shouldn't need me to run as admin) so I right click and try to run as administrator and it won't let me do that either. Keeps asking me for a password witch I have never set up and have never needed one before. Mind you I was running a Beta version of the app with 4 tables installed before the new 1.0 was released.

Okay it keeps telling me this now:
Oops, the 'B2S backglass server' is not registered. Have you started this app as 'Administrator'?
(Cannot create ActiveX component.)

I'm stumped here! Weird thing is last night when I just copy pasted the new 1.0 into the tables folder it registered no problem but the 4 previous tables I had running with the beta wouldn't work. Now with a fresh install nothing is working.
Sigh.....

Edited by ICPjuggla, 13 February 2013 - 12:02 AM.

[kruge99]

For what it's worth, I'm running XP, I simply over-wrote the existing B2S Server files in my Tables directory and everything works fine in the Pin*Bot directB2S that I downloaded yesterday.  (Note, this is on my pincab and I don't have separate directories for regular/UVP/B2S etc.)  Everything is thrown into Visual Pinball/Tables.

 

(It even works with my pinDMD)

 

 

Best Regards,

Todd.

[ICPjuggla]

Okay, well I un-installed everything to start over!
Here is what's going on I followed the directions to a T, I click on the B2SBackglassServerRegisterApp and it prompts me to run as administrator. (I'm running XP witch it shouldn't need me to run as admin) so I right click and try to run as administrator and it won't let me do that either. Keeps asking me for a password witch I have never set up and have never needed one before. Mind you I was running a Beta version of the app with 4 tables installed before the new 1.0 was released.
Okay it keeps telling me this now:
Oops, the 'B2S backglass server' is not registered. Have you started this app as 'Administrator'?
(Cannot create ActiveX component.)
I'm stumped here! Weird thing is last night when I just copy pasted the new 1.0 into the tables folder it registered no problem but the 4 previous tables I had running with the beta wouldn't work. Now with a fresh install nothing is working.
Sigh.....

I've had a long day at work today...... I forgot to put the dll file in the tables folder. lol :-)

On another note the 4 original tables I had running with the beta still don't work. Cosmic Gunfight, Sorcerer, Pinbot and Taxi are still giving me the

startIndex cannot be larger than length of string.
Parameter name:startIndex

[luvthatapex]

Remember none of the beta backglasses will work with the 1.0 backglass designer. The format was changed.

You have to load the directb2s into the designer and regenerate a new directb2s for each pre 1.0 backglass you made.

 

Okay, well I un-installed everything to start over!
Here is what's going on I followed the directions to a T, I click on the B2SBackglassServerRegisterApp and it prompts me to run as administrator. (I'm running XP witch it shouldn't need me to run as admin) so I right click and try to run as administrator and it won't let me do that either. Keeps asking me for a password witch I have never set up and have never needed one before. Mind you I was running a Beta version of the app with 4 tables installed before the new 1.0 was released.
Okay it keeps telling me this now:
Oops, the 'B2S backglass server' is not registered. Have you started this app as 'Administrator'?
(Cannot create ActiveX component.)
I'm stumped here! Weird thing is last night when I just copy pasted the new 1.0 into the tables folder it registered no problem but the 4 previous tables I had running with the beta wouldn't work. Now with a fresh install nothing is working.
Sigh.....

I've had a long day at work today...... I forgot to put the dll file in the tables folder. lol :-)

On another note the 4 original tables I had running with the beta still don't work. Cosmic Gunfight, Sorcerer, Pinbot and Taxi are still giving me the

startIndex cannot be larger than length of string.
Parameter name:startIndex

Edited by luvthatapex, 13 February 2013 - 01:38 AM.

[Herweh]

On another note the 4 original tables I had running with the beta still don't work. Cosmic Gunfight, Sorcerer, Pinbot and Taxi are still giving me the

startIndex cannot be larger than length of string.
Parameter name:startIndex

 

IC, sorry, I found a bug in the server. Seems to be "your" bug. This happens in some backglasses with Dream7-LEDs as default when you set them to 'Use simple LEDs' in the backglass settings. I will PM you a new server in a few hours.

Edited by Herweh, 13 February 2013 - 10:39 AM.

[blur]

When i quit the table, Aero stays disabled. Aero is enabled only after i quit VP.
When i started a dB2S, quit the table and start it again, VP crashes.
For Hyperpin this isn't a problem, only when you use no frontend.

 

I have with some (not all) tables the same issue, but only with Win7 64 bit, while it works fine with 32 bit. Works fine from Hyperpin, crashes when called directly.

 

I think (think means not sure) that it hits only tables which don't stop correctly, I mean the sound of the ROM continue to play for 3-5 seconds after I pressed ESC.

 

Try to open the script and insert:

 

sub Table_Exit  '  in some tables this needs to be table1_exit

Controller.Stop

end sub

 

Then the sound stops immediately and so far I never run into crashes again if I relaunched the table.

 

Testing that I think that tables without ROM, such as ACDC don't crash while tables with ROM have the sound issue and crash (except I added code to stop the controller).

 

This is great find - only it can be table_exit or table1_exit or tableobjectname_exit - depending what you renamed table object to.

 

This could be used to close rosve's old b2s backglass from table - so that fplaunch doesn't have to do it and that you don't have to rename table to end with B2S.

 

There is one problem with rosve's b2s launch code (in b2s.vbs) - it doesn't support blanks in b2s exe name.

But that can be easily fixed like this - go to b2s.vbs and in launchbackglass routine change

      exename=exename+".exe"

to

      exename=""""+exename+".exe"""

 

On exit to close this b2s exe you have to add this to table script:

 

sub Abracadabra_Exit  '  in some tables this needs to be table1_exit

    'Controller.Stop

    Dim WshShell

    Set WshShell = CreateObject("WScript.Shell") 

    WshShell.Run "taskkill /F /IM ""Abra Ca Dabra (Gottlieb) (1975) (pinuck) (2.0.0) B2S.exe"""

end sub

 

It could be even automated to take vpt name and use it for backglass name - so that you can change name however you want and never have to edit table script.

 

 

Herweh does directb2s closes exe if it is run in exe mode?

Edited by blur, 13 February 2013 - 11:50 AM.

[ICPjuggla]

On another note the 4 original tables I had running with the beta still don't work. Cosmic Gunfight, Sorcerer, Pinbot and Taxi are still giving me the
startIndex cannot be larger than length of string.
Parameter name:startIndex

 
IC, sorry, I found a bug in the server. Seems to be "your" bug. This happens in some backglasses with Dream7-LEDs as default when you set them to 'Use simple LEDs' in the backglass settings. I will PM you a new server in a few hours.

Thank you in advance Herweh.

[Herweh]

Herweh does directb2s closes exe if it is run in exe mode?

 

Yes, it does. The server is starting the EXE and is keeping the reference to this started process. For closing the server tries to close this process with "process.Kill". And to get for sure it is trying to close the first available process called "Form1" with "SendMessage(<handle of the Form1>, WM_SYSCOMMAND, SC_CLOSE, 0)".

[luvthatapex]

I haven't been keeping up with the changes, so if this was mentioned before sorry about that.

 

I noticed a bug when you set the backglass to EXE mode and use an animation.

If you issue the command Controller.B2SStopAllAnimations() 
to stop all animations when you start a game, you will get an error "Length cannot be less than zero"

When I deselected the EXE mode it worked perfectly again.

 

Anyway, not a big deal but I just thought I'd mention it since it took me a few minutes to figure out what was wrong today

[blur]

Herweh does directb2s closes exe if it is run in exe mode?

Yes, it does. The server is starting the EXE and is keeping the reference to this started process. For closing the server tries to close this process with "process.Kill". And to get for sure it is trying to close the first available process called "Form1" with "SendMessage(<handle of the Form1>, WM_SYSCOMMAND, SC_CLOSE, 0)".

Great - you know that if you don't expect fplaunch to close it you can call that window any way you want - no need to call it Form1 you can call it for example "Herweh's great unique directB2S server" or just B2S server.

 

Any way - i see that you implemented this idea to put b2s backglass design (project) and table run time all in one file - so that when you have b2s backglass you can always edit it - great - tnx!

 

Did you see pause in vpinmame thread - there is one problem with b2s - when table loses the focus - ball stops and table doesn't do anything - but b2s backglass continues to run - that's not big deal if rom is not doing anything important - but if some count down i running - it will run of while you are in exit menu.

 

Is there a way for vp to detect loss of focus and do something about it? In plain vpinmame - i can send p to vpinmame window - but not with b2s backglass. UVP on the other hand stops rom as soon as vp loses focus.

Edited by blur, 14 February 2013 - 12:12 PM.

[Slydog43]

Where are the settings stored for the options when you click on backglass and hit s?  In the registry, directb2s file (which I looked at and don't think so)?

 

B2s are so incredible, thanks

 

 

I just assumed it was a table by table  setting, but I guess not.  Anyway to implement settings stored inside the directb2s file so each table could have its own settings?  Some tables might net exe mode, etc

Edited by Slydog43, 15 February 2013 - 02:36 AM.

[ICPjuggla]

Hey all I just want to put this out there.....

I can't thank Herweh enough for this awesome system he has put together for all of us. The bells and whistles included are amazing and the flexibility included into the system is incredible. It's great you can tweak each and every backglass and the options included are spot on. I for one can't wait to see the release of the actual editor.. I also can't imagine how much time and effort he has put into a project like this.. Hats off Herweh and fantastic job..

Also, I wanted to thank Herweh publicly as well for helping me when something was off for my system. I had an issue it seems no one else has had but Herweh stepped right in with a PM to get it fixed right away. I'm also going to thank luvthatapex as well for lending a hand and ideas when the problem 1st occurred. In my book a couple of classy guys here going out of there way to help someone in need.. Once again thank you

-ICPjuggla

Edited by ICPjuggla, 15 February 2013 - 04:16 AM.

[Herweh]

I noticed a bug when you set the backglass to EXE mode and use an animation.

If you issue the command Controller.B2SStopAllAnimations() 

Should be fixed in the next version but needs a few tests. Thanks LTA.

 

Herweh does directb2s closes exe if it is run in exe mode?

Yes, it does. The server is starting the EXE and is keeping the reference to this started process. For closing the server tries to close this process with "process.Kill". And to get for sure it is trying to close the first available process called "Form1" with "SendMessage(<handle of the Form1>, WM_SYSCOMMAND, SC_CLOSE, 0)".

Great - you know that if you don't expect fplaunch to close it you can call that window any way you want - no need to call it Form1 you can call it for example "Herweh's great unique directB2S server" or just B2S server.

 

Any way - i see that you implemented this idea to put b2s backglass design (project) and table run time all in one file - so that when you have b2s backglass you can always edit it - great - tnx!

 

Did you see pause in vpinmame thread - there is one problem with b2s - when table loses the focus - ball stops and table doesn't do anything - but b2s backglass continues to run - that's not big deal if rom is not doing anything important - but if some count down i running - it will run of while you are in exit menu.

 

Is there a way for vp to detect loss of focus and do something about it? In plain vpinmame - i can send p to vpinmame window - but not with b2s backglass. UVP on the other hand stops rom as soon as vp loses focus.

Yeah, blur, I picked up your idea of the directB2S file import into the designer. A great feature. To be honest I had it already in the back of my head but you motivated me to think more about it.

I'll investigate this focus and pause issue. I don't know whether I can do anything. It was very tricky already to get the 'VP is stopped' info.

 

Where are the settings stored for the options when you click on backglass and hit s?  In the registry, directb2s file (which I looked at and don't think so)?

 

B2s are so incredible, thanks

 

 

I just assumed it was a table by table  setting, but I guess not.  Anyway to implement settings stored inside the directb2s file so each table could have its own settings?  Some tables might net exe mode, etc

These infos are going into a XML file called 'B2STableSettings.xml' in the folder with the B2SBackglassServer.dll. You can open it with any text editor but please be careful and do NOT change any values.

 

Hey all I just want to put this out there.....

I can't thank Herweh enough for this awesome system he has put together for all of us. The bells and whistles included are amazing and the flexibility included into the system is incredible. It's great you can tweak each and every backglass and the options included are spot on. I for one can't wait to see the release of the actual editor.. I also can't imagine how much time and effort he has put into a project like this.. Hats off Herweh and fantastic job..

Also, I wanted to thank Herweh publicly as well for helping me when something was off for my system. I had an issue it seems no one else has had but Herweh stepped right in with a PM to get it fixed right away. I'm also going to thank luvthatapex as well for lending a hand and ideas when the problem 1st occurred. In my book a couple of classy guys here going out of there way to help someone in need.. Once again thank you

-ICPjuggla

Thanks IC.

[TedB]

Only now had time to install and try out this piece of awesomeness  

Easy to install and a nice user friendly gui to change settings. Already having so much backglasses so soon after the release is a sure sign the table creators like it as well. Having a nice b2s for a VP table makes any table a lot more 'real' and attractive on my cabinet. 

 

Thanks Herweh!