4027 replies to this topic

[kiwi]

I have a 16/10 screen (1920x1200), is it possible to have the 1920x1080 (windowed) resolution available in the video options ?

[laylow]

Thanks for the update, but table crashes after closing in exclusive fullscreen.

[kiwi]

It also crashes to me when I exit the game and return to the editor.

Crash report VPX rev4131
============
Process: VPinballX4131.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 001B:00533F6C
Attempt to read from 0x0722E220
Thread ID: 0x8C0 [2240]

Call stack
==========
00533F6C  (0x00000002 0x00000000 0x00000000 0x0013e334)
00423F9F  (0x00423F50 0x00100420 0x00000002 0x00000000)
7E398816  GetDC + 0x14F (0x00000000 0x00423F50 0x00100420 0x00000002)
7E3A8EA0  DefWindowProcW + 0x180 (0x038AC1A0 0x00000002 0x00000000 0x00000000)
7E3A8EEC  DefWindowProcW + 0x1CC (0x0013E3EC 0x00000018 0x038AC1A0 0x00000002)
7C91E453  KiUserCallbackDispatcher + 0x13 (0x00000010 0x00000000 0x00000000 0x00100420)
00533F7A  (0x00000010 0x00000000 0x00000000 0x0013e790)
00423F9F  (0x00423F50 0x00100420 0x00000010 0x00000000)
7E398816  GetDC + 0x14F (0x00000000 0x00423F50 0x00100420 0x00000010)
7E3A927B  GetParent + 0x16C (0x008AC1A0 0x038B3018 0x00000000 0x00000000)
7E3AF40B  SendMessageA + 0x49 (0x00100420 0x00000010 0x00000000 0x00000000)
00530FF3  (0x00000000 0x00000000 0x00000000 0x00000000)

Environment
===========
Date/time: 23/5/2020, 20:12:39:234
Number of CPUs: 4
Processor type: 586
System: Windows XP

Memory status
=============
Total Reserved: 49860K (48M) bytes
Total Commited: 145556K (142M) bytes
Total Free: 1901672K (1857M) bytes
Largest Free: 1045540K (1021M) bytes

Registers
=========
EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000000
ESI=0722E220 EDI=00000002 EBP=0722E220 ESP=0722E228 EIP=00000000
FLG=00010246 CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000


Failed to save minidump.

 

[fuzzel]

It also crashes to me when I exit the game and return to the editor.

Crash report VPX rev4131
============
Process: VPinballX4131.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 001B:00533F6C
Attempt to read from 0x0722E220
Thread ID: 0x8C0 [2240]

Call stack
==========
00533F6C  (0x00000002 0x00000000 0x00000000 0x0013e334)
00423F9F  (0x00423F50 0x00100420 0x00000002 0x00000000)
7E398816  GetDC + 0x14F (0x00000000 0x00423F50 0x00100420 0x00000002)
7E3A8EA0  DefWindowProcW + 0x180 (0x038AC1A0 0x00000002 0x00000000 0x00000000)
7E3A8EEC  DefWindowProcW + 0x1CC (0x0013E3EC 0x00000018 0x038AC1A0 0x00000002)
7C91E453  KiUserCallbackDispatcher + 0x13 (0x00000010 0x00000000 0x00000000 0x00100420)
00533F7A  (0x00000010 0x00000000 0x00000000 0x0013e790)
00423F9F  (0x00423F50 0x00100420 0x00000010 0x00000000)
7E398816  GetDC + 0x14F (0x00000000 0x00423F50 0x00100420 0x00000010)
7E3A927B  GetParent + 0x16C (0x008AC1A0 0x038B3018 0x00000000 0x00000000)
7E3AF40B  SendMessageA + 0x49 (0x00100420 0x00000010 0x00000000 0x00000000)
00530FF3  (0x00000000 0x00000000 0x00000000 0x00000000)

Environment
===========
Date/time: 23/5/2020, 20:12:39:234
Number of CPUs: 4
Processor type: 586
System: Windows XP

Memory status
=============
Total Reserved: 49860K (48M) bytes
Total Commited: 145556K (142M) bytes
Total Free: 1901672K (1857M) bytes
Largest Free: 1045540K (1021M) bytes

Registers
=========
EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000000
ESI=0722E220 EDI=00000002 EBP=0722E220 ESP=0722E228 EIP=00000000
FLG=00010246 CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000


Failed to save minidump.

Hmm does it always crash? Or just on a specific table? The call stack doesn't point to the real crash location.

[jpsalas]

Yes, very similar (or the same as mine). I'm editing a new table, so it has minimal with graphics.

 

Crash report VPX rev4131

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

Process: VPinballX7.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00422C78

Attempt to read from 0x00000006

Thread ID: 0x4BC [1212]

 

Call stack

==========

00422C78 VPinballX7.exe (0x00000002 0x00000000 0x00000000 0x00000002)

00423F9F VPinballX7.exe (0x00423F50 0x00610C66 0x00000002 0x00000000)

760267BC user32.dll CallWindowProcW + 0xB2C (0x00423F50 0x00000000 0x00000002 0x00000000)

7602635A user32.dll CallWindowProcW + 0x6CA (0x0397BA90 0x00000000 0x00000002 0x00000000)

7603312F user32.dll IsRectEmpty + 0x20F (0x0019E2E4 0x00000020 0x0019E540 0x779f2a10)

779F2ADD ntdll.dll KiUserCallbackDispatcher + 0x4D (0x00000010 0x00000000 0x00000000 0x00610c66)

00533F7A VPinballX7.exe (0x00000010 0x00000000 0x00000000 0x00000010)

00423F9F VPinballX7.exe (0x00423F50 0x00610C66 0x00000010 0x00000000)

760267BC user32.dll CallWindowProcW + 0xB2C (0x00423F50 0x00000000 0x00000010 0x00000000)

76025F6D user32.dll CallWindowProcW + 0x2DD (0x0397BA90 0x00000000 0x00000000 0x00000001)

76016E1D user32.dll SendMessageA + 0x11D (0x00610C66 0x00000010 0x00000000 0x00000000)

00530FF3 VPinballX7.exe (0x0019E83C 0x00000000 0x00000000 0x760169b0)

00570A50 VPinballX7.exe (0x0019FF24 0x002AB000 0x00000000 0x00000001)

00570A90 VPinballX7.exe (0x00000000 0x00000001 0x002AB000 0x0070e070)

00570BE0 VPinballX7.exe (0x00000001 0x002AB000 0x0070E070 0x00000000)

 

Environment

===========

Date/time: 23/5/2020, 21:14:51:411

Number of CPUs: 8

Processor type: 586

System: Windows 10 (10.0 17763)

 

Memory status

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

Total Reserved: 277368K (270M) bytes

Total Commited: 385000K (375M) bytes

Total Free: 3531872K (3449M) bytes

Largest Free: 2095440K (2046M) bytes

 

Registers

=========

EAX=00422C70 EBX=00423F50 ECX=0CF555E0 EDX=00000000

ESI=0CF555E0 EDI=00000002 EBP=00000463 ESP=0019E85C EIP=00570BE0

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

 

 

Mini dump saved successfully.

[fuzzel]

Thanks...looks like something went wrong with the script engine...I'll take a look.

[toxie]

I have a 16/10 screen (1920x1200), is it possible to have the 1920x1080 (windowed) resolution available in the video options ?

Is it not popping up in the latest build? Could you please post a screenshot of the displayed windowed modes then with that build?

 

 

btw: Regarding 'only load/generate GDI/UI version of texture if table not played from command line (i.e. never needed then)'

 

This in practice means that if a table is launched via '-Play' then all images for the UI won't be loaded, so also not in the image manager. This saves memory and some processing time.

Does that make sense? Anybody doesn't like that behavior?

 

I'm even thinking to directly exit to the command line/windows again if a table is started with '-Play' and is then 'Quit'.

Would that be good? Or not?

[jpsalas]

 

I have a 16/10 screen (1920x1200), is it possible to have the 1920x1080 (windowed) resolution available in the video options ?

Is it not popping up in the latest build? Could you please post a screenshot of the displayed windowed modes then with that build?

 

 

btw: Regarding 'only load/generate GDI/UI version of texture if table not played from command line (i.e. never needed then)'

 

This in practice means that if a table is launched via '-Play' then all images for the UI won't be loaded, so also not in the image manager. This saves memory and some processing time.

Does that make sense? Anybody doesn't like that behavior?

 

I'm even thinking to directly exit to the command line/windows again if a table is started with '-Play' and is then 'Quit'.

Would that be good? Or not?

 

 

Yes, I think it will be good for people who just play tables and never use the editor.

[arngrim]

I have the resolution 1440*1080 added, not yet 1920*1080 

 

 Sans titre.png   31.1KB   9 downloads

Edited by arngrim, 24 May 2020 - 06:59 AM.

[kiwi]

 

I have a 16/10 screen (1920x1200), is it possible to have the 1920x1080 (windowed) resolution available in the video options ?

Is it not popping up in the latest build? Could you please post a screenshot of the displayed windowed modes then with that build?

 

[onemanproject]

VP 10.7 beta crashed:

 

Crash report VPX rev4131
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00422C78
Attempt to read from 0x00000006
Thread ID: 0x1734 [5940]

Call stack
==========
00422C78 VPinballX.exe (0x00000002 0x00000000 0x00000000 0x00000002)
00423F9F VPinballX.exe (0x00423F50 0x00010E92 0x00000002 0x00000000)
761F4FFC USER32.dll CallWindowProcW + 0xB2C (0x00423F50 0x00000000 0x00000002 0x00000000)
761F454F USER32.dll CallWindowProcW + 0x7F (0xFFFFFFFFFFFF0CB1 0x00010E92 0x00000002 0x00000000)
70316F0A DINPUT.dll DllUnregisterServer + 0x11A (0x00010E92 0x00000002 0x00000000 0x00000000)
7031745E DINPUT.dll DllUnregisterServer + 0x66E (0x00000002 0x00000000 0x00000000 0x00000002)
703172E9 DINPUT.dll DllUnregisterServer + 0x4F9 (0x00000000 0x00000000 0x00000000 0x7030f000)
7030F098 DINPUT.dll DirectInputCreateEx + 0x33C8 (0x00010E92 0x00000002 0x00000000 0x00000000)
7031745E DINPUT.dll DllUnregisterServer + 0x66E (0x00000002 0x00000000 0x00000000 0x00000002)
70317380 DINPUT.dll DllUnregisterServer + 0x590 (0x00010E92 0x00000002 0x00000000 0x00000000)
762144BB USER32.dll AddClipboardFormatListener + 0x4B (0x70317320 0x00010E92 0x00000002 0x00000000)
761F4FFC USER32.dll CallWindowProcW + 0xB2C (0x70317320 0x00000000 0x00000002 0x00000000)
761F4B9A USER32.dll CallWindowProcW + 0x6CA (0x03ABB4C0 0x00000000 0x00000002 0x00000000)
761FE1DF USER32.dll IsRectEmpty + 0x1FF (0x0019DFB4 0x00000020 0x0019E210 0x777141c0)
7771428D ntdll.dll KiUserCallbackDispatcher + 0x4D (0x00000010 0x00000000 0x00000000 0x00010e92)
00533F7A VPinballX.exe (0x00000010 0x00000000 0x00000000 0x00000010)
00423F9F VPinballX.exe (0x00423F50 0x00010E92 0x00000010 0x00000000)
761F4FFC USER32.dll CallWindowProcW + 0xB2C (0x00423F50 0x00000000 0x00000010 0x00000000)
761F454F USER32.dll CallWindowProcW + 0x7F (0xFFFFFFFFFFFF0CB1 0x00010E92 0x00000010 0x00000000)
70316F0A DINPUT.dll DllUnregisterServer + 0x11A (0x00010E92 0x00000010 0x00000000 0x00000000)
7031745E DINPUT.dll DllUnregisterServer + 0x66E (0x00000010 0x00000000 0x00000000 0x00000010)
703172E9 DINPUT.dll DllUnregisterServer + 0x4F9 (0x00000000 0x00000000 0x00000000 0x7030f000)
7030F098 DINPUT.dll DirectInputCreateEx + 0x33C7031745E DINPUT.d70317380 DINPUT.USER32
Environment
===========
Date/time: 24/5/2020, 17:59:40:89
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 18363)

Memory status
=============
Total Reserved: 234760K (229M) bytes
Total Commited: 649568K (634M) bytes
Total Free: 3309912K (3232M) bytes
Largest Free: 2095296K (2046M) bytes

Registers
=========
EAX=00422C70 EBX=00423F50 ECX=1CB9D030 EDX=00000000
ESI=1CB9D030 EDI=00000002 EBP=0019E574 ESP=0019E550 EIP=762144BB
FLG=00010206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.
 

[fuzzel]

totally unstable layers

suddenly disappear from the gui

possibility to switch to the old layer system ?

 

 

no link between the table components and the layers

when we click on any component of the table, the layer affect is not displayed.

maybe we have to go through the collections ?

No there is no way back to the old layers. This is a beta test version so it's normal that things aren't working as expected. If you don't like it don't use the 10.7 and stay on 10.6.

I don't know what you expect from the layers window. The main use case is to create as many layers as you want and give the layers names to identify the content they hold. The other use case is to show/hide only selected layers/elements.

No other feature is implemented.

 

UPDATE: The crash is fixed and comes with the next update.

Edited by fuzzel, 24 May 2020 - 07:27 PM.

[toxie]

@arngrim & @kiwi: next build will have a massive selection of modes, please let me know if that works for you then

[fripounet]

 

 If you don't like it don't use the 10.7 and stay on 10.6.

 

10.7 will have the same graphic characteristics as 10.6?

 

wall 228 selected and no indicator appears (neither the layer nor the wall228 for example).

 

 

so how to know ?  and layer 4 remains grayed out......not logic

indexing is not carried out.

 

and the treeView and the selection of the object must always act in both directions.

 

and this function should be added to the context menu

 

Edited by fripounet, 24 May 2020 - 09:16 PM.

[Steely]

@ Toxie, Hello

Sorry to say... I did not have any luck with the new GetMaterial or GetMaterialPhysics commands. I got Window messagebox errors only.

 

POST EDIT: My mistake the calls were there, program was pointing to previous beta. Sorry, disregard the immediate following...oops

(I looked in my MS ObjectBrowser, where I can point to a dll or exe, and see all available commands. But these new commands were not listed anywhere. So I'm thinking they did not build for some reason.)

Edit: Anyways, I'm having trouble getting it to work, If anyone else has an luck??? end edit

 

My thought on a call would be... GetMaterial(As string "materialname") using the name only to call the object/array since we don't know the other values. I'm not sure either how that all works on your end or how it could interface with vbs exactlly.

 

As an possible example in vbs I may say...

 

Dim MaterialObject, MatObj(16), propertyvalue

Set MaterialObject = GetMaterial "material001"

If IsArray MaterialObject = True then

  count = 0

  For Each propertyvalue in MaterialObject

    MatObj(count) = propertyvalue

    count = count + 1

  Next

End If

 

Thanks again

Edited by Steely, 24 May 2020 - 10:55 PM.

[Steely]

 Toxie, ok, I think I've found a clue with the GetMaterial...  
   
The following errors with a messagebox saying "type missmatch"
If I dim a variable, give it a number value (or not). It returns the error.

Dim wrapLight, etc...
wrapLight = 0
GetMaterial "string",wrapLight,etc,etc,0,0,0,0,0,0,0,0,0,0,0,0,0

error retuned

 

This does not error
GetMaterial "string",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
or
GetMaterial "string",0,6,0.5,0,0,0,42,0,0,0,0,0,0,0,0,0
as long as it's a number it does not error

I still can't Read anything. Probilly because I can't assign a varible name to it.

-----------------------------------------

 

There is a separate problem...I also have a messagebox appear after esc play, which will not close.

They continue to reproduce after each play (like rabbits) it reads....

 

"Preparing Table" "Backing Up Table State" w/progression line

 

It / they only go away after I close vp editor program

[fuzzel]

 
and this function should be added to the context menu
 

I thought about that too but this feature won't help you anymore if you have lots of layers with long names. The layer window is more like the layers in Photoshop. You have to select a layer where you like to add an element. So the intent workflow is select a layer then select multiple elements in the editor and assign them to the selected element.
The layers dialog is not an element browser!

[fuzzel]

the center of the table is at 1421 , 1064

however I cannot place the lightseq at this point because x is limited to 999 and not beyond !!!!!
 

This is indeed strange. But this issue is also present in 10.6. If you enter a X position greater than 999 or a Y position greaten than 1999 the value is rejected. It looks like that the limits are coming from some old backglass use cases. I can remove that but I'm unsure about side effects.

[fuzzel]

I don't really know if that is the force of VPX but I won't remove this yet. As it points out that there are some other dependencies in the code which I don't understand and I don't want to break compatibility.

[fuzzel]

rev4134 is up:

 

- do not start minimized on -play/-pov
- add many many more different windowed mode resolutions
- fix crash while quitting the player

 

 

I don't really know if that is the force of VPX but I won't remove this yet. As it points out that there are some other dependencies in the code which I don't understand and I don't want to break compatibility.

you cannot quickly done compile this version without this limitation,

I test it with other tables.and tell you if it's ok ?

 

do you really have the majority of VPX tables? I don't see really a need in changing that now because it's a 'feature' in all VPX versions so far.