130 replies to this topic

[jpsalas]

The table was meant to be played with VPX7, and it shouldn't look too bad with VPX8 either. Have you adjusted anything? Do you have your own script in the table's folder?

[Zuxif]

So I have vpx8, the latest beta. I also have the exact same bloom issue with this table. Default script and settings, so I'm not sure what's causing it. I also have some other tables that do this with vpx8, but never this much bloom lol. Hopefully jp will update this for VPX 8 soon 😉

[jpsalas]

I'll wait a  little before updating more tables for VPX8, since VPX8 is still being worked on a lot. I did update 22 tables to VPX8, mostly to find bugs, check how the tables looked under VPX8,  and also to check the new features. All the display and editor bugs I found were fixed, so just now most of the VPX7 tables should play fine under VPX8. there are many changes being done in the editor, so I'll wait a little before updating more tables, mostly because I can't reproduce those bloom errors. If I could reproduce them then I could report them it as a bug.

[Zuxif]

Yea vpx8 definitely still has some bugs and issues to work out. It's expected though with a new version, especially with how much has changed with vpx8. Personally, vpx8 has been great overall for me, with the only real issue I've encountered being this bloom issue on certain tables. I can't exactly pinpoint the cause. I'll try and mess with some video settings and see if one of them are causing the bloom issues.

Either way, you rock JP! I appreciate everything you do and have done for this hobby

Zuxif

[wiesshund]

only real issue I've encountered being this bloom issue on certain tables. I can't exactly pinpoint the cause. I'll try and mess with some video settings and see if one of them are causing the bloom issues.

 

cause is overly amped light intensities due to differences between vpx 7 lighting and vpx 8 lighting

[Imhotep]

The table was meant to be played with VPX7, and it shouldn't look too bad with VPX8 either. Have you adjusted anything? Do you have your own script in the table's folder?

Yes, I'm on VPX8 and did not change anything. Thanks anyway JP, your work is much appreciated and I will just wait until you update this table for VPX8, no problem

[SmilesLikeJoker]

Hi friends, when I startup this table it looks like this:

Do I need to adjust some settings? Or what could be the reason?

Thanks so much, Sven

I can tell you for a fact this was fixed in VPX 10.8 some time back as I had put a lot of info on it in the bug tracker.  It was fixed on 6 Jun.  It affected a bunch of tables.  Basically, you need to update.  If you're curious, here is the link to the bug tracker:

https://github.com/v...ball/issues/538

Right now, there is a known bug if you change something on any jpsalas table, save the table, and then try to open it again.  Vincent is aware.  To avoid this current bug, you want to use the following action revision:

Update to 2.28.5 vpinball#2217 - 10.8 DX rev 1697

https://github.com/v...runs/6746634781

 

The above revision is only a week or so old.  Any revision after this one has the new bug.

Edited by SmilesLikeJoker, 10 November 2023 - 12:04 PM.

[wiesshund]

 

I can tell you for a fact this was fixed in VPX 10.8 some time back as I had put a lot of info on it in the bug tracker.  It was fixed on 6 Jun.  It affected a bunch of tables.  Basically, you need to update.  If you're curious, here is the link to the bug tracker:

https://github.com/v...ball/issues/538
 

 

No, that is still an issue for tables that have what are now overly high lamp intensities

 

TRON does it in all angles and all views
because the offending lamps have an intensity of 200

Causes too much bloom.
 

Still have to drop the lamp intensities down

Pain in butt on tables where the author didnt use layers to separate things

[SmilesLikeJoker]

The JP Star Trek picture in the bug report was mine.  It matches what the dude posted.  Here is a picture of the table now.  He needs to update VPX to fix the specific issue he shows in his screenshot.
 

Attached Files

•  fixed.jpg   149.88KB   2 downloads

Edited by SmilesLikeJoker, 10 November 2023 - 05:13 PM.

[wiesshund]

The JP Star Trek picture in the bug report was mine.  It matches what the dude posted.  Here is a picture of the table now.
 

JP's Star Trek, i never had an issue with
But try TRON Legacy

 

Put on sun glasses 1st

[SmilesLikeJoker]

I was wondering which Tron you were referring to lol.  Here is my table screenie lol.  Running 10.8 DX x64 rev 1697.  Table last saved 18 May so I haven't done anything to it in awhile (probably just pov changes at the time).  I do remember that this table had the same issue as JP Star Trek, but didn't add it to the bug report.  I figured I had added enough tables to help Vincent out lol.

 

SIDENOTE: Nice little info you added on the current bug   I hope Vincent can figure it out lol. 

Attached Files

•  tl.jpg   97.82KB   2 downloads

Edited by SmilesLikeJoker, 10 November 2023 - 05:46 PM.

[wiesshund]

I was wondering which Tron you were referring to lol.  Here is my table screenie lol.  Running 10.8 DX x64 rev 1697.  Table last saved 18 May so I haven't done anything to it in awhile (probably just pov changes at the time).  I do remember that this table had the same issue as JP Star Trek, but didn't add it to the bug report.  I figured I had added enough tables to help Vincent out lol.

 

SIDENOTE: Nice little info you added on the current bug   I hope Vincent can figure it out lol. 

 

Not same tron table version
can tell by the colors flippers and strobe caps

 

I will have to see whose version i have.

it's the one with the lamps set at 200 to 300 intensity

[SmilesLikeJoker]

I have the VPin Workshop one.  We can take this to PM to work it out so we're not flooding JP's table with it if you want lol.
 

 

For the issue for the guy that posted his super bright JP Star Trek table though, he just needs to update VPX.

Edited by SmilesLikeJoker, 10 November 2023 - 06:20 PM.

[Mitchell]

This will get rid of the blooms. Name go here.bloomstrength = 0

 

For example. Table1.bloomstrength = 0

 

Rise the number up for the blooms.

[wiesshund]

This will get rid of the blooms. Name go here.bloomstrength = 0

 

For example. Table1.bloomstrength = 0

 

Rise the number up for the blooms.

 

It will but it is global to the table

so that will remove wanted bloom also

better to just correct the out of spec lamps?

[X Vector]

 

The table was meant to be played with VPX7, and it shouldn't look too bad with VPX8 either. Have you adjusted anything? Do you have your own script in the table's folder?

Yes, I'm on VPX8 and did not change anything. Thanks anyway JP, your work is much appreciated and I will just wait until you update this table for VPX8, no problem

 

I've tried JPS' Star Trek LE 4.3 on VP 10.8 Beta 5 (r1347) and the extra bloom is very mild, not even close to what the earlier screenshot shows.

[jpsalas]

You can always reduce the bloom strength in the table's Visuals tab, Bloom Strength from 0,3 to 0,1, that will do.

[wiesshund]

You can always reduce the bloom strength in the table's Visuals tab, Bloom Strength from 0,3 to 0,1, that will do.

 

i prefer to just adjust the offending lamps, as that cuts bloom for all things, even non offending lamps

[Mitchell]

I will try that out.

You can always reduce the bloom strength in the table's Visuals tab, Bloom Strength from 0,3 to 0,1, that will do.

[Imhotep]

Thanks so much, in fact updating VPX 10.8 to Beta5 was enough to fix the blooming.

https://github.com/v....0-1347-3d585e7

 

Looks and plays great now! Thanks again, Sven

 

 

I can tell you for a fact this was fixed in VPX 10.8 some time back as I had put a lot of info on it in the bug tracker.  It was fixed on 6 Jun.  It affected a bunch of tables.  Basically, you need to update.  If you're curious, here is the link to the bug tracker:

https://github.com/v...ball/issues/538

Right now, there is a known bug if you change something on any jpsalas table, save the table, and then try to open it again.  Vincent is aware.  To avoid this current bug, you want to use the following action revision:

Update to 2.28.5 vpinball#2217 - 10.8 DX rev 1697

https://github.com/v...runs/6746634781

 

The above revision is only a week or so old.  Any revision after this one has the new bug.

 

Edited by Imhotep, 13 November 2023 - 04:09 PM.