918 replies to this topic

[ravarcade]

@GInsonic, @Carny_Priest: I have found one more user with same problem but on Win 7. He have nVidia card with 361.43 drivers. 

Today i try to install that drivers on my GTX 550Ti, but instalation fails. Strange, 550Ti is on list with supported cards. Tomorrow i will try with borrowed GTX 960.

Error log helps alredy. I know what proc fails but don't know why. In 1-2 days i should solve problem.

[GInsonic]

Many thanks Ravarcade for the progress report ! Tell me please, if I can help testing...

[ravarcade]

Many thanks Ravarcade for the progress report ! Tell me please, if I can help testing...

I tested drivers 361.43 on GTX 960 and Win 7 64. All works fine for me without error.

I need your help and i have few questions:

1. Did you run FP/BAM with frontend or just run FPLoader.exe?

2. It crashes always or randomly?

3. On all tables?

4. Did you try "New table" from FP File menu? (It is simple, almost empty table)

5. In window mode with one display. It crashes or not?

 

If you were so kind and checked this debug version of renderingengine.dll:

http://www.ravarcade...eringengine.dll

Copy it to BAM dir and run FPLoader.exe, when set window mode.

This version will display 9 MessageBoxes.  First with message: "ReleaseAll()" and next 8 with "~Font() - 1", "~Font() - 2", ... "~Font() - 8".

If you give in info what was last seen message before crash it should give me clue where may be problem.

[Baronir2d2]

I will wait for the test you are performing.

More in my case here, I'm opening the FPLoader.exe only in all tables have the same result.

But oddly enough yesterday I opened all the tables and the closing had no problem, I did not change anything in the system, only functioned normally.

Today I will double check.

[GInsonic]

Thanks Ravarcade, I will report my results soon, but it needs some time...

[GInsonic]

And here are the results of the Austrian jury 

 

1. Normally I run FP and BAM with PinballX, but now I tried also without Frontend starting FpLoader only
2. In my test cases it crashes always, regardless which table, regardless with or without Frontend
3. Yes on all tables
4. The same with New Table
5. In window mode the same, but since I have all three screens enclosed in my cabinet, I can not try with only one screen, sorry,

The renderingengine.dll file shows these debug windows (in sequential order):

 

ReleaseAll()

Font() - 1

Font() - 2

Font() - 3

Font() - 4

Font() - 5

Font() - 6

Font() - 7

Font() - 8

ReleaseAll() (a second time)

 

then it crashes and sends Future Pinball.exe into executable heaven 

 

I hope, I could help a bit.

Ready for more tests, if you need them !

 

Edited by GInsonic, 06 January 2016 - 02:34 PM.

[ravarcade]

 

And here are the results of the Austrian jury 

 

1. Normally I run FP and BAM with PinballX, but now I tried also without Frontend starting FpLoader only
2. In my test cases it crashes always, regardless which table, regardless with or without Frontend
3. Yes on all tables
4. The same with New Table
5. In window mode the same, but since I have all three screens enclosed in my cabinet, I can not try with only one screen, sorry,

The renderingengine.dll file shows these debug windows (in sequential order):

 

ReleaseAll()

Font() - 1

Font() - 2

Font() - 3

Font() - 4

Font() - 5

Font() - 6

Font() - 7

Font() - 8

ReleaseAll() (a second time)

 

then it crashes and sends Future Pinball.exe into executable heaven 

 

I hope, I could help a bit.

Ready for more tests, if you need them !

 

 

I think i solved problem. That info was helpfull. Problem occurs only when backbox on second display was enabled.

 

Try this debug BAM.dll:

http:\\www.ravarcade.pl\debug\BAM.dll

 

You can also revert to previous renderingengine.dll.

 

Let me know if it solve problem.

[GInsonic]

It actually solves the problem, congratulations   

[Carny_Priest]

No crashes here! 

 

Ball is still transparent, though. It doesn't matter which renderer I select. 

 

Or rather, what I may be seeing is the surface reflection of the ball and not the ball itself. I did not have this issue before on any previous releases.

[ravarcade]

No crashes here! 

 

Ball is still transparent, though. It doesn't matter which renderer I select. 

 

Or rather, what I may be seeing is the surface reflection of the ball and not the ball itself. I did not have this issue before on any previous releases.

I know why it happends and solution for you is only mather of FP settings.

Two things must happend to reproduce problem:

1. Playfield is rotated (90 or 180 or 270 deg)

2. Ball Marks (Dirt) is unchecked.

Solution: Please enable "Ball Marks (Dirt)".

 

Why it happends:

FP draws ball different if playfield is rotated. It produces artifacts. In short if playfield is rotated ball is draw in 3 rendering passes instead of one. In last pass "Ball Marks" are drawed. If you disable it, Ball is not drawed, becase i remove all 3 ball draw and raw ball my own way in last pass and that pass never happends.

More on this thread:

http://gopinball.com...php?f=86&t=5583

 

In future i will detect this conditions and avoid problems.

[Carny_Priest]

Yes, I'm using a cab so I rotate 270deg and I had Ball Marks unchecked. Checking Ball Marks cleared up my issue. Thanks, Rav!

[vampirolatino2]

Had the same issue of transparent ball after update BAM. I had dirt ball unckeck because I didn't like it. After checking the ball marks the ball is shown, but is brownish/gold looking.... hate it. So I think I'm going back to working version.

[Baronir2d2]

Folks,

I come here to ask for more help and share knowledge.

 

I could install the BAM on my system, I had to change my motherboard due to chiset be the Intel H55 which has an incompatibility with the Kinect for Xbox 360.

 

I am now with a motherboard Gigabyte AM3 AMD Phenom X6 and processor 3.0Ghz. This board uses NEC chipset.

Interestingly my knect does not work if connected to the USB mother board.

so I installed an external USB card into the PCI-Ex1 bus, and interestingly also uses NEC chipset, but this time it worked.

 

I used to test several days and works perfectly.

But yesterday started happening a problem. to start the table kinect is triggered and works perfectly for a few minutes, after a while it just stops working, the LED infra red kinect is turned off and the BAM stops working. already I tested with several tables and always the same thing happens.

 

I thought it was problem of having another device sharing the USB, but there is only kinect in the external USB.

 

May be a hardware problem or is it software?

[Baronir2d2]

Good,

360 kinect is working in my cabinet in Kinect Desktop mode. If I select the Kinect mode the display is tremendous and it is virtually impossible to play due to the game's image is suffering distortions. Kinect Desktop mode works well, but I think to use in a CAB Kinect mode should be better, am I correct?

 

I'm thoughtful in exchange kinect 360 by the Xbox one kinect, this V2 is better at BAM?

someone has already done this test?

[Baronir2d2]

Black screen to reload table in BA

 

RAV, hello!

so now my HAIR is finished and I'm setting up the tables and the complete system.

I noticed that the tables are losing the BAM configuration, when I install a new table I open them with FP BAM directory, the table opens but nothing appears on the screen, get the black screen, I press the Q key and it appears the table image, then make the settings I want and then save the changes in the BAM menu for the name of the table. so far so good, the table is now active with BAM and my kinect accompanies my movements normally.

But if I turn off or leave the table and reenter everything back as it was before, that is, kinect is on but the table opens in black, I need to press the Q button again, when I press the Q everything works perfectly, but I again to configure the BAM menu as I want.

This is a FP problem or something I'm doing wrong?

I use the latest version of BAM that is on your site, windows 7 64bit, PinballX, and updated ATI driver.

[ravarcade]

 

...This is a FP problem or something I'm doing wrong?...

I don't think so.

It is probably bug in BAM. Don't waste time in checking hardware or drivers.

 

I need to replicate your problems. I will need few files and ansewers for few questions. Here is list of thing to do:

1. Backup BAM config files and send it to me. Needed files from BAM dir:

- reality.dat

- default.cfg

- cfg dir (or few files from there).

- plugins/Kinect.cfg (if you use Kinect for XBOX 360).

Please do it before you try to solve problem.

2. I will need screenshot of FP menu: Video/Rendering Options. This allow me to do own tests with same settings.

 

 

Now few questions:

3. Did you try to use BAM/FP without PinballX? I need to know, if problem occurs only with PinballX or not. 

 

4. Try to: 

- delete from BAM/cfg one config file of one table. (Select one).

- run BAM/FPloader.exe.

- load same table as deleted confing file.

Do you get black screen?

 

5. When you get black screen: 

- don't run BAM menu.

- try first show yourself to Kinect. Just make sure, that Kinect should find your head and head tracking should work without entering BAM menu.

- If you still have black screen, when press Q and look at Cam position displayed in menu. What is it: 0,0,0? 1.$, 1.$, 1.$? or something else?

 

6. What is FP dir? Is it default dir: "c:\games\Future Pinball" or something else?

[Baronir2d2]

Hello,

Rav, I was conducting the testing and raising the data you asked me to help solve the problem of the table start at black screen with kinect.

In an attempt I just managed to configure the plugin "kinect" and it left active tracking skeleton. Is working perfectly, the plugin "Kinect Desktop" shows the black screen issue. but the plugin "Kinect" has no problems.

 

Thanks for the help, if you still want to check what is happening with the "desktop" plugin is only to say that you send files as asked.

 

Thanks again!

 

May the force be with you!

[Baronir2d2]

Hello,

Rav, I was conducting the testing and raising the data you asked me to help solve the problem of the table start at black screen with kinect.

In an attempt I just managed to configure the plugin "kinect" and it left active tracking skeleton. Is working perfectly, the plugin "Kinect Desktop" shows the black screen issue. but the plugin "Kinect" has no problems.

 

Thanks for the help, if you still want to check what is happening with the "desktop" plugin is only to say that you send files as asked.

 

Thanks again!

 

May the force be with you!

[TerryRed]

Had the same issue of transparent ball after update BAM. I had dirt ball unckeck because I didn't like it. After checking the ball marks the ball is shown, but is brownish/gold looking.... hate it. So I think I'm going back to working version.

 

Same problem here...

 

LOVE BAM, but unfortunately there is a serious issue with the newest build. I use BAM in my pinball cabinet with 3 screens.

 

--------------------------------

 

On older BAM versions, if you had your playfield screen orientation in portrait (with NO rotation in video options), the ball would have a messed up ugly looking texture in all of BAM's lighting modes, except for "new renderer". In the "new renderer" lighting mode the ball would look normal, but way too bright,.

 

So FP would need to have the playfield screen in landscape orientation with 270 rotation. Then the ball in BAM would look beautiful in all modes.

 

--------------------------------

 

With this newer version of BAM, it doesn't matter what orientation your playfield is, or what rotation you use..... the ball ALWAYS has the ugly messed up texture no matter what in the same light modes...and "new renderer" still makes the ball too bright.

 

This makes BAM unusable for me.... I want my pretty ball back.....  

 

Is it possible to fix this?

 

 

Also, on a separate note.... when using "Force Arcade Mode", it works as intended and shows translite objects on the playfield which is good (like SLAMT1LT's Back to the Future time circuits), but it also causes movie clips (Tron Legacy, Nightmare on Elm Street, etc ) to play too fast and out of sync. This only happens when a second screen is enabled for the backglass in BAM. Works fine with only one screen. Any idea how to fix that?

 

Thanks for all your hard work!

Edited by TerryRed, 01 March 2016 - 09:26 PM.

[ravarcade]

 

..  the plugin "Kinect" has no problems.

God to know that it works for you.

"Kinect Desktop" is not designed for cabine. It is for standard TV with Kinect use (like with XBOX). 

 

 

...

On older BAM versions, if you had your playfield screen orientation in portrait (with NO rotation in video options), the ball would have a messed up ugly looking texture in all of BAM's lighting modes, except for "new renderer". In the "new renderer" lighting mode the ball would look normal, but way too bright,.

 

So FP would need to have the playfield screen in landscape orientation with 270 rotation. Then the ball in BAM would look beautiful in all modes.

 

--------------------------------

 

With this newer version of BAM, it doesn't matter what orientation your playfield is, or what rotation you use..... the ball ALWAYS has the ugly messed up texture no matter what in the same light modes...and "new renderer" still makes the ball too bright.

 

This makes BAM unusable for me.... I want my pretty ball back.....  

 

Is it possible to fix this?

Ball... well few things are alredy changed in this "beta":

http://www.ravarcade.pl/debug/beta.zip

It will be in next release, but you may try it now.

FP have realy broken ball drawning when playfield is rotated. In new version almost all errors are corrected.

Here is left whats left:

- if playfield is rotated, reflection of ball in playfield will not rotate with ball move. It is very hard to see. I will not fix it.

- If playfield is rotated and new renderer is not used reflection texture is not rotated. I will not fix it. 

 

... and in new BAM ("beta" for now) there is "balls" dir with additiona ball textures. You can press N or P to swtich ball during game. You may also delete this folder ... it is optional.

... and in addons menu you can change ball brighness.

... and in script users may create many balls with different textures on playfield visible same time.

Like this:

http://www.ravarcade...mo - teaser.png

(ball textures created by miownkhan)

 

You realy need to enable "dirt marks" again in FP to get all candies.