73 replies to this topic

[wiesshund]

What about apollo backglass?

[Tesla]

What about apollo backglass?

 

I tried all the steps you wrote.

 

No change.

 

I guess I'll try uninstalling and re-installing. I saved my original downloaded archives.

[wiesshund]

 

What about apollo backglass?

 

I tried all the steps you wrote.

 

No change.

 

I guess I'll try uninstalling and re-installing. I saved my original downloaded archives.

 

for giggles
rename table and directb2s file

just rename to ap13test

You could also try redownloading the backglass incase soemthing happened to it

[Tesla]

What about apollo backglass?

 

It turned out to be the screenres.txt file after all. I added a Comment.

 

# X/Y position of the DMD area relative to the upper left corner of the backglass screen - For 3 screen setup

# For Apollo-13 (Blastoff-13MB) try 1920,840 here. In B2S-Server, B2S-DMD should be Visible.

1920

840

 

I'm a noob.    I must have edited that file (working on other problems) and just hadn't ran Apollo-13 is a while. Then, I noticed it was broken and I thought related to other problem (mis-configuration of Freezys DMDExt during Heavy-Metal's Phase-2 install with Flex-DMD and all). 

 

So, nothing wrong with my core VPX install after all. All 3 Tables are 100% working again. Goodness gracious. 

 

Thanks for your help and sticking with me.

[wiesshund]

 

What about apollo backglass?

 

It turned out to be the screenres.txt file after all. I added a Comment.

 

# X/Y position of the DMD area relative to the upper left corner of the backglass screen - For 3 screen setup

# For Apollo-13 (Blastoff-13MB) try 1920,840 here. In B2S-Server, B2S-DMD should be Visible.

1920

840

 

I'm a noob.    I must have edited that file (working on other problems) and just hadn't ran Apollo-13 is a while. Then, I noticed it was broken and I thought related to other problem (mis-configuration of Freezys DMDExt during Heavy-Metal's Phase-2 install with Flex-DMD and all). 

 

So, nothing wrong with my core VPX install after all. All 3 Tables are 100% working again. Goodness gracious. 

 

Thanks for your help and sticking with me.

 

Well, then Tom and Jerry table will be fine too
When you get that one

It also has a 3 screen backglass

[Tesla]

 

 

What about apollo backglass?

 

It turned out to be the screenres.txt file after all. I added a Comment.

 

# X/Y position of the DMD area relative to the upper left corner of the backglass screen - For 3 screen setup

# For Apollo-13 (Blastoff-13MB) try 1920,840 here. In B2S-Server, B2S-DMD should be Visible.

1920

840

 

I'm a noob.    I must have edited that file (working on other problems) and just hadn't ran Apollo-13 is a while. Then, I noticed it was broken and I thought related to other problem (mis-configuration of Freezys DMDExt during Heavy-Metal's Phase-2 install with Flex-DMD and all). 

 

So, nothing wrong with my core VPX install after all. All 3 Tables are 100% working again. Goodness gracious. 

 

Thanks for your help and sticking with me.

 

Well, then Tom and Jerry table will be fine too
When you get that one

It also has a 3 screen backglass

 

Thanks for the recommendation, I'll add it to my list of tables I want to install and play.

 

This whole experience has been a little painful (for both of us I fear) but I now have new-found confidence to be able and install and configure new Tables properly.

[garnel]

Decided to get my first VP standard full size build working again with a new computer after building a three display widebody. Getting the backglass working after loading VP10.7.2 was a  STRUGGLE. No backglass display at all. Both the Playfield and DMD displays were good.  I'm using Windows 11 in both cabs. Issue  was not caused by Windows display number changes.

Turns out I had two instances of B2S Server - one in the Virtual Pinball folder and the other in the Tables folder and both dll's were registered. To get things working again - downloaded "regdllview.zip" and found both dll's. Tried to unregister them, but it wouldn't let me. Then tried the next regdllview option of deleting the associated files - that worked - and unregistered as well. So deleted both instances this way.  then reinstalled B2S in my Tables folder, registered the dll, rebooted the computer and it worked. I used my already existing screenres.txt file.

Thanks to everyone who contributed to this thread - it helped solve my problem.

 

 

B2S technically does not care where it lives at.

 

 
- In \B2S folder, I did the DLL registration process (and it said it was ready to go)

 

 
If you had the server in your tables folder and want to move it to a folder you should check for your old dll and deregister it with regdllview.
I guess you have two registered dll´s now. I had to deregister the old one before registering the server in its own folder.
https://www.nirsoft....d_dll_view.html
Open the programm scroll down a lot to find the dll or use find "b2s" and check for one or two dlls and the path of them. If you find only one dll at the right place (where your server is been installed). -> everthing ok.


 
I made a little video:

How to de-register a Backglass-DLL

https://youtu.be/QZ8VG_1IJZw

 

 

In Windows 11 to unregister the dll you need to select the option to delete the associated files - that will unregister as well. I tried using the "unregister" option and it came back with a 'unregister failed' message.

[Tesla]

 

Decided to get my first VP standard full size build working again with a new computer after building a three display widebody. Getting the backglass working after loading VP10.7.2 was a  STRUGGLE. No backglass display at all. Both the Playfield and DMD displays were good.  I'm using Windows 11 in both cabs. Issue  was not caused by Windows display number changes.

Turns out I had two instances of B2S Server - one in the Virtual Pinball folder and the other in the Tables folder and both dll's were registered. To get things working again - downloaded "regdllview.zip" and found both dll's. Tried to unregister them, but it wouldn't let me. Then tried the next regdllview option of deleting the associated files - that worked - and unregistered as well. So deleted both instances this way.  then reinstalled B2S in my Tables folder, registered the dll, rebooted the computer and it worked. I used my already existing screenres.txt file.

Thanks to everyone who contributed to this thread - it helped solve my problem.

 

.

 

Good to hear they were able to help you also.

 

Yeah, this is a definitely a good " help a newbie get his new install of VPX  running after using the v10.7.2 full-installer" thread.

 

Part of my problem was that (I've been away for 8 years and) I didn't really know what all was SUPPOSE to be happening. The posted Installation Guide was certainly helpful, but seems a little dated.

 

I think also ... if I ever do it again, I'll accept the full-installer's default options (ie, no B2S) and then install B2S manually later (via it's stand-alone installer). 

 

I agree. Nirsoft's RegDLLview is a nice find. I added it to my daily-driver Windows-11 machine as well. 

Edited by Tesla, 25 February 2023 - 12:58 AM.

[Tesla]

I like to get each configured properly first and then play a bit before moving to the next one on the list.

 

I've only installed 6 VPX tables so far, but this is fun and is getting addictive. 

[Tesla]

Well, then Tom and Jerry table will be fine too
When you get that one

 

It also has a 3 screen backglass

 

 

Thanks for the recommendation. It's pretty cool.

 

I tried to PM you just now, but it said I could not any more.

[Tesla]

A new strange B2S-Server problem cropped-up.

 

https://www.vpforums...=51049&p=516193

[Tesla]

if you want some colorized DMD's

 

when you are in F1, check to colorize, and check use external DLL

 

These are the DMD's i have color for (entire alt color folder zipped)

https://drive.google...?usp=share_link

 

 

 

Thanks.

 

So, how would I go about using some of these?

 

Where do I copy the .pal files to and do I need to change an option or install something new to get them to work? If there is a pre-written directions, I can just read those.

[digitalarts]

Folder named "altcolor" besides Rom folder. Inside a subfolder named like the Rom. Inside this folder a .pal and a .vni file. The name is always the "pin-2-dmd" (here I change the name to protect the innocent :⁠,⁠-⁠) )
In F1 Rom settings menu be sure to check colorized Rom...

There exist some other color formats...
.pac (only work with lucky1 dll)
.Crz (works with newest freezys dll)

[Tesla]

Folder named "altcolor" besides Rom folder. Inside a subfolder named like the Rom. Inside this folder a .pal and a .vni file. The name is always the "pin-2-dmd" (here I change the name to protect the innocent :⁠,⁠-⁠) )
In F1 Rom settings menu be sure to check colorized Rom...

There exist some other color formats...
.pac (only work with lucky1 dll)
.Crz (works with newest freezys dll)

 

 

I got it working with the first one I tried, Apollo-13. Very cool. Thanks.

Edited by Tesla, 22 March 2023 - 09:50 PM.