1488 replies to this topic

[Shockman]

I don't think the ratio should make any difference. But if it did then yes "Test Cabinet" probably would make more sense.

I did not suggest it because we have more users, and would have suggested it if we had in fact much less users. If I noticed "Test Cabinet" I would wonder about that too.

 

DeskTop users are playing tables not taking advantage of a programs test mode.

 

Afford a cabinet? The arrogance did carry over from VP9. I have played VP on a cabinet. I have the main electronics needed, almost all the material to build a cabinet. the skill too. I don't ask what a Vcab costs, I ask if it is looks less flat and fixed, and it turns out to be more so, if I would use it with 3 vintage pinball arcades in town, if it's real enough to be more immersive, if it's worth the space it would take up. etc. And the flippers look like they would dig in deep into the table if used unless fixed with layback then the back stuff is even more flat. In my opinion there are no hybrid pinball in this respect, but only real and video game and the option of some very cool controllers. About the only advantage for me to get a cabinet is that the VP program, less Muskuste (booted (ok more like shunned)) favors it in the development. Sometimes in evil ways like the VP9 nudging and sometimes in silly ways like this mislabel.

Edited by Shockman, 08 April 2019 - 10:55 PM.

[Umpa]

I don't think the ratio should make any difference. But if it did then yes "Test Cabinet" probably would make more sense.
I did not suggest it because we have more users, and would have suggested it if we had in fact much less users. If I noticed "Test Cabinet" I would wonder about that too.
 
DeskTop users are playing tables not taking advantage of a programs test mode.
 
Afford a cabinet? The arrogance did carry over from VP9. I have played VP on a cabinet. I have the main electronics needed, almost all the material to build a cabinet. the skill too. I don't ask what a Vcab costs, I ask if it is looks less flat and fixed, and it turns out to be more so, if I would use it with 3 vintage pinball arcades in town, if it's real enough to be more immersive, if it's worth the space it would take up. etc. And the flippers look like they would dig in deep into the table if used unless fixed with layback then the back stuff is even more flat. In my opinion there are no hybrid pinball in this respect, but only real and video game and the option of some very cool controllers. About the only advantage for me to get a cabinet is that the VP program, less Muskuste (booted (ok more like shunned)) favors it in the development. Sometimes in evil ways like the VP9 nudging and sometimes in silly ways like this mislabel.

I think there are alot more cabinet users than you think. Also you come on here after being away how long? Who cares what the damn label says. You want to play on desktop go for it. You cant come to terms building a cab ok. Who cares. Let's get this thread back on track. You can start another thread bashing on vpx and all the great work toxie, fuzzel and others have done. Damn.

Sent from my SAMSUNG-SM-G935A using Tapatalk

[gtxjoe]

The word Test is used because that setting is temporary, not permanent. If you toggle that checkbox and save table or close VP, it will revert back to the actual setting defined Preferences->Video. Call it Test Desktop or Test Cabinet, it doesnt matter, that checkbox is only meant for testing purposes

[Shockman]

@gtxjoe

Thanks for being constructive. I see it is temporary. Of course I never saved the table while in that test mode till just now. 

 

So if I do want to test my full screen settings I quit testing desktop. Still makes no sense from where I'm setting. what was a joke before is not anymore it should say test desktop if you are in cab mode and test cab mode if you are in desktop.

 

It makes sense after all for a cab user that wants to test desktop settings to see a button that says "Test Desktop", but I think you know where I could go from here.

 

Thanks again gtxjoe

Edited by Shockman, 09 April 2019 - 12:44 AM.

[rascal]

VPX developers and most of the table authors are so trying to make everyone happy with the ability to switch from desktop to cabinet and now even FSS. So lets not nit pick about some insignificant wording. It wouldn't be worth the coding to make it change from test desktop to test cabinet. We all know what it does, or will ask what it does. This is my opinion of course and just that.

 

I'm a desktop user and I approve this message.

Edited by rascal, 09 April 2019 - 01:05 AM.

[adamstillman]

 

Hey there,  with any version of 10.6 the monster faces on the playfield, on tom towers monsterbash, never light up,  tried different versions of 10.5,  still did not work.

 

I then tried the final 10.4 version and it worked fine.  also, this is with all the scripts, bass, ect with the 10.6 beta, the only thing i changed was the vpinballx.exe program,  so there is something definitely in there that causing this.

 

also, the light inserts are of different shade too, comparing 10.4 to 10.6 betas.  very possibly related...

 

Remember that when updating to 10.6 beta to also use matching/current bass.dll! Is that the case?

 

hi, when i download a beta i replace all the files in the beta, so all scripts, bass.dll.  everything get swapped out with the new beta..( after a backup )

 

re-downloaded monster bash 1.3 and tried again tonight.  still no lighting on the faces.. tried with 10.4 and it works..

 

i am just using 10.4 for mb so its all ok...using hyperfine to launch mb with 10.4, everything else is 10,6 beta

 

again.. all the files are from the beta, bass.dll, scripts, ect. are in my vpfolder,  only the vp exe...10.4 and 10.6 beta I'm swapping from.

 

does this make sense??

[Shockman]

VPX developers and most of the table authors are so trying to make everyone happy with the ability to switch from desktop to cabinet and now even FSS. So lets not nit pick about some insignificant wording. It wouldn't be worth the coding to make it change from test desktop to test cabinet. We all know what it does, or will ask what it does. This is my opinion of course and just that.

 

I'm a desktop user and I approve this message.

 

Changing it to "Test Cabinet" wouldn't make ANY sense nor be logical. You don't get it.

 

I understand they are trying to make everyone happy. That's why I thought they would be interested in this. It's not as logical and straightforward in one mode as it is the other because they couldn't be bothered as long as a certain one of those modes worked logically. 

Edited by Shockman, 09 April 2019 - 07:30 AM.

[Rawnei]

 

VPX developers and most of the table authors are so trying to make everyone happy with the ability to switch from desktop to cabinet and now even FSS. So lets not nit pick about some insignificant wording. It wouldn't be worth the coding to make it change from test desktop to test cabinet. We all know what it does, or will ask what it does. This is my opinion of course and just that.

 

I'm a desktop user and I approve this message.

 

Changing it to "Test Cabinet" wouldn't make ANY sense nor be logical. You don't get it.

 

I understand they are trying to make everyone happy. That's why I thought they would be interested in this. It's not as logical and straightforward in one mode as it is the other because they couldn't be bothered as long as a certain one of those modes worked logically. 

 

 

Your point is fine and maybe it's not your intention but I think you come across as pretty harsh and demanding, the impression I get is that you are pissed off.

 

I really doubt that changing a text label for a radio button is a big deal but I don't really thing it's prioritized either.

[kiwi]

I don't know if it has already been reported, if I delete the last image (Image Manager),

the Alpha Mask of the previous image is set by itself to 1,

I noticed this because I had a value of 254 placed to mask the junction with the playfield and VUK.

[rascal]

I'm sorry Shockman, I know you're just trying to help make VPX better. Now that you know that it is a "test" selection, how would you logically make the interface? Check out this online UI Design tool.

http://framebox.org/

 

This is a idea I had for it with a selection box and all three modes. Preview mode shows the selection box in action.

http://framebox.org/AiVKA

 

So lets see your idea.

Edited by rascal, 09 April 2019 - 02:47 PM.

[jpsalas]

I don't know if it has already been reported, if I delete the last image (Image Manager),

the Alpha Mask of the previous image is set by itself to 1,

I noticed this because I had a value of 254 placed to mask the junction with the playfield and VUK.

 

Yes I have noticed that sometimes the alpha mask reverts to 1, but I never remember what I did before it changed to 1.

[Shockman]

- It could be part of the mode section that is below it. It has 10 settings that is unique to each mode. It could have 11 and also show the 10 settings for the test mode too.

 

- Radio or dropdown or something that is designed to give more than one choice, or a single function that requires different wording.

 

- It could be added to the dropdown that selects the three modes. But then there would be redundancy there if the in use test mode was grayed out.

 

- It could be just like it is with a case or if that would show the unused mode on the button.

 

- It could not exist and change modes instead of testing.

 

- They could share a hot key.

 

- Could be a menu item with redundancy grayed.

 

- It could simply say "Test" then all users could be equally confused.

 

- The button could display a constant. Like the one that lets us do things in scripting depending on the mode. (if the table was in cabinet mode the constant for testing would be "Desktop"

 

- Each build could switch the wording on the button so it would apply correctly at least part the time.

 

I've seen what VP and this user base becomes when Desktop mode holds less importance. VP9 took an otherwise outsider at the time to fix nudging for desktop because the devs, admin., and cab users refused to even acknowledge the problem. It might take an outsider for this simple problem.

 

 Apathy based on laziness either has a home here or it doesn't. There are other ways to run your table in other modes. I have done that before this command. 

 

Angry? Yeah a bit. We have been here before and I was hoping that was behind us. If anyone thinks the label was happenstance or a coin was flipped is most likely wrong.

 

I ask for these things and more. Not because they are hard, but because they are easy. 

[millansoft]

- It could be part of the mode section that is below it. It has 10 settings that is unique to each mode. It could have 11 and also show the 10 settings for the test mode too.

 

- Radio or dropdown or something that is designed to give more than one choice, or a single function that requires different wording.

 

- It could be added to the dropdown that selects the three modes. But then there would be redundancy there if the in use test mode was grayed out.

 

- It could be just like it is with a case or if that would show the unused mode on the button.

 

- It could not exist and change modes instead of testing.

 

- They could share a hot key.

 

- Could be a menu item with redundancy grayed.

 

- It could simply say "Test" then all users could be equally confused.

 

- The button could display a constant. Like the one that lets us do things in scripting depending on the mode. (if the table was in cabinet mode the constant for testing would be "Desktop"

 

- Each build could switch the wording on the button so it would apply correctly at least part the time.

 

I've seen what VP and this user base becomes when Desktop mode holds less importance. VP9 took an otherwise outsider at the time to fix nudging for desktop because the devs, admin., and cab users refused to even acknowledge the problem. It might take an outsider for this simple problem.

 

 Apathy based on laziness either has a home here or it doesn't. There are other ways to run your table in other modes. I have done that before this command. 

 

Angry? Yeah a bit. We have been here before and I was hoping that was behind us. If anyone thinks the label was happenstance or a coin was flipped is most likely wrong.

 

I ask for these things and more. Not because they are hard, but because they are easy. 

 

[rascal]

- It could be part of the mode section that is below it. It has 10 settings that is unique to each mode. It could have 11 and also show the 10 settings for the test mode too.

 

- Radio or dropdown or something that is designed to give more than one choice, or a single function that requires different wording.

 

- It could be added to the dropdown that selects the three modes. But then there would be redundancy there if the in use test mode was grayed out.

 

- It could be just like it is with a case or if that would show the unused mode on the button.

 

- It could not exist and change modes instead of testing.

 

- They could share a hot key.

 

- Could be a menu item with redundancy grayed.

 

- It could simply say "Test" then all users could be equally confused.

 

- The button could display a constant. Like the one that lets us do things in scripting depending on the mode. (if the table was in cabinet mode the constant for testing would be "Desktop"

 

- Each build could switch the wording on the button so it would apply correctly at least part the time.

 

I've seen what VP and this user base becomes when Desktop mode holds less importance. VP9 took an otherwise outsider at the time to fix nudging for desktop because the devs, admin., and cab users refused to even acknowledge the problem. It might take an outsider for this simple problem.

 

 Apathy based on laziness either has a home here or it doesn't. There are other ways to run your table in other modes. I have done that before this command. 

 

Angry? Yeah a bit. We have been here before and I was hoping that was behind us. If anyone thinks the label was happenstance or a coin was flipped is most likely wrong.

 

I ask for these things and more. Not because they are hard, but because they are easy. 

Well I gave it a go, and I tried to care about your cause, but now I don't give a crap. 

[Shockman]

I understand. That's how I'm feeling about the credo here.

[robertms]

Is this why we have this emoji   ?

[Shockman]

It certainly is, if it's settled.

[toxie]

 

 

Hey there,  with any version of 10.6 the monster faces on the playfield, on tom towers monsterbash, never light up,  tried different versions of 10.5,  still did not work.

 

I then tried the final 10.4 version and it worked fine.  also, this is with all the scripts, bass, ect with the 10.6 beta, the only thing i changed was the vpinballx.exe program,  so there is something definitely in there that causing this.

 

also, the light inserts are of different shade too, comparing 10.4 to 10.6 betas.  very possibly related...

 

Remember that when updating to 10.6 beta to also use matching/current bass.dll! Is that the case?

 

hi, when i download a beta i replace all the files in the beta, so all scripts, bass.dll.  everything get swapped out with the new beta..( after a backup )

 

re-downloaded monster bash 1.3 and tried again tonight.  still no lighting on the faces.. tried with 10.4 and it works..

 

i am just using 10.4 for mb so its all ok...using hyperfine to launch mb with 10.4, everything else is 10,6 beta

 

again.. all the files are from the beta, bass.dll, scripts, ect. are in my vpfolder,  only the vp exe...10.4 and 10.6 beta I'm swapping from.

 

does this make sense??

 

 

Yes, thanks for verifying! Could you post a screenshot of your video preferences, please?

[Shockman]

What does the "display image in editor" do these days?

Maybe related or not, Why when you have show playfield set that it shows that image over everything now not just the playfield?

[BorgDog]

it only shows the image on objects if you are set to solid, if you are set to outline it does not show.  likely same issue with the playfield image, when you are on outline you will see the playfield everywhere. Under the View menu, Outline or Solid.