How to reset light source?

[madmrmax]

Sometime I must have messed with BAM's light source, but now I can't figure out how to restore it to a more "default" style. It is so strong as if it is a flashlight directly on the playfield. Look at the ball shadow for an example.

Note this is with the "reset to DEFAULT" selected. Currently this default light source is making most of the chrome/sphere mapped textures looking off as well.


Note I now realize it is an aspect of the "ray traced ball shadows". What is the default ball attributes for BAM?

 

[madmrmax]

And a follow up question -- what the heck do the WASD keys do to the BAM overhead light reflection on a ball? Regardless of being in the BAM menu.

Below are two images. The front ball is a newton ball model with sphere mapped. The ball behind it is a real ball created at runtime via script.

The light source seen reflected in the real ball is moving as I press and hold down either the WASD keys.

 

[madmrmax]

My BAM keyboard configs:

 

[TerryRed]

You can try to increase your Z height to a very large amount. Then play around with where you want your Y position to be.




Note, that if you enable Free Camera mode and move around, this will do some funky things with lens flares on lights, etc.

So for example, if you use F11 for Free Camera, then use mouse and WSAD to move your view around, then you press C to switch to a BAM camera a view... the lens flares etc won't look correct. You need to use a FP camera (F1 to F8) first to reset everything so they will "face the camera" correctly again. Then you can use a BAM camera view with C afterward.



As for Default BAM settings.... you can try a new (temporary) alternate install of FP and BAM located in a different folder (installed from the essentials AIO zip) and don't install my BAM settings, and just test with New Table and see what values come up.

 

[madmrmax]

You can try to increase your Z height to a very large amount.

As for Default BAM settings.... you can try a new (temporary) alternate install of FP and BAM located in a different folder (installed from the essentials AIO zip) and don't install my BAM settings, and just test with New Table and see what values come up.

Thanks! Between looking at your settings as well as installing FP & BAM on a new device to get original settings sounds like a good plan.

Note, that if you enable Free Camera mode and move around, this will do some funky things with lens flares on lights, etc.

This! So much so.

So for example, if you use F11 for Free Camera, then use mouse and WSAD to move your view around, then you press C to switch to a BAM camera a view... the lens flares etc won't look correct. You need to use a FP camera (F1 to F8) first to reset everything so they will "face the camera" correctly again. Then you can use a BAM camera view with C afterward.

Does this affect custom camera views that are created in Script? E.G., if I provide a option where users can use camera view designed for a particular table (or use an camera pan animation), I assume I'll see issues with lens flares and reflections during anything that is not stock FP camera? I'll mess around with some stuff. I think the "use a FP camera first" is a key part that I had not tried.

 

[TerryRed]

Using a BAM custom camera view is fine and won't mess up anything. It's only when you use F11 Free Camera and move around that messes up things.

In-game you can go back and forth between FP camera views (Fxx keys), and scripted views and bam camera views without messing up stuff just fine.