4035 replies to this topic

[fuzzel]

rev4043 is up:

 

- fix element information in the status bar
- fix color button in the flasher properties
- fix collidable checkbox in ramp properties
 

[javier1515]

I forgot to mention that when I select multiple ramps they change to flat automatically, in my case they were in one wire. Sorry for not mentioning it earlier.

Enviado desde mi SM-A205G mediante Tapatalk

[kiwi]

Custom colors saved with the table are missing.

 

 

Thanks

The added colors are saved together with the table, if you open the table with VPX06 the "Colori personalizzati" boxes are not empty.

[supered]

rev4043 is up:

 

- fix element information in the status bar
- fix color button in the flasher properties
- fix collidable checkbox in ramp properties
 

 

Hi,

 

Still have the issue with the "Select Element". I tested it with a blank table with no issue, loading my table gives an issue (program crash).

So, for some reason there is something with my file.

 

I can do 2 things.

1. Get the latest working version of my table (that is the one before I changed some things and saved it with 10.7

2. Send you my table and perhaps you can see if there is a bug or that my file is corrupt.

 

Here is a dump of the windows error log, maybe it helps....

 

Faulting application name: VPinballX.exe, version: 10.7.0.0, time stamp: 0x5ea1b8cb

Faulting module name: VPinballX.exe, version: 10.7.0.0, time stamp: 0x5ea1b8cb

Exception code: 0xc0000409

Fault offset: 0x001a4297

Faulting process id: 0x4198

Faulting application start time: 0x01d6199941f57be6

Faulting application path: C:\Visual Pinball\VPinballX.exe

Faulting module path: C:\Visual Pinball\VPinballX.exe

Report Id: d21672e4-fa95-4a2d-aafa-4e12c5417a01

Faulting package full name: 

Faulting package-relative application ID: 

 

Any thoughts ? Option 1 is not an issue, but perhaps you want to find out whats happening

 

Regards

Ed

Edited by supered, 23 April 2020 - 06:23 PM.

[DJRobX]

 

Also found (during previous build 4035) that when adding a timer to the playfield, it was not usable in the script(s)

I see that in build 4040 I don't have this issue. Did you change something?

 

 

 

I noticed something like this too.  I copy/pasted a flasher element then renamed it.   It was all good in VPX editor, but the script editor did not highlight it as it normally does a table object.     Even playing the table it was not able to access the element, even though it was named correctly.   I saved the table and loaded it back, then it worked fine.

 

Another editor glitch: The moving primitive bug is fixed, but if I move a primitive by dragging it, then change to the tab to show the X/Y/Z values, it will pop back to its old position.   

[toxie]

If I disable the new retract mode in the key preferences, the behavior is the same as in 10.6

 

Next version should be fixed and the retracting plunger should behave the same as the 'old' plunger. Also, it will move 1.5 the speed.

Edited by toxie, 23 April 2020 - 07:30 PM.

[fuzzel]

Custom colors saved with the table are missing.
 
 
Thanks

The added colors are saved together with the table, if you open the table with VPX06 the "Colori personalizzati" boxes are not empty.

Found it and will be fixed in the next update.

[danomyte]

Oh god 10.7 Beta.  Here we go again.  Is it to soon to be doing this?  I just finally upgraded to 10.6 after enduring 6 months of a pop up telling me my tables might not run correctly because I was on 10.5.   

 

While I do appreciate all the hard and fine work you all do with all this development I do BEG you all so that 10.7 Beta doesn't prompt us that we need to upgrade when starting tables.   Anyone that uses VPX knows the lay of the land.  It makes my virtual cab go bonkers and my guests don't clue in how to hit the plunger to get past it.  

 

Is there a way to stifle it?

[toxie]

Yes, its very simple: Don't use tables that require a 10.7 beta !

[batch]

I'm working on the table Nemesis from Peyper but I did most of it using VPX_6

 

If I finish it using VPX_7, people will need this version to be able to play this table

 

So, perhaps it's better that I finish it with VPX_6, so that everybody can play it

 

Am I right ?

[The Loafer]

Seriously Danomyte, either follow Toxie's advice, don't download any 10.7 tables OR download 10.7 beta and just use it as your base (keep 10.6 also if you are worried)

[Umpa]

Woohoo 10.7! Want to thank everyone involved in advance. I'm sure there will be plenty more thank you's in the future!

Sent from my SM-G965U1 using Tapatalk

[toxie]

I'm working on the table Nemesis from Peyper but I did most of it using VPX_6

 

If I finish it using VPX_7, people will need this version to be able to play this table

 

So, perhaps it's better that I finish it with VPX_6, so that everybody can play it

 

Am I right ?

For some more time, please do so, yes. As you can see from the amount of bug reports coming in it's not stable enough yet.

[danomyte]

First and foremost I didn't mean to offend.  I really do appreciate everyone's blood sweat and tears that goes into all this.  

 

A little background on why I posted my previous request.  I believe in Beta testing and realize its importance.  I actually jumped on 10.6 as soon as it was available for my desktop version but because its a little trickier for me to always update my virtual pin cabinet I decided to wait for final release to jump to 10.6 on the cabinet.  Plus test on one (desktop) and compare to the other official release (cabinet).  Also as previous mentioned I realize you have to hit enter twice because of the pop up but on my virtual cabinets some of my guests may not realize this.

 

With the above said I found almost 99% of the tables made with 10.6 worked fine on 10.5.  Exceptions I found were Flintstones and Ice Fever (I'm sure there was more).  So tons of tables created fine with 10.6 work on 10.5 so why not play them until 10.6 became official?  What wasn't working fine during the beta process was 10.6 itself (which is fine as that is part of the beta process i guess).  So obviously there was a lot of 10.6 beta releases.  At times several a week.  There was no way I was going to move half my pinball machines (I have over 20) to get at the back of my virtual pin to keep upgrading.  Plus the 10.6 beta went on for an extremely long time.  That's fine but why should I wait in playing a new table I know works fine on either version when the problem is only the beta itself?  All I simply asked is there a way to suppress the warning  that your not on the beta to work around the issue especially because there was so many versions of the beta and the beta went a long time.  That would make a whole problem go away.  Besides isn't that part of the beta process finding out things and offering suggestions to make the product better?  Is not asking for the ability to disable the error pop up a legit request?  It doesn't have to be implemented but isn't any question a valid question during beta period?  Just offering some advice for 10.7 beta so we can evolve and solve problems.  Besides other areas in VPX has options to "ignore errors".

 

As I write this I am already regretting it because it will probably spew a bunch of backlash and hurt feelings.  Something I am not trying to do.  If you look at my previous comments in the past I have actually tried to help others (with little knowledge I have lol).  I love this group.  I'm also regretting this post because its gonna spark a ton of responses going off topic in how I manage both machines, remote connection tools, backups, running multiple versions, etc.

 

I guess I will live with the error pop up and go underground.  Don't worry I learned no more comments from me.  If you take one thing from this email I am very sorry to offend and keep up the great work all.

[toxie]

Table loading warnings ONLY pop up if the table is likely to be corrupted due to the higher version number! That's the important thing to consider.

 

We only ever increase the table version if we change something that is not forwards compatible, meaning if this newer table version would be loaded on an older version it likely would be corrupted. And this is very important, as if you would then change something and save the table you could end up with garbage! Or experiencing crashes during the load/during gameplay, potentially dragging other work down with it.

 

So the other important thing to note here is, that it's NOT about the VPX version, but only the internal table version. So some VPX (final) versions are perfectly compatible with each other and will also not throw errors in that aspect, while others MUST warn about the different table version to not corrupt peoples work.

[supered]

In my opinion you’re not offending (but I am not the programmer)

I think that VPX will be the best because it’s a combination of thoughts. Some of them are better then the rest, but still.... we’re in this together I presume.

Keep up the good work you programmers!!!


Verzonden vanaf mijn iPhone met Tapatalk

[toxie]

And sorry, i cannot resist but note that

 

"There was no way I was going to move half my pinball machines (I have over 20) to get at the back of my virtual pin to keep upgrading. ... ... That's fine but why should I wait in playing a new table I know works fine on either version when the problem is only the beta itself?"

 

doesn't make any sense. Cause why do you upload the new tables, but do not upload the newer beta at the same time?? 

[wrd1972]

 

"There was no way I was going to move half my pinball machines (I have over 20) to get at the back of my virtual pin to keep upgrading. ... ... That's fine but why should I wait in playing a new table I know works fine on either version when the problem is only the beta itself?"

 

doesn't make any sense. Cause why do you upload the new tables, but do not upload the newer beta at the same time?? 

 

Dano,

You are likely the only person on the planet that has to move real pins in order to support the virtual cab. Seriously! Might do yourself a big favor and get a wireless K400 keyboard, and do the required support sitting at the front of the cab  like the rest of us. I cant imagine why this would not resolve your apparent upgrade difficulties.

Edited by wrd1972, 24 April 2020 - 05:18 PM.

[gtxjoe]

To avoid the popup, I think all you would have to do is open the 10.6 beta table in Vpinball 10.5, make a minor change and change it back and the hit Save? Now the table is saved as a 10.5 table and wont display the warming popup

Someone correct me if this is wrong

[chepas]

@toxie I built x64 VPinball yesterday. Whilst trying to get something working this what I needed, it does turn out that I won't be using this x64 method now though.

 

I was just wondering about how long it takes to load the "VP Player Render". It's significantly slower loading on the x64 build, just wondered if this is normal or missing something?