- 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
1488 replies to this topic
#1203
Posted 07 October 2019 - 05:50 PM
#1206
Posted 07 October 2019 - 09:33 PM
Thanks thalamus, stat and toxie. I finally got it installed and running.
Ive must have clicked the same button 15 times and nothing changed. Then one click and it changed on display 1 and it worked. I have no clue what was going on but it works now.
Here is a picture of my setting that worked for me.
Again thanks to all,
Mike
Ive must have clicked the same button 15 times and nothing changed. Then one click and it changed on display 1 and it worked. I have no clue what was going on but it works now.
Here is a picture of my setting that worked for me.
Again thanks to all,
Mike
Attached Files
#1207
Posted 08 October 2019 - 11:22 AM
Thanks thalamus, stat and toxie. I finally got it installed and running.
Ive must have clicked the same button 15 times and nothing changed. Then one click and it changed on display 1 and it worked. I have no clue what was going on but it works now.
Here is a picture of my setting that worked for me.
Again thanks to all,
Mike
Yeah, sorry for that. The code for this still seems to be a bit flaky.. Hopefully Caligula will revisit it at some point again.. :/
error message ver 3788 os win10 pro 1903 18362.388 nvidia 436.48
Interesting.. Was there anything special that you did that could have caused this? Or just out of nowhere during normal gameplay?
#1208
Posted 08 October 2019 - 04:42 PM
Quick question. Now that x/y scale is linked. Do we still need to use z offset? I like how adjusting x/y now maintains a 1:1 ratio.
Sent from my SM-G965U1 using Tapatalk
Its really your call depending on how you like your POV. Personally I use a z-offset of 0 for all tables...right or wrong. And yes the linked X/Y scale has been extremely useful for me to maintain 1:1 as close as possible.
My VP Pincab /MAME Arcade Specs: Dell T3400 workstation with Core2 Quad core 3.0GHZ (Q9650) CPU - 8GB of RAM - Nvidia GTX 970
40" PF Sony gaming LED TV, Dual 21" Dell monitors in the backbox - Pinscape dual boards - Full DOF - Full MAME arcade support.
#1211
Posted 09 October 2019 - 02:45 PM
Crash.txt:
Crash report VPX rev3788
============
Process: VPinballX.exe
Reason: 0xE06D7363 - UNKNOWN at 0023:75DC3562
Thread ID: 0x1C64 [7268]
Call stack
==========
75DC3562 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x0019c3c0)
00534840 VPinballX.exe (0x0019C3DC 0x006941E4 0x00562214 0x108d45e8)
00530E09 VPinballX.exe (0x0058CFDC 0x0041AA32 0x02DCBFC0 0x02dbd120)
0041C1DA VPinballX.exe (0x00000507 0x00470E80 0x02DCBF90 0x0019eee4)
00470E80 VPinballX.exe (0x0000010A 0x0000004E 0x00000000 0x00473e70)
004740E2 VPinballX.exe (0x000B0FC6 0x0000004E 0x00000000 0x0019f3b8)
76A648EB USER32.dll AddClipboardFormatListener + 0x4B (0x00473E70 0x000B0FC6 0x0000004E 0x00000000)
76A4613C USER32.dll CallWindowProcW + 0xB2C (0x00473E70 0x00000000 0x0000004E 0x00000000)
76A45CDA USER32.dll CallWindowProcW + 0x6CA (0x036BF660 0x00000000 0x0000004E 0x00000000)
76A4E6BF USER32.dll IsRectEmpty + 0x1FF (0x0019F2DC 0x00000020 0x0019F544 0x77674100)
776741CD ntdll.dll KiUserCallbackDispatcher + 0x4D (0x036BF660 0x00000000 0x0019F3B8 0x00000001)
76A5A59D USER32.dll SendMessageA + 0x11D (0x000B0FC6 0x0000004E 0x00000000 0x0019f3b8)
6DC587AA SciLexerVP.DLL (0x00000001 0x43590000 0x43640000 0x0015103c)
6DC282B3 SciLexerVP.DLL (0x00000003 0x02DC2D40 0x0015103C 0x6dc5ba80)
6DC573B8 SciLexerVP.DLL (0x00000113 0x00000006 0x00000000 0x00000113)
6DC5BB99 SciLexerVP.DLL Scintilla_DirectFunction + 0x139 (0x0015103C 0x00000113 0x00000006 0x00000000)
76A648EB USER32.dll AddClipboardFormatListener + 0x4B (0x6DC5BA80 0x0015103C 0x00000113 0x00000006)
76A4613C USER32.dll CallWindowProcW + 0xB2C (0x6DC5BA80 0x00000000 0x00000113 0x00000006)
76A4528E USER32.dll DispatchMessageW + 0x22E (0x00000006 0x0019F9AC 0x0019F9A4 0x00000000)
76A49291 USER32.dll IsDialogMessageW + 0x101 (0x000B0FC6 0x0019F9A4 0x0019F9A4 0x0019f9cc)
76A6102E USER32.dll IsDialogMessage + 0x4E (0x000B0FC6 0x0019F9A4 0x76A5EE70 0x76a661e0)
0052E2E2 VPinballX.exe (0x0019F9A4 0x0019F9CC 0x00000000 0x0069fc08)
00520987 VPinballX.exe (0x00400000 0x7771DCA0 0x02D31920 0x00000000)
Environment
===========
Date/time: 6/10/2019, 20:14:10:22
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 18362)
Memory status
=============
Total Reserved: 70428K (68M) bytes
Total Commited: 323980K (316M) bytes
Total Free: 3799832K (3710M) bytes
Largest Free: 2095452K (2046M) bytes
Registers
=========
EAX=0019C330 EBX=0019C3DC ECX=00000003 EDX=00000000
ESI=00582BDC EDI=006941E4 EBP=00000000 ESP=00294008 EIP=FFFFFFFF
FLG=00000216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B
Mini dump saved successfully.
#1212
Posted 09 October 2019 - 03:28 PM
I have a question about fov.
Is it possible to develop for the fov, a separate setting fov for x and for y?.. For exemple, like if table were on a cylindrer not a pyramide like today ? My idea is to keep table rectangulare and only setting Y FOV and Backdrop and inclinaison, to have a "very sloping" table on back but not on the front with pyramidale table. I do not know if I'm clear
#1213
Posted 09 October 2019 - 07:38 PM
History : Flintstones released. At the same time updating to 10.6 official. On first load of table - crash with dialogbox unknown error. Opening other tables, no problem. Reboot, Flintstones ok several times in a row all evening long no other tables with problems either. Rob releases unoffical fix https://vpinball.com.../6/#post-147456. Clean startup of computer, rename offical vpinballx and replace. Same crash as above. Can't load this table. Trying to start with renamed exe - same issue. New reboot and Rob' is working without any problems.
So, what I'm saying. It seems that once this happens, only a reboot will help to play this table.
Crash report VPX rev3788
============
Process: VPinballX_106_official.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004D3A7E
Attempt to read from 0x00000000
Thread ID: 0xB90 [2960]
Call stack
==========
004D3A7E VPinballX_106_official.exe (0x183CCE80 0x00000000 0xFFFFFFFFFFFFFFFF 0x0018ee14)
004D4D8A VPinballX_106_official.exe (0x000121D3 0x000C0166 0x000C0A4E 0x02e497b0)
004D1B20 VPinballX_106_official.exe (0x00000004 0x00000004 0x00000004 0x00000000)
74D93E5D kernel32.dll lstrcmpiA + 0x2F (0x00000004 0x02E497B0 0x000C0166 0x000c0a4e)
004B6CA1 VPinballX_106_official.exe (0x00000000 0x00000000 0x00008012 0x00040a18)
0052BD92 VPinballX_106_official.exe (0x00008012 0x03010D68 0x00040A18 0x00000000)
0052EA30 VPinballX_106_official.exe (0x00040A18 0x00000111 0x00008012 0x00050a1a)
76E962FA user32.dll gapfnScSendMessage + 0x332 (0x0052E930 0x00040A18 0x00000111 0x00008012)
76E96D3A user32.dll GetThreadDesktop + 0xD7 (0x00000000 0x0052E930 0x00040A18 0x00000111)
76E9965E user32.dll GetWindow + 0x3F0 (0x032565E0 0x00000000 0x0052E930 0x00008012)
76E996C5 user32.dll SendMessageW + 0x4C (0x00040A18 0x00000111 0x00008012 0x00050a1a)
7163CE60 COMCTL32.dll CreateToolbar + 0x286C (0x02E04E60 0x00050A1A 0x00000202 0x00008012)
7161B01F COMCTL32.dll CreateMappedBitmap + 0xA42 (0x00050A1A 0x00000202 0x00000000 0x00700053)
76E962FA user32.dll gapfnScSendMessage + 0x332 (0x716180BB 0x00050A1A 0x00000202 0x00000000)
76E96D3A user32.dll GetThreadDesktop + 0xD7 (0x00000000 0x716180BB 0x00050A1A 0x00000202)
76E977C4 user32.dll CharPrevW + 0x138 (0x716180BB 0x00000001 0x0018FA20 0x00520993)
76E97BCA user32.dll DispatchMessageA + 0xF (0x0018F9BC 0x00000000 0x0069FC08 0x00000000)
00520993 VPinballX_106_official.exe (0x00000000 0x0069FC08 0xFFFFFFFFFFFDE000 0x00684920)
00520AF6 VPinballX_106_official.exe (0x00400000 0x00000000 0x02D9444F 0x00000001)
0053288B VPinballX_106_official.exe (0xFFFFFFFFFFFDE000 0x0018FFD4 0x774B9902 0xfffffffffffde000)
74D9336A kernel32.dll BaseThreadInitThunk + 0x12 (0xFFFFFFFFFFFDE000 0x774F55DF 0x00000000 0x00000000)
774B9902 ntdll.dll RtlInitializeExceptionChain + 0x63 (0x02BC6340 0xFFFFFFFFFFFDE000 0x00000000 0x00000000)
774B98D5 ntdll.dll RtlInitializeExceptionChain + 0x36 (0x02BC6340 0xFFFFFFFFFFFDE000
Environment
===========
Date/time: 9/10/2019, 21:25:23:591
Number of CPUs: 4
Processor type: 586
System: Windows 7
Memory status
=============
Total Reserved: 78016K (76M) bytes
Total Commited: 2001624K (1954M) bytes
Total Free: 2114600K (2065M) bytes
Largest Free: 2039036K (1991M) bytes
Registers
=========
EAX=00000000 EBX=0D23BAC0 ECX=00000006 EDX=0018EA30
ESI=7EA550D0 EDI=183CCE80 EBP=0018FFEC ESP=0018FFDC EIP=774B98D5
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B
Mini dump saved successfully.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
#1215
Posted 09 October 2019 - 08:34 PM
Not surprised. I haven't had any issues with any regular tables in ages. ( Well, except for reports that you devs has been informed of related to at91jit and freezy.) Just this one that has been acting out on me a few times. i can investigate a bit with older versions next week. Just to make it clear. If table starts successfully, there is no issues - at least not yet ![]()
Edited by Thalamus, 10 October 2019 - 04:02 PM.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
#1216
Posted 10 October 2019 - 02:42 PM
and actually not with the build before that one? (see versions from here: https://vpinball.com.../vp-10-6-beta/)
(same question for Thalamus btw)
Edited by toxie, 10 October 2019 - 02:42 PM.
#1217
Posted 10 October 2019 - 04:00 PM
Not at home until next week. So that is why I said I won't test until next week. I will once I'm back.
Busy with this event ![]()
Edited by Thalamus, 10 October 2019 - 04:01 PM.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Also tagged with one or more of these keywords: beta, 10.6 beta
Visual Pinball →
VR Discussion →
Visual Pinball VR Support →
DMD Issues with beta 10.8.1Started by pachakamakk , 15 Nov 2025 |
|
||
Visual Pinball →
Visual Pinball →
Insanely bright lights on some tables (VP10.8 final & VPinMAME 3.7 beta)Started by SixOfTwelve , 17 Jul 2025 |
|
||
Visual Pinball →
Visual Pinball →
VPX 10.7 and VPX 10.8 betaStarted by telmoabff , 12 Jul 2023 |
|
||
Visual Pinball →
Visual Pinball →
The VP 10.8 beta threadStarted by toxie , 19 May 2023 |
|
||
Visual Pinball →
VP Help Center →
Script button not workingStarted by JSpradlin , 10 Sep 2017 |
|


Top


















are all trademarks of VPFORUMS.