Jump to content



Photo
* * * * * 8 votes

The VP 10.6 beta thread

beta 10.6 beta

  • Please log in to reply
1488 replies to this topic

#401 lukpcn

lukpcn

    Enthusiast

  • Members
  • PipPipPip
  • 249 posts

  • Flag: Poland

  • Favorite Pinball: I love all !!! :)

  • PS3 Gamer Tag: N/A
  • 360 Gamer Tag: N/A

Posted 08 February 2019 - 04:14 PM

Me too:

 

Crash report VPX rev3623
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0051EBB0
Attempt to read from 0x00000000
Thread ID: 0x1828 [6184]

Call stack
==========
0051EBB0 VPinballX.exe (0x17E4BDB0 0x2770F100 0x3F9020CD 0x00000000)
004DFADE VPinballX.exe (0x00000000 0x00000002 0x2770F100 0x74b66360)
004E597E VPinballX.exe (0x004EA65D 0x004EA68E 0x02E9E120 0x0019fa2c)
6FBD3F37 d3d9.dll (0x004EA68E 0x02E9E120 0x0019FA2C 0x74b66360)
004EA65D VPinballX.exe (0x02E9E120 0x0019FA2C 0x74B66360 0x00000001)
004EA68E VPinballX.exe (0x38408B00 0x006A006A 0x6A088B57 0xffffffffff505200)
0005DBE9  (0x006A006A 0x6A088B57 0xFFFFFFFFFF505200 0x00008891)
38408B00  (0x6A088B57 0xFFFFFFFFFF505200 0x00008891 0x0fc08500)
006A006A VPinballX.exe (0xFFFFFFFFFF505200 0x00008891 0x0FC08500 0xffffffffffff5789)
6A088B57  (0x00000000 0x00000000 0x00000000 0x00000000)

Environment
===========
Date/time: 8/2/2019, 14:57:19:269
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 17134)

Memory status
=============
Total Reserved: 431256K (421M) bytes
Total Commited: 1054908K (1030M) bytes
Total Free: 2708076K (2644M) bytes
Largest Free: 2095548K (2046M) bytes

Registers
=========
EAX=100DC689 EBX=00000002 ECX=00000000 EDX=00000000
ESI=0DE40940 EDI=0DE408B0 EBP=006A006A ESP=004EA671 EIP=6A088B57
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.
 


Regards

Luk

My Pinball Youtube Channel: https://www.youtube....lPinballFanatic


#402 psmiraglia

psmiraglia

    Enthusiast

  • Members
  • PipPipPip
  • 114 posts

  • Flag: Argentina

  • Favorite Pinball: Star Trek

Posted 08 February 2019 - 09:09 PM

FYI : POV can be extracted easily with the filenames intact today via the cmd prompt. I basically make a wrapper to extract table scripts ( same thing - just and option change )

 

See what pov exists - see what tables exists - for tables that pov doens't exists already - run a loop and extract - done.

@Thalamus where can I get the command-line reference fro VPX ? I'm interested in both bolk creating the POVs, and see what other options I can use at launch (forcing vsync would be handy for me). I was not able to find a good list of command line switches...



#403 Thalamus

Thalamus

    Pinball Wizard

  • Platinum Supporter
  • 4,976 posts

  • Flag: Norway

  • Favorite Pinball: GOT, Alien Star, LOTR, TOM

Posted 08 February 2019 - 09:44 PM

I believe it supports --help or was it that if you added a illegal option it would spew it out.

 

You can get a list of options with

 

c:\xxx\vpinballx.exe /?


Edited by Thalamus, 09 February 2019 - 11:15 AM.

From now on. I won't help anyone here at VPF. Please ask Noah why that is.


#404 fuzzel

fuzzel

    spaghetti code

  • VP Dev Team
  • PipPipPipPipPip
  • 2,818 posts

  • Flag: Germany

  • Favorite Pinball: yes I have

Posted 09 February 2019 - 02:03 PM

rev3628 is up:

 

- add-on patch by Caligula for display selection, incl. proper handling for multiGPU setups
- updating hitthreshold handling


#405 chepas

chepas

    t.me/horsepin

  • Members
  • PipPipPipPip
  • 1,966 posts

  • Flag: ---------

  • Favorite Pinball: BSD, Tr0n, SW:Stern

Posted 09 February 2019 - 04:51 PM

Crash report VPX rev3608
============
Process: vpinballx.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:005432AE
Attempt to read from 0x06CDF000
Thread ID: 0x2290 [8848]

Call stack
==========
005432AE vpinballx.exe (0x6F170030 0x06C8A3A5 0x004087E7 0x0018ef74)
0048ABCB vpinballx.exe (0x69E90057 0xFFFFFFFFB800007C 0x0057B05C 0x007c5fe9)
B074B800  (0xFFFFFFFFA59599A2 0xFFFFFFFF9DA7989B 0xFFFFFFFF9D9FAA9A 0xffffffffac9ea1ab)
9498A193  (0xFFFFFFFF9DA7989B 0xFFFFFFFF9D9FAA9A 0xFFFFFFFFAC9EA1AB 0xffffffffa1aa9fa2)
A59599A2  (0xFFFFFFFF9D9FAA9A 0xFFFFFFFFAC9EA1AB 0xFFFFFFFFA1AA9FA2 0xffffffff9a9da79d)
9DA7989B  (0xFFFFFFFFAC9EA1AB 0xFFFFFFFFA1AA9FA2 0xFFFFFFFF9A9DA79D 0xffffffff9f9599a2)
9D9FAA9A  (0xFFFFFFFFA1AA9FA2 0xFFFFFFFF9A9DA79D 0xFFFFFFFF9F9599A2 0xffffffff939d9295)
AC9EA1AB  (0xFFFFFFFF9A9DA79D 0xFFFFFFFF9F9599A2 0xFFFFFFFF939D9295 0xffffffff8c919a8f)
A1AA9FA2  (0xFFFFFFFF9F9599A2 0xFFFFFFFF939D9295 0xFFFFFFFF8C919A8F 0xffffffff998b8f99)
9A9DA79D  (0xFFFFFFFF939D9295 0xFFFFFFFF8C919A8F 0xFFFFFFFF998B8F99 0xffffffff919b8b8f)
9F9599A2  (0xFFFFFFFF8C919A8F 0xFFFFFFFF998B8F99 0xFFFFFFFF919B8B8F 0xffffffff8f929c8e)
939D9295  (0xFFFFFFFF998B8F99 0xFFFFFFFF919B8B8F 0xFFFFFFFF8F929C8E 0xffffffff9c90929c)
8C919A8F  (0xFFFFFFFF919B8B8F 0xFFFFFFFF8F929C8E 0xFFFFFFFF9C90929C 0xffffffff929c9092)
998B8F99  (0xFFFFFFFF8F929C8E 0xFFFFFFFF9C90929C 0xFFFFFFFF929C9092 0xffffffff92939d91)
919B8B8F  (0xFFFFFFFF9C90929C 0xFFFFFFFF929C9092 0xFFFFFFFF92939D91 0xffffffff9e92929d)
8F929C8E  (0xFFFFFFFF929C9092 0xFFFFFFFF92939D91 0xFFFFFFFF9E92929D 0xffffffff94a19293)
9C90929C  (0xFFFFFFFF92939D91 0xFFFFFFFF9E92929D 0xFFFFFFFF94A19293 0xffffffff9596a393)
929C9092  (0xFFFFFFFF9E92929D 0xFFFFFFFF94A19293 0xFFFFFFFF9596A393 0xffffffffa59598a5)
92939D91  (0xFFFFFFFF94A19293 0xFFFFFFFF9596A393 0xFFFFFFFFA59598A5 0xffffffff94a39496)
9E92929D  (0xFFFFFFFF9596A393 0xFFFFFFFFA59598A5 0xFFFFFFFF94A39496 0xffffffff9192a292)
94A19293  (0xFFFFFFFFA59598A5 0xFFFFFFFF94A39496 0xFFFFFFFF9192A292 0xffffffffa69292a3)
9596A393  (0xFFFFFFFF94A39496 0xFFFFFFFF9192A292 0xFFFFFFFFA69292A3 0xffffffff93a69394)
A59598A5  (0xFFFFFFFF9192A292 0xFFFFFFFFA69292A3 0xFFFFFFFF93A69394 0xffffffff9392a594)
94A394969192A292A69292A393A693949392A594A1757C7979 S
Environment
===========
Date/time: 9/2/2019, 16:48:38:99
Number of CPUs: 6
Processor type: 586
System: Unknown Windows version - 6.3 (9600)

Memory status
=============
Total Reserved: 590716K (576M) bytes
Total Commited: 1793836K (1751M) bytes
Total Free: 1809688K (1767M) bytes
Largest Free: 1655160K (1616M) bytes

Registers
=========
EAX=69DFA395 EBX=004087E7 ECX=000ECEE3 EDX=00000003
ESI=06CDEFFD EDI=6F1C4C88 EBP=8280808B ESP=007C7465 EIP=757C7979
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

I only get crashes (not all the time) when I try to go back to the editor after a game. It's only really just started to get annoying because I have to clear out the dump which can be 1-2gb.


Bump maps are the new auto-tune :BDH:
VPX - RSS Updates ---- blog.flippingflips.xyz/en/ -- Visual Pinball No.1 (2021) . Est.2000


#406 Mark70

Mark70

    Enthusiast

  • Members
  • PipPipPip
  • 421 posts

  • Flag: Germany

  • Favorite Pinball: Godzilla 70th anniv. T2, Jack*Bot, ToM, ST-2013, Pinball Champ 82

Posted 09 February 2019 - 05:14 PM

Thanks to all involved for another update!



#407 BorgDog

BorgDog

    We come in peace.. shoot to kill.. shoot to kill.

  • Members
  • PipPipPipPip
  • 1,427 posts
  • Location:Leavenworth, WA

  • Flag: United States of America

  • Favorite Pinball: Alien Star, TNA



Posted 09 February 2019 - 05:17 PM

Been getting a lot of crashes with the last two betas.  This one is with latest, 1 table open, played a game, went to exit back to editor and crash. 

win10x64, geforce 940m driver ver 398.36

 

https://www.dropbox..../crash.zip?dl=0



#408 Thalamus

Thalamus

    Pinball Wizard

  • Platinum Supporter
  • 4,976 posts

  • Flag: Norway

  • Favorite Pinball: GOT, Alien Star, LOTR, TOM

Posted 09 February 2019 - 10:54 PM

http://thalamus.no-ip.com/devs/

 

Win7-64bit - nVidia 1080.driver 373.06

 

My first crash in a long time on the cab. Have seen instabilities in this, 3628, and the 2 previous versions on my desktop machine.

 

Deleted after seeing Fuzzel explaining first line in call stack needs to be VPinballX.


Edited by Thalamus, 13 February 2019 - 01:36 PM.

From now on. I won't help anyone here at VPF. Please ask Noah why that is.


#409 DJRobX

DJRobX

    Pinball Fan

  • VP Dev Team
  • PipPipPipPip
  • 941 posts
  • Location:Valencia, CA

  • Flag: United States of America

  • Favorite Pinball: F14 Tomcat

Posted 10 February 2019 - 12:27 AM

The new video display settings with the display number does not work correctly on my cab.

 

It shows Display 3* which is my correct primary monitor, but does not list the correct display modes available for that display.    The correct modes are being shown under display 1.   But display 1 is my DMD so VPX tries to start in 4k there.   Not good.   :(

I know most people have their primary display as #1, but I can't set mine that way.   #1 is the DVI-I/VGA output that I need for my DMD display.


Edited by DJRobX, 10 February 2019 - 12:45 AM.


#410 psmiraglia

psmiraglia

    Enthusiast

  • Members
  • PipPipPip
  • 114 posts

  • Flag: Argentina

  • Favorite Pinball: Star Trek

Posted 10 February 2019 - 01:56 AM

I believe it supports --help or was it that if you added a illegal option it would spew it out.

 

You can get a list of options with

 

c:\xxx\vpinballx.exe /?

Thanks! I could have sworn I tried this before...



#411 toxie

toxie

    VPF Veteran

  • VP Dev Team
  • PipPipPipPipPipPip
  • 5,734 posts
  • Location:berlin, germany

  • Flag: Germany

  • Favorite Pinball: AFM

Posted 10 February 2019 - 11:53 AM

Thanks for all the reports, we'll try to sort this out!



#412 rothbauerw

rothbauerw

    Enthusiast

  • Members
  • PipPipPip
  • 345 posts
  • Location:Wisconsin - USA

  • Flag: United States of America

  • Favorite Pinball: Dr Who, Tee'd Off, Jive Time

Posted 11 February 2019 - 10:21 PM

Just to add on in case it helps.  I've been getting crashes on all 10.6 versions on Win 7, but I haven't been seeing it on Win 10.  It crashes every time on Windows 7 after launching and closing the table the 2nd time in a work session.

Crash report VPX rev3623
============
Process: VPinballX.exe
Reason: 0xE0434352 - UNKNOWN at 0023:756BC42D
Thread ID: 0x1604 [5636]

Call stack
==========
756BC42D KERNELBASE.dll RaiseException + 0x58 (0xFFFFFFFFE0434352 0x00000001 0x00000005 0x7eadf4d0)
73B18FDB clr.dll CopyPDBs + 0x15478 (0x00000000 0x1E3FA9A2 0x77AC0464 0x779b92f4)
73AFDEA5 clr.dll DllGetClassObjectInternal + 0x19F52 (0x7EADF770 0x73B1A75D 0x7EADF8A0 0x163f20c8)
68B349D9  (0x77A23514 0x7EADF710 0x79C5DA07 0x779ba1cc)
79C4AB43 mscorlib.ni.dll (0x779BA1CC 0x00000000 0x00000000 0x00000000)
79C5DA07 mscorlib.ni.dll (0x00000000 0x779BA200 0x00000000 0x7eadf740)
79C5D956 mscorlib.ni.dll (0x00000000 0x779BA200 0x00000000 0x77a234e0)
79C5D921 mscorlib.ni.dll (0x779BA200 0x00000000 0x00000000 0x7eadf770)
79C4AACC mscorlib.ni.dll (0x0770E1B8 0x7EADF7B8 0x739CF237 0x7eadf804)
739C2552 clr.dll (0x7EADF804 0x7EADF7A8 0x73B18AD2 0x7eadf8a0)
739CF237 clr.dll DllUnregisterServerInternal + 0x3A83 (0x79D58280 0x7EADF7DC 0x739CBDC7 0x79951000)
739CFF60 clr.dll DllUnregisterServerInternal + 0x47AC (0x7EADF870 0x1E3FA466 0x7EADFA84 0x7eadfacc)
73A8B7AD clr.dll DllGetActivationFactoryImpl + 0x235D (0x7EADFB28 0x0770E1B8 0x7EADFACC 0x7eadfa68)
739D4306 clr.dll DllUnregisterServerInternal + 0x8B52 (0x1E3FA646 0x7EADFACC 0x00000000 0x00000000)
739D4374 clr.dll DllUnregisterServerInternal + 0x8BC0 (0x1E3FA6EA 0x73A8B5A9 0x0770E1B8 0x00000000)
739D4441 clr.dll DllUnregisterServerInternal + 0x8C8D (0x00000001 0x00000000 0x00000001 0x73a8b6b0)
739D44AF clr.dll DllUnregisterServerInternal + 0x8CFB (0x00000001 0x00000002 0x1E3FA74A 0x73a8b5a9)
73A8B669 clr.dll DllGetActivationFactoryImpl + 0x2219 (0x0770E1B8 0x623AB118 0x6869DA18 0x7eadfc84)
73B5A909 clr.dll GetMetaDataInternalInterfaceFromPublic + 0x1B084 (0x0C340000 0x7EADFFD4 0x77809882 0x0c340000)
751B337A kernel32.dll BaseThreadInitThunk + 0x12 (0x0C340000 0x0933966C 0x00000000 0x00000000)
77809882 ntdll.dll RtlInitializeExceptionChain + 0x63 (0x73B5A8C0 0x0C340000 0x00000000 0x00000000)
77809855 ntdll.dll RtlInitializeExceptionChain + 0x36 (0x73B5A8C0 0x0C340000 0x00000000 0x00000000)

Environment
===========
Date/time: 11/2/2019, 16:28:36:416
Number of CPUs: 4
Processor type: 586
System: Windows 7

Memory status
=============
Total Reserved: 239024K (233M) bytes
Total Commited: 1902964K (1858M) bytes
Total Free: 2052252K (2004M) bytes
Largest Free: 1888320K (1844M) bytes

Registers
=========
EAX=7EADF414 EBX=00000005 ECX=00000005 EDX=00000000
ESI=7EADF4D0 EDI=00000001 EBP=7EADFFEC ESP=7EADFFDC EIP=77809855
FLG=00000216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.



#413 fuzzel

fuzzel

    spaghetti code

  • VP Dev Team
  • PipPipPipPipPip
  • 2,818 posts

  • Flag: Germany

  • Favorite Pinball: yes I have

Posted 11 February 2019 - 10:55 PM

That crash isn't related to VPX. It looks like your win 7 setup has some issues. The call stack shows only addresses in windows or .net dolls.

#414 Thalamus

Thalamus

    Pinball Wizard

  • Platinum Supporter
  • 4,976 posts

  • Flag: Norway

  • Favorite Pinball: GOT, Alien Star, LOTR, TOM

Posted 11 February 2019 - 11:28 PM

Are you talking about the last report from Roth or in general ? Because non of my Win7 has had updates in a long time.


From now on. I won't help anyone here at VPF. Please ask Noah why that is.


#415 fuzzel

fuzzel

    spaghetti code

  • VP Dev Team
  • PipPipPipPipPip
  • 2,818 posts

  • Flag: Germany

  • Favorite Pinball: yes I have

Posted 11 February 2019 - 11:35 PM

Yes I meant Roth's crash report.

#416 randr

randr

    I'm just a hardware guy so...

  • VIP
  • 2,650 posts
  • Location:Minnesota

  • Flag: United States of America

  • Favorite Pinball: Twilight Zone

Posted 12 February 2019 - 12:23 AM

I have constant crashes on win7 virtual machine with last few betas also. Haven’t tried on win10 vm but can try it and report back

randr___pinball.png                         


#417 rothbauerw

rothbauerw

    Enthusiast

  • Members
  • PipPipPip
  • 345 posts
  • Location:Wisconsin - USA

  • Flag: United States of America

  • Favorite Pinball: Dr Who, Tee'd Off, Jive Time

Posted 12 February 2019 - 02:28 AM

That crash isn't related to VPX. It looks like your win 7 setup has some issues. The call stack shows only addresses in windows or .net dolls.

 

I'll admit I don't know how to read the crash report, but 10.5 never crashes.



#418 BobAlbright

BobAlbright

    Pinball Wizard

  • Platinum Supporter
  • 2,304 posts
  • Location:York, Pa. USA

  • Flag: United States of America

  • Favorite Pinball: Attack from Mars

Posted 12 February 2019 - 02:41 AM

  Been following this crash thread and have not commented before  but I've been crashing as well. Sometimes in the middle of a game , and often if I escape to editor. I'm on win7 with 1060 vidcard


"and in the end , the love you take is equal to the love you make"


#419 rothbauerw

rothbauerw

    Enthusiast

  • Members
  • PipPipPip
  • 345 posts
  • Location:Wisconsin - USA

  • Flag: United States of America

  • Favorite Pinball: Dr Who, Tee'd Off, Jive Time

Posted 12 February 2019 - 04:27 PM

I went back and did some testing on 10.5.  Indeed I do see crashing there as well.



#420 toxie

toxie

    VPF Veteran

  • VP Dev Team
  • PipPipPipPipPipPip
  • 5,734 posts
  • Location:berlin, germany

  • Flag: Germany

  • Favorite Pinball: AFM

Posted 12 February 2019 - 09:41 PM

On an unrelated sidenote, we since sometime this year have now > 600 unique (i.e. not counting MODs, LEs vs PROs, etc) tables running in VPX! (and approaching 650 actually soonish)

Insane!!







Also tagged with one or more of these keywords: beta, 10.6 beta