Does this look ok? I do have some problems as soon as I us B2S and is searching for the cause of it.
Posted 13 January 2015 - 07:49 PM
Does this look ok? I do have some problems as soon as I us B2S and is searching for the cause of it.
Posted 13 January 2015 - 09:22 PM
Nothing out of the ordinary there .. have you used b2s_debug.exe ? What's the issue you are seeing?
I can run VP without backglass. Playfield and DMD is ok. As soon as I start using the B2S I get the backglass and DMD to show and then VP craches with the error: "Fatal Error: HRESULT 88760868 at RenderDevice.cpp:420".
I had problems to get VP to work at first both in FS and desktop version.
Takut gave me this answer and that made VP work both in VP and FS but not with B2S.:
Download the VBS Scripts 3.43.0 and extract it to the Tables folder (usually C:\Program Files (x86)\Visual Pinball\Tables)
http://www.vpforums....ads&showfile=17
More in another thread: http://www.vpforums....showtopic=30186
I just asked here as it was a question about the logfile from b2s_debug.exe.
Posted 14 January 2015 - 01:17 AM
is this with every table or are you just getting things started? Which table are you using? Can you put a link to it here?
Did you edit it .. to make it work with B2S perhaps?
And when you say B2S .. you know the difference right between directB2s backglasses and B2S.exe backglasses?
I am assuming this one is a .directb2s file that is used for whichever table you are working on.
Does B2S_Debug show up properly?
Edited by allknowing2012, 14 January 2015 - 01:17 AM.
Posted 14 January 2015 - 04:51 AM
It is backglass with the extension .directb2s.
When I run the debug I get a backglass with several score wheels showing up. I guess that is what should happen? I think I have 1920x1080 on screen 1 but the debug says 1920x1040.
I first tested with Twister and then also with Taxi. I can not put the links here at the moment as I have the VP comuter in another location ans I am not 100% sure exact what linkes I used. I will see if I can find out as soon as possible.
And I really did not know that there where some B2S.exe backglasses.
Edited by jangus, 14 January 2015 - 04:53 AM.
Posted 14 January 2015 - 03:02 PM
"and in the end , the love you take is equal to the love you make"
Posted 14 January 2015 - 06:33 PM
Here is something of a guess...
"1027"," Screen2ResY"
Make that an even number ... like a power of 2. Its very unlikely you have a screen that is 1027 pixels.
And did you post your screenres.txt file?
Edited by allknowing2012, 14 January 2015 - 06:34 PM.
Posted 14 January 2015 - 08:10 PM
The b2s exe tables are older. They are indicated in the download section as being b2s. The exe that is needed comes with the download. With respect to your Fatal Error issue...I've had that and the advice that I got from others which usually fixed it was to lower in the settings down from unlimited to one of the lower numbers
I will try that. Is that settings for the playfield? Is it the Preferences->Video Options->Max Texture Dimension?
The playfield is run on a new GeForce something with 8GB so I find a bit odd if I need to lower the settings. But the onboard card for DMD and backglass might be a low-end card.
Here is something of a guess...
"1027"," Screen2ResY"
Make that an even number ... like a power of 2. Its very unlikely you have a screen that is 1027 pixels.
And did you post your screenres.txt file?
Yes, we did that yesterday. Changed it to 1024 but the problem did not go away.
Which table are you using? Can you put a link to it here?
I did a new install on my work computer today. Followed my notes exactly and here they are, with links.
I did the same with my actual VP computer yesterday and then after installing B2S I only got the errors. When I had downloaded a full screen vpt it first worked (as in step 18 above). I resized the playfield and DMD to fit the screens. Then I downloaded and installed the B2S backglass server.
After that I edited the script to use B2S but then it started to crash every time I tried to run a vpt. If I reedited the script to not use B2S it worked again.
Edited by jangus, 14 January 2015 - 08:31 PM.
Posted 15 January 2015 - 03:28 AM
i was debugging something similar with someone else and it was likely 2 vpinmame.dll files. Can u check that u have just one in the vpinmame directory. Not one in the vp directory. Run the esetup.exe in vpinmame, does it show cabinet mode as an option?
Be sure to run install and click both of the setup options there. The exe should be run as admin in xp compat mode if that is applicable
Posted 15 January 2015 - 07:43 AM
i was debugging something similar with someone else and it was likely 2 vpinmame.dll files. Can u check that u have just one in the vpinmame directory. Not one in the vp directory. Run the esetup.exe in vpinmame, does it show cabinet mode as an option?
Be sure to run install and click both of the setup options there. The exe should be run as admin in xp compat mode if that is applicable
I am at work and only have access to my work computer. I will take a look at my dedicated VP computer this evening. I will also run the setup.exe and see what options I have there.
But at my work computer there are no vpinmame.dll in the vp directory, only in the vpinmame directory. In the setup.exe I see: Install, Uninstall, Setup Paths, Setup Defaults, Test, Info and Quit. No show cabinet mode.
Here is the test resuts for the last part of my installation on my work computer. And this is confusing as it works perfekt?!!? But there is one differens that I know and that is that I only have 2 screens here.
(So I guess that I have understood how to install. Just have to redo the steps one more time on my VP computer and see if it is some compatibility with the computer parts?)!
Step nr 1 here starts after step 19 in my previous post.
Edited by jangus, 15 January 2015 - 07:49 AM.