4027 replies to this topic

[wiesshund]

@Thalamus  Hey thanks for the reply, I have the version which is posted in the first post, uploaded 

 Latest build is

 

Actions · vpinball/vpinball (github.com)

[vpxfx3fp]

Hello that is not listed in the first original post for which im assuming its not stable. Also when i clicked actions it doesnt say anything about releases or where they are on github, this mite sound stupid even when i eventually find the releases it only show 270 version

[Thalamus]

I said your vp version is old because of "rev3788" - that is the old rev numbering before github if I'm not mistaken.

So we're talking about many months of development. I would expect to see 270 and I agree in that you should stick with what is released here.

Github betas is something I try, but, I don't put them in as my default VP, if the latest here is not proven to be a problem, like it was on 239.

[Uncle Monkey]

@vpxfx3fp Just to avoid confusion, I want to be sure that you're aware that Fuzzel has been regularly updating the version available in the first post. The version 270 has only been available there for about two and a half weeks.

[batch]

No more transparency on playfield using a PNG image with VP10.7 ?

 

Perhaps a setting I can't find ?

 

                  

[jpsalas]

No more transparency on playfield using a PNG image with VP10.7 ?

 

Perhaps a setting I can't find ?

 

                  

 

The material of the playfield must be dynamic, this is its opacity must be under 0, like 0,9999 and it must be activated, as shown here:

 

 

It has always been like this in VPX, in all versions.

Edited by jpsalas, 06 August 2021 - 12:30 PM.

[wiesshund]

 

No more transparency on playfield using a PNG image with VP10.7 ?

 

Perhaps a setting I can't find ?

 

                  

 

The material of the playfield must be dynamic, this is its opacity must be under 0, like 0,9999 and it must be activated, as shown here:

 

Capture.PNG

 

It has always been like this in VPX, in all versions.

 

 

Keep in mind
If nothing is behind the playfield, and the table's background color is black
It will still look like batch's pictures for the most part, though perhaps a little more depth

 

On the wire triggers, i like to put them on a surface a few points lower than the playfield
then make the slot transparent, seems to give a nice illusion of depth

 

I have wrapped the slot in wall before, and gave it a side texture of plywood, looked kind of neat and didnt require making a playfield mesh
but was kind of tedious

[jpsalas]

I tried Revision 288, and after two days I get also this error. And I can reproduce it

Just select "Throw balls in Player" and add a ball by clicking with the left mouse and that works fine, but instead of one single click then doubleclick, and bang the error comes up. I know, I know why doubleclick, there is no meaning in doing that  

 

 

 

Crash report VPX rev288 (08bd334)

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

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00504817

Attempt to read from 0x00000000

Thread ID: 0xB18 [2840]

 

Call stack

==========

00504817 VPinballX.exe (0x0019E894 0x004F80D0 0x00000000 0x01000000)

004F82B4 VPinballX.exe (0x033C91CC 0x0F217CE0 0xFFFFFFFF86664004 0x037dd3a8)

6FD154C5 vbscript.dll DllGetClassObject + 0x1C55 (0x0F217CE0 0x00000000 0x037DD3A8 0x0019ea48)

6FD153EB vbscript.dll DllGetClassObject + 0x1B7B (0xFFFFFFFF86664004 0x00000000 0x037DD2E8 0x0019ea48)

6FD0BD43 vbscript.dll (0x00000000 0xFFFFFFFFB33060A9 0x0F1F95B0 0x00000000)

6FD079BE vbscript.dll (0x00000000 0x00000000 0x037DD3A8 0x037da630)

6FD078D5 vbscript.dll (0x00000000 0x00000000 0x0F1F95B0 0x0f1f95b0)

6FD0D35A vbscript.dll (0x0F1CB340 0x00000000 0x00000000 0x00000000)

6FCF69DF vbscript.dll (0x0F2132B0 0x00000514 0x006262B4 0x00000400)

004B3C00 VPinballX.exe (0x00000514 0x0019EC74 0x0AF5CBA0 0x00001d7e)

 

Environment

===========

Date/time: 7/8/2021, 09:45:34:738

Number of CPUs: 16

Processor type: 586

System: Windows 10 (10.0 19043)

 

Memory status

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

Total Reserved: 167988K (164M) bytes

Total Commited: 474956K (463M) bytes

Total Free: 3551296K (3468M) bytes

Largest Free: 2095464K (2046M) bytes

 

Registers

=========

EAX=00000000 EBX=0019E7E0 ECX=00000000 EDX=00000000

ESI=00000002 EDI=033C91CC EBP=00000000 ESP=0019EC50 EIP=005337C5

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

 

 

Mini dump saved successfully.

[jsm174]

@jpsalas,

 

I just committed a PR that updates the CI to also make debug builds.

 

You can check it out at:

 

https://github.com/v...runs/1108181733

 

 

Just make sure the VPinballX.pdb and VPinballX.exe file are in the same folder. This way the stack trace will contain the actual line number of the crash.

[jpsalas]

Hey jsm174!

 

I have tried the new revision and it gives me this:

 

Crash report VPX rev294 (7eaab15)

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

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:008AB9E3

Attempt to read from 0x00000000

Thread ID: 0x1C98 [7320]

 

Call stack

==========

008AB9E3 VPinballX.exe common_strnlen_simd<1,1,unsigned short> + 0x133 strnlen.cpp(152+0011 byte(s)) (0x00000000 0xFFFFFFFFFFFFFFFF 0x03FAE81C 0x008ac8f0)

008AB62B VPinballX.exe common_strnlen<1,unsigned short> + 0x1B strnlen.cpp(185+0013 byte(s)) (0x00000000 0xFFFFFFFFFFFFFFFF 0x03FAE828 0x0030d20c)

008AC8F0 VPinballX.exe wcslen + 0x10 strnlen.cpp(218+0011 byte(s)) (0x00000000 0x03FAE8C4 0x0066431B 0x00000000)

0030D20C VPinballX.exe std::_WChar_traits<wchar_t>::length + 0xC xstring(270+0009 byte(s)) (0x00000000 0x278D1FA3 0x03FAEA74 0x03fae8d8)

0066431B VPinballX.exe std::operator<<<wchar_t,std::char_traits<wchar_t> > + 0x4B ostream(820+0009 byte(s)) (0x03FAE95C 0x00000000 0x00A5D67C 0x03faea84)

00652958 VPinballX.exe CodeViewer::OnScriptError + 0x248 codeview.cpp(934+0021 byte(s)) (0x043B12BC 0x0CAFEC20 0xFFFFFFFF86664004 0x048bd3b0)

701754C5 vbscript.dll DllGetClassObject + 0x1C55 (0x0CAFEC20 0x00000000 0x048BD3B0 0x03faec38)

701753EB vbscript.dll DllGetClassObject + 0x1B7B (0xFFFFFFFF86664004 0x00000000 0x048BD2F0 0x03faec38)

7016BD43 vbscript.dll (0x00000000 0x53F3467F 0x0CAF7D70 0x00000000)

701679BE vbscript.dll (0x00000000 0x00000000 0x048BD3B0 0x048bb640)

701678D5 vbscript.dll (0x00000000 0x00000000 0x0CAF7D70 0x0caf7d70)

7016D35A vbscript.dll (0x0CAF8218 0x00000000 0x00000000 0x00000000)

701569DF vbscript.dll (0x0CAFDA68 0x00000514 0x00B6EA60 0x00000400)

007EC592 VPinballX.exe EventProxy<Timer,&DIID_ITimerEvents>::FireDispID + 0xA2 eventproxy.h(88+0042 byte(s)) (0x00000514 0x03FAEE5C 0x03FAEEF8 0xffffffffcccccccc)

0036CE66 VPinballX.exe EventProxyBase::FireVoidEvent + 0x56 eventproxy.h(14+0022 byte(s)) (0x00000514 0x278D19BB 0x03FAEFF0 0x03faeef8)

007EC779 VPinballX.exe EventProxy<Timer,&DIID_ITimerEvents>::FireVoidGroupEvent + 0x139 eventproxy.h(76) (0x00000514 0x0CB79834 0x03FAEFF0 0x0061802a)

007EC620 VPinballX.exe Timer::FireGroupEvent + 0x20 timer.h(75+0032 byte(s)) (0x00000514 0x03FAF108 0x03FAF11C 0x1e5cbd7c)

0061802A VPinballX.exe Player::UpdatePhysics + 0x7FA player.cpp(3064+0023 byte(sVPinbal

Environment

===========

Date/time: 7/8/2021, 19:10:34:969

Number of CPUs: 16

Processor type: 586

System: Windows 10 (10.0 19043)

 

Memory status

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

Total Reserved: 169680K (165M) bytes

Total Commited: 408144K (398M) bytes

Total Free: 3616416K (3531M) bytes

Largest Free: 2086952K (2038M) bytes

 

Registers

=========

EAX=00000000 EBX=048BD478 ECX=00000000 EDX=00000000

ESI=03FAF11C EDI=03FAF108 EBP=03FAF114 ESP=03FAEFF8 EIP=0061FDD2

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

 

 

Mini dump saved successfully.

 

I simply tried the "New" table, and the error happens when you use the "Throw balls in player", and you click very fast and you click on the same ball, then the script fails in the line 319, like this

Runtime error

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

Line: 319

Class not registered

 

which is  BOT = GetBalls

 

So it is the GetBalls which fail if you click on a ball, because that's what  happens when you doubleclick

 

But if you don't use the GetBalls in the script then you can click on a ball if you want to throw this ball somewhere.

[jsm174]

@jpsalas,

 

Thanks! Can you check this build out before I commit? 

 

https://github.com/v...runs/1108645423

[richy76]

Can someone test circus volitaire, i have even re downloaded it, it says something like "there is malicious code in the script and your av wont allow it to run" for me.

Thanks.

[wiesshund]

Can someone test circus volitaire, i have even re downloaded it, it says something like "there is malicious code in the script and your av wont allow it to run" for me.

Thanks.

 

Not a beta issue
That is a "your av configuration issue"
See the thread already open for that and you will find a solution

[jpsalas]

@jpsalas,

 

Thanks! Can you check this build out before I commit? 

 

https://github.com/v...runs/1108645423

 

It is better now as VPX doesn't crash, but still I get the script error in the line with the GetBalls command:

 

Starting script

 

Runtime error

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

Line: 319

Class not registered

 

To reproduce it, just start VPX, choose file new, new table. Run it. Press D and select "Throw balls in player", and then click on the ball which rests on the plunger. Or throw a ball and left click on it. 

 

Without the instruction GetBalls on the script you can left click on the ball  and throw away that same ball. But if the script has the GetBalls in it, then it gives the error,

 

But at least now it doesn't crash VPX 

[jsm174]

Cool. Thanks for testing. I committed that fix into master. 

 

As for the "Class not registered", maybe someone else here has an idea?

[stedal]

how do you adjust flippers in 10.7 so they are more like the real machine and you can make shots plz help thank you like on acdc the flippers end to high and it is hard to  make shots

Edited by stedal, 08 August 2021 - 12:32 PM.

[richy76]

 

Can someone test circus volitaire, i have even re downloaded it, it says something like "there is malicious code in the script and your av wont allow it to run" for me.

Thanks.

 

Not a beta issue
That is a "your av configuration issue"
See the thread already open for that and you will find a solution

 

Thanks, can anyone point me in the direction of the thread?.

Strange as i have played this machine before in the past with no problems, that is why i said it in this thread,

Thanks.

[richy76]

And then it starts working again on its own lol.

Thanks.

[JochenB]

Sorry for the stupid question, but how do I do the update from 10.6.0 to 10.7? Just copy the downloaded files into my existing Visual Pinball directory? Or do I have to do a complete reinstall? 

 

Are there any other steps necessary then because of B2S, VPinMame or so?

 

I'm still relatively new in the virtual pinball world, so sorry if I might ask some stupid questions.

 

Thanks

Edited by JochenB, 09 August 2021 - 11:23 AM.

[Thalamus]

Rename VPinballX.exe to VPinballX62.exe or something. Extract, overwrite everything. Now double clicking or running tables via frontend will be 10.7.

Go back ? Rename VPinballX.exe to VPinballX7beta.exe - rename VPinballX62.exe back to VPinballX.exe

 

I is basically as easy as that. Advantage. You get updates "scripts" folder, with imo essential upgrades. 10.7 has a new gui, and has had and probably still do have few bugs related to the work that has been done on that. But, it is absolutely not a problem using it as default to play with and well, more stable as an editor too, even with a bug or two. Not like the old didn't have any

 

Only table that I know of that is broken is Kiwi's Tri Zone - I'm sure it will be updated once 10.7 becomes official.

Edited by Thalamus, 09 August 2021 - 12:42 PM.