228 replies to this topic

[Swisslizard]

I dont know it this is technically deasible at all, but real multi monitor support would be phantastic. This not only allow to have a animated backglass directly in the table file, but also for a better way to emulate tables like Banzai Run

[arngrim]

we need an option to be able to switch from DOF ini files from feedback to nofeedback files, when files are generated from the config tool, we have these files, and the nofeedback files is the same one than the normal one but without the noisy toys, contactors, gears, knocker etc.

 

But i have no clue where it can fit better, in DOF itself, at vp with a special command line to call the nofeedback file, or from the frontend?

[unclewilly]

Wire ramps with 3 sections that are selectable per control point like the fp wire ramps.

With maybe the option for a ring at the control points

[ClarkKent]

A compatibility mode would be nice. I do not know how VP10 will look like and how good compatibility for VP9 tables will be. But some kind of an option to ensure that no other separate older version is needed would just be nice.

[DJRobX]

A compatibility mode would be nice. I do not know how VP10 will look like and how good compatibility for VP9 tables will be. But some kind of an option to ensure that no other separate older version is needed would just be nice.

 

As much as I like this idea, I think doing so would hold back VP too much.   Development of the new VP will be much faster, and the end result leaner and cleaner, if the developers don't have to tip-toe through a mine field of compatibility hacks.   It's just not hard to set up modern front-ends to treat VP9 files differently than a new engine (just as we do with Future Pinball / Visual Pinball / Unit3D pinball / etc today).

 

That said, I do think VP10 should use a different file extension (VPX) so there's never any confusion as to which player to use (as we have today with VP8 and VP9).

[unclewilly]

That's a really good idea, to use a different file extension.

I for one don't want to be limited by compatibility.

I'm also looking forward to remaking tables with a new toolset.
I think this will revitalize the community and hopefully usher in a new generation of authors and revitalize existing authors.
Speaking for myself I have to say that just the Introduction of the new features in vp9 has motivated me to become more active in table building again.

[melon]

Another suggestion. For primitives and ramps, add a slider for the transparency. Yes, now we can open the file in Gimp/photoshop and change the transparency, abd then import again the image in VP, but it would be interesting.

And the posibility to add rings at the wire ramps would be sooo great.

Note that all my suggestions are focused on building a table. All the things I'm talking about can be achieved with what we have now, but it needs to be easier.

 

 

Speaking for myself I have to say that just the Introduction of the new features in vp9 has motivated me to become more active in table building again.

 

Same here. Without all the new features (primitives, alpha flashers & GI ...) I think I wouldn't have been back building tables... Thank you very much guys!

[Slydog43]

wow those last 2 comments from Melon and Unclewilly should really make you VP devs proud and shows how important the stuff that you guy do is.  I can't think of a greater compliment than these improvements have made table authors excited again.  Keep up the awesome work, thanks

[Practicedummy]

If we get more objects built in to VP and improvements on current ones, this will open the doors for new authors to create tables. I miss the time back years ago when VP had all kinds of original tables (good and bad) made by seemingly countless authors and VP look like a huge community. Nowadays, creating an original took more work and was intimidating to wannabe authors than they could wrap their heads around, which most tables we see released today are recreations and very few originals.

Edited by Practicedummy, 26 March 2014 - 11:13 PM.

[DJRobX]

Another suggestion. For primitives and ramps, add a slider for the transparency.

...

Note that all my suggestions are focused on building a table. All the things I'm talking about can be achieved with what we have now, but it needs to be easier.

 

 

Keep suggestions like this coming.   There are probably a lot of things we can do to VP to make table authoring more efficient. 

[Otherguy]

I am new to Visual Pinball and love it.  I set up my computer up with several tables  and I'm getting ready to build a "Mini Pin" case shortly.  

 

From my brief experience so far, I would like to throw out my 2 cents:

 

1.  Possibly a way to have the Roms for the boards built in.  There are so many ROMS and I just DL all of them for the name of the board because I never know which one is needed. A simpler way to do this would be nice.

 

2. After getting used to it, setting up the tables gets alot easier however it still is time consuming.  An easier and faster way to set-up, load the boards, and link them to Hyperpin would be nice.

 

Just my ideas.  Thanks for all the work everyone puts into the boards and the system itself.  Since a real machine is a little too big and they are expensive, VP is an awesome solution. 

 

`Otherguy

[AaronShupp]

I couldn't agree more with UW and DJRobX's sentiment. It often seems like the devs are forced to spend huge amounts of time to ensure that 5+ year old, janky files still work for the 10 people still using them instead of pressing forward.

 

If you love the old table files, that's cool! You just have to keep using the old software. Even the likes of Microsoft and Apple eventually have to cut the cord on old formats because it's not technically feasible to support everything every single bit of legacy.

Edited by AaronShupp, 31 March 2014 - 05:07 PM.

[marco helmink]

Multicolor dmd support??

[Slydog43]

I was thinking that I spend alot of time collecting the flyer, instruction cards, videos, etc for each table it might be nice to have these included.

 

Not sure about that idea, but it really could use built in instruction card(s).  Having 1 vector based instruction card wouldn't take much space and benefit all.  Its so nice playing a game and getting a readable instruction card pop up on the backglass is incredible.

[zany]

MulticolorDMD would be a PinMame suggestion, not VP10.

Edited by zany, 31 March 2014 - 07:02 PM.

[faralos]

stretchable rubbers like the ones used in FP for custom shaped posts and plastics

a moveable spotlight that can be repositioned or turned off (into another color perhaps?)while playing

the ability to import full motion video clips into the pins... again like FP has

and maybe just maybe a NON buggy version of vp 9.2?  with everything working as it is supposed to

[arngrim]

Separate sound system for the mechanical sounds, so we can deactivate them more easily

[BananaBoat]

An in game, on screen menu to allow you to make adjustments in real time, such as table size, depth etc...

That would be very useful for configuring tables to individual tastes.

[kiwi]

It would be nice to have the objects in the editor of different colors depending on the type.
Example : walls brown, ramps blue, primitive purple, flippers ....................

With different coloring, the objects are easier to identify.

 

Max

[freezy]

One thing that would be really really useful: Define global options in VP that can be read in a table script. And make it possible to override them with command line parameters when launching VP. This would mean:

• No more editing of table scripts for changing the ROM
• Ability to run different ROMs for the same table directly from your favorite frontend
• No more editing of table scripts for trivial settings such as controller or rotation params
• No more need for table authors to code up fancy menu dialogs

Imagine a new user who wants to setup his 100 favorite tables. While downloading all the different types of media (table, b2s, media pack, videos, roms) is already taking ages, he then has to go through all tables again, open them up in VP and adapt them to his setup. Being able to configure this on a global level would be a huge time saver.