4027 replies to this topic

[Pin-Pete]

I'm having some stuttering.

[fuzzel]

I have some beer

[wiesshund]

I have some beer

Share!

[Dracarius]

drag the divider down on the properties window, you have layers taking up all the room

 

or pull the layers panel loose and then pin it to the bottom?

 

 

 

This was it - First time I have used the new software so even full screen all I had was layers.   Thanks!

 

[ebor]

Hi,
I'm sorry but I'm back with my problem of modifying scripts on a table registered in 10.7.
If I take for example the Batman (Data East 1991) BW Mod table from S1gbsoN (https://www.vpforums...&showfile=15678) and I go into the script, it's impossible for me to modify the code (I can move around in the code but impossible to insert or delete text, the 'paste' with the right mouse button is greyed out).
No problem with a table provided in 10.6 and opened in VPX 10.7.
I have the release 154, all DLLs are unlocked, no file is read-only and VPX 10.7 is launched as administrator.
Does anyone have an idea?
Thanks

[toxie]

FYI, the latest build is still giving me the sporadic "Could not create sound buffer for load" pop-up when loading first table.  Is there any workaround for this?

Is this with all tables? Can you please show your sound/audio settings?

[gtxjoe]

I believe I have seen that happen in 10.6 if you open a menu item like Sound manager or Collection manager and leave it open. Typing in script window may not work as expecyed

[ebor]

I believe I have seen that happen in 10.6 if you open a menu item like Sound manager or Collection manager and leave it open. Typing in script window may not work as expecyed

Thank you for your answer.
I have opened and closed all the options in the Table menu.
Still impossible to edit the script.
I made another test, I deleted in the registry all the key HKEY_CURRENT_USER\Software\Visual Pinball, launched VPX 10.7 but still the same problem.

[Outhere]

Hi,
I'm sorry but I'm back with my problem of modifying scripts on a table registered in 10.7.
If I take for example the Batman (Data East 1991) BW Mod table from S1gbsoN (https://www.vpforums...&showfile=15678) and I go into the script, it's impossible for me to modify the code (I can move around in the code but impossible to insert or delete text, the 'paste' with the right mouse button is greyed out).
No problem with a table provided in 10.6 and opened in VPX 10.7.
I have the release 154, all DLLs are unlocked, no file is read-only and VPX 10.7 is launched as administrator.
Does anyone have an idea?
Thanks

There should be no need to run any Pinball Related Software As Administrator (Admin)
see – # 7 & 23 -- https://www.nailbust...doku.php?id=faq

[ebor]

yes but I try a bit of everything out of desperation

[dopdahl]

Possible bug in latest 10.7 beta... Maybe earlier versions as well.  Not sure if this is the right place to post bugs...

 

If I have a POV file saved and associated with a table and then I go into Table options in the editor and change the Day/Night slider settings and save the table, the Day/Night change is not saved (or perhaps it's overriden by the POV?).

 

In any event, when a POV already exists, modifying at least that setting will not save.  The next time the table loads, it's back to the original setting.

 

Also when the table is run, the change doesn't manifest.

 

Might also be true for other table options as well, I haven't tested yet.

 

Seems like a bug.  Works as expected when no POV file exists.

Edited by dopdahl, 02 May 2021 - 12:16 AM.

[wiesshund]

Possible bug in latest 10.7 beta... Maybe earlier versions as well.  Not sure if this is the right place to post bugs...

 

If I have a POV file saved and associated with a table and then I go into Table options in the editor and change the Day/Night slider settings and save the table, the Day/Night change is not saved (or perhaps it's overriden by the POV?).

 

In any event, when a POV already exists, modifying at least that setting will not save.  The next time the table loads, it's back to the original setting.

 

Also when the table is run, the change doesn't manifest.

 

Might also be true for other table options as well, I haven't tested yet.

 

Seems like a bug.  Works as expected when no POV file exists.

 

That would be works as intended
If you have a POV, it will over ride any of that stuff you save to the table

What you have to do is click file > export > POV
and export it over the top of your existing POV

[kiwi]

 

FYI, the latest build is still giving me the sporadic "Could not create sound buffer for load" pop-up when loading first table.  Is there any workaround for this?

Is this with all tables? Can you please show your sound/audio settings?

 

This happened to me once, maybe twice, after a long session and after opening a lot of tables

I don't remember the table but I closed and reopened VP and reopened the same table with no problem.

[wiesshund]

table sound manager being open seems to be able to cause this crash a lot

Crash report VPX rev156 (0ddb9d4)
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:27AA6F2E
Attempt to read from 0x00000004
Thread ID: 0x14AC [5292]

Call stack
==========
27AA6F2E  (0x216BE708 0x218FD4D0 0x00000000 0x00000000)
27AA637C  (0x25AED960 0x00000000 0x00000000 0x25aed960)
27AA623C  (0x00000000 0x00000000 0x25AED960 0x27aa61e8)
0ABDD49D  (0x23D1D010 0x00000000 0x00000000 0x25aed960)

Environment
===========
Date/time: 1/5/2021, 22:54:53:387
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 219132K (213M) bytes
Total Commited: 902108K (880M) bytes
Total Free: 3073000K (3000M) bytes
Largest Free: 2094912K (2045M) bytes

Registers
=========
EAX=218E2FC8 EBX=216BC5F4 ECX=67961468 EDX=2639C720
ESI=218E2FC8 EDI=00000000 EBP=00000000 ESP=117CFC08 EIP=23900F62
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

Crash report VPX rev156 (0ddb9d4)
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:257E718E
Attempt to read from 0x00000004
Thread ID: 0xA6C [2668]

Call stack
==========
257E718E  (0x1D6BE708 0x1D8E9D30 0x00000000 0x00000000)
257E65DC  (0x21AED960 0x00000000 0x00000000 0x21aed960)
257E649C  (0x00000000 0x00000000 0x21AED960 0x257e6448)
0B4CD49D  (0x1FD1D010 0x00000000 0x00000000 0x21aed960)

Environment
===========
Date/time: 1/5/2021, 23:01:01:570
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 203352K (198M) bytes
Total Commited: 846980K (827M) bytes
Total Free: 3143908K (3070M) bytes
Largest Free: 2094912K (2045M) bytes

Registers
=========
EAX=1D8E07A0 EBX=1D6BC5F4 ECX=67961468 EDX=092EF580
ESI=1D8E07A0 EDI=00000000 EBP=00000000 ESP=0C10FC08 EIP=1F900F62
FLG=00010206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

[Shockman]

 

Any chance of getting analog trigger with a range of two for the flippers (top and bottom) using an xbox controller? (for us desktop maggots)

set the analog triggers to digital and you can use all 4 shoulder buttons

 

How to?

[dopdahl]

 

Possible bug in latest 10.7 beta... Maybe earlier versions as well.  Not sure if this is the right place to post bugs...

 

If I have a POV file saved and associated with a table and then I go into Table options in the editor and change the Day/Night slider settings and save the table, the Day/Night change is not saved (or perhaps it's overriden by the POV?).

 

In any event, when a POV already exists, modifying at least that setting will not save.  The next time the table loads, it's back to the original setting.

 

Also when the table is run, the change doesn't manifest.

 

Might also be true for other table options as well, I haven't tested yet.

 

Seems like a bug.  Works as expected when no POV file exists.

 

That would be works as intended
If you have a POV, it will over ride any of that stuff you save to the table

What you have to do is click file > export > POV
and export it over the top of your existing POV

 

I see.  That's a decent work around I suppose.  It would be a nice feature to "auto-export" the pov if one is already on disk though.  I can't think of a scenario where you already have a separate POV, but would not want any changes you make to be automatically updated in that POV.

[Segovia11]

Dear Development Team  please find enclosed a political question,

                                                                                                           should the VPX title be changed to VPXI due to the loss of its backward compatibility?  A popup menu that warns the user before saving the file would also jog a memory or two, or more!. 

 

Thanks a million Devs for the time you have dedicated to the upgrades

VPX is a joy 

      

[fuzzel]

Dear Development Team  please find enclosed a political question,
                                                                                                           should the VPX title be changed to VPXI due to the loss of its backward compatibility?  A popup menu that warns the user before saving the file would also jog a memory or two, or more!. 
 
Thanks a million Devs for the time you have dedicated to the upgrades
VPX is a joy 
      

No VPX is fully compatible to older versions. If you save a table with 10.7 you will get a notification message when you load that table in earlier versions.

[mdienstl]

Hi,

 

Are tables created with VP 10.6 or before working the same (e.g. physics) with VP 10.7 (beta)?

 

Martin

[wiesshund]

 

 

Possible bug in latest 10.7 beta... Maybe earlier versions as well.  Not sure if this is the right place to post bugs...

 

If I have a POV file saved and associated with a table and then I go into Table options in the editor and change the Day/Night slider settings and save the table, the Day/Night change is not saved (or perhaps it's overriden by the POV?).

 

In any event, when a POV already exists, modifying at least that setting will not save.  The next time the table loads, it's back to the original setting.

 

Also when the table is run, the change doesn't manifest.

 

Might also be true for other table options as well, I haven't tested yet.

 

Seems like a bug.  Works as expected when no POV file exists.

 

That would be works as intended
If you have a POV, it will over ride any of that stuff you save to the table

What you have to do is click file > export > POV
and export it over the top of your existing POV

 

I see.  That's a decent work around I suppose.  It would be a nice feature to "auto-export" the pov if one is already on disk though.  I can't think of a scenario where you already have a separate POV, but would not want any changes you make to be automatically updated in that POV.

 

 

Many people do not do POV's as external files

They just save changes directly to the table

 

POV is optional, not required

Hi,

 

Are tables created with VP 10.6 or before working the same (e.g. physics) with VP 10.7 (beta)?

 

Martin

should be, yes