4027 replies to this topic

[Segovia11]

 

10.7 Bug Report for Table Designers & Devs,

 

When grouped elements together is checked the names in the collection manager would normally remain unchanged, however the name in the property editor will be changed. Its is identified with a new collection name. One some occasion the following can occur : 

 

Although the bug is difficult to reproduce. This bug seemed to only affect Targets that were checked as grouped elements together in the collections manager.

The collection manager chooses one Target from the collection & renames it with the collection name. The Table code fails to identify the Target as a result. 

I now uncheck when I have finished using the grouped elements together during table design periods. 

 

All Table designers need to watch out for this bug. You will notice the bug when your code fails to respond. The name can only be changed manually after unchecking grouped elements together. 

 

The bug was not identified in 10.6.

 

   

 

10.7 has dodgy selection bugs and more, playing 10.7 is fine, just editor issues, I rolled back to 10.6 last week.

 

 

Most of them are non critical bugs & you can work round the majority of them. Some of the bugs are few & far between and difficult to reproduce. It probably will take a few years to iron them all out. 

The worst bug I have experienced in 10.7 was when Visual Pinball prevented editor access to the flashers. For some unknown reason it identified all flashers as a collection. The flashers were not in the collection manager. I rolled back to a later beta revision and low and behold the collection manager released the flashers. When i reinstalled the newest beta revision all was well again. 

I am sticking with 10.7 for the time being. Its looking good & is moving in the right direction.   

Once again devs Thankyou

[chepas]

 

 

10.7 Bug Report for Table Designers & Devs,

 

When grouped elements together is checked the names in the collection manager would normally remain unchanged, however the name in the property editor will be changed. Its is identified with a new collection name. One some occasion the following can occur : 

 

Although the bug is difficult to reproduce. This bug seemed to only affect Targets that were checked as grouped elements together in the collections manager.

The collection manager chooses one Target from the collection & renames it with the collection name. The Table code fails to identify the Target as a result. 

I now uncheck when I have finished using the grouped elements together during table design periods. 

 

All Table designers need to watch out for this bug. You will notice the bug when your code fails to respond. The name can only be changed manually after unchecking grouped elements together. 

 

The bug was not identified in 10.6.

 

   

 

10.7 has dodgy selection bugs and more, playing 10.7 is fine, just editor issues, I rolled back to 10.6 last week.

 

 

Most of them are non critical bugs & you can work round the majority of them.

 

Critical or not, it's actually very time consuming creating a game compared to 10.6.

[Segovia11]

 

 

 

10.7 Bug Report for Table Designers & Devs,

 

When grouped elements together is checked the names in the collection manager would normally remain unchanged, however the name in the property editor will be changed. Its is identified with a new collection name. One some occasion the following can occur : 

 

Although the bug is difficult to reproduce. This bug seemed to only affect Targets that were checked as grouped elements together in the collections manager.

The collection manager chooses one Target from the collection & renames it with the collection name. The Table code fails to identify the Target as a result. 

I now uncheck when I have finished using the grouped elements together during table design periods. 

 

All Table designers need to watch out for this bug. You will notice the bug when your code fails to respond. The name can only be changed manually after unchecking grouped elements together. 

 

The bug was not identified in 10.6.

 

   

 

10.7 has dodgy selection bugs and more, playing 10.7 is fine, just editor issues, I rolled back to 10.6 last week.

 

 

Most of them are non critical bugs & you can work round the majority of them.

 

Critical or not, it's actually very time consuming creating a game compared to 10.6.

 

 

Well, for me it wasn't. In general, If the truth be known table production is time consuming. There is a lot of work involved during the manufacturing of a new table.    

[chepas]

 

 

There is a lot of work involved during the manufacturing of a new table

 

Indeed. I wasn't aware of anything I encountered until I did, but after that I solemnly swore to use 10.6 going forward as it put an extra day on plus released bug table.

[Segovia11]

 

 

 

There is a lot of work involved during the manufacturing of a new table

 

Indeed. I wasn't aware of anything I encountered until I did, but after that I solemnly swore to use 10.6 going forward as it put an extra day on plus released bug table.

 

Your very luck with 10.6, i moved away from 10.6 due to the crashes. The latest 10.7 revision 129 is running well for me. Although it will crash if you press key F1. Hopefully the devs got the bug report!

Thinking back i wish i had taken a screen shot during the non reproducible buggy moments. Will do next time. 

[wiesshund]

Something about my sound was really bugging me... and now I just seen what's happening. (Dunno if this is a bug or not though).

 

I currently keep two Vpinball.exe files in my install... latest 10.6 and the latest 10.7.  I rename one of them if I need to go to the other. Generally, if I tweak a table I always do it in 10.6 because if I save it in 10.7 then it won't load properly in 10.6.

 

But I noticed that whenever I switch between the .exes my sound setting alters each time. I have 10.6 set as 7.1 surround. But it always defaults to 2.1 if I ever use 10.7 exe. Similarly I like to have 10.7 set to enhanced 7.1. But if I use 10.6 at all that switches to standard 10.7. I don't have to load any tables, just opening the other exe will do it.

 

Like I say, you might consider my switching files like this to be non-standard use, but I was wondering why 10.6 kept sending flipper sounds to back glass.

 

this could be due to having an extra sound option that previous versions do not, which creates an extra sound type entry that the older exe may see as invalid, causing it to fallback to 2 channel audio settings

[Thalamus]

Yepp. It is important, if you want to run both versions with the enhanced 7.1 - to get 10.6.2. And I of course recommend to stay on the very latest version of 10.7 too.

[wolis]

Hi VPX 10.7.0 (Rev 111)

 

I am noticing a faint circle around the ball shadow.. 

 

 

Anyone else notice this?

 

This is in New York (Gottlieb 1976) but I see it in most other playfields with plan or light tables.

 

No doubt someone else has mentioned this but its rather hard finding mention of it in these forums 

Edited by wolis, 19 April 2021 - 06:51 AM.

[Wylte]

Hi VPX 10.7.0 (Rev 111)
 
I am noticing a faint circle around the ball shadow.. 
 

That's an artifact of the Ambient Occlusion seeing the ballshadow as an object (which it kinda is). Present in 10.6 as well. Only fix I know of is to make sure the shadow z heights are as low as possible without clipping, so the AO applies as little to it as possible.
Other solution is to turn off the AO entirely, which some people prefer anyway.

[wiesshund]

 

Hi VPX 10.7.0 (Rev 111)
 
I am noticing a faint circle around the ball shadow.. 
 

That's an artifact of the Ambient Occlusion seeing the ballshadow as an object (which it kinda is). Present in 10.6 as well. Only fix I know of is to make sure the shadow z heights are as low as possible without clipping, so the AO applies as little to it as possible.
Other solution is to turn off the AO entirely, which some people prefer anyway.

 

Instead of using prims for the ball shadow, i use flashers
they dont seem to have the ring, at least as far as i can tell

they also seem to be easier to keep them from shifting transparencies depending on what other objects they run over.

[ronaldvg]

Something about my sound was really bugging me... and now I just seen what's happening. (Dunno if this is a bug or not though).

 

I currently keep two Vpinball.exe files in my install... latest 10.6 and the latest 10.7.  I rename one of them if I need to go to the other. Generally, if I tweak a table I always do it in 10.6 because if I save it in 10.7 then it won't load properly in 10.6.

 

But I noticed that whenever I switch between the .exes my sound setting alters each time. I have 10.6 set as 7.1 surround. But it always defaults to 2.1 if I ever use 10.7 exe. Similarly I like to have 10.7 set to enhanced 7.1. But if I use 10.6 at all that switches to standard 10.7. I don't have to load any tables, just opening the other exe will do it.

 

Like I say, you might consider my switching files like this to be non-standard use, but I was wondering why 10.6 kept sending flipper sounds to back glass.

There is a new version of 10.6 released at about the same time as this new Sound option became available. If you use that executable you will be able to choose the Enhanced 7.1 in 10.6 and the sound option is retained. I believe it is 10.6.2 ?

 

edit: link Visual Pinball X (Standalone EXE) - VPForums.org

 

edit 2: Sorry I just saw that Thalamus already answered this question

Edited by ronaldvg, 19 April 2021 - 07:49 PM.

[lukpcn]

Was wondering, for some like myself who don't have powerful CPU or GPU some particular tables are stuttering, maybe it would be a good idea to have opportunity to be able to switch on/off via command line parameter the following switches in gfx options:

- AO

- AO Update

- ScreenSpace Refl.

- Reflect dynamic Elements On Playfield

- Elements Detail Level (be able to set that level 1-10)

[ronaldvg]

Was wondering, for some like myself who don't have powerful CPU or GPU some particular tables are stuttering, maybe it would be a good idea to have opportunity to be able to switch on/off via command line parameter the following switches in gfx options:

- AO

- AO Update

- ScreenSpace Refl.

- Reflect dynamic Elements On Playfield

- Elements Detail Level (be able to set that level 1-10)

You can already change the settings per table in the table options and those settings are saved inside the table.

[lukpcn]

 

Was wondering, for some like myself who don't have powerful CPU or GPU some particular tables are stuttering, maybe it would be a good idea to have opportunity to be able to switch on/off via command line parameter the following switches in gfx options:

- AO

- AO Update

- ScreenSpace Refl.

- Reflect dynamic Elements On Playfield

- Elements Detail Level (be able to set that level 1-10)

You can already change the settings per table in the table options and those settings are saved inside the table.

 

Ah yes, forgot about that possibility. Thanks

[ebor]

Hi,

I Have the same issue with this :

"is it me, or doesn’t the script editor accept the “Enter” key for a new line ?!?"

rev 133.

Is there something to do ?

Thx

[wiesshund]

 

Hi,

I Have the same issue with this :

"is it me, or doesn’t the script editor accept the “Enter” key for a new line ?!?"

rev 133.

Is there something to do ?

Thx

 

can not replicate that
enter goes to a new line
not seeing an option to not have it do it either

[ebor]

it was the same for me with previous releases of v10.7. Ok with 10.6.2.
Is it ok for all the other people I asked on another french forum

[Niclase]

Hi all. Great work on the vpx 10.7 beta. Is there any bug tracker online or is it all in the dev's hands? Was thinking about the F11 FPS measuremets that seem off (think someone posted about this earlier), overall i get avg. FPS approximately 1.5 times higher then the current FPS which seems odd.

 

/ Niclas 

[ryesteve]

When launching 10.7, the first table I load gives me a "could not create sound buffer for load" error.  Never saw that on previous versions.  Doesn't matter which sound driver I use.  Any ideas?

[toxie]

 

We already crank up the windows timer resolution on our own, so this is not needed for VPX or PinMAME.  

(also nowadays that trick with using other apps that do this does not work anymore, as Windows 10 by now "tries" to keep the timer resolution to its default value for each app)

 

Weird. Somebody else around here with a Fraps license that could check this?

 

 

 

 

 

 

I have fraps license

But i do not really see any behavior different from not having fraps running
F11 always induces load, and fps will drop from it's max uncorked speed

but unless the PC can not maintain the 60 fps, it should not budge

Interesting.. How many milliseconds (or fps) are lost when employing the F11 menu?

We are talking my GPU-less laptop
so that is probably not worth exploring
On my desktop it is probably not very noticeable

Laptop on example table, with vsync off will go from over 100fps to down to around 60 or so

 

That's really really weird. And you're sure that this is with the 'simple' stats (not the detailed/approximate GPU profiling stats)?

Cause for me, on my laptop (NVIDIA though) it drops from 180 (measured with reshade) to 178.