4027 replies to this topic

[Segovia11]

Segovia11, on 01 Jun 2020 - 10:22 PM, said:

 

                       The VpTemp fonts sometimes need to be manually deleted, normally Visual Pinball will delete them during shut down. Visual Pinball will manufacture more VpTemp fonts when it fails to delete them.  -  i had less problems with the VpTemp fonts when the image 

manager was reduced to 456.  Although it may have been a coincidental moment.

 

Which table did you use that shows this problem?

 

Was only able to replicate the bug when the Image manager exceeded 456 images - using 10.7 beta 4134 - with my TexasPoker Table only - bug was resolved after deleting the unused images.

I could not replicate the bug with my other two Tables - Skittles and Invader.

Edited by Segovia11, 02 June 2020 - 11:22 PM.

[Umpa]

Newby here but I am having an issue with exiting a vpx table in Pinup Popper Frontend with the last few 10.7 builds.  In REV4098 and prior 10.7 builds when I press Q to exit a table it closes the table - normal behavior.  In any of the later builds including REV4139 the table stays open and active and I have to close it using the esc key.  I have reinstalled REV4098 after trying the new builds and it goes back to exiting correctly.  Am I the only one experiencing this?  Is there a change I need to make in pinup popper? 
 
Thanks

Same for me. I just updated to latest vpx and have the same behavior. Did you figure out what needs to be changed?

Sent from my SM-G965U1 using Tapatalk

[ssteph1984]

I only have problems with the pinup popper front end.  In Pinbally and Pinballx the vpx tables exit fine.  Unfortunately no one has reached out to help yet.  I really appreciate all the work being done on the 10.7 beta.  Hopefully someone who cares about this problem will offer help.

[Shockman]

 

Just tried the latest beta (4134) and the plunger doesnt work correctly on Fluppers Diner and White Water. It pulls back really slowly in small increments and seems to be now underpowered. Is this a known bug?

 

This is not a bug, its a feature. It pulls back slower, but the force, etc is exactly the same. This was optionally (see kiwis post) changed to help desktop/keyboard players to be more accurate with the plunger.
 

...

 

 

It pulls back quite a bit slower. I don't understand. What am I missing? There has always been a pull back speed to set in the editor. There still is. This 'feature' does nothing but destroys the effect of all authors that have used that setting to their liking. Wouldn't the windows settings for key repeat speed effect this? Meaning that those desktop users that have set the plunger speed to their liking could be using different numbers to produce the same speed? Regardless, if you change the speed universally users are going to have to change the numbers on every table to get back what they worked at.

 

The speed using keyboard keys is too fast. But couldn't you have changed the default that would be over written by editor settings instead of added value so those that have set the speed to their liking would still be set?

Edited by Shockman, 03 June 2020 - 02:47 AM.

[NailBuster]

The reason Pinup Popper does not close with latest builds of vpx:

 

Windows title of vpx player use to be  "Visual Pinball Player"

 

in latest builds, the vpx player window title is Empty/Blank.

[fuzzel]

rev4142 is up:

 

- add player window title name (fix for different front ends)
- fix copy paste errors for new custom settings in POV files
- fix flasher color button look
 

[toxie]

 

 

Just tried the latest beta (4134) and the plunger doesnt work correctly on Fluppers Diner and White Water. It pulls back really slowly in small increments and seems to be now underpowered. Is this a known bug?

 

This is not a bug, its a feature. It pulls back slower, but the force, etc is exactly the same. This was optionally (see kiwis post) changed to help desktop/keyboard players to be more accurate with the plunger.

 

It pulls back quite a bit slower. I don't understand. What am I missing? There has always been a pull back speed to set in the editor. There still is. This 'feature' does nothing but destroys the effect of all authors that have used that setting to their liking. Wouldn't the windows settings for key repeat speed effect this? Meaning that those desktop users that have set the plunger speed to their liking could be using different numbers to produce the same speed? Regardless, if you change the speed universally users are going to have to change the numbers on every table to get back what they worked at.

 

The speed using keyboard keys is too fast. But couldn't you have changed the default that would be over written by editor settings instead of added value so those that have set the speed to their liking would still be set?

You did see the multiple posts mentioning that this new behaviour is optional?

And i did set it as the new default, as it works IMHO much much better for desktop/keyboard/button players on all(!) my tested tables.

 

In addition, the main new feature here is, that the plunger will retract after being at the end pos for 1s!

Edited by toxie, 03 June 2020 - 12:37 PM.

[NailBuster]

Latest build shows the proper win-title now for 'Visual Pinball Player'.  

 

May want to keep in mind that 10.7 vpx windows are still different than 10.6:   if I run 10.6 and compare the windows in taskmanager (and titles) with 10.7 (just blank table) you will see a missing window with the [tablename] is not there.

 

Rob did think that b2s may use the [tablename] in window title for loading.   This doesnt' affect pinup and b2s seems to be working ok....  but perhaps if some weird b2s issues come up in future that may be something to look at.

Edited by NailBuster, 03 June 2020 - 08:17 PM.

[davidcd13]

with the latest version:

When "force exclusive fullscreen mode" is activated and you enter "interactive edit table" (f6), then "Escape", then "Quit to editor". VPX hangs, cannot return to the editor.

If "force exclusive fulscreen mode" is deactivated, it works, we can return to the editor.

[fuzzel]

That's a known issue. At the moment it's unclear what causes this.

[Segovia11]

Non Critical Bug report - VPX_7_beta_rev4142 - OPS(Operating Sytem) Windows 10 64 bit - VPinballX Application is with compatibility mode Windows XP (Service Pack 3)

 

All layers in the Layers editor Toolbar vanish when you assign selected elements to a selected layer, without first selecting an element/table object - (In short - If nothing on the Table is selected first then all Layers will disappear - this only occurs when selecting with the hand icon) 

 

Although one should be selecting an element / table object first before assigning to a layer. 

 

Its not a critical bug - all is corrected after reloading the table.

 

Vanish = to assume the value zero

            = to cause to disappear      

            = to pass quickly from sight

 

Operating Sytem = the low-level software that supports a computer's basic functions, such as scheduling tasks and controlling peripherals.

 

Library = a place in which literary,musical,artistic or reference materials (such as books, manuscripts,recordings,films,or picture images) are kept for use but not for sale.

 

Keep Up the good work & Thank You

Edited by Segovia11, 06 June 2020 - 11:29 PM.

[kiwi]

It is just an irrelevant oddity, it is the second case that I see, it is not referred only to this beta because it also does it with the official version 10.6.

 
Take Baywatch and select layers 1 and 3 as visible, select the ramp "RampLG6", top left, in the area of the lifeguard tower,
if the point at the top of the ramp is selected, "Gate25" is also highlighted.

 
In the second case, instead of the ramp, there is a control point of a wall which, when selected, highlights a gate.

 

[reggert32]

Hi,

 

Been updating the 1.07 with the latest version every time one comes up. The interface has become very nice and the new features are incredible.

Only problem i have been having is that loading a table take a very long time and after that starting a table is also very slow.

 

Is there some setting that is causing this or is it a bug in the current beta ?

Loading the same table in the 1.06 final is only a matter of seconds and starting also.

 

best regards,

 

reggert32

[fuzzel]

That is strange. The loading process was optimized in 10.7 and for me it's really noticeable compared to 10.6. So something must be different on your system

[toxie]

Which table did you test exactly?

[Segovia11]

Non Critical Bug report - VPX_7_beta_rev4142 - OPS(Operating Sytem) Windows 10 64 bit - VPinballX Application is with compatibility mode Windows XP (Service Pack 3)

 

Dear Fuzzel,

                     The screen flickers white after using the zoom in/out in backglass view and during scroll movements.

                     The flicker event corrects it-self when you move back to Table view after untoggling the backglass view.   

                     The non critical bug event also occurs in reverse order and will correct it-self after moving into the opposite view.    

Edited by Segovia11, 06 June 2020 - 11:29 PM.

[reggert32]

Lots of different tables : Independance day, Terminator 2, NBA Fastbreak, Jurassic Park, Tee'd Off, Robocop, 24, The Flintstones and more. Sometimes they load fast and take ages to start playing and sometimes it takes a long time to load and when pressing F5 they start almost instantly. So i don't know what is the problem, because with 10.6 i have no problems at all.

[Segovia11]

Non Critical Fatal error shader compilation Bug report - VPX_6 and 7_beta_rev4142 - OPS(Operating System) Windows 10 64 bit - VPinballX Application is with compatibility mode Windows XP (Service Pack 3)

 

Dear Forum,

                     Just Changed Post Proc AA from FXAA to Quality SMAA, since the change i haven't had a fatal error: shader compilation failed! Unkown (0xffffffff: n/a)Projects\VP10\RenderDevice.cpp:799) message which would only occur after working with my TexasPoker Table.

 

Will test my TexasPoker Table with FXAA selected again. Will confirm error, If i can replicate the fatal error message. Unless somebody else has a definitive answer, these problems tend to be blurry in nature!

                    

Web Site SMAA vs FXAA Quote

"SMAA, or Subpixel Morphological Anti-Aliasing, uses the same technique as FXAA — that is, MLAA (Morphological Anti-Aliasing).  SMAA addresses this, and provides even better anti-aliasing and less blurring than FXAA. It's the joint work of Crytek and the Universidad de Zaragoza in Spain.7 Jan 2012 "  

 

 

 

 

FXAA and SMAA is interacting with shaders - self study result so far -  - my subject matter knowledge is gapped - more self study needed

 

https://en.wikipedia.org/wiki/SMAA

https://en.wikipedia...e_anti-aliasing

 

 

The above issue resolved its self after removing Windows Xp SP3 compatibility mode.

Edited by Segovia11, 23 June 2020 - 07:53 PM.

[toxie]

Is there any reason that you use 'VPinballX Application is with compatibility mode Windows XP (Service Pack 3)' ?

Cause everything should just work fine without any compatibility mode.

[Segovia11]

Dear Toxie,

                   Thankyou for the update. Will remove Windows XP compatibility mode.