1488 replies to this topic

[3rdaxis]

Having small issues with the default font in the editor.  Its now a proportional font vs courier new.  This causes alignment issues with indents, etc.  Any chance this can be changed back to Courier or courier new? Thanks

[fuzzel]

You mean the font in the script editor?

[toxie]

I also saw that this changed some time ago.. I just thought it's a quirk with my windows or something though.. Apparently not.. :/

(@fuzzel: yes in the script editor)

[jpsalas]

Mine is still Courier, on both my computers. You can change the font in the editor preferences (open the editor, choose script, preferences), and at the bottom you'll find the font button where you can select another font.

[3rdaxis]

Yea I did change it back the issue is when someone else downloads a table if using 10.6 the scripting is jumbled all up unless they also switch it back to the standard courier new. 

Especially when using ASCII art. 

 

 

  _________  __  _____  ___________    
 / ___/ __ \/ / / / _ \/  _/ __/ _ \  
/ /__/ /_/ / /_/ / , _// // _// , _/
\___/\____/\____/_/|_/___/___/_/|_| 

 

 

Now it's this...

 

 

 

_________ __ _____ ___________

/ ___/ __ \/ / / / _ \/ _/ __/ _ \
/ /__/ /_/ / /_/ / , _// // _// , _/
\___/\____/\____/_/|_/___/___/_/|_|

[jpsalas]

Do you mean if you open with VPX 10.5 a table which was saved with 10.6, then the font in wrong? It doesn't happen to me. I can open a 10.6 table with 10.5 and the font is still Courier. And the same if I open an older table with 10.6, the font is still courier. I still use Windows 10 1607.

[BorgDog]

I just did a clean install on a new machine (10.5 all in one installer then 10.6 beta), and when I go to those font settings the font is blank, which I think it then defaults to arial or some system font or something Calibri?  On my other machines it retains the correct font stuff as far as I can tell.

[toxie]

Maybe this is due to me removing the table encryption so the font setting is screwed up due to this?? not much else has changed in that aspect with 10.6.

 

10.5 is still correct for you guys, right??

[randr]

I’ve seen this happen on 10.5 final thought it was just my setup causing it

[3rdaxis]

Yea 10.5 is fine for me. 

[Pookamoondo]

Hey guys, just for reference, when I updated to VPX beta 6 (R3541)… the table Vector (Bally 1982) v1.2 no longer works and gives an error trying to run fast flips (Line 226: Object Doesn't support this Property or method: VPMFlips.CallbackL) ...

 

The older version of core.vbs from the 15th of July (VPX 5 version) works fine though....

Edited by Pookamoondo, 15 November 2018 - 12:48 AM.

[Thalamus]

@pookamoondo Partly explained in the fast flip thread.

 

https://www.vpforums...=38651&p=417583

[jpsalas]

Hey guys, just for reference, when I updated to VPX beta 6 (R3541)… the table Vector (Bally 1982) v1.2 no longer works and gives an error trying to run fast flips (Line 226: Object Doesn't support this Property or method: VPMFlips.CallbackL) ...

 

The older version of core.vbs from the 15th of July (VPX 5 version) works fine though....

I guess this is an older method to use the fastflips. I simply removed those two lines, 226 and 227, and changed the Solenoids = 0 with Solenoids = 2, and fastflips seems to work fine (checked with F11)

[Schlabber34]

As long as you don't see DT's droping when you hit the flipperbuttons it should be OK. That's what was happening before DJRobX made fastflips work plus stuff getting out of sync. Usesolenoids=2 didn't work out of the box with 10.5, good to hear that it is now!

[Thalamus]

Yeah. Well. With 10.6 there is a new core.vbs and I don't know the details. It might very well be that tables that has useSolenoids=2 should be changed. Maybe DjRobX, Toxie or nFozzy could explain ?

[toxie]

nFozzy must, its his code, just ask in the fast flips thread, please: https://www.vpforums...showtopic=38651

I’ve seen this happen on 10.5 final thought it was just my setup causing it

 

Could you please retest this with 10.5 final, just to be sure? And just in case it does not work (like you said), could you please find the first version that still works for you??

[toxie]

I’ve seen this happen on 10.5 final thought it was just my setup causing it

 

Could you please retest this with 10.5 final, just to be sure? And just in case it does not work (like you said), could you please find the first version that still works for you??

 

Forget about it, i found the issue in one commit for 10.6, fixed with next version, so it will show Courier again by default in the script editor.

[rascal]

At some point can touch screen features be revisited? It would be nice to have a touch screen tool in the editor, where we could place touchscreen buttons on the screen where we want them. Once placed, the options of the object could have image settings and transparency settings maybe. Maybe a dropdown menu where you can select what it is for (coin, left flipper, right flipper, etc...). This could also be assigned through script I guess. It would be nice to have a touchscreen drag and release plunger slider object possibly also. Pull the plunger back and release with a touchscreen slider. It would be nice to be able to design the touchscreen interface as you would like it, and be able to place semi transparent visible buttons.

I apologize if this is not the place to put this request. You developers are doing an awesome job accommodating everyone's requests, and VPX is the greatest program ever! Please keep up the great work. Being an old timer of the VP scene, I am amazed at the progress and the quality of the tables being released these days. And to think, it's not costing me anything!!! That's the best part.

Edited by rascal, 16 November 2018 - 03:23 PM.

[toxie]

Absolutely the right place to ask for that, and i'd love to have that, too, btw..

 

I guess doing this on a per-table basis would not make sense, as the majority of table authors might just ignore touch-support..

So would doing this globally be good enough?

[rascal]

Absolutely the right place to ask for that, and i'd love to have that, too, btw..

 

I guess doing this on a per-table basis would not make sense, as the majority of table authors might just ignore touch-support..

So would doing this globally be good enough?

Awesome man! Globally would be great, or just a checkbox somewhere to enable this support per table would be cool too. Off by default.

 

Thinking about it more, global would be the best and the dropdown for the touchscreen button object could contain most if not all of the key assignments in the Key, Nudge, and DOF settings. In other words you set any one of them to that button.

Edited by rascal, 16 November 2018 - 05:30 PM.