616 replies to this topic

[fuzzel]

Backglass monitor?

I think that's not possible either because the dialogs are VBA created/controlled and not directly from VP. The VBA stuff is a Microsoft dll/service without the possibility to change the way dialogs are created or handled, afaik

[kiwi]

 

I noticed that the built in timer support for ramp objects in 10.2 are not supported - script error

 

Thanks! Its fixed.

The table is automatically saved even with the checkbox "Auto-Save" disabled.

 

Is this still the case? Will add a small tweak just to be sure, so please recheck with the next build.

 

Autosave is fine now, I've tried with it enabled and disabled.

 
If I play a bit with the "Test desktop" and "FSS mode" checkboxes, the POV textboxes freeze, going to the editor and returning to the backdrop the "mode" drop-down menu will work again.

 

Thanks!

[fuzzel]

rev3051 is up (vbs scripts were changed!):

 

- backdrop images are shown as in-use in the image manager

- VPX warns user on deleting multiple elements if they are part of collections
- tweak autosave id
- add missing timer properties for ramp
- add copy/paste/paste-at to context menu
- add new configurable key for a lockbar/fire button (accessible via "LockbarKey" in the script)
- add more key mappings to help dialog
- fix loading old POV format if no FSS settings were saved.
 

Edited by fuzzel, 22 April 2017 - 04:12 PM.

[toxie]

actually the vbs files are almost the same (except for the help dialog routine), just in case you are wondering why there is no change in the scripts changelog..

[fripounet]

Error of .exe 3040 instead of 3051

[arejst]

Hi.

 

Not sure if anybody else reported this, but under "Keys, -nudge and DOF" I don't seem to get the option "Disable B2S" to stick. Everytime I go in and out, it always is back to not activated.

[nFozzy]

What about keybinds for staged upper flippers?

[roccodimarco]

Every time I start any table I get this error message. Any ideas
https://imgur.com/gallery/TWskW

[Thalamus]

Hi.

 

Not sure if anybody else reported this, but under "Keys, -nudge and DOF" I don't seem to get the option "Disable B2S" to stick. Everytime I go in and out, it always is back to not activated.

 

Been trying to get their attention to the nudge-filter.

[Drybonz]

Thanks fuzzel and toxie... did that last update change vpmkeys.vbs?

[toxie]

originally yes, but then i removed it again, so overall no.. 

[BorgDog]

Feature requests:

 

Can you make the Dimensions Manager more useful by having an Apply button, so that you can click on a machine, hit Apply and it sizes the currently open table to those dimensions.  

 

On File, New can it be made to run through a series of dialogs to setup a table, first being the Dimensions Manager that would set the size of your new table, then maybe a table type, em, original ss, or rom controlled that would then load basic templates for each of those types with a bunch of generic parts and appropriate/approximate default physics applied.  And yes a set of template tables would need to be developed or sourced from existing shared ones, because frankly there is not much right about the current default other than having a selection of parts, size is not a standard anything, physics are messed up, etc.

 

Just trying to make it easier for new table builders to get started down the right path.  Nothing more frustrating then seeing someone put in a bunch of work and making something look really nice and it's sized incorrectly so it will never play right.

 

Thanks for all the work guys, some fun stuff going on.

[Shockman]

There is something more frustrating. Apathy. The drum has been beaten ragged for a logical start to table building for years. 

[Drybonz]

There is something more frustrating. Apathy. The drum has been beaten ragged for a logical start to table building for years. 

 

Ok?  ... and you thought a new feature in the VPX beta might help you with that?

[gtxjoe]

Yes, +1 for adding an "Apathy" menu item, button and also add to the right click context menu.

Thanks!

[Shockman]

 

There is something more frustrating. Apathy. The drum has been beaten ragged for a logical start to table building for years. 

 

Ok?  ... and you thought a new feature in the VPX beta might help you with that?

 

I thought it might help everyone. The old new table was much more useful than the new one. It's just stupid to have to have a table start to be loaded in, and an example table built in and still call the thing "new table". The dimension manager as a start of a build makes sense to me. And don't fucking attack me for agreeing with BorgDog, Fuck with him if you think it's a stupid idea. 

[mkl66]

Hi

 

just tested the new build 3051 especially the image manager (which is getting better and better). There I found an issue when loading the Terminator 2 table.

The backdrop image (DT Image) is _t2 but this image is not tagged as in use in the image editor.

 

cheers

[kiwi]

 

 

I noticed that the built in timer support for ramp objects in 10.2 are not supported - script error

 

Thanks! Its fixed.

The table is automatically saved even with the checkbox "Auto-Save" disabled.

 

Is this still the case? Will add a small tweak just to be sure, so please recheck with the next build.

 

Autosave is fine now, I've tried with it enabled and disabled.

 
If I play a bit with the "Test desktop" and "FSS mode" checkboxes, the POV textboxes freeze, going to the editor and returning to the backdrop the "mode" drop-down menu will work again.

 

Thanks!

 

I confirm, the backdrop images are not reported if they are in use.
If you could have this new feature also for audio samples and for materials, if it is not a big deal.

 
Autosave does not work, the previous revision saved the table after about one and a half hours of VPX usage (with autosave disabled), ten minutes after my previous post.
The current revision has the same bug.

 

Thanks

[toxie]

Feature requests:

 

Can you make the Dimensions Manager more useful by having an Apply button, so that you can click on a machine, hit Apply and it sizes the currently open table to those dimensions.  

 

On File, New can it be made to run through a series of dialogs to setup a table, first being the Dimensions Manager that would set the size of your new table, then maybe a table type, em, original ss, or rom controlled that would then load basic templates for each of those types with a bunch of generic parts and appropriate/approximate default physics applied.  And yes a set of template tables would need to be developed or sourced from existing shared ones, because frankly there is not much right about the current default other than having a selection of parts, size is not a standard anything, physics are messed up, etc.

 

Just trying to make it easier for new table builders to get started down the right path.  Nothing more frustrating then seeing someone put in a bunch of work and making something look really nice and it's sized incorrectly so it will never play right.

 

Thanks for all the work guys, some fun stuff going on.

 

If some of you guys would want to help out with that, then this could be a fantastic idea.

The most simple variant to do this (for us) would be that this scheme basically just selects one out of X existing new table templates, so we would need to have these first to do this (e.g. one empty table per proposed template, with the appropriate flipper and playfield settings and a basic script (including all the newskool stuff like DOF/Controller.vbs) in place).

 

Anybody up for this??

 

 

The table is automatically saved even with the checkbox "Auto-Save" disabled.

 

Is this still the case? Will add a small tweak just to be sure, so please recheck with the next build.

 

Autosave is fine now, I've tried with it enabled and disabled.

 

Autosave does not work, the previous revision saved the table after about one and a half hours of VPX usage (with autosave disabled), ten minutes after my previous post.
The current revision has the same bug.

 

 

Hmmm.. Thanks for reporting.. So if i get this right, the autosave being disabled will still trigger a save after ten minutes, but the autosave enabled will trigger a save after the expected/setup time?

Or both variants after 10 minutes??

[kiwi]

 

 

 

The table is automatically saved even with the checkbox "Auto-Save" disabled.

 

Is this still the case? Will add a small tweak just to be sure, so please recheck with the next build.

 

Autosave is fine now, I've tried with it enabled and disabled.

 

Autosave does not work, the previous revision saved the table after about one and a half hours of VPX usage (with autosave disabled), ten minutes after my previous post.
The current revision has the same bug.

 

 

 

 

Hmmm.. Thanks for reporting.. So if i get this right, the autosave being disabled will still trigger a save after ten minutes, but the autosave enabled will trigger a save after the expected/setup time?

Or both variants after 10 minutes??

 

In both cases, automatic save enabled-disable, the table is saved after the expected time.

 
It may be that playing with the backdrop parameters does not activated the autosave,

that is why the previous time I waited an hour and a half before the problem was present,

in the end I went into the editor and the autosave was self- Activated.