1488 replies to this topic

[ashleyb]

Hey guys, having some strange issues and I'm not sure if it's just on my end. First is I get this strange static or strobe effect randomly.. 
https://www.youtube....h?v=YOjyCZWyTXo
And second (more importantly) I get the no "rom path error" that on some table comes up only if I try to go into cabinet mode and other tables all the time. My tables included...
https://www.youtube....h?v=SmnTfMYwj6M
Again this could be just on my end but I have no idea...

Yeah, I get that strange static, is that Bords Pinbot table in your video? Its really noticeable for me on that table also and other dark tables. This problem started for me probably July/Aug 2019, I have seen other mentions of it on forums (possibly in this 10.6 beta topic)I believe it was identified as starting after one of the 10.6 betas, but forget which now.

https://www.vpforums...ndpost&p=438138

https://www.vpforums...=66#entry438144

Isnt your second problem related to needing the directdraw attribute set for the rom when using the full screen option in vpx?

https://www.vpforums...988#entry436493

Thanks Ashleyb!! Don't know if it always was but I un-checked Force Exclusive Fullscreen mode and that did the trick. Thanks for directing me to that. 
Now onto the static issue...

Great! Glad to be able to help.

Really hope we can get to the bottom of the static issue - it’s noticeable on quite a few tables, you can even see it very slightly in the darker areas of yours and g5k’s superb Addams Family table.

[toxie]

Same question to you: Do you run in 10bit mode (see video preferences)?

[ashleyb]

Same question to you: Do you run in 10bit mode (see video preferences)?

Unfortunately unable to check my cab at the moment as not at home due to Coronavirus isolation. Hopefully back home next weekend and Ill let you know then if no one else has responded.

Edited by ashleyb, 29 March 2020 - 11:13 AM.

[toxie]

Okay, thanks..

[Bushav]

I wish force exclusive full screen was not a global setting

The new Iron Maiden table will only run properly in my cab when it is in full screen mode. However a few other tables run best when Not in full screen mode.

It would be nice if this were a per table setting.

[kiwi]

If it were possible to have an option that keeps the aspect ratio of the DMD made with the Textbox intact,
so that it adapts to the type of resolution and aspect ratio of the end user screen.

[ashleyb]

Same question to you: Do you run in 10bit mode (see video preferences)?

I'm set to 8-bit bit depth in gfx preferences.

[toxie]

Currently revisiting the dithering, will post a test build for you guys later-on..

[toxie]

Replaced the dithering code completely. The pattern that apparently half of the world uses/used simply sucks for some configurations.

We will hopefully start soon with the 10.7 beta phase, so it will be in there then.

[onemanproject]

Sounds good

[mrjcrane]

PROPOSED NEW FEATURE: "CUSTOM" table layout in Backglass/POV Screen a 4th Video Presentation Mode.

Want to suggest in v10.6 the idea of adding a 4th video mode in the Backglass/POV menu for the table orientation called "Custom", where the user can define their own size, shape and orientation to each table, without needing to alter the original formatting/shaping of the DESKTOP, FULLSSCREEN or FULL_SINGLE_SCREEN modes. The benefit is one could always reference the original table formatting back to what the table designer intended for the default POV, without messing with it. This would allow those of us running our Cabinet OS in Portrait Mode (1080x1920) to reformat our table size and shapes based on a 0 degree (Portrait) table rotation instead of a 270 degree (Landscape) orientation. Eliminates the need to use 3rd party screen rotation tools for the playfield for those of us running our OS and VPX in "Portrait" mode and helps that we can always reference back to the original FULLSCREEN POV version of what the table was supposed to look like. There are several other significant advantages to doing this that I will expound on in a later posting.

Edited by mrjcrane, 10 April 2020 - 05:41 PM.

[Theguyoverthere]

Is this the correct place to post about a problem I get when I run VPX from the editor on my monitor? It just freezes on "Initializing Visuals", but it only happens after the first time running a table. The first time I run a table it works great, but every other time after that it will freeze and I'll have to quit VP. I'm using a NVIDIA GeForce GTX 1660 Ti graphics card and a monitor with G-sync that goes up to 140hz. 

 

Note that unchecking "Force Exclusive Fullscreen Mode" fixes the issue but is NOT a solution because then it has horrible frame rate performance.

Changing the VSync / FPS options to 1 did not help.

Edited by Theguyoverthere, 10 April 2020 - 08:49 PM.

[Thalamus]

No, this is not the correct place to ask questions. That question has been asked many times before, use the search box next time. The solution is to set ddraw=0 in registry if you want forced fullscreen. If you are updated, like you should be. Then you can delete the registry key all together as that is the default now.

Edited by Thalamus, 10 April 2020 - 08:54 PM.

[Theguyoverthere]

I'm sorry I was instructed to ask it here in my other thread https://www.vpforums...965#entry447095

 

The ddraw solution seems to only be for pinMAME tables. I'm getting this problem from a fresh table. Is there a solution for that?

[Thalamus]

Ok. That is new to me. Sorry. I agree. The question is valid here after all. And nothing comes to mind.

[Slydog43]

Is this the correct place to post about a problem I get when I run VPX from the editor on my monitor? It just freezes on "Initializing Visuals", but it only happens after the first time running a table. The first time I run a table it works great, but every other time after that it will freeze and I'll have to quit VP. I'm using a NVIDIA GeForce GTX 1660 Ti graphics card and a monitor with G-sync that goes up to 140hz. 

 

Note that unchecking "Force Exclusive Fullscreen Mode" fixes the issue but is NOT a solution because then it has horrible frame rate performance.

Changing the VSync / FPS options to 1 did not help.

 

 

 

Try setting changing a few values under Video/Graphics Options

 - set "FPS Limiter/VSync" from 0 to 1

 -set Maxiumum pre-rendered Frams from 0 to 1

 

uncheck Foce exclusice Fullscreen Mode

 

run table and look for stutters, I bet none.

[The Loafer]

unselecting "force exclusive fullscreen" is not really a solution "why is selecting "force exclusive fullscreen" crashing with just a new table" though.  This is def a worthwhile question to ask.

 

I suspect the devs will ask next to post the crash output file as that is likely to contain the reason for the crash.  Please duplicate the crash scenario Theguyoverthere and then look to see if there is a file dump in the "Visual pinball" folder. I'm not near my pc so don't recall what it's call but I think the name may be crash something, should be obvious by the name it is what you are looking for.

[Theguyoverthere]

I see these crash files but I have no idea what crash they pertain to. I tried deleting them, reproducing the problem, and seeing if they came back but they did not, so I'm afraid they are probably related to something else.

When I experience the problem, it doesn't crash, it just hangs indefinitely until I force quit with the Task manager.

 

There was also a dump file but it is too large to attach.

Attached Files

•  crash.txt   1.18KB   1 downloads

[onemanproject]

VP 10.6 crashed again

 

Crash report VPX rev3788
============
Process: vpinballx.exe
Reason: 0xE06D7363 - UNKNOWN at 0023:77054192
Thread ID: 0x29E0 [10720]

Call stack
==========
77054192 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x0019c3c0)
00534840 vpinballx.exe (0x0019C3DC 0x006941E4 0x00562214 0x291e7a88)
00530E09 vpinballx.exe (0x0058CFDC 0x0041AA32 0x0917A880 0x09afb7d0)
0041C1DA vpinballx.exe (0x0000E40F 0x00470AEB 0x0917A880 0x0019eee4)
00470AEB vpinballx.exe (0x000001AC 0x0000004E 0x00000000 0x00473e70)
004740E2 vpinballx.exe (0x006A0EA4 0x0000004E 0x00000000 0x0019f3b8)
7665444B user32.dll AddClipboardFormatListener + 0x4B (0x00473E70 0x006A0EA4 0x0000004E 0x00000000)
76634F8C user32.dll CallWindowProcW + 0xB2C (0x00473E70 0x00000000 0x0000004E 0x00000000)
76634B2A user32.dll CallWindowProcW + 0x6CA (0x0373A170 0x00000000 0x0000004E 0x00000000)
7663E16F user32.dll IsRectEmpty + 0x1FF (0x0019F2DC 0x00000020 0x0019F544 0x77d34110)
77D341DD ntdll.dll KiUserCallbackDispatcher + 0x4D (0x0373A170 0x00000000 0x0019F3B8 0x00000001)
76649E0D user32.dll SendMessageA + 0x11D (0x006A0EA4 0x0000004E 0x00000000 0x0019f3b8)
623C87AA SciLexerVP.DLL (0x00000001 0x42A60000 0x43910000 0x00320d8e)
623982B3 SciLexerVP.DLL (0x00000003 0x0C191EB8 0x00320D8E 0x623cba80)
623C73B8 SciLexerVP.DLL (0x00000113 0x00000006 0x00000000 0x00000113)
623CBB99 SciLexerVP.DLL Scintilla_DirectFunction + 0x139 (0x00320D8E 0x00000113 0x00000006 0x00000000)
7665444B user32.dll AddClipboardFormatListener + 0x4B (0x623CBA80 0x00320D8E 0x00000113 0x00000006)
76634F8C user32.dll CallWindowProcW + 0xB2C (0x623CBA80 0x00000000 0x00000113 0x00000006)
766340DE user32.dll DispatchMessageW + 0x22E (0x00000006 0x0019F9AC 0x0019F9A4 0x00000000)
766380E1 user32.dll IsDialogMessageW + 0x101 (0x006A0EA4 0x0019F9A4 0x0019F9A4 0x0019f9cc)
766509FE user32.dll IsDialogMessage + 0x4E (0x006A0EA4 0x0019F9A4 0x7664E840 0x76655d40)
0052E2E2 vpinballx.exe (0x0019F9A4 0x0019F9CC 0x00000000 0x0069fc08)
00520987 vpinballx.exe (0x00400000 0x77DDDCA0 0x02E11928 0x00000000)

Environment
===========
Date/time: 12/4/2020, 15:12:24:625
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 18363)

Memory status
=============
Total Reserved: 191540K (187M) bytes
Total Commited: 1717832K (1677M) bytes
Total Free: 2284868K (2231M) bytes
Largest Free: 1957180K (1911M) bytes

Registers
=========
EAX=0019C330 EBX=0019C3DC ECX=00000003 EDX=00000000
ESI=00582BDC EDI=006941E4 EBP=00000000 ESP=0021D008 EIP=FFFFFFFF
FLG=00000216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.
 

[toxie]

Replaced the dithering code completely. The pattern that apparently half of the world uses/used simply sucks for some configurations.

We will hopefully start soon with the 10.7 beta phase, so it will be in there then.

Please test the new dithering code via https://www.vpforums...showtopic=44135