740 replies to this topic

[jipeji16]

Hi everybody, i've notice a lot of crashes cloning materials...

i saw that when the name is longer, 31 or 32 characters, it crash cloning. if you reduce the name it doesn't crash the application... in the 3237 and 3251 version.

 

have you notice that too ?

 

Another time thanks for your hard work !!!!!

[Rajo Joey]

I have problems with the taito.vbs the last weeks. After installing the last updates of 10.4, all Taito-tables produce the following error-message.

 taito-error.jpg   10.36KB   20 downloads

So I test older ones and in the minimal setup I found a script, which works. All Taito-tables run fine with it.

Now I find the different entries in these scripts.

These is the script (excerpt), which doesn't work for me.

' Keyboard handlers
Function vpmKeyDown(ByVal keycode)
    On Error Resume Next
    vpmKeyDown = True ' assume we handle the key
    With Controller
        Select Case keycode
            Case RightFlipperKey .Switch(swLRFlip) = True : vpmKeyDown = False
            Case LeftFlipperKey  .Switch(swLLFlip) = True : vpmKeyDown = False
            Case keyInsertCoin1  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
            Case keyInsertCoin2  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
            Case keyInsertCoin3  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin

And here is the script, which works for me.

' Keyboard handlers
Function vpmKeyDown(ByVal keycode)
	On Error Resume Next
	vpmKeyDown = True ' assume we handle the key
	With Controller
		If keycode = RightFlipperKey Then .Switch(swLRFlip) = True
		If keycode = LeftFlipperKey  Then .Switch(swLLFlip) = True
		Select Case keycode
			Case keyInsertCoin1  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin2  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin3  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin

In the last 3259 is again the non working vbs. What's the problem? Or is my installation a problem?

Edited by Joey2001, 03 December 2017 - 12:42 PM.

[flupper1]

Hey guys,
 
i have a problem regarding the rendering of insert lights. The problem is, when you are using a lot of (GI) light on the table, this will effect the brightness of the insert lights. I'm fighting this problem from the first day i was playing around with lighting. I usually do darker tables with big GI lights and i run into this problem every day! I have fooled around on the table i'm doing right now and i found out that the problem is the image that you are using for the lights when the bulb is disabled. To me it looks like VPX uses the rendered playfield for the image (when you have chosen the playfield for the image) which will double the amount of light on the insert light. I made a series of pictures that should make this clear (for whatever reason i'm not allowed to post a picture in the thread):
 
https://1drv.ms/i/s!...n9eP_AhN9Wscllw
 
The most important picture is the one with the IL intensity at 0,01! Compare it to the one with the IL turned off.
 
I have two questions for the devs now:
 
1. Is it possible that VPX is using the rendered playfield picture for the IL?
2. Would it be possible to add a checkbox to turn lighting on the light image on and off?
 
Big thanks to the devs! You guys are out of this world!
 
I'm in a hurry, i will answer any questions tomorrow!
 
Thanks

If you look at my tables (bk2000 or diner) you can see the workaround I use for this:
There is a non collidable wall at height 1 with an almost complete transparent texture
Only the light inserts are non transparent (black)
The insert light is placed on this wall and lights the insert
There is a normal light on the playfield level which cannot light up the insert ( because it is at height 0)
This way you can have any light 1 vp unit below the insert light, which does not affect the insert light

[Schlabber34]

Hey guys,
 
i have a problem regarding the rendering of insert lights. The problem is, when you are using a lot of (GI) light on the table, this will effect the brightness of the insert lights. I'm fighting this problem from the first day i was playing around with lighting. I usually do darker tables with big GI lights and i run into this problem every day! I have fooled around on the table i'm doing right now and i found out that the problem is the image that you are using for the lights when the bulb is disabled. To me it looks like VPX uses the rendered playfield for the image (when you have chosen the playfield for the image) which will double the amount of light on the insert light. I made a series of pictures that should make this clear (for whatever reason i'm not allowed to post a picture in the thread):
 
https://1drv.ms/i/s!...n9eP_AhN9Wscllw
 
The most important picture is the one with the IL intensity at 0,01! Compare it to the one with the IL turned off.
 
I have two questions for the devs now:
 
1. Is it possible that VPX is using the rendered playfield picture for the IL?
2. Would it be possible to add a checkbox to turn lighting on the light image on and off?
 
Big thanks to the devs! You guys are out of this world!
 
I'm in a hurry, i will answer any questions tomorrow!
 
Thanks

If you look at my tables (bk2000 or diner) you can see the workaround I use for this:
There is a non collidable wall at height 1 with an almost complete transparent texture
Only the light inserts are non transparent (black)
The insert light is placed on this wall and lights the insert
There is a normal light on the playfield level which cannot light up the insert ( because it is at height 0)
This way you can have any light 1 vp unit below the insert light, which does not affect the insert light

Crazy stuff! I understood what you explained. But it sounds like it's a bit timeconsuming. I can only work at a snail pace and i have to take every short cut i can get.

Thanks for the reply! You do awesome stuff man!

Gesendet von meinem SM-A510F mit Tapatalk

[toxie]

@Joey: What i did should be an equivalent cleanup, so did you also update VPMKeys.vbs? That one changed, too!

 

Otherwise i changed

Function vpmKeyDown(ByVal keycode)
	On Error Resume Next
	vpmKeyDown = True ' assume we handle the key
	With Controller
		If keycode = RightFlipperKey Then .Switch(swLRFlip) = True
		If keycode = LeftFlipperKey  Then .Switch(swLLFlip) = True
		Select Case keycode
			Case keyInsertCoin1  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin2  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin3  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case StartGameKey    .Switch(swStartButton)   = True
			Case keyUp		   .Switch(swDiagnostics)   = Not .Switch(swDiagnostics)
			Case keyHiScoreReset .Switch(swStatistics)    = Not .Switch(swStatistics)
			Case keySelfTest     .Switch(swService)       = Not .Switch(swService)
			Case keyDown         .Switch(swAdjustments)   = Not .Switch(swAdjustments)
			Case 12              .Switch(swConfigurations)= True
			Case keyEnter        .Switch(swEnter)         = True
			Case keySlamDoorHit  .Switch(swSlamTilt)      = True
			Case keyCoinDoor     If toggleKeyCoinDoor Then .Switch(swCoinDoor) = Not .Switch(swCoinDoor) Else .Switch(swCoinDoor) = Not inverseKeyCoinDoor
			Case 13		   .Switch(swSoundDiag)     = Not .Switch(swSoundDiag)
			Case keyMasterEnter  .Switch(swBoxDoor)       = Not .Switch(swBoxDoor)
			Case keyBangBack     vpmNudge.DoNudge   0,6
			Case LeftTiltKey     vpmNudge.DoNudge  75,2
			Case RightTiltKey    vpmNudge.DoNudge 285,2
			Case CenterTiltKey   vpmNudge.DoNudge   0,2
			Case keyVPMVolume    vpmVol
			Case Else            vpmKeyDown = False
		End Select
	End With
	On Error Goto 0
End Function

to:

nction vpmKeyDown(ByVal keycode)
	On Error Resume Next
	vpmKeyDown = True ' assume we handle the key
	With Controller
		Select Case keycode
			Case RightFlipperKey .Switch(swLRFlip) = True : vpmKeyDown = False
			Case LeftFlipperKey  .Switch(swLLFlip) = True : vpmKeyDown = False
			Case keyInsertCoin1  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin2  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin3  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case StartGameKey    .Switch(swStartButton)   = True
			Case keyUp	         .Switch(swDiagnostics)   = Not .Switch(swDiagnostics)
			Case keyHiScoreReset .Switch(swStatistics)    = Not .Switch(swStatistics)
			Case keySelfTest     .Switch(swService)       = Not .Switch(swService)
			Case keyDown         .Switch(swAdjustments)   = Not .Switch(swAdjustments)
			Case keyConfigurations .Switch(swConfigurations) = True
			Case keyEnter        .Switch(swEnter)         = True
			Case keySlamDoorHit  .Switch(swSlamTilt)      = True
			Case keyCoinDoor     If toggleKeyCoinDoor Then .Switch(swCoinDoor) = Not .Switch(swCoinDoor) Else .Switch(swCoinDoor) = Not inverseKeyCoinDoor
			Case keySoundDiag    .Switch(swSoundDiag)     = Not .Switch(swSoundDiag)
			Case keyMasterEnter  .Switch(swBoxDoor)       = Not .Switch(swBoxDoor)
			Case keyBangBack     vpmNudge.DoNudge   0,6
			Case LeftTiltKey     vpmNudge.DoNudge  75,2
			Case RightTiltKey    vpmNudge.DoNudge 285,2
			Case CenterTiltKey   vpmNudge.DoNudge   0,2
			Case keyVPMVolume    vpmVol
			Case Else            vpmKeyDown = False
		End Select
	End With
	On Error Goto 0
End Function

Edited by toxie, 04 December 2017 - 06:35 AM.

[Rajo Joey]

 

@Joey: What i did should be an equivalent cleanup, so did you also update VPMKeys.vbs? That one changed, too!

 

Otherwise i changed

Function vpmKeyDown(ByVal keycode)
	On Error Resume Next
	vpmKeyDown = True ' assume we handle the key
	With Controller
		If keycode = RightFlipperKey Then .Switch(swLRFlip) = True
		If keycode = LeftFlipperKey  Then .Switch(swLLFlip) = True
		Select Case keycode
			Case keyInsertCoin1  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin2  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin3  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case StartGameKey    .Switch(swStartButton)   = True
			Case keyUp		   .Switch(swDiagnostics)   = Not .Switch(swDiagnostics)
			Case keyHiScoreReset .Switch(swStatistics)    = Not .Switch(swStatistics)
			Case keySelfTest     .Switch(swService)       = Not .Switch(swService)
			Case keyDown         .Switch(swAdjustments)   = Not .Switch(swAdjustments)
			Case 12              .Switch(swConfigurations)= True
			Case keyEnter        .Switch(swEnter)         = True
			Case keySlamDoorHit  .Switch(swSlamTilt)      = True
			Case keyCoinDoor     If toggleKeyCoinDoor Then .Switch(swCoinDoor) = Not .Switch(swCoinDoor) Else .Switch(swCoinDoor) = Not inverseKeyCoinDoor
			Case 13		   .Switch(swSoundDiag)     = Not .Switch(swSoundDiag)
			Case keyMasterEnter  .Switch(swBoxDoor)       = Not .Switch(swBoxDoor)
			Case keyBangBack     vpmNudge.DoNudge   0,6
			Case LeftTiltKey     vpmNudge.DoNudge  75,2
			Case RightTiltKey    vpmNudge.DoNudge 285,2
			Case CenterTiltKey   vpmNudge.DoNudge   0,2
			Case keyVPMVolume    vpmVol
			Case Else            vpmKeyDown = False
		End Select
	End With
	On Error Goto 0
End Function

to:

nction vpmKeyDown(ByVal keycode)
	On Error Resume Next
	vpmKeyDown = True ' assume we handle the key
	With Controller
		Select Case keycode
			Case RightFlipperKey .Switch(swLRFlip) = True : vpmKeyDown = False
			Case LeftFlipperKey  .Switch(swLLFlip) = True : vpmKeyDown = False
			Case keyInsertCoin1  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin2  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case keyInsertCoin3  vpmTimer.AddTimer 750,"vpmTimer.PulseSw swCoin1'" : Playsound SCoin
			Case StartGameKey    .Switch(swStartButton)   = True
			Case keyUp	         .Switch(swDiagnostics)   = Not .Switch(swDiagnostics)
			Case keyHiScoreReset .Switch(swStatistics)    = Not .Switch(swStatistics)
			Case keySelfTest     .Switch(swService)       = Not .Switch(swService)
			Case keyDown         .Switch(swAdjustments)   = Not .Switch(swAdjustments)
			Case keyConfigurations .Switch(swConfigurations) = True
			Case keyEnter        .Switch(swEnter)         = True
			Case keySlamDoorHit  .Switch(swSlamTilt)      = True
			Case keyCoinDoor     If toggleKeyCoinDoor Then .Switch(swCoinDoor) = Not .Switch(swCoinDoor) Else .Switch(swCoinDoor) = Not inverseKeyCoinDoor
			Case keySoundDiag    .Switch(swSoundDiag)     = Not .Switch(swSoundDiag)
			Case keyMasterEnter  .Switch(swBoxDoor)       = Not .Switch(swBoxDoor)
			Case keyBangBack     vpmNudge.DoNudge   0,6
			Case LeftTiltKey     vpmNudge.DoNudge  75,2
			Case RightTiltKey    vpmNudge.DoNudge 285,2
			Case CenterTiltKey   vpmNudge.DoNudge   0,2
			Case keyVPMVolume    vpmVol
			Case Else            vpmKeyDown = False
		End Select
	End With
	On Error Goto 0
End Function

Ah, that's the problem. I don't change the VPMKeys.vbs, because I edit it a while ago for some tables, so I can use special buttons.

OK, update it and the problem is solved.

[Joppnl]

 

rev5259 is up:

 

 

 

I guess it should be 3259 as that's the one in the start-post ?  (and that one does have the nudge-table)...

[fuzzel]

 

 

rev5259 is up:

 

 

 

I guess it should be 3259 as that's the one in the start-post ?  (and that one does have the nudge-table)...

 

yes right...was a typo

[SPAMP]

Is there a beginners thread for optimizing play and graphics? New to the hobby a few weeks and everything was working fine. I then noticed some ball stutter withing PinballX so I reverted to playing exclusively with direct VPX launches. over time things got worse and tables are unplayable even in VPX directly. I have core i5 with 16GB ram and GTX 1050 ti ... i realize there are multiple layers between global settings on the card vs application control and then within VPX I assume there are global vs table specific settings. Is there a good article or materials I can read to get the gist of all of this or is there a reco'd setting that works for most things but may not be the best graphically I can apply. With dozens of setting and multiple layers between the card and the program it can be a little overwhelming. 

~Thanks!

 

PS I am running 10.4 beta

Edited by SPAMP, 07 December 2017 - 03:01 PM.

[fuzzel]

Is there a beginners thread for optimizing play and graphics? New to the hobby a few weeks and everything was working fine. I then noticed some ball stutter withing PinballX so I reverted to playing exclusively with direct VPX launches. over time things got worse and tables are unplayable even in VPX directly. I have core i5 with 16GB ram and GTX 1050 ti ... i realize there are multiple layers between global settings on the card vs application control and then within VPX I assume there are global vs table specific settings. Is there a good article or materials I can read to get the gist of all of this or is there a reco'd setting that works for most things but may not be the best graphically I can apply. With dozens of setting and multiple layers between the card and the program it can be a little overwhelming. 
~Thanks!
 
PS I am running 10.4 beta

Use the search option and you will find a lot of informations how to tweak your system for smooth game play. You should post your questions in the help section. This thread is for testing the beta version of VP and for reporting bugs

[32assassin]

can you please add this mesh to the Stand up target list

https://www.dropbox....target.obj?dl=0

 

another missing stand up target

I found more than one table that has flat rectangle stand up targets

 

by the ramp entrance

http://www.ipdb.org/...000&picno=48041

 

and 

http://www.ipdb.org/...no=41861&zoom=1

 

 

can you duplicate the "Drop Target Flat Simple" mesh and add it as a stand up target

[BorgDog]

Hi,

 

......

 

Only annoying is that one: opening the material manager does not switch the cursor focus towards the manager, so that hitting the "Del" key (while editing the material name) is deleting any marked table object.

 

Regards

Michael

 

Can this very annoying bug be looked at?  I don't know how many times I've deleted playfield objects when I was editing the name of a material or collection and pressed the delete key expecting to delete a character in the field I'm in but nope, deleted whatever playfield object was selected at that time.  Backspace key works, delete key does not.

[BorgDog]

can we also revisit the add/remove collection workings.  It's fine if you are only doing one object, but the real strength could be when you select multiple objects, but it's current restrictions make it mostly useless at that.  

 

Maybe it would be easier if the Add and Remove were separate options.  for example, I could select a bunch of objects then right-click and say Add to Collection and all of them would be added to that collection whether they were in it or not and if they were already in there it would not double-add of course.  or select a bunch of objects and say Remove from Collection and they would all be removed.  this would eliminate the confusion involved with have a bunch of objects selected that may or may not be in the same collections.

 

It basically becomes make sure all these are in this collection or make sure all these are not in this collection.  Along with this I could see that the only time the check mark by the collection comes into play is if all of the selected objects (whether 1 or many) are in a collection.

[fuzzel]

Hi,
 
......
 
Only annoying is that one: opening the material manager does not switch the cursor focus towards the manager, so that hitting the "Del" key (while editing the material name) is deleting any marked table object.
 
Regards
Michael

 
Can this very annoying bug be looked at?  I don't know how many times I've deleted playfield objects when I was editing the name of a material or collection and pressed the delete key expecting to delete a character in the field I'm in but nope, deleted whatever playfield object was selected at that time.  Backspace key works, delete key does not.

Yes that is annoying but the only fast way in fixing this is to change the dialog to modal. If a dialog ist modeless you have to handle all special key strokes by your own.

[BorgDog]

is there a drawback to that?  you just switched the properties dialogs to modal, any reason to not do all the dialogs?

[fuzzel]

Well it was a request to have modeless dialogs for the managers.
And no there is no drawback if I switch them back.

Edited by fuzzel, 13 December 2017 - 03:28 PM.

[wrd1972]

Toxie, Fuzzel,

Please take a look at the flipper physics testing thread and see my last reply.

http://www.vpforums....984#entry395097

 

Many thanks guys.

[fuzzel]

rev3262 is up:

 

- add support for loading auto POV settings if they exists. You can now define an extra POV xml file for each table and name it like the VPX file.

  Example: you have custom POV settings for the table "QBerts Quest (Gottlieb 1983).vpx" then save the POV settings into the file "QBerts Quest (Gottlieb 1983).xml" and place it 

           in the same directory as the VPX file. Now VPX will load the POV settings when loading the "QBerts Quest (Gottlieb 1983).vpx" (in the editor/player).

  Or if you like to have a default POV settings that is used for all other tables save it under "autopov.xml"

 

- only allow material names with a max size of 31 characters

[toxie]

@wrd1972: hopefully soon.. but no promises.. :/

[jimmihenry]

Unfortunely the VPX_4_beta_rev3262 does not start . It loads the table and crashes. Is there a log file to see what happens?

All files were updated and dll's allowed. MS .NET Framework 4.7 is installed also MS XNA Framework Redis... 3.0 and 3.1 and 4.0.

Previous Beta (VPX_4_beta_rev3259) doesen't crash. Any ideas?