1031 replies to this topic

[krazyscotsman]

Just wanted to thank everyone. Love VPX. My wife and I play all the time. 

Edited by krazyscotsman, 05 August 2018 - 04:36 AM.

[Steve39]

Just got back into VP and have to say, all this work is awesome. Thank you.

[fuzzel]

I'm sure you guys don't remember this, but I mentioned some problems I was having with weird, white artifacts on my ball images.  It turns out it is related to the "overwrite ball image" option in the preferences.  

 

More discussion here:  https://www.vpforums...672#entry410856

I tried to reproduce the white artifacts you mentioned but I'm not sure if I really did it the right way. Can you send me the images and settings you used and a screenshot how the ball looks like? If you use a decal the alpha value of the decal image is used to blend onto the ball (e.g. the scratches on the metal ball) in logo mode however the decal image is additively blended. And that could cause the artifacts.

Edited by fuzzel, 05 August 2018 - 07:48 PM.

[Drybonz]

There's a whole thread about it with pictures at the "other site".  Pictures are a pain here.

[toxie]

I boiled it down to a case where just using the same ball image once within the blank table and once within the global preferences results in different renderings, and that should not be the case, right?

(and the ball test image i got from drybonz has no alpha at all)

[FreeLunch]

Out of curiosity, how much trouble would it be to fix the Editor UI and Player's text elements with variable Windows DPI Scaling? Given a DPI Scaling above 100%, Compatibility DPI Scaling in Windows 10 using System or System (Enhanced) will scale the aspect ratio correctly on the Editor UI, but the Player will display undersized or oversized. Not using DPI Scaling or using Compatibility DPI Scaling by Application does not fix the UI scaling or text elements in the Player.

 

I think this is a minor issue all things considered, but it's a convenience fix I would appreciate if there's ever a time Visual Pinball becomes too perfect and there's nothing better to work on. Regardless, thank you to all the devs for making Visual Pinball the amazing pinball sandbox it is today.

[fuzzel]

The UI is a mess and very outdated. I tried to optimize it a bit and made it a bit more usable from a developer's point of view but there are some wired hacks in there that makes it impossible to optimize every aspect of the UI (e.g. the preferences). So in an ideal world we have to drop the complete win32 UI and port everything to QT or any other highend UI framework, but that would mean to rewrite more than half of the whole application and some aspects are bound to the old UI e.g. the COM interface and how it is connected to the preferences of the elements.

[Slydog43]

This question is probably not in the right spot, but here goes.  Checking the CommandReference.txt file (which is awesome by the way) I was looking at the Light object and how to change its Color and FullColor.  According to the text file

 

*Color(OLE_COLOR) - 'normal' color

*ColorFull(OLE_COLOR) - full brightness color

 

so they can't be changed in script, but they can!!!  I like this feature, just wondering if its ok to use or not.  

 

I just use something like Light1.Color = 255 'Red and the light will be red.  Am I missing something (I have only tested on an example table with a round light in middle)

 

 

I just found the same thing with Primitve.Material as long as static is not checked  (although material is not mentioned in the CommandReference.txt, I think it should be)

Thanks

Edited by Slydog43, 10 August 2018 - 11:31 PM.

[wrd1972]

Think I found a crash bug.

Maybe someone else can confirm if its a widespread issue. Or something localized to my system..

 

If I create a new collection, and attempt to move that collection DOWN in the list. VP crashes every single time.

[Slydog43]

wrd I think your right, happens on Example table on my system also

 

You don't even have to create a new collection, just try to move down an existing collection down.

Edited by Slydog43, 11 August 2018 - 03:53 AM.

[kiwi]

Can we still use this thread for requests?

 
If it were possible to visualize the XY coordinates of the center of the walls in the property panel, and if possible to handle them.

 
Thanks for all the time you have dedicated to improving VPX!

[fuzzel]

Think I found a crash bug.

Maybe someone else can confirm if its a widespread issue. Or something localized to my system..

 

If I create a new collection, and attempt to move that collection DOWN in the list. VP crashes every single time.

is fixed in the next beta

[nFozzy]

 

This question is probably not in the right spot, but here goes.  Checking the CommandReference.txt file (which is awesome by the way) I was looking at the Light object and how to change its Color and FullColor.  According to the text file

 

*Color(OLE_COLOR) - 'normal' color

*ColorFull(OLE_COLOR) - full brightness color

 

so they can't be changed in script, but they can!!!  I like this feature, just wondering if its ok to use or not.  

 

I just use something like Light1.Color = 255 'Red and the light will be red.  Am I missing something (I have only tested on an example table with a round light in middle)

 

 

I just found the same thing with Primitve.Material as long as static is not checked  (although material is not mentioned in the CommandReference.txt, I think it should be)

Thanks

 

Yes but it uses some kind of reversed hex color code. You can use the RGB() function, so for example RGB(255,255,255) for white.

[kiwi]

With an old version of VP we had the option to smooth or not smooth the primitive, now the default primitive is always smooth, can we get this option back?

[toxie]

You mean vertex normal smoothing? (i.e. a faceted look vs using interpolation)

[kiwi]

Like the good old VP915, the primitive had the checkbox for "Smooth Side Normals".

[fuzzel]

oh that's old but honestly you should do all the primitive stuff in a 3D tool like Blender or 3DSMAX and import the mesh. The build in mesh doesn't have a future and will be removed in VP11 for sure.

[toxie]

Maybe we should add vertex normal import, too, then (or do we already have it, i totally forgot)?!

[fuzzel]

It's all in there already

[toxie]

Thanks, in that case kiwi could just do the facetted look within Blender, etc on his own, export, and be good.