4027 replies to this topic

[wiesshund]

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?

usually means a sound file in the table is not right
in a format it can not read or encoded oddly

 

10.6 for example will give that error if you have it open a table that has OGG files in it

 

What table is giving this error?

[wiesshund]

 

 

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.

 

Just hitting F11 once
but like i said, this thing has no GPU, your laptop does
Anything can drop FPS on this

 

 

[ryesteve]

 

 

What table is giving this error?

 

 

Unfortunately, this issue is more sporadic than I originally thought.  It's not as if some always give me the pop up and some never do.  A couple tables where I've usually gotten the pop up are Hot Shots (rascal) and NBA Fastbreak (VPW)

[wiesshund]

 

 

 

What table is giving this error?

 

 

Unfortunately, this issue is more sporadic than I originally thought.  It's not as if some always give me the pop up and some never do.  A couple tables where I've usually gotten the pop up are Hot Shots (rascal) and NBA Fastbreak (VPW)

 

 

Is this with fresh starts of vpx, or after loading multiple tables in the same vpx session?

[ryesteve]

Is this with fresh starts of vpx, or after loading multiple tables in the same vpx session?

 

 

I've only ever seen it on a fresh start.

[Niclase]

 

 

 

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.

 

Just hitting F11 once
but like i said, this thing has no GPU, your laptop does
Anything can drop FPS on this

 

 

 

 

Here's a video of fraps vs F11 on my cabinet

 

https://youtu.be/YZDWOo1OXlk

 

/ Niclas

[toxie]

I've been told to report here, so if it's wrong time/place don't blame me 

 

But this morning while trying out 10.7.0-133 67fe160 I found that The Getaway table (nFozzy v1.2 built with 10.4) exhibited strange behaviour in that the kickback plunger was operating all the time right from when the table first loads. Dunno if that's a fault of table or a bug in 10.7 but it plays flawlessly in 10.6.

 

EDIT:  Let me add that I simply swapped the 10.6 exe file for the new one. If I require any of the other files in the download which is causing this, then that's my fault and apologies.

mfuegemann contacted me now on this and says that the fix here is to simply set the autoplunger checkbox.

[toxie]

 

 

 

 

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.

 

Just hitting F11 once
but like i said, this thing has no GPU, your laptop does
Anything can drop FPS on this

 

 

Here's a video of fraps vs F11 on my cabinet

 

https://youtu.be/YZDWOo1OXlk

 

/ Niclas

 

Oh wow. This is really strange, also as it makes the builtin FPS measurement then kinda useless.  :/

Niclas, whats even more confusing is that once it dropped 'only' from 175 to 165 in your vid, and the other times much lower.

[Niclase]

 

 

 

 

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.
 

Just hitting F11 once
but like i said, this thing has no GPU, your laptop does
Anything can drop FPS on this
 

 
Here's a video of fraps vs F11 on my cabinet
 
https://youtu.be/YZDWOo1OXlk
 
/ Niclas
 

Oh wow. This is really strange, also as it makes the builtin FPS measurement then kinda useless.  :/
Niclas, whats even more confusing is that once it dropped 'only' from 175 to 165 in your vid, and the other times much lower.

The time it went down to 165 i believe i pressed F11 to quick and it was the "other" F11 mode. I press F11 a couple of times more with larger time span between the presses with the normal F11 mode and it gives the same strange result.

Fraps works great by the way, love it as a complement to F11 since some tables might be troublesome in the middle of play and having the fraps fps count visable is not that disturbing.

Edited by Niclase, 20 April 2021 - 09:20 PM.

[toxie]

 

 

Development Team please find enclosed a VPX_7_beta_rev129 bug report 

1. From the main editor position VP10.7 crashes when you press F1. It also manufactures a dump file & a crash report.

 

 

 

F1 crash

Crash report VPX rev127 (c9c069f)
============
Process: VPinballX.exe
Reason: 0xE06D7363 - UNKNOWN at 0023:76D9A6E2
Thread ID: 0xD94 [3476]

Fixed. Now shows the About dialog.

[tgx]

Not sure if this has been reported but if I try to resize any table in 10.7 using F6 or camera mode,

when I exit the mode 10.7 crashes. Thus I am unable to interactively adjust any game camera settings

since they do not get saved when the app crashes. I can. however, go old school VP9 and manually

set the table settings.

[wiesshund]

Not sure if this has been reported but if I try to resize any table in 10.7 using F6 or camera mode,

when I exit the mode 10.7 crashes. Thus I am unable to interactively adjust any game camera settings

since they do not get saved when the app crashes. I can. however, go old school VP9 and manually

set the table settings.

Is it leaving a crash.txt you could paste?
i've not run across that one yet

[toxie]

Not sure if this has been reported but if I try to resize any table in 10.7 using F6 or camera mode,

when I exit the mode 10.7 crashes. Thus I am unable to interactively adjust any game camera settings

since they do not get saved when the app crashes. I can. however, go old school VP9 and manually

set the table settings.

And this is with the current version (1st post here)? And which command line options do you use, or just a plain start of the VPX exe?

[Juwellez]

Just Updated to VPX 10.7 133 and notice that when running the new sound setting 7.1, that my right flipper sound has diminished.  switch back to old 7.1 setting and the sound is matched to left flipper sound levels. Last couple tables updated  Baywatch, Batman dark night(skitso) just to name a few.  Everything else is working fantastic... Thanks for your hard work!!!!!!!!!!!

Edited by Juwellez, 21 April 2021 - 03:18 PM.

[Thalamus]

Juwellez : Sure you're "sound" isn't stereo or something that is not optimized for the new and improved ?

[wiesshund]

Just Updated to VPX 10.7 133 and notice that when running the new sound setting 7.1, that my right flipper sound has diminished.  switch back to old 7.1 setting and the sound is matched to left flipper sound levels. Last couple tables updated  Baywatch, Batman dark night(skitso) just to name a few.  Everything else is working fantastic... Thanks for your hard work!!!!!!!!!!!

Keep in mind, the 7.1 enhanced setting is kind of for specific setups, and may not work well on all setups, and in fact might work worse for some.

 

works well for thalamus, works like ass for me, but we have entirely different audio setups

[Juwellez]

Thalamus - as Weisshund says may be table itself...   I tested the original before it was incorporated into 10.7 and was no issues.  Will check out some other tables and see if it is isolated or not....  I had to edit some scripts in a few EM tables that allowed for it and it balanced out.  had to change the left and right flipper sound settings to match  -0.5 to both one had 0.5 and the other -0.5.  not at my pinball machine so can't grab the actual script at this time.  These were EM tables though.

[NailBuster]

issue with changing "name" in vpx editor in latest build:   (confirmed with another)

 

start a blank table,  try changing/typing in the "name" of something (light..etc) and press ESC instead of ENTER and now the properties editor is stuck/frozen.

 

@toxie:  btw.. i pmd you here on some code changes ive been working on...

[wiesshund]

issue with changing "name" in vpx editor in latest build:   (confirmed with another)

 

start a blank table,  try changing/typing in the "name" of something (light..etc) and press ESC instead of ENTER and now the properties editor is stuck/frozen.

 

@toxie:  btw.. i pmd you here on some code changes ive been working on...

Confirmed
You are held hostage at that point if you need to do anything to properties

[toxie]

@toxie:  btw.. i pmd you here on some code changes ive been working on...

yes, i saw that, thanks! currently short on time for excessive reviews, but will not forget about it!