41 replies to this topic

[Tesla]

So, I was installing Addams Family and having a little trouble getting the VpinMame DMD to not only appear, but to stay on top of screen-3's B2S-DMD.

 

I was mainly just messing with F1-VpinMame options and B2S-Server options. Then VPX crashed/hard-locked the PC. I WAS NOT messing with my screenres.txt file. After I finally got it working, I then went to run it once more and I started getting the strange error message about not having a screenres.txt file in the Table folder.

 

Problem is, since the beginning ... I keep my single screenres.txt file in my C:\Visual Pinball\B2S\  folder . I've never really had one in \Tables\ . 

 

Addams Family and various other Tables were now giving the error or not starting-up properly. Strangely, some seemed fine. The only temporary fix (for Tables that didn't already have a tablename.res) was to move my screenres.txt to my \Tables\ folder. All Tables again working fine again. Weird but whatever.

 

Reason for my post now ... I just went to install Rescue-911. I can edit Camera settings and what-not, but first time I try to run it, I'm getting that same weird message again. I fear something is broken ... maybe with B2S-Server? I used B2SBackglassServer-1.4.1_x86.zip months ago and all has been fine until now.

 

Edited by Tesla, 15 March 2023 - 04:10 AM.

[Tesla]

Well, I see in the B2S-Server Release Notes, it says:

 

When the B2S Server loads a backglass, it tries to find them in this order:

tablename.res next to the tablename.vpx

Screenres.txt ( or whatever you set in the registry) in the same folder as tablename.vpx

Screenres.txt ( or whatever you set in the registry) as tablename/Screenres.txt

Screenres.txt ( or whatever you set in the registry) in the folder where the B2SBackglassServerEXE.exe is located. ** NEW **

 

Not sure what happened to my Install, but that "New Feature" isn't working any more.

I used B2SBackglassServer-1.4.1_x86.zip months ago and all has been fine until now.

I double-checked with RegDLLview-x64, and B2SBackglassServer.DLL is still properly Registered.

 

For now, I'll just move my single screenres.txt to my \Tables\ folder.

PROBLEM SOLVED (by work-around).

 

EDIT: I like to have just ONE screenres.txt file on my VPX system. As required (like for a 4:3 Backglass), over-ridden by a tablename.res .

Edited by Tesla, 14 March 2023 - 04:39 PM.

[Tiki]

 

When the B2S Server loads a backglass, it tries to find them in this order:

tablename.res next to the tablename.vpx

Screenres.txt ( or whatever you set in the registry) in the same folder as tablename.vpx

Screenres.txt ( or whatever you set in the registry) as tablename/Screenres.txt

Screenres.txt ( or whatever you set in the registry) in the folder where the B2SBackglassServerEXE.exe is located. ** NEW **

 

This is the description of Backglass Server 2.0 ->https://github.com/v...l/b2s-backglass
Did you upgrade to 2.0?
I hope that can solve your problem..
 

Edited by Tiki, 14 March 2023 - 08:46 PM.

[Tesla]

This is the description of Backglass Server 2.0 ->https://github.com/v...l/b2s-backglass

 

a. Did you upgrade to 2.0?

b. I hope that can solve your problem..

 

 

Thanks for the reply.

 

a. No, not yet ... I'm still on v1.4.1 .
I originally installed from B2SBackglassServer-1.4.1_x86.zip months ago (to C:\Visual Pinball\B2S\  ) and all has been fine until now. 

 

v1.4.1 Release Notes

 

- B2SBackglassServerEXE.exe can now be started from command line and in explorer to "debug" directb2s files.

- Add installation folder to the search path of ScreenRes.txt file. Current search "path":

1. tablename.res

2. Screenres.txt ( or whatever you set in the registry) in the table folder

3. tablename\Screenres.txt ( or whatever you set in the registry)

4. Screenres.txt ( or whatever you set in the registry) in the B2SServer folder.

- Add additional setting FormNoFocus complementing FormToFront. When set also FormToFront will stay in front and will ignore mouse key presses.

- B2SBackglassServerRegisterApp: Added registration of a .vpx file context menu copying template res files next to the table. Incl. small cmd to copy the file.

- B2S_ScreenResIdentifier: Better automated setup proposals

- Sort screens left to right for screen assignment

 

b. Possibly ... probably. Maybe what ever facilitates that "full search path" will be more resilient in v2.x ?

 

But even then, since I just have the one \Tables\ folder, I suppose I'm happy to keep my one screenres.txt there. That seems to be the more historically accepted place (however the B2S-Server folder makes more sense to me). I kinda just want it to work. It caused me extra troubleshooting work when it failed.

 

I'm a newbie ... I'll let yall upgrade now and test it. I'll follow behind after the dust-settles.

Edited by Tesla, 14 March 2023 - 09:05 PM.

[Tiki]

 

I'm a newbie ... I'll let yall upgrade now and test it. I'll follow behind after the dust-settles.

 

hehe, not a bad strategy.. :-)
did you try to just re-register your server?
 

[Tesla]

 

 

I'm a newbie ... I'll let yall upgrade now and test it. I'll follow behind after the dust-settles.

 

hehe, not a bad strategy.. :-)
did you try to just re-register your server?
 

 

 

Academically, that would be good to know if that would fix it.

But no, I did not since moving my single screenres.txt to \Tables\ worked.

 

If it hadn't worked, if v1.4.1 was still the latest version, or if v2.x wasn't just release ... yes, that was my next move.

[Tesla]

What I did do ...

 

Moved my single ScreenRes.txt to my single \Tables\ folder.

Started each of my 16 tables and made sure they were working (ready to play, and Backglass and DMD look exactly correct)

Saved B2S-Server settings on each Table (to B2STableSettings.xml)

 

Then I backed up (to a folder called "16 Tables Working 3-14-2023"):

ScreenRes.txt
B2STableSettings.xml

Any table.res files

DmdDevice.ini
PinMAME32ui.ini

Edited by Tesla, 15 March 2023 - 12:53 AM.

[Tesla]

Well, it was fun while it lasted guys ... apparently my system is totally screwed-up now after that crash.

 

This is what I seeing now ...

 

I've tried to install two new tables now:
Rescue-911 (Gottlieb )

Getaway HighSpeed-2 

 

They both install, config, and run ... but they are super laggy . Rescue-911 helicopter flies very slow. Table eventually locks some balls and then gets confused. Getaway is not really playable as the ball is not visible most of the time (must be running at 5fps or something).

 

This is after un-registering and re-registering B2S-Server v1.4.1 (all that seemed to go fine, BTW). 

 

I also noticed that if I try to run one of these two new Tables WITHOUT a .directB2S file , VPX (v10.7.2) locks-up before actually rendering the playfield. I have to use TaskManager to end the task.

 

Here's the weird part ... all my existing Tables (like 15 of them) including ST-TNG, Theatre of Magic, and F14-Tomcat run just fine (Playfield, Backglass, DMD, everything). Seems to me ... that means that B2S-Server v1.4.1 must be Registered and working, right? Like, how could it NOT be?

 

I wonder what is wrong? I want to walk away from it, but I don't think that is going to help it get fixed. It's kinda stressing me out.

Edited by Tesla, 15 March 2023 - 05:21 AM.

[fhjui]

you can check the registration of DLLs using the Nirsoft tool "RegDllview": https://www.nirsoft....d_dll_view.html.

And B2Sserver has -a lot- of classes in the registry for 32-bit in the Classes\WOW6432Node and for 64bit in the \classes-node.

[Tesla]

you can check the registration of DLLs using the Nirsoft tool "RegDllview": https://www.nirsoft....d_dll_view.html.

And B2Sserver has -a lot- of classes in the registry for 32-bit in the Classes\WOW6432Node and for 64bit in the \classes-node.

 

Thanks for the reply.

 

Yes, I used Nirsoft's RegDLLview-x64 (because I'm running Windows-10 64bit). It shows 28 Registration entries for B2SBackglassServer.DLL v1.4.1 (just like it did back when I originally installed it 30 days ago ... I made a notation about it). B2S-Server and everything has been fine until recently (I play, tweak, and/or install VPX Tables practically every-day).

 

I checked it before I Un-Registered it, and it still said 28 entries.

I checked for it immediately AFTER Un-Registering it (and rebooting) and it wasn't listed at all (so, 0 entries which is correct at this stage).

I also checked it AFTER Re-Registering it with the provided B2SBackglassServerRegisterApp.exe in the v1.4.1 package (again, 28 entries shown).

 

Please take note that all my existing Tables (like 15 of them) installed before a few-days ago (including ST-TNG, Theatre of Magic, and F14-Tomcat) have never stopped running properly (as well as right now). 

 

Either Rescue-911 and Getaway-HighSpeed-2 are "bad tables" (which seems unlikely) or there is something damaged/corrupt about my VPX install. I don't see how the problem can be with B2S-Server v1.4.1 if those 15-Tables are working.

Edited by Tesla, 15 March 2023 - 07:03 PM.

[digitalarts]

There are some different versions of 911 and HS2...
What exactly tables (from where...) you have?
Because if all your other 15 tables work - backglass ok, DMD ok, Rom ok,... all your settings are fine.
So it should only relays on the two new tables

[Tesla]

I used the Windows Drive Error-Check (including Full-Scan). No open or cross-linked files were found on the SSD. 0 bad files or locations found.

 

With Microsoft Defender Anti-Virus I did a full/long scan of whole system and 0 issues were found.

 

I'm just trying to cover all the bases before I move forward.

 

I'm going to try installing one more new VPX table ... Gilligan's Island .

[Tesla]

There are some different versions of 911 and HS2...
What exactly tables (from where...) you have?
 

 

I got the Tables and Backglasses from here on this forum. I can also supply the exact URLs for Backglasses if you want them.

 

https://www.vpforums...&showfile=15977

 

https://www.vpforums...&showfile=13130

 

The Getaway rom I got from here. The Rescue-911 rom I got from elsewhere. I got 2 different copies but neither helps (and they appear to be the same inside).

1. Because if all your other 15 tables work - backglass ok, DMD ok, Rom ok,... all your settings are fine.

2. So it should only relays on the two new tables

 

1. Thank you for verifying that. Really, that helps alot.

 

2. When the Gottlieb table didn't work ... while it would be the first that I found so far, I wasn't that surprised. But when the Getaway table did the same laggy-thing (but worse) I figured it had to be my install.

 

So, you are saying it's most likely my bad-luck and I just need to try yet another table, huh?

Edited by Tesla, 15 March 2023 - 07:37 PM.

[Carny_Priest]

Maybe you overwrote your screenres.txt or deleted B2STableSettings.xml or you have multiple instances installed?

[Tesla]

Because if all your other 15 tables work - backglass ok, DMD ok, Rom ok,... all your settings are fine.
So it should only relays on the two new tables

 

I installed Gilligan's Island and it installed, configured, and ran perfectly ... smooth as butter.

 

Sorry to panic about my core-VPX-install (again)    

I'm just not very good at identifying problems and troubleshooting all the various parts of VPX as a whole.

 

Thanks again for the help ... all of yall ... really helps to have someone who uses the software to bounce problems and ideas off of.

[Tesla]

Maybe you overwrote your screenres.txt or deleted B2STableSettings.xml or you have multiple instances installed?

 

Good ideas, but no ... they were fine and I just have one of each.

 

So, the 2 somehow-broken/super-laggy tables were just that ... some isolated table issue.

 

But when did VPX start locking/up-crashing when you try to play a table without a .directB2S file beside it? Not that I really do that, but as I was trouble-shooting I tried it and I thought it meant something was broken. Seems it's just by-design (the new normal) now?

[wiesshund]

 

So, the 2 somehow-broken/super-laggy tables were just that ... some isolated table issue.

 

But when did VPX start locking/up-crashing when you try to play a table without a .directB2S file beside it? Not that I really do that, but as I was trouble-shooting I tried it and I thought it meant something was broken. Seems it's just by-design (the new normal) now?

 

 

When B2STablesettings.XML has show errors enabled
and VPX is in exclusive Fullscreen mode and you cant see the popup dialog telling you no b2s exists.

 

Try disabling show errors (or show warning forget verbage.)

[Tesla]

 

 

So, the 2 somehow-broken/super-laggy tables were just that ... some isolated table issue.

 

But when did VPX start locking/up-crashing when you try to play a table without a .directB2S file beside it? Not that I really do that, but as I was trouble-shooting I tried it and I thought it meant something was broken. Seems it's just by-design (the new normal) now?

 

 

When B2STablesettings.XML has show errors enabled
and VPX is in exclusive Fullscreen mode and you cant see the popup dialog telling you no b2s exists.

 

Try disabling show errors (or show warning forget verbage.)

 

 

This is what I have now.

Is this Enabled or Disabled ?

 

<B2STableSettings>

  <ArePluginsOn>0</ArePluginsOn>

  <DefaultStartMode>1</DefaultStartMode>

  <DisableFuzzyMatching>0</DisableFuzzyMatching>

  <LogPath>

  </LogPath>

  <IsLampsStateLogOn>0</IsLampsStateLogOn>

  <IsSolenoidsStateLogOn>0</IsSolenoidsStateLogOn>

  <IsGIStringsStateLogOn>0</IsGIStringsStateLogOn>

  <IsLEDsStateLogOn>0</IsLEDsStateLogOn>

  <IsPaintingLogOn>0</IsPaintingLogOn>

  <IsStatisticsBackglassOn>0</IsStatisticsBackglassOn>

  <ShowStartupError>0</ShowStartupError>

  <ScreenshotPath>

  </ScreenshotPath>

  <ScreenshotFileType>0</ScreenshotFileType>

   <HeavyMetal>

[wiesshund]

ok you have error off there

make sure is same if you have more than one xml

[Tesla]

ok you have error off there

make sure is same if you have more than one xml

 

OK, good ... thanks for verifying that.

 

I checked. I only have ONE B2STablesettings.XML file on the whole SSD-drive.

There are some different versions of 911 

So it should only relays on the two new tables

 

The laggy-ness. slow helicopter, and the table getting confused was apparently caused by the .directB2S file posted here on the forum.

 

Wildman's B2S from VPU fixed the table for me. Runs fine now.

 

It was dragging-it-down somehow. Very weird ... I've never seen anything like that before.

Edited by Tesla, 16 March 2023 - 03:35 AM.