1353 replies to this topic

[BorgDog]

Feature Request:

 

Can we get a keyboard shortcut to Camera Mode please?  F6 I do not believe does anything in the editor and would be a good spot I think.

 

Thanks

[fuzzel]

Will be available with the next update.

[Drybonz]

Will be available with the next update.

 

You guys are pounding out the improvements lately... thanks so much.  

[arngrim]

ok, now that we have new betas ongoing i talked about the idea to have the controller.vbs user values inside the registry instead of a txt file in the user folder, this will simplify the setup for the users, easier to manage since it would be avaiable in the vp menu, and would simplify the vbs itself, since we wouldn't need to create the txt file at the first usage, but we will have default values in the registry, all dof toys to 0, for the force disable, not sure what default value would be better, on or off?

 

first let me know what you think of it

[fuzzel]

Yes why not but you still have to support the old way for VP 10.0 and 10.1 tables.

[Drybonz]

I know this might be taking several steps further, Arngrim, but what about settings within the editor itself?  For instance, we have video settings, what if there were a "registry settings" dialog that you could open within the editor with check boxes corresponding to yes/no, true/false... even if it were only for the most popular settings it would pretty much revolutionize ease of use.

 

Probably a lot to add, but maybe something to think about for down the road?

[arngrim]

fuzzel, worse case a table doesn't implement controller.vbs, then it won't use these settings, this won't give any errors.
so there are 2 set of options, forcedisableb2s in video settings will disable b2s,
the others maybe in sound settings would stop or start sound or force feedback depending on the option

[hauntfreaks]

 

feature request: can there be normal maps for the playfield?

Should be possible but I haven't checked the code yet. What you want to achieve with a normal map on the playfield?

 

 

PM sent

[freneticamnesic]

Don't keep it to PM! I'm curious too!!! Are you aging the playfield??? I'm freakin' loving normal maps. I'm probably abusing them like I do all new features but I ain't care

[hauntfreaks]

Don't keep it to PM! I'm curious too!!! Are you aging the playfield??? I'm freakin' loving normal maps. I'm probably abusing them like I do all new features but I ain't care

 

something like that

very early rendering

 

Attached Files

•  Capture.PNG   1.18MB   19 downloads

Edited by hauntfreaks, 22 July 2016 - 07:02 PM.

[gabrom78]

To use a normal map at the playfield i use a plane primitive (toy) bigger as the playfield. ^-^ 

 

It would be nice to add another omni light over the playfield or move the actual one towards and Bakwards 

[hauntfreaks]

personally i would love to be able to move the light source (light box) like moving the camera

[Gromit21]

Feature Request:

 

Love the Table Camera/Lighting editor in VP10. Small nitpick... currently you need to press the shift key to move 1 increment at a time. Would be nice to just hold the shift key to continuously raise/lower the values. Or is there already some key that does that? 

[fuzzel]

Feature Request:

 

Love the Table Camera/Lighting editor in VP10. Small nitpick... currently you need to press the shift key to move 1 increment at a time. Would be nice to just hold the shift key to continuously raise/lower the values. Or is there already some key that does that? 

That's not that easy to implement because the key handler reacts on key events (key is down or key is released) there is no polling if a key is still down. It seems that this is a limitation of the old DirectInput API. Changing that would mean a lot hassle for users who use a joystick as input method.

[Ben Logan]

That aged playfield looks badass, Hauntfreaks.

[arngrim]

Yes why not but you still have to support the old way for VP 10.0 and 10.1 tables.

i read again..
the difference of the old and the new way is where it gets the data, migration could be easy that we put default values in the registry the first time we use new method, and a popup can explain where it gets the data from and where the values can be changed (ideally in vp options)
that's at least how i see it

[Gromit21]

 

Feature Request:

 

Love the Table Camera/Lighting editor in VP10. Small nitpick... currently you need to press the shift key to move 1 increment at a time. Would be nice to just hold the shift key to continuously raise/lower the values. Or is there already some key that does that? 

That's not that easy to implement because the key handler reacts on key events (key is down or key is released) there is no polling if a key is still down. It seems that this is a limitation of the old DirectInput API. Changing that would mean a lot hassle for users who use a joystick as input method.

 

 

Thanks Fuzzel.... I'll just keep clicking those flippers! The on-screen editor is great as is.

[ScottyVH]

That aged playfield looks badass, Hauntfreaks.

Here's an idea for 10.2… How about an "age" slider bar?

I'm just the ideas man… it's up to you brilliant devs to figure out and implement my crazy functional requirements!:-)

[Shockman]

Is it possible to script spin into the ball?

 

also

Is there a key to destroy the oldest ball?

Edited by Shockman, 24 July 2016 - 04:31 AM.

[hauntfreaks]

 

That aged playfield looks badass, Hauntfreaks.

Here's an idea for 10.2… How about an "age" slider bar?

I'm just the ideas man… it's up to you brilliant devs to figure out and implement my crazy functional requirements!:-)

 

 

here ya go instant aged  

 

 ColorGradeLUT256x16_Sepia.png   5.18KB   20 downloads