4027 replies to this topic

[Thalamus]

So, common between me and lukpcn is Intel i7 ( 11700F vs 12700F ) - both nvidia 3080, Win10 with latest updates.

 

It could be so weird that it is a combination of all these things. We just have to wait and get more detailed feedback from people.

 

We should differentiate on hanging vpx processes and crashing ones. Important, be specific to what version you are running. Like lukpcn just did.

 

LoadedWeapon' problem might be a completely different case. He should try the latest build I made, if he hasn't already.

Edited by Thalamus, 23 September 2022 - 10:51 AM.

[lukpcn]

So, common between me and lukpcn is Intel i7 ( 11700F vs 12700F ) - both nvidia 3080, Win10 with latest updates.

 

It could be so weird that it is a combination of all these things. We just have to wait and get more detailed feedback from people.

 

We should differentiate on hanging vpx processes and crashing ones. Important, be specific to what version you are running. Like lukpcn just did.

 

LoadedWeapon' problem might be a completely different case. He should try the latest build I made, if he hasn't already.

 

but Your special build (the revision 0 ) works like it should be on both
 

[LoadedWeapon]

Send me a link I will try anything..
For the most part mine works perfect only about 3 tables I have found so far just close vpx. Doesn't matter if I open the table directly or open the editor first.
i7
16 GB memory
2070 super
Windows 10 fully updated

[Cliffy]

Ok so here's a weird crash. Was trying Thalamus' rev0 (285) this morning and didn't open a table. Just vpx itself. I went to prefs -editor/ui options and clicked reset windows positions and the side panels pushed out to the sides (boo) so I clicked reset windows positions again and bang- crashed closed. Fluke, I say to myself, so I opened task manager to see if it was running in the background- it was not but 2 "video applications" were- strange because those only show up when I run a pup table and I haven't run anything yet, fresh start in the morning. Meh. Killed those tasks and tried again to open vpx, prefs, reset windows positions and again pushed to sides so clicked again and crash again. Crash log below

 

Windows 10 16gb, GTX 1060 6gb, Intel I7-6700 3.4gz

 

Crash report VPX rev0 (unknown)

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

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00432E58

Attempt to read from 0xFFFFFFFE

Thread ID: 0x2BD4 [11220]

 

Call stack

==========

00432E58 VPinballX.exe (0x00000000 0x0019F3C4 0x00060812 0x00011101)

004339E1 VPinballX.exe (0x00000000 0x0019F3C4 0x00060812 0x00011101)

0044DC1A VPinballX.exe (0x0000036E 0x0019FB60 0x03373D00 0x0019f34c)

0043EF85 VPinballX.exe (0x0000036E 0x00060812 0x000C075C 0x0019fb60)

00434D69 VPinballX.exe (0x00000111 0x0000036E 0x00060812 0x00000111)

00430E0E VPinballX.exe (0x00430DB0 0x000C075C 0x00000111 0x0000036e)

76044316 USER32.dll EnumChildWindows + 0xC66 (0x000C075C 0x00000111 0x0000036E 0x00060812)

76043A80 USER32.dll EnumChildWindows + 0x3D0 (0x03BFE530 0x00000000 0x00000111 0x0000036e)

760386F5 USER32.dll wvsprintfA + 0x2D5 (0x000C075C 0x00000111 0x0000036E 0x00060812)

76050BCB USER32.dll AddClipboardFormatListener + 0x4B (0x760386D0 0x000C075C 0x00000111 0x0000036e)

76047B8A USER32.dll GetClassLongW + 0x7AA (0xFFFFFFFFCADCCD80 0x00007FFD 0x00000111 0x0000036e)

76046F69 USER32.dll GetSystemMetricsForDpi + 0x1449 (0x03BFE530 0x00000000 0x00060812 0x00000000)

760455AF USER32.dll SendMessageW + 0x6F (0x000C075C 0x00000111 0x0000036E 0x00060812)

76069F8B USER32.dll LoadCursorFromFileW + 0x1DFB (0x03BFCD60 0x00000000 0x00000000 0x0a3cf830)

76069C90 USER32.dll LoadCursorFromFileW + 0x1B00 (0x0A3CF830 0x00000000 0x03BFCD60 0x00000202)

76069198 USER32.dll LoadCursorFromFileW + 0x1008 (0x03BFCD60 0x00000000 0x00000202 0x00000000)

76068632 USER32.dll LoadCursorFromFileW + 0x4A2 (0x00060812 0x00000202 0x00000000 0x0009002e)

76050BCB USER32.dll AddClipboardFormatListener + 0x4B (0x760685E0 0x00060812 0x00000202 0x00000000)

76047B8A USER32.dll GetClassLongW + 0x7AA (0xFFFFFFFFCADCCD20 0x00007FFD 0x00000202 0x00000000)

760458FA USER32.dll DispatchMessageW + 0x24A (0x0004080E 0x00000000 0x000C075C 0x00000000)

76049B08 USER32.dll IsDialogMessageW + 0x108 (0x000C075C 0x0019E914 0x0004080E 0x00000001)

760345AE USER32.dll DialogBoxIndirectParamAorW + 0x25E (0x00000000 0x00000001 0x00400000 0x760425f0)

76034464 USER32.dll DialogBoxIndirectParamAorW + 0x114 (0x0004080E 0x00430DB0 0x00000000 0x00000003)

76034382 USER32.d7606E3AC 

Environment

===========

Date/time: 23/9/2022, 07:52:24:918

Number of CPUs: 8

Processor type: 586

System: Windows 10 (10.0 19044)

 

Memory status

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

Total Reserved: 63240K (61M) bytes

Total Commited: 215152K (210M) bytes

Total Free: 3915848K (3824M) bytes

Largest Free: 2095464K (2046M) bytes

 

Registers

=========

EAX=00432E50 EBX=00000002 ECX=000509AE EDX=00000000

ESI=FFFFFFFE EDI=FFFFFB1C EBP=0019E9B8 ESP=0019E990 EIP=7606E3AC

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

[Thalamus]

LoadedWeapon : https://www.dropbox....nballX.exe?dl=0

 

Interresting Cliffy : Editor, and its size /preferences, is something I've solved, kind of in a different way. Start regedit - export HKLU\Softeware\VisualPinball\VP10\Editor - save it somewhere - like desktop. If the editor is fucked up, just exit, double click the registry file to import all the settings and it will be fine next time around. Obviously, you do this when the editor is as you want it. If it is all messed up, you can just delete that reigstry hive all together and start fresh. Then do what I said. BUT YES, this is now hit is supposed to be. A workaround that works, kind of

[Cliffy]

As a follow up to the above I just did the same test on the release version 10.7.2 rev 285 and reset windows positions works as it should. The panels move to the correct positions and I can click till the sun goes down without a crash. 

I realize Thalamus' compile likely wasn't intended as much for editing as play testing, however, so no shade intended on our friend Thalamus Just putting data points up here that might be helpful

[Cliffy]

LoadedWeapon : https://www.dropbox....nballX.exe?dl=0

 

Interresting Cliffy : Editor, and its size /preferences, is something I've solved, kind of in a different way. Start regedit - export HKLU\Softeware\VisualPinball\VP10\Editor - save it somewhere - like desktop. If the editor is fucked up, just exit, double click the registry file to import all the settings and it will be fine next time around. Obviously, you do this when the editor is as you want it. If it is all messed up, you can just delete that reigstry hive all together and start fresh. Then do what I said. BUT YES, this is now hit is supposed to be. A workaround that works, kind of

heh heh Ok yeah that works to restore prefs. I just grabbed your new exe and now when I click restore positions the panels stay in place but all the dockers disappear. Clicking restore defaults brings them back. I didn't have to delete/reinsert the registry hive.

[Thalamus]

Not really the same thing I'm explaining, well, ok, partly it might be, but, doing what I said, you have a "backup" of how you want the editor to be setup. Options you've set, colors your prefer etc. Can even move it to another machine and restore it there. It has happened, and will surely happen again that one of the coordinates is almost impossible to get to; like the coordinates is outside of reach. Solution. Restore from the registry backup. Or, well, delete the hive and you will have to set up the few ( I have 6-7 changes ), manually again. I prefer the lazy backup method. Takes me no time at all.

 

I don't know why you would see anything different from my build than upstream. All code is 100% the same, only built with a slighly different compiler I expect, and, yeah, on my machine

Edited by Thalamus, 23 September 2022 - 04:38 PM.

[Cliffy]

I can't 'splain it either my friend but it happens how it happens. Now, I happy to report that your version hasn't crashed once while editing/play test/editing/play test at least 15 times all in one session. I was fiddle farting with godzilla limited edition getting the side rails positioned correctly (I'm in desktop mode with 1920 x 1200 so 16:10) and your version let me do it with no crash out or lockup. Thanks again for your stable version Thalamus

[Thalamus]

Starting and restarting a edit inside the same session has as long as I remember been a game of chance. If you do real work, make god damn sure you save very often, because vpx will crash - be almost 100% sure of that. I'm quite sure it is related to pinmame though. IF you are serious about editing - use the 64bit version, not 32 ! Then, you will have a much much more table editor. You will have to register piname64 if you want to test your work though. And, well, don't use it for modern stern games and db2s games

[Cliffy]

Starting and restarting a edit inside the same session has as long as I remember been a game of chance. If you do real work, make god damn sure you save very often, because vpx will crash - be almost 100% sure of that. I'm quite sure it is related to pinmame though. IF you are serious about editing - use the 64bit version, not 32 ! Then, you will have a much much more table editor. You will have to register piname64 if you want to test your work though. And, well, don't use it for modern stern games and db2s games

Oh yes indeed. Remember I remarked about that with the release version a while back which is why I was happy to report it not crashing out in your version. 

[wiesshund]

Starting and restarting a edit inside the same session has as long as I remember been a game of chance. If you do real work, make god damn sure you save very often, because vpx will crash - be almost 100% sure of that. I'm quite sure it is related to pinmame though. IF you are serious about editing - use the 64bit version, not 32 ! Then, you will have a much much more table editor. You will have to register piname64 if you want to test your work though. And, well, don't use it for modern stern games and db2s games

 

You can use it for B2S games, but you need the 64bit b2s server, it's in the github (and 64bit freezys dll if it has DMD)
stern ROMs are a grab bag, i never personally had 64bit vpinmame outright crash on them (but i know it can), but i definitely did have the DMD and the table play
walk out of sync with each other, and perhaps other parts that i was just not aware of.
Still, it might be ok enough, just for editing purposes, harmless to try anyways.

 

At the time, i just kept 2 VPX folders, c:\VPX32 and c:\VPX64
Whichever one i was going to use, i just renamed the folder c:\VPX, saved me having to re-register b2s each time.

 

Me? I do just like you, SAVE before EVERY relaunch, even if all i did was set 1 light 2 points brighter
cause you never know when it will randomly pull that D3d compiler error and crash

 

save save save or suffer suffer suffer

[LoadedWeapon]

LoadedWeapon : https://www.dropbox....nballX.exe?dl=0

 

Interresting Cliffy : Editor, and its size /preferences, is something I've solved, kind of in a different way. Start regedit - export HKLU\Softeware\VisualPinball\VP10\Editor - save it somewhere - like desktop. If the editor is fucked up, just exit, double click the registry file to import all the settings and it will be fine next time around. Obviously, you do this when the editor is as you want it. If it is all messed up, you can just delete that reigstry hive all together and start fresh. Then do what I said. BUT YES, this is now hit is supposed to be. A workaround that works, kind of

Thanks I tried it but still the same thing.. Table opens then closes..

[wiesshund]

 

LoadedWeapon : https://www.dropbox....nballX.exe?dl=0

 

Interresting Cliffy : Editor, and its size /preferences, is something I've solved, kind of in a different way. Start regedit - export HKLU\Softeware\VisualPinball\VP10\Editor - save it somewhere - like desktop. If the editor is fucked up, just exit, double click the registry file to import all the settings and it will be fine next time around. Obviously, you do this when the editor is as you want it. If it is all messed up, you can just delete that reigstry hive all together and start fresh. Then do what I said. BUT YES, this is now hit is supposed to be. A workaround that works, kind of

Thanks I tried it but still the same thing.. Table opens then closes..

 

 

What table does this? Is it just one table?

 

It isnt a table that someone put asininely huge images in?
like one of the tables that have 14k playfields and 10k imgaes for targets and stuff?

 

Just curious, cause to fix one of those, 1st you have to drag vpx's texture memory slider to minimum, open table and export nutty images
resize them to some sane size, 4k for playfield, use common sense for other images (a target doesnt need 10k definition)
reimport and fixed

i sort of have a feeling you know this already though, and it might not even be the case here

[Thalamus]

 

LoadedWeapon : https://www.dropbox....nballX.exe?dl=0

 

Interresting Cliffy : Editor, and its size /preferences, is something I've solved, kind of in a different way. Start regedit - export HKLU\Softeware\VisualPinball\VP10\Editor - save it somewhere - like desktop. If the editor is fucked up, just exit, double click the registry file to import all the settings and it will be fine next time around. Obviously, you do this when the editor is as you want it. If it is all messed up, you can just delete that reigstry hive all together and start fresh. Then do what I said. BUT YES, this is now hit is supposed to be. A workaround that works, kind of

Thanks I tried it but still the same thing.. Table opens then closes..

 

Have you considered NOT running pup - ie, renaming the associated video folder ?!

 

And, by the way - new compiled vpx (rev 289) with these fixes ( Not my doing, fixes from Vincent )

- updating the image drop down

- tabbing through drag point fields with multiple points selected

Edited by Thalamus, 24 September 2022 - 10:10 AM.

[LoadedWeapon]

 

 

LoadedWeapon : https://www.dropbox....nballX.exe?dl=0

 

Interresting Cliffy : Editor, and its size /preferences, is something I've solved, kind of in a different way. Start regedit - export HKLU\Softeware\VisualPinball\VP10\Editor - save it somewhere - like desktop. If the editor is fucked up, just exit, double click the registry file to import all the settings and it will be fine next time around. Obviously, you do this when the editor is as you want it. If it is all messed up, you can just delete that reigstry hive all together and start fresh. Then do what I said. BUT YES, this is now hit is supposed to be. A workaround that works, kind of

Thanks I tried it but still the same thing.. Table opens then closes..

 

 

What table does this? Is it just one table?

 

It isnt a table that someone put asininely huge images in?
like one of the tables that have 14k playfields and 10k imgaes for targets and stuff?

 

Just curious, cause to fix one of those, 1st you have to drag vpx's texture memory slider to minimum, open table and export nutty images
resize them to some sane size, 4k for playfield, use common sense for other images (a target doesnt need 10k definition)
reimport and fixed

i sort of have a feeling you know this already though, and it might not even be the case here

 

These are tables that I have played many times. I have tried them with and without puppack or backglass.

One of the tables are Tales from the crypt new one from VPU and I have played it a lot.

but now it just crashes

[Cliffy]

 

 

 

LoadedWeapon : https://www.dropbox....nballX.exe?dl=0

 

Interresting Cliffy : Editor, and its size /preferences, is something I've solved, kind of in a different way. Start regedit - export HKLU\Softeware\VisualPinball\VP10\Editor - save it somewhere - like desktop. If the editor is fucked up, just exit, double click the registry file to import all the settings and it will be fine next time around. Obviously, you do this when the editor is as you want it. If it is all messed up, you can just delete that reigstry hive all together and start fresh. Then do what I said. BUT YES, this is now hit is supposed to be. A workaround that works, kind of

Thanks I tried it but still the same thing.. Table opens then closes..

 

 

What table does this? Is it just one table?

 

It isnt a table that someone put asininely huge images in?
like one of the tables that have 14k playfields and 10k imgaes for targets and stuff?

 

Just curious, cause to fix one of those, 1st you have to drag vpx's texture memory slider to minimum, open table and export nutty images
resize them to some sane size, 4k for playfield, use common sense for other images (a target doesnt need 10k definition)
reimport and fixed

i sort of have a feeling you know this already though, and it might not even be the case here

 

These are tables that I have played many times. I have tried them with and without puppack or backglass.

One of the tables are Tales from the crypt new one from VPU and I have played it a lot.

but now it just crashes

 

Have you deleted the config in the user folder and maybe delete the nv file too? TFTC works fine on my end, both the VPW 1.22 and the Bigus mod 1.4.

[Thalamus]

 

 

 

LoadedWeapon : https://www.dropbox....nballX.exe?dl=0

 

Interresting Cliffy : Editor, and its size /preferences, is something I've solved, kind of in a different way. Start regedit - export HKLU\Softeware\VisualPinball\VP10\Editor - save it somewhere - like desktop. If the editor is fucked up, just exit, double click the registry file to import all the settings and it will be fine next time around. Obviously, you do this when the editor is as you want it. If it is all messed up, you can just delete that reigstry hive all together and start fresh. Then do what I said. BUT YES, this is now hit is supposed to be. A workaround that works, kind of

Thanks I tried it but still the same thing.. Table opens then closes..

 

 

What table does this? Is it just one table?

 

It isnt a table that someone put asininely huge images in?
like one of the tables that have 14k playfields and 10k imgaes for targets and stuff?

 

Just curious, cause to fix one of those, 1st you have to drag vpx's texture memory slider to minimum, open table and export nutty images
resize them to some sane size, 4k for playfield, use common sense for other images (a target doesnt need 10k definition)
reimport and fixed

i sort of have a feeling you know this already though, and it might not even be the case here

 

These are tables that I have played many times. I have tried them with and without puppack or backglass.

One of the tables are Tales from the crypt new one from VPU and I have played it a lot.

but now it just crashes

 

Take the crash.* dump files and post them as a bug on github - is my suggestion.

[LoadedWeapon]

Update: Fixed!     

Ok guys after trying everything I finally figured out my issue... I was running the new mod for the new color pac files and it works for the .pal files also well some of my folders had double files like if I got a new one I would name the old one old.pal    and somehow I guess the new system does not like that.. does not like the .ini files either,, Once I deleted the old file all tables work perfectly! 

Edited by LoadedWeapon, 27 September 2022 - 11:18 PM.

[Redwings13]

On my cabinet in the altcolor folder, the color files .pal, .inv, I just add .off on them and haven’t had any problems running the .pac files.

I don’t like deleting files is the reason I add .off