740 replies to this topic

[sliderpoint]

I've had a few crashes. Here is the .dmp file:  https://www.dropbox..../crash.zip?dl=0

 

-Mike

[wrd1972]

Really digging the new feature that shows which images are in use for the table. This greatly helps to weed out useless images and reduce table size.

 

Am I correct in saying that the "in use" feature does NOT detect images that are apply to PRIMs which are only applied via scripting? And NOT into the image field within PRIM properties? Would it be possible to audit the script for the image name and add the "in use" indicator within the image manager?

 

Also can a similar 'in use" indicator be added to the materials as well?

 

Thanks guys.

[toxie]

It will not detect script usage, yes.. That would be much more complicated as what is there right now..

[vogliadicane]

what about a numeric value for the day night slider? Just showing up (not editable). This would be handy, if you changed it and there is an update for a table. Now, we must guess. I switch between the two versions and compare optically, which is ok, but a value would facilitate this.

[fuzzel]

I've had a few crashes. Here is the .dmp file:  https://www.dropbox..../crash.zip?dl=0

 

-Mike

The call stack only shows functions in the  Windows kernel so it's not really helpful.

[sliderpoint]

The call stack only shows functions in the  Windows kernel so it's not really helpful.

 

 

 

 

Thanks, I'll try a reboot.   Maybe just too many things open.

[gStAv]

Can I some how stop the start a table dialogue every time I start VPX?

Just find it a bit annoying as I just want to edit a table directly and not run it and as it autostarts I have to close the window and open a table from the menu.

No biggie, but would be neat with a checkbox option to skip this.

[hauntfreaks]

Can I some how stop the start a table dialogue every time I start VPX?

Just find it a bit annoying as I just want to edit a table directly and not run it and as it autostarts I have to close the window and open a table from the menu.

No biggie, but would be neat with a checkbox option to skip this.

preferences>editor opions
bottom check box <--uncheck

[Shockman]

what about a numeric value for the day night slider? Just showing up (not editable). This would be handy, if you changed it and there is an update for a table. Now, we must guess. I switch between the two versions and compare optically, which is ok, but a value would facilitate this.

This is a personal preference feature. I would rather set it to my visual preference than a number, even a table default. Table updates are not likely to change this setting, but ports from earlier versions of VP will create this option. For example my mmpac was created before this feature and therefore can only use a small portion of the slider before the effect becomes whack. I think this is fairly common.

 

The idea of a reset to default for this that the table builder can set is not a bad one though. But I think it still might be best to go with what looks good to you.

 

A better idea might be to let the builder set a range of the sliders to be minimum to maximum. Then the clock sync may, though be much more subtle, remain realistic.

[sliderpoint]

I'm confused, that slider is already just representing a number (0-100).  Are you saying you would also like to know what that number is when moving the slider?

 

-Mike

[vogliadicane]

Table updates are not likely to change this setting, ...

 

 

A better idea might be to let the builder set a range of the sliders to be minimum to maximum. Then the clock sync may, though be much more subtle, remain realistic.

 

 

First sentence: I didn't mean that, maybe I wasn't clear enough. I meant, yes the first time I chose this setting manually and optically, and everything fine. If there is an update for the table I would like to NOT have do that procedure again, but only look at the numeric value I liked when customizing the first time and use it for the updated table.

 

Second sentence: Agree 100% I already proposed that (somewhere in this thread)

 

I'm confused, that slider is already just representing a number (0-100).  Are you saying you would also like to know what that number is when moving the slider?

 

-Mike

 now I'm confused, or we talk about different things. I'd like to see the value, that the slider's position represents as a number. e.g. Like this:

 

[hauntfreaks]

 

Table updates are not likely to change this setting, ...

 

 

A better idea might be to let the builder set a range of the sliders to be minimum to maximum. Then the clock sync may, though be much more subtle, remain realistic.

 

 

First sentence: I didn't mean that, maybe I wasn't clear enough. I meant, yes the first time I chose this setting manually and optically, and everything fine. If there is an update for the table I would like to NOT have do that procedure again, but only look at the numeric value I liked when customizing the first time and use it for the updated table.

 

Second sentence: Agree 100% I already proposed that (somewhere in this thread)

 

I'm confused, that slider is already just representing a number (0-100).  Are you saying you would also like to know what that number is when moving the slider?

 

-Mike

 now I'm confused, or we talk about different things. I'd like to see the value, that the slider's position represents as a number. e.g. Like this:

 

 

I like the idea.... other reasons would be when your questioned "what do you have the slider set to" you could give a # 

wait did shock just recommend to set a restriction for the end user to set the slider.... time for your meds sir...

Edited by hauntfreaks, 12 October 2017 - 07:04 PM.

[sliderpoint]

Sure seeing the number wouldn't be a bad idea.  Not sure why the need to be so specific but that seems fine.

 

As for defining your own start and end values, that seems pretty lazy.  My opinion is that the table author should try to make a table that can work at both ends of the slider (0 being excluded as that just shuts it off).  I think most people change the slider to their preference anyways.  Maybe more use that daytime sync than I think.

 

-Mike

Edited by sliderpoint, 12 October 2017 - 07:06 PM.

[vogliadicane]

ooh I was wrong I didn't propose the night/day min and max in this thread, but here: http://www.vpforums....757#entry389287

sorry

 

and I think Shock meant the same.

 

Edit: actually I would really like to use the automatic day night feature, but I disabled it, simply because it is too extreme. On the other hand if I play a table at daylight (very rarely) I think, no my night customizations don't really fit here. An author's choice to set, what if it is played a t daylight what if at night would solve that.

 

Edit 2: maybe like this (if the user chose to let VPX do the lighting, the range from the author is used):

 

Edited by vogliadicane, 12 October 2017 - 07:44 PM.

[DJRobX]

ooh I was wrong I didn't propose the night/day min and max in this thread, but here: http://www.vpforums....757#entry389287

sorry

 

I think this is an excellent idea.  I also wanted to use the automatic day/night option early on, but I think it's just not useful in its current implementation with the majority of tables. 

 

For loading old tables, the default min/max could be the table's current day/night setting.   That would mean tables saved in previous versions are always limited to their current value, which seems appropriate since most tables aren't designed to look right at the extremes.    

Then new tables with a range specified could be "scaled" with the min/max values with the real day/night time. 

Sure seeing the number wouldn't be a bad idea.  Not sure why the need to be so specific but that seems fine.

 

As for defining your own start and end values, that seems pretty lazy.  My opinion is that the table author should try to make a table that can work at both ends of the slider (0 being excluded as that just shuts it off).  I think most people change the slider to their preference anyways.  Maybe more use that daytime sync than I think.

 

 

That would be ideal, but it seems pretty clear it's not realistic.  Lighting in VPX is a complex topic, and I think a lot of table authors struggle to make it look right in just one setting.    I doubt anyone is using day/night sync right now because so few tables support it.     This "lazy" method would make it easier for authors and/or end-users to configure their tables to support it the way they want. 

[hauntfreaks]

what might be cool is if the author or whoever could set the tables "zero" point

-10 -9 -8 -7 -6 -5 -4 -3 -2 -1   0   1 2 3 4 5 6 7 8 9 10

 

make sense?

[BorgDog]

A change a feature request.

 

Can the Disable B2S checkbox be moved to the Video Options page, maybe next to the Use always FS backdrop settings.  While it is related to DOF, I think it makes more sense to be in video options, or maybe have it in both places and either one can change it.  While most people will only have to change it once, I turn mine on and off all the time when working on tables and often while changing video options settings as well.

 

Also, is there a way to turn off the Falloff circles on light objects?  I like that they stay on now when you adjusting light points and such, but having all of them on all of the time is just a bit too many lines for my old tired eyes.

 

Thanks.

[mrjcrane]

Proposing New Feature for VPX 10.5 or later for cabinet support: Suggest adding a feature "Rotate Table by Degree 0, 90, 180 & 270 Degrees" in the VPX Video Configuration Screen. Pinball FX3 has this same feature in its "Cabinet Mode".  Adding it to VP 10 would make it possible to run the default OS Level display in Portrait mode (instead of Landscape), then then rotate the table display separately in VPX as needed whether we run the VP tables on a Desktop in Landscape mode (which is probably what a lot of people do) OR whether we have a full blown VP Cabinet that is better suited for the FS oriented tables. I'm kind of new to the forums so my apology if this topic has already been proposed.

 

The basic idea here is that when an FS designed table rotated 90 degrees AND when the PC Display at the OS level is set to Portrait Mode, and when the display monitor has been rotated 90 degrees (like a VP Cabinet)  it should look normal, like a cabinet where the playfield is long and narrow and all the aspect ratios still look correct.

 

But I think there are some extra advantages to setting the OS Default display mode to Portrait for a VP Cabinet

 

I'll explain later why I think this is a very cool idea for game cabinets.  To see where I am headed with this, physically rotate your desktop monitor 90 degrees like a game cabinet then change that monitor to display to Portrait instead of Landscape and desktop looks normal but just presented lengthwise with a narrow width (just like a game cabinet). Now fire up VPX and try to run a normal game like JP's Ghostbuster Slimer and try a FS game like T2Chrome FS. So, if the games had a user level control for the specific rotation of the table by 90 degrees, I think it would adjust the aspect ratios correctly so the playfields will still look correct.  BUT now the VP Cabinet can also easily handle Steam, Pinball X, Pinball Arcade, Pinball FX3, MAME, iTunes making a VP game cabinet into super cabinet that looks like an unassuming pinball machine. And you can drop into the OS with ease on a VP Cabinet and maneuver between other Apps and games that may be in the cabinet.

 

Happy to work with anyone or be a tester for the "Table Rotation Feature" if it is possible. I'll try to post some pictures of this idea when I can figure out how to. - mrjcrane

 

 

 

[Thalamus]

I agree on the falloff circles. I wouldn't mind to see it solved by more available layers to play with.

[Shockman]

what might be cool is if the author or whoever could set the tables "zero" point

-10 -9 -8 -7 -6 -5 -4 -3 -2 -1   0   1 2 3 4 5 6 7 8 9 10

 

make sense?

Who needs their meds, again?

 

What I suggested is to set a min and max for the clock to use. Not the end user.

 

I know, stupid to suggest visuals stay in a realistic range, because .... reasons. Right? 

Edited by Shockman, 13 October 2017 - 12:47 AM.