4027 replies to this topic

[wiesshund]

@Toxie

Did something inadvertently happen with the renderer?

 

If tables were soldiers, it would kinda look like omaha beach here

but i cant find any commonality to it

 

For example ACDC is guaranteed to crash, with a stock 170h rom, if you try enabling external dll
and i tried every version of freezys back to 1.6

and tried on pinmame 3.2, 3.3b and 3.3b sambuild

The plain Luci table

 

And yet, metallica monsters, which uses a similar ROM, and 4k textures?
It runs, and i have no idea why

And it runs with a colorized rom at that.

[Segovia11]

 

 

Out of curiosity. It has often on my end, with loading - been related to having external dmd enabled. I would call that a known problem. Using extenal dmd and you will crash more often. If that is a timing thing or something else ? It's not that. Using external is something I do have enable for almost all tables. But, if I turn it off, it before this release at least. it seems to be rock solid. But, then again, the truth is, since using external is my default. It doesn't run through as many tests as having it enabled does.

 

I mentioend pin-bot crashing, that I haven't seen before. So, I expect there is still something not 100% right with this release. But, to early to say. Was the only table that crashed on loading in the few tables I tried tonight. But, then again - has never crashed before.

 

Yes confirmed, Pinbot is crashing here too with trhe same error: Fatal error E_OUTOFMEMORY (0x80070000e: Ran out of memory) at D:\a\vpinball\vpinball\pin\player.cpp:1767

 

I do not know what the D:\a... stands for because I do not have a D disk in the cab. Probably it means something else.

 

 

Bug Report

 

I do not use Roms or an external DMD system & my tables are standalone desktop tables which work very well with the 4406 & 98 rev. The Desktop configuration in use is an : Intel® Core™ i7-9700 CPU : @ 3.00GHz x 8 and 16 GB of Ram plus a NVIDIA Geforce RTX 2070 using Windows 10 with the latest updates.

 

However, I tested one of my tables with the Intel® Core™ i5-7400  : CPU @ 3.00GHz x 4 which has 8 GB of Ram & + NVIDIA Geforce RTX 1050 again using Windows 10 with the latest updates &, with this set up I got a Fatal error E_OUTOFMEMORY (0x80070000e: Ran out of memory) at D:\a\vpinball\vpinball\pin\player.cpp:1767 report with Visual Pinball Rev 98. Although rev 4406 was error free.

I also tested Abra Ca Dabra (1975) which has a file size of 31,940 kb which is larger than my 79,220 kb file size & the the table loaded without problems.

 

It looks as though I got away with it thanks to my i7 setup. (Maybe somebody is promoting desktop upgrades!)

 

   

 

 

I have just tested my recently upgraded tables with the i5 GTX 1070 setup & to my surprise there was no error report, the tables loaded successfully. The i5 with the 1070 setup now only suffers from lag & is slow with loading, which is why I purchased the i7 with the GTX 2070. Since then all has been bliss.

 

Bug report

On some occasions I still experience the following error report during table load, which is difficult to replicate;

 

"The temporary file C:\VisualPinball\VPTemp0.ttf could not be written" 

 

Its not a fatal error. When it does occur the table does not suffer from any side effects. 

The VPTemp0.ttf files are normally self deleting until the error message appears, after this error message the VPTemp0.ttf file must then be deleted manually. However, you must log off first prior to the attempted deletion.

Edited by Segovia11, 20 March 2021 - 11:28 AM.

[Thalamus]

Believe hat VPTemp0.ttf comes from pinbinary.cpp - constructed and written at line 153. I have no clue to if it needs to be written to disk or not. I've seen it pop up on a very few occasions myself, always ok to just accept the warning. To me it sounds like your process isn't exiting cleanly, keeping the file "open", and that is why you have to log off, forcing the program to end. This is far away from my area of expertise, so, don't take my word on this.

[CVpeet]

Thank you.... it is doIng great and i love the new plunger behavior.

[fuzzel]

 

Other tables gives this smaller error, like for example The Flintstones, The Flintstones – VPINBALL.COM

Mostly are tables with a lot of graphics.

 

Edit: This is using only VPX and vpinmame  3.3b (without front ends, db2s, or external dmd)

Crash report VPX rev98 (f9a3765)
============
Process: VPinballX.exe
Reason: 0xE06D7363 - UNKNOWN at 0023:75FAA8B2
Thread ID: 0xE80 [3712]

Call stack
==========
75FAA8B2 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x034fe150)
67EA75B6 VCRUNTIME140.dll CxxThrowException + 0x66 (0x034FE16C 0x008E1628 0x007AB0BC 0x008afb64)
0076E321 VPinballX.exe (0x000F423F 0x0000C21A 0x4F20D0E0 0x00000000)
005E80B2 VPinballX.exe (0x0000C21A 0x00000000 0x00000000 0x000e04e8)
006A3210 VPinballX.exe (0x034FE704 0x00000000 0x00000000 0x76194b70)
75D662FA MSCTF.dll TF_Notify + 0x2FA (0x005E7F30 0x000E04E8 0x0000C21A 0x00000000)

Environment
===========
Date/time: 20/3/2021, 06:20:02:157
Number of CPUs: 16
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 148260K (144M) bytes
Total Commited: 1537276K (1501M) bytes
Total Free: 411552K (401M) bytes
Largest Free: 139700K (136M) bytes

Registers
=========
EAX=034FE0D0 EBX=19930520 ECX=00000003 EDX=00000000
ESI=4F20D108 EDI=008E1628 EBP=00000000 ESP=034FE664 EIP=75585ECA
FLG=00000212 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

Thanks JP. It looks like that our autobuild on Github seems to optimize the exe a little too much. I don't get any crashes when playing Flintstones with a version I built with Visual Studio. So jsm174 has to take a look at this.

[Segovia11]

Believe hat VPTemp0.ttf comes from pinbinary.cpp - constructed and written at line 153. I have no clue to if it needs to be written to disk or not. I've seen it pop up on a very few occasions myself, always ok to just accept the warning. To me it sounds like your process isn't exiting cleanly, keeping the file "open", and that is why you have to log off, forcing the program to end. This is far away from my area of expertise, so, don't take my word on this.

 

I guess that Visual Pinball would need to write the font file somewhere so that it can read the fonts that have been stored in Visual Pinballs Font Manager. 

In line 56 : if (hfile == Invalid_Handle_Value)  { const string bla  = "the temporary file \ "" + szfilename + "\" could not be written."; showError(bla); return false; }

The next step would be to identify the Invalid_Handle_Value.  Will not be able to make progress until I have identified a link with the Invalid_Handle_Value dim

More research needed !

   

Edited by Segovia11, 20 March 2021 - 01:14 PM.

[Pin-Pete]

Can't open VP. There seems to be critical error.

[cmd]

Latest build gives me system error: msvcp140.dll and vcruntime140.dll was not found.

[Pin-Pete]

Latest build gives me system error: msvcp140.dll and vcruntime140.dll was not found.

Same over here.

[fuzzel]

Latest build gives me system error: msvcp140.dll and vcruntime140.dll was not found.

Same over here.

Which Windows version do you use?

[Pin-Pete]

 

 

Latest build gives me system error: msvcp140.dll and vcruntime140.dll was not found.

Same over here.

Which Windows version do you use?

Windows 10

[njk70]

I submitted my last PR ti github for sound stuff for 10.7 (inline conversion of mono .WAV samples to dual channel so they don't play to center speaker in a surround sound setup).  I'm done poking at it.  One thing I wish we had was interactive control of PinMame's volume, but I am not going down that rabbit hole any time soon. Going to work on building my cabinet out and setting up the pup stuff and maybe even play a few games of something other than attack from mars.

[Thalamus]

Thanks a bunch @njk70 and good luck with your build. There is a lot of tables that plays very well, and now they sound even better - thank to you.

[cmd]

 

 

 

Latest build gives me system error: msvcp140.dll and vcruntime140.dll was not found.

Same over here.

Which Windows version do you use?

Windows 10

Windows 10 Home 64bit

[wiesshund]

 One thing I wish we had was interactive control of PinMame's volume, but I am not going down that rabbit hole any time soon. Going to work on building my cabinet out and setting up the pup stuff and maybe even play a few games of something other than attack from mars.

 

Well technically we do, though i doubt anyone would be fond of it, especially on a cab 

VPM must be in focus

[cmd]

Got the dll files and now it works.

 

@Pin-Pete: If you have Windows 10 64bit you will have to download msvcp140.dll both 32bit and 64bit versions. Keep them separate because they both have the same filename. Place 64bit version in Windows\Syster32 folder. Place 32bit version in Windows\SysWOW64 folder.

 

Download vcruntime.dll and place in Windows\System32 folder and Windows\SysWOW64 folder.

Edited by cmd, 21 March 2021 - 04:09 AM.

[wiesshund]

Got the dll files and now it works.

 

@Pin-Pete: If you have Windows 10 64bit you will have to download msvcp140.dll both 32bit and 64bit versions. Keep them separate because they both have the same filename. Place 64bit version in Windows\Syster32 folder. Place 32bit version in Windows\SysWOW64 folder.

 

Download vcruntime.dll and place in Windows\System32 folder and Windows\SysWOW64 folder.

just an fyi
if you reinstall VC++ 2015 32 and 64bit, it will put both those files back

any any others you may be missing from that one

 

Visual C++ Redistributable Runtimes All-in-One (Mar 2021

 

that will just update all of them in 1 shot

[cmd]

Cool! I hardly ever update VC++.

[wiesshund]

Cool! I hardly ever update VC++.

Dont normally need to, unless a new one rolls out and something needs it
but when pieces have gone missing, it's a safe bet for fixing them all up

[BrandonLaw]

All AC/DC's dump out of the program with 10.7.  No 'error' just program exit.  Investigating further.

 

Crash report VPX rev98 (f9a3765)

============

Process: VPinballX.exe

Reason: 0xE06D7363 - UNKNOWN at 0023:75F9A8B2

Thread ID: 0x2298 [8856]

 

Call stack

==========

 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x18fdfafc)

 (0x18FDFB28 0x6C386ADC 0xFFFFFFFF9686B128 0x5168e160)

 (0x00001000 0x18FDFB58 0x6C35589C 0x18b4cae4)

 (0x18B4CAE4 0x5168E160 0x000000C1 0x00000000)

 (0x4F9435B0 0x4F91D0A8 0x18FDFDD4 0x4f8d6e88)

 

Environment

===========

Date/time: 21/3/2021, 05:23:52:150

Number of CPUs: 12

Processor type: 586

System: Windows 10 (10.0 19042)

 

Memory status

=============

Total Reserved: 224240K (218M) bytes

Total Commited: 1730576K (1690M) bytes

Total Free: 142272K (138M) bytes

Largest Free: 8136K (7M) bytes

 

Registers

=========

EAX=18FDFA68 EBX=18FDFB28 ECX=00000003 EDX=00000000

ESI=6C395E88 EDI=6C386ADC EBP=00000000 ESP=18FDFB60 EIP=4F50A7F4

FLG=00000212 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Failed to save minidump.

 

SOLVED:  Applied the 4gb Patch.

Edited by BrandonLaw, 21 March 2021 - 12:38 PM.