- View New Content
-
Getting Started
-
Tutorials
Tutorial Categories
Tutorials Main Page Installation and Setup Downloadable TutorialsROM Adjustments
Number of Balls Adjustments Volume Adjustments
-
Visual Pinball Tables
VP 8 Desktop Tables
All VPM Recreations VP Recreations VP/VPM MODs VP Originals ROMsVP 9 Desktop Tables
All VPM Recreations VP Recreations VP/VPM MODs VP Originals ROMsVP9 Cabinet Tables
All Full Screen Cabinet Full Screen B2S Cabinet Spanned Cabinet Tables Media Packs ROMsVPX Tables
All VPinMAME Recreations VPX- - /VPinMAME - MOD Tables VPX Recreations VPX Originals Media Packs ROMs VR
-
Frontend Media & Backglass
Media Packs
Complete Media Packs Wheel Logos VideosBackglasses
dB2S Animated Backglasses UVP Animated Backglasses Topper Images
- Future Pinball Tables
-
Design Resources
Main Resources
Table Templates Playfield Images Image Library Sound Library Key CodesVP Guides
VP8 Guide - English VP8 Guide - Deutsch VP9 Guide - English VP9.1.x Guide - English VP Object Guide VPM DocumentationFuture Pinball Resources
Playfield Images 3D Model LibraryFuture Pinball Guides
FP Script Guide Big Draco Script Guide FP Table Design Guide FP DMD Guide
- Other Features
- Bug Tracker
- Image Gallery
- Blogs
-
More
VP9.1.6 Alpha/Beta Bugs & Feedback
Started By
toxie
, Apr 07 2013 06:00 AM
1394 replies to this topic
#1201
Posted 02 December 2013 - 11:13 PM
Are you saying I should abandon 2008?
#1203
Posted 02 December 2013 - 11:28 PM
Minor issue with using tab to navigate text fields - appears to be present for a long time,
I noticed that tabbing from one text field to another does not always select the existing value which makes editing values harder to do quickly. For example, editing a Ramp, if I select and edit the Hit Threshold value and then use the tab key to go to Slingshot Force, the current value is not selected. You have to manually delete or highlight the value to change it. However, if you go into the Color editor, using tab key works properly when tabbing through the various color fields
#1205
Posted 03 December 2013 - 06:19 AM
ver 768 seems to be broken ... tables will not load for me ... last stable seems to be 756
thanks
You need the dll, SciLexer.dll, you can get it from the latest scintilla, here: http://www.scintilla...TEDownload.html just download the full executable and copy that dll to you VP folder.
If you want to check my latest uploads then click on the image below:
Next table? A tribute table to Stern's Foo Fighters
#1207
Posted 03 December 2013 - 06:30 AM
It is also available in my downloads folder with all the previous builds.
#1209
Posted 03 December 2013 - 07:13 AM
..and is in with rev 720
from the changelog:
- add additional (optional) parameters to PlaySound to set the pan and/or randomize the pitch of the played sound effect: Instead of PlaySound "name",loopcount,volume one can now use PlaySound "name",loopcount,volume,pan,randompitch
pan ranges from -1.0 (left) over 0.0 (both) to 1.0 (right)
randompitch ranges from 0.0 (no randomization) to 1.0 (vary between half speed to double speed)
so f.e. PlaySound "FlipperUp",0,0.5,-1.0,1.0 would play the sound not looped (0), at half the volume (0.5), only on left speaker (-1.0), with varying pitch (1.0)
Hey Toxie, love this feature but I believe there is a bit of a bug with the pan parameter. -.5 or .5 completely removes the sound from the other speaker so maybe it's really a 1.0 setting total value with the swing to either sides of 0 being maxed at -.5 and .5. You can check it out yourself, just load up the default table (maybe with headphones
and change the flipper sounds left and right with your new code above accordingly and you'll see that if you have the pan at only .5 it is fully panned.
This was using version 753 and I imagine it hasn't changed in later ones / have not tested in the latest versions. Really great add-on / feature though and maybe it's just a documentation thing. However, I think it would work better if there was the full range to -1 and 1 and works a bit better / simpler with some formulas and routines I'm working on but isn't a big deal to manipulate with a factor / value knowing if it's gonig to stay as is being fully panned with only -.5 or .5.
EDIT: And thanks fuzzel for adding that per-table alpha slider feature . To be honest I haven't tried it yet as I haven't updated to any versions since 753 as for a couple reasons but was also waiting a bit for the dust to settle a little with this latest script / dll stuff.
Edited by jimmyfingers, 03 December 2013 - 07:19 AM.
#1210
Posted 03 December 2013 - 10:55 AM
Because some of you asked for an updated (reference)manual. I created a quick overview of all commands VP understands, I don't have much time so this is really a rough overview but it should give you some information what's usable and what not.
I attached that command reference here and added it to the repository so perhaps we can include it in the next release.
Attached Files
#1212
Posted 03 December 2013 - 12:02 PM
Thanks Fuzzel. Been waiting for a list like this.
On a side note. I didn't read the thread and downloaded the latest rev. Didn't download the news dll. I had made some changes to monster bash in the editor then opened the script editor to continue scripting. It wouldn't work. So I saved and came and looked at the thread. Because I had opened the script editor and then saved when I came back to the table I had completely lost the script.
So authors make sure you download the .dll before you save.
Thank god for autosave
On a side note. I didn't read the thread and downloaded the latest rev. Didn't download the news dll. I had made some changes to monster bash in the editor then opened the script editor to continue scripting. It wouldn't work. So I saved and came and looked at the thread. Because I had opened the script editor and then saved when I came back to the table I had completely lost the script.
So authors make sure you download the .dll before you save.
Thank god for autosave
"it will all be ok in the end, if it's not ok, it's not the end"
Monster Bash VP10 WIP https://dl.dropboxus... (vpx)WIP15.vpx
#1214
Posted 03 December 2013 - 03:04 PM
..and is in with rev 720
from the changelog:
- add additional (optional) parameters to PlaySound to set the pan and/or randomize the pitch of the played sound effect: Instead of PlaySound "name",loopcount,volume one can now use PlaySound "name",loopcount,volume,pan,randompitch
pan ranges from -1.0 (left) over 0.0 (both) to 1.0 (right)
randompitch ranges from 0.0 (no randomization) to 1.0 (vary between half speed to double speed)
so f.e. PlaySound "FlipperUp",0,0.5,-1.0,1.0 would play the sound not looped (0), at half the volume (0.5), only on left speaker (-1.0), with varying pitch (1.0)Hey Toxie, love this feature but I believe there is a bit of a bug with the pan parameter. -.5 or .5 completely removes the sound from the other speaker so maybe it's really a 1.0 setting total value with the swing to either sides of 0 being maxed at -.5 and .5. You can check it out yourself, just load up the default table (maybe with headphones
and change the flipper sounds left and right with your new code above accordingly and you'll see that if you have the pan at only .5 it is fully panned.
This was using version 753 and I imagine it hasn't changed in later ones / have not tested in the latest versions. Really great add-on / feature though and maybe it's just a documentation thing. However, I think it would work better if there was the full range to -1 and 1 and works a bit better / simpler with some formulas and routines I'm working on but isn't a big deal to manipulate with a factor / value knowing if it's gonig to stay as is being fully panned with only -.5 or .5.
The thing is that it works the same as the normal volume setting, so 0.5 doesn't mean that it is "half as loud"..
Please look at the parameters i used in the default table, this should give you an impression on what is useful..
a bit unrelated, but meanwhile i think i found the fix for the crackling sound issue (volume at max, etc) on WMS sound emulation..
i noticed some members of the pinmame team, lets see if this was really the issue or if its just luck on my machine..
so this is also now in the pinmame svn.. ![]()
#1215
Posted 03 December 2013 - 06:44 PM
I attached that command reference here and added it to the repository so perhaps we can include it in the next release.
The newest version will always be here, btw: http://sourceforge.n...ndReference.txt
#1217
Posted 03 December 2013 - 07:36 PM
..and is in with rev 720
from the changelog:
- add additional (optional) parameters to PlaySound to set the pan and/or randomize the pitch of the played sound effect: Instead of PlaySound "name",loopcount,volume one can now use PlaySound "name",loopcount,volume,pan,randompitch
pan ranges from -1.0 (left) over 0.0 (both) to 1.0 (right)
randompitch ranges from 0.0 (no randomization) to 1.0 (vary between half speed to double speed)
so f.e. PlaySound "FlipperUp",0,0.5,-1.0,1.0 would play the sound not looped (0), at half the volume (0.5), only on left speaker (-1.0), with varying pitch (1.0)Hey Toxie, love this feature but I believe there is a bit of a bug with the pan parameter. -.5 or .5 completely removes the sound from the other speaker so maybe it's really a 1.0 setting total value with the swing to either sides of 0 being maxed at -.5 and .5. You can check it out yourself, just load up the default table (maybe with headphones
and change the flipper sounds left and right with your new code above accordingly and you'll see that if you have the pan at only .5 it is fully panned.
This was using version 753 and I imagine it hasn't changed in later ones / have not tested in the latest versions. Really great add-on / feature though and maybe it's just a documentation thing. However, I think it would work better if there was the full range to -1 and 1 and works a bit better / simpler with some formulas and routines I'm working on but isn't a big deal to manipulate with a factor / value knowing if it's gonig to stay as is being fully panned with only -.5 or .5.
The thing is that it works the same as the normal volume setting, so 0.5 doesn't mean that it is "half as loud"..
Please look at the parameters i used in the default table, this should give you an impression on what is useful..
I have reviewed those parameters in the default table and it is similar to what I've arrived at on my own, but I think maybe we're not on the same page still as to my original point as the thing I don't understand is if the paramter range is supposed to be effective over -1.0 to 1.0 (left to right respectively) why is it that at -.5 it is already fully panned to the left and at .5 it is fully panned to the right (negates the need for anything above .5 it seems and therefore the -1 + 1 listing of the parameter range does not seem practical). I'm not really considering it an aspect of any volume qualities in general but more the absense of any signal from the opposite speaker when "fully" panned.
If you listen with headphones (even on the default table) on you will be able to hear that at the -/+.5 mark there is no more sound coming out of the other side. I get that I can adjust the level down and where I might have wanted .2 I'll use .1 now, but the thing is what point is it to have a pan range to -1 and 1 if it's already panned fully to left or right at -.5 and .5 (i.e. .6 .7 .8 etc. don't seem to pan any further away from the other side than .5 already does). Does it just make even the left or right past -.5 / .5 even quieter? I'm a home music studio dude / musician so have lot's of experience with audio and this just doesn't make sense to me as the defintion / function stands currently.
Don't get me wrong, I / anybody can still use it as is and just adjust the levels - it's truly an awesome added feature - but it seems that we would be compensating in a way for the range of effective vs. documented parameters.
Because some of you asked for an updated (reference)manual. I created a quick overview of all commands VP understands, I don't have much time so this is really a rough overview but it should give you some information what's usable and what not.
I attached that command reference here and added it to the repository so perhaps we can include it in the next release.
This is great but could you clarify regarding the ones that have no effect meaning whether they're just not able to change anything from within the script or do not execute anything in the script. Reason I ask is I just recently found from trial and error the tablename.width and tablename.height values and was able to read them in the script to get their values which was extremely useful for a new routine I'm working on. I didn't see the exact .width / .height in your list but saw some reference still to width and height but with the asterisk (that one also seemed to need the tablename.parameter style of command as well).
So, are those ones that have the asterisk safe to say they can still be read in but just not altered? Or maybe those will just be trial and error to see which ones can while some others do nothing at all.
#1218
Posted 03 December 2013 - 08:39 PM
the ones marked with an asterisk cannot be set from the script, but you should be able to grab the current values from the script.
#1219
Posted 03 December 2013 - 09:24 PM
i DLd all 4
command ref
scilexer.dll
wscite.336
scite.336
>>You need the dll, SciLexer.dll, you can get it from the latest scintilla, here: http://www.scintilla...TEDownload.html just download the full executable and copy that dll to you VP folder.<<<<<
extract and copy paste to which vp table folder or all vp table folders?



Contributor
Top














are all trademarks of VPFORUMS.