503 replies to this topic

[ClarkKent]

I can not test Taxi for the LEDs on 3rd monitor as there is no new version of the dB2S backglass.

 

I still noticed the problem with "Elvira and the party monsters" when using the EXE of dB2S - a lot of double LED letters. But without EXE ball stutters...

 

Hello, I had problems on the Elvira table too with wierd letters and numbers showing up. I set 'EXE' mode then enabled Dream 7 leds and the problem went away. Worth a shot? Maybe only enabling dream 7 leds might work for you as you seem to have trouble with exe mode.

Unfortunately Dream 7 LEDs were activated anyway. And simple LEDs is even worse...

 

 

Have you played my Taxi backglass? This is using a 'B2S DMD', a second screen (beside the backglass) to show the LEDs. This window is integrated in the backglass on a 2 screen setup. And on a 3 screen setup you can put it whereever you want to have it. But of course you have to declare where to put it. And this can be done with these two settings, 'LED Display X Offset' and 'LED Display Y Offset'.

As I mentioned setting these both values to 0 means 2 screen setup, grill visible and maybe existing B2S DMD integrated in the backglass. Set one of these values larger than 0 and your B2S DMD is a standalone window in a 3 screen setup and gets to these offset coordinates (these offset values starts in the upper left corner of the backglass). Just try it, start with Sorcerer or PinBot with a value of maybe 200 for X and 100 for Y and see what happens. Both backglasses have got in version 1.0 an image for the third monitor. Stop the table and change the offset values. Locate it to your third monitor.

I just tried to play around with the new Taxi dB2S. Tried 200 for X and 100 for Y. OK, I see a separate DMD window at the bottom of the backglass. Can't move it by mouse so I tried to enter different values like 800 for x and 200 for y. But the DMD window did not move a bit. What would be the values for the 3rd monitor?

[Herweh]

I just tried to play around with the new Taxi dB2S. Tried 200 for X and 100 for Y. OK, I see a separate DMD window at the bottom of the backglass. Can't move it by mouse so I tried to enter different values like 800 for x and 200 for y. But the DMD window did not move a bit. What would be the values for the 3rd monitor?

 

Have you saved the file?

[rosve]

I can not test Taxi for the LEDs on 3rd monitor as there is no new version of the dB2S backglass.

 

I still noticed the problem with "Elvira and the party monsters" when using the EXE of dB2S - a lot of double LED letters. But without EXE ball stutters...

 

Hello, I had problems on the Elvira table too with wierd letters and numbers showing up. I set 'EXE' mode then enabled Dream 7 leds and the problem went away. Worth a shot? Maybe only enabling dream 7 leds might work for you as you seem to have trouble with exe mode.

Unfortunately Dream 7 LEDs were activated anyway. And simple LEDs is even worse...

 

 

Have you played my Taxi backglass? This is using a 'B2S DMD', a second screen (beside the backglass) to show the LEDs. This window is integrated in the backglass on a 2 screen setup. And on a 3 screen setup you can put it whereever you want to have it. But of course you have to declare where to put it. And this can be done with these two settings, 'LED Display X Offset' and 'LED Display Y Offset'.

As I mentioned setting these both values to 0 means 2 screen setup, grill visible and maybe existing B2S DMD integrated in the backglass. Set one of these values larger than 0 and your B2S DMD is a standalone window in a 3 screen setup and gets to these offset coordinates (these offset values starts in the upper left corner of the backglass). Just try it, start with Sorcerer or PinBot with a value of maybe 200 for X and 100 for Y and see what happens. Both backglasses have got in version 1.0 an image for the third monitor. Stop the table and change the offset values. Locate it to your third monitor.

I just tried to play around with the new Taxi dB2S. Tried 200 for X and 100 for Y. OK, I see a separate DMD window at the bottom of the backglass. Can't move it by mouse so I tried to enter different values like 800 for x and 200 for y. But the DMD window did not move a bit. What would be the values for the 3rd monitor?

 

Offset values  X=200, Y=100 should display the B2S DMD window close to the top of the backglass not at the bottom.

How are your displays configured?

[ClarkKent]

Displays are configured correctly - 1st pf, 2nd bg, 3rd dmd. All is working normally - except dB2S DMD.

 

The interesting part is that no matter what values I use for LED Display X and Y Offset - the LEDs always appear in the middle of the bottom of the bg. I can not move it to the 3rd screen.

 

The only values that changes the display is the LED display width and height - if the values are 0 then I see nothing. So 800 and 200 seems a good value - but they are on the 2nd screen.

[maceman]

Does anyone know if all the new directB2S's have grills?

I ask because the F14 one has no grill for me when i try to set it to on in the SMenu.

If there is a grill then i need to troubleshoot this as well

[ClarkKent]

The only weird thing is that I have to enter display 3 for bg in the screenres.txt otherwise the bg is displayed on real display 3, the dmd monitor.

 

Maybe that's the reason why I can not reposition it?

[ClarkKent]

I just clicked on "check monitors" in the B2S Backglass Server prefs. It tells me that the BG is display 3. But in Windows monitor settings it is definately display 2. I just read from another user here in the forum having the same strange behavior on his PC...

 

As long as I do not use .hidden=1 in the script I see the DMD on my 3rd monitor, the correct DMD monitor. But as soon as I use .hidden=1 and want to use the LED DMD from dB2S it does not see my BG as display 2 and DMD as display 3. This is just weird.

[Pinball999]

Hi there,

 

Thanks a lot to everyone involved in this project. These backglasses are a real treat and really help to reduce the stutter I had on some table.

Unfortunately, I have to report that on my setting, the new directB2S tables make VP crash when exiting.

I've tried with different builds, even made a new install of VP914, but the issue is the same, and it's only happening on direct B2S tables.

 

What could have caused the issue, is that I've tried to launch a Beta backglass by mistake. I'm not sure if the probem happened before or just after.

I've then deleted all beta files, reinstalled B2S Backglass Server 1.0, but it did not solve the problem.

Any idea of what could be wrong?

 

 

EDIT: Taxi seems to be the only table on the system not crashing VP

Edited by Pinball999, 12 February 2013 - 11:30 PM.

[ArcadiusMaximus]

Does anyone know if all the new directB2S's have grills?

I ask because the F14 one has no grill for me when i try to set it to on in the SMenu.

If there is a grill then i need to troubleshoot this as well

 

From what I gathered all b2s backglasses created with the editor have a speaker grill. There is a space designated in the editor as the speaker grill so when you check "Hide grill" that area is removed from the backglass. Its pretty ingenious since now that same file works for both 2 and 3 monitor setups.

Edited by ArcadiusMaximus, 13 February 2013 - 12:59 AM.

[htamas]

For what I gathered all b2s backglasses created with the editor have a speaker grill.

 

Not necessarily, although the idea you described is indeed great and should work for all cabinet setups.

The today released Cactus Canyon backglass doesn't have a grill, so it is only for 3-screen cabinets. I tried to fiddle with the checkboxes that control whether the grill should show or not, but couldn't get a grill to appear on this one.

[Slydog43]

Hi there,

 

Thanks a lot to everyone involved in this project. These backglasses are a real treat and really help to reduce the stutter I had on some table.

Unfortunately, I have to report that on my setting, the new directB2S tables make VP crash when exiting.

I've tried with different builds, even made a new install of VP914, but the issue is the same, and it's only happening on direct B2S tables.

 

What could have caused the issue, is that I've tried to launch a Beta backglass by mistake. I'm not sure if the probem happened before or just after.

I've then deleted all beta files, reinstalled B2S Backglass Server 1.0, but it did not solve the problem.

Any idea of what could be wrong?

 

 

EDIT: Taxi seems to be the only table on the system not crashing VP

 I had that trouble when I was testing B2S Server and reinstalled OS a few times trying to improve things.  I dont have this at all now and I think one important thing was to add a registry setting ddraw=0 under visual pinball defaults, which will get added to each table.  Not sure if you have to add it to every table or not since I started fresh again today.  there is another setting that might help direct3d I think.  Hope this helps.   This is such a huge improvement for VP, Thanks Herweh

Edited by Slydog43, 13 February 2013 - 01:22 AM.

[Pinball999]

Hi there,

 

Thanks a lot to everyone involved in this project. These backglasses are a real treat and really help to reduce the stutter I had on some table.

Unfortunately, I have to report that on my setting, the new directB2S tables make VP crash when exiting.

I've tried with different builds, even made a new install of VP914, but the issue is the same, and it's only happening on direct B2S tables.

 

What could have caused the issue, is that I've tried to launch a Beta backglass by mistake. I'm not sure if the probem happened before or just after.

I've then deleted all beta files, reinstalled B2S Backglass Server 1.0, but it did not solve the problem.

Any idea of what could be wrong?

 

 

EDIT: Taxi seems to be the only table on the system not crashing VP

 I had that trouble when I was testing B2S Server and reinstalled OS a few times trying to improve things.  I dont have this at all now and I think one important thing was to add a registry setting ddraw=0 under visual pinball defaults, which will get added to each table.  Not sure if you have to add it to every table or not since I started fresh again today.  there is another setting that might help direct3d I think.  Hope this helps.   This is such a huge improvement for VP, Thanks Herweh

... I was so busy tweaking my cab for the last days, that I completely forgot that i did this to T2 (page 17 of this thread). Thank you Slydog43, will check this for the problematic table tonight.

[Pinball999]

And as expected, it worked.. The funny thing is that I have this problem almost on all direct.B2S now, whereas only one was affected with the beta version.

[ClarkKent]

Where are the settings saved for each single dB2S? In the file itself or in the registry?

[ClarkKent]

Just want everybody to know that I solved the "Elvira And The Partymonsters"-problem. I was using an old B2S-version to drive the new dB2S backglass. After downloading the regular FS version all is well...

[Slydog43]

I was thinking about that also, Should I remove all references from a old  B2S style table and the timer that enabled the leds (I think that is what it is for) to speed things up?  A few of my tables I just removed the launching of the tables B2S exe and changed the controller line to use the B2S.Server.  Not sure if it would help or not for optimal speed.

 

Another topic, but do you think there is any difference between a 3.4 i7 and a overclocked i7 running at 4.x in terms of speed or microstutter? 

[Herweh]

I was thinking about that also, Should I remove all references from a old  B2S style table and the timer that enabled the leds (I think that is what it is for) to speed things up?  A few of my tables I just removed the launching of the tables B2S exe and changed the controller line to use the B2S.Server.  Not sure if it would help or not for optimal speed.

 

Pretty important, Sly, do not use the special B2S tables from Rosve. Just use the standard tables. In Rosve's tables there are a lot special 'older' B2S commands communicating with the 'old' EXE backglass over the registry. This is all overhead. The new server is listening to VPinMAME and do not need these customized tables.

Edited by Herweh, 14 February 2013 - 12:02 AM.

[kruge99]

Does anyone with access to the current editor want to build a High Speed directB2S?  Like I said here, the UVP version used to bring my system to it's knees.

 

http://www.vpforums....072#entry211817

[darquayle]

As long as no one else is doing it, I'll be happy to do High Speed.  It was on my list of potential ones to work on anyway....

[ArcadiusMaximus]

Something I noticed with the new directb2s backglasses is when they are set to exe mode and you exit a table back to hyperpin, there is a few seconds in which the rom will still play (dmd will still display) or stutter while on the hyperpin main screen. Is this timing something that can be refined in a later release or is it just something you have to deal with? It's not TOO bad I'm just looking for things that can be improved upon in future releases. This thing is near damn perfect so this is just me being picky . Excellent work everyone involved !