Hi,
got it. I have to use GICallBack2, as this one is returning the brightness level instead of True/False...
Implementing it just now.
Michael
Posted 11 October 2017 - 11:08 PM
Broken record comment on my part I know but I'm very excited about comments such as ball jumping over plastics, etc. VPX's ball physics have really been blowing me away, much more organic than a couple of years ago. Can't wait to try this, looks like it's coming together well and it's uniqueness is very appreciated by many of us
Posted 12 October 2017 - 10:09 PM
Very nice Michael - a VPX of this table is something I'm really looking forward to have in my collection. This is one of the tables that are great on VP9, but, I'm sure - can't even come close to VPX once you've finished it. So, thank you in advance ![]()
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 15 October 2017 - 09:41 AM
Hi,
after releasing the VPX version, I looked a bit into the existing B2S backglasses. As there seems to be no backglass with accurate GI and solenoid handling, I started a new B2S project and realized soon that the normal ROM communication regarding solenoids and GI strings is a bit faulty. So I set up a manual B2S communication.
The backglass now has proper GI string 3 support with two levels of intensity, working flashers and correct light positions (as far as I was able to locate the normal bulbs).
The new B2S calls will be implemented in the next table version.
Michael
Posted 15 October 2017 - 11:55 AM
Edited by mattbini, 15 October 2017 - 12:13 PM.
Posted 15 October 2017 - 01:38 PM
The beta updates as any other stand alone package. So, yes - overwrite. You could however rename your old to 10.3.xxx.exe and then do the update. I advice everyone to go for 10.4. Especially if you are editing tables. It has a lot of stability improvements and in general is as expected, better than 10.3 ;-)
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 15 October 2017 - 03:29 PM
Edited by mattbini, 15 October 2017 - 04:21 PM.
Posted 15 October 2017 - 04:22 PM
The problem you are experiencing is most probably that you haven't set ddraw in registry to a 0. You need that when you run exclusive mode or it will crash. Honestly. I don't know why we still have ddraw set to 1 as default. It seems to work pretty good with it disable for both windows/exclusive fullscreen.
This tables uses cp_16 rom ... so change
\\hkcu\software\freeware\visual pinmame\ch_16\ddraw to a 0. ( from memory - might be slightly wrong )
Edited by Thalamus, 15 October 2017 - 04:24 PM.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 15 October 2017 - 05:29 PM