4027 replies to this topic

[toxie]

One of the most important tools for me is the debug editor. I use it all the time and really cannot do my debug in VR version as it is lacking this editor. So even small updates to that would help table authoring a lot.

• For example if I just could resize it? It becomes quite small when tracing some debug prints.

This one is now implemented. Code completion goes way over my head. And ESC hopefully could be added by fuzzel.

[toxie]

..seems like pressing ESC in a scintilla editor window (i.e. what the debugger also uses) cannot be easily catched.. :/

[Pinballman]

I have a question, and I apologize if its been already answered and I just missed it.  I've been on 10.7 and decided to roll back to 10.6 for a bit.  I get a message saying that the table was saved with 10.7 and may not play right. Didn't see a way to cancel and clicked on OK.  Table showed no graphics. Tried another table and got same thing.  I then went back to 10.7, and when I tried to load either table it seemed to be corrupted and VP crashes. Didn't want to try again and mess up another table - does this mean that any table played on 10.7 can no longer be played on 10.6?  Thanks!

[Wylte]

I have a question, and I apologize if its been already answered and I just missed it.  I've been on 10.7 and decided to roll back to 10.6 for a bit.  I get a message saying that the table was saved with 10.7 and may not play right. Didn't see a way to cancel and clicked on OK.  Table showed no graphics. Tried another table and got same thing.  I then went back to 10.7, and when I tried to load either table it seemed to be corrupted and VP crashes. Didn't want to try again and mess up another table - does this mean that any table played on 10.7 can no longer be played on 10.6?  Thanks!

If you *save* a table in 10.7, then you can't go back without some work. That's why a lot of tables are specifying their version in this in-between period.
Shouldn't be a problem going the other way normally, but saving back and forth probably isn't a great idea.

Edited by Wylte, 10 July 2021 - 01:40 AM.

[wiesshund]

I have a question, and I apologize if its been already answered and I just missed it.  I've been on 10.7 and decided to roll back to 10.6 for a bit.  I get a message saying that the table was saved with 10.7 and may not play right. Didn't see a way to cancel and clicked on OK.  Table showed no graphics. Tried another table and got same thing.  I then went back to 10.7, and when I tried to load either table it seemed to be corrupted and VP crashes. Didn't want to try again and mess up another table - does this mean that any table played on 10.7 can no longer be played on 10.6?  Thanks!

 

Do the tables still crash if you load them in VP6?

 

It kind of sounds as if you saved some kind of change in VP7, then opened in VP6
and then wound up saving it again in VP6.

 

I am not sure of you can fix the affected table files now.

I have an older build of 10.7, the last one that could open a 10.7 file and save it in a fully 10.6 compatible form, but i think it is too late

for you to do that now.

You can try it, at this point, i dont think it can hurt the table file any further

https://drive.google...iew?usp=sharing

 

And no, you can play all the tables you want in 10.7 and then play them in 10.6
But you can not save any changes into the table file.
If you edit the POV, you need to export the POV to a tablename.POV file and not save the table itself.

Edited by wiesshund, 10 July 2021 - 02:11 AM.

[fuzzel]

 
rev225 is up (Release Cadidate):

 
What about the layers do you see them as good or nothing can be done with renaming?
 
All we have to do is use F2, every layer, every object in that list, then no need for spending up to 5 seconds pissing about trying to get a rename edit.
 
Lower case search on the filter?

Well come with the next update...

[chepas]

 

 

 
rev225 is up (Release Cadidate):

 
What about the layers do you see them as good or nothing can be done with renaming?
 
All we have to do is use F2, every layer, every object in that list, then no need for spending up to 5 seconds pissing about trying to get a rename edit.
 
Lower case search on the filter?

Well come with the next update...

 

 

Awesome, well done!

[jipeji16]

Hi super guys 

 

I have a script error, when in the scritp it talks about Controller.B2sSetData, and when i use the commandd : for each x in GI (for example) when it says that :"Line 1 : Index was out of range. Must be non negative and less than the size of the collection. Parameter name index."

It was working with the rev 213

 

and not with the last rev 225

not test between them.

Tested with the Guardians

 

Thanks for all

 

JPJ

[chepas]

 

 

 
rev225 is up (Release Cadidate):

 
What about the layers do you see them as good or nothing can be done with renaming?
 
All we have to do is use F2, every layer, every object in that list, then no need for spending up to 5 seconds pissing about trying to get a rename edit.
 
Lower case search on the filter?

Well come with the next update...

 

 

Just added Pull for LightSequence flashers.... I have only just realized your change was in the whole time I was doing that, so just tested and perfect.

[Pinballman]

 

I have a question, and I apologize if its been already answered and I just missed it.  I've been on 10.7 and decided to roll back to 10.6 for a bit.  I get a message saying that the table was saved with 10.7 and may not play right. Didn't see a way to cancel and clicked on OK.  Table showed no graphics. Tried another table and got same thing.  I then went back to 10.7, and when I tried to load either table it seemed to be corrupted and VP crashes. Didn't want to try again and mess up another table - does this mean that any table played on 10.7 can no longer be played on 10.6?  Thanks!

 

Do the tables still crash if you load them in VP6?

 

It kind of sounds as if you saved some kind of change in VP7, then opened in VP6
and then wound up saving it again in VP6.

 

I am not sure of you can fix the affected table files now.

I have an older build of 10.7, the last one that could open a 10.7 file and save it in a fully 10.6 compatible form, but i think it is too late

for you to do that now.

You can try it, at this point, i dont think it can hurt the table file any further

https://drive.google...iew?usp=sharing

 

And no, you can play all the tables you want in 10.7 and then play them in 10.6
But you can not save any changes into the table file.
If you edit the POV, you need to export the POV to a tablename.POV file and not save the table itself.

 

 

Thank you for your response and suggestions, really appreciate it!. I've been using VP7 pretty much exclusively for over a year. It appears that any table that I've made changes in POV or images are the ones affected (I'd say several hundred as I prefer tables tuned in a certain way). My only two reasons for switching back to VP6 for a bit is I don't like losing the ui image in the image manager after a table is played, requiring to close and reload it, and I find the layer option easer to use when up in the table options rather than down at the bottom. Dumb reasons, I know!!

 

Thank you for sending me beta revision 4356 - however I have the same problem with it as well. Fortunately instead of clicking OK I went into task manager and ended process and table was fine. However I did find a beta revision 4406 in my files and have confirmed that this allows compatibility from VP7 to VP6 without a problem. There's probably a later version that may work too, but for now I'll be using beta revision 4406 until this gets hopefully gets squared away.  Again, thank you!

Edited by Pinballman, 11 July 2021 - 05:31 AM.

[wiesshund]

 

 

 

 

Thank you for your response and suggestions, really appreciate it!. I've been using VP7 pretty much exclusively for over a year. It appears that any table that I've made changes in POV or images are the ones affected (I'd say several hundred as I prefer tables tuned in a certain way). My only two reasons for switching back to VP6 for a bit is I don't like losing the ui image in the image manager after a table is played, requiring to close and reload it, and I find the layer option easer to use when up in the table options rather than down at the bottom. Dumb reasons, I know!!

 

Thank you for sending me beta revision 4356 - however I have the same problem with it as well. Fortunately instead of clicking OK I went into task manager and ended process and table was fine. However I did find a beta revision 4406 in my files and have confirmed that this allows compatibility from VP7 to VP6 without a problem. There's probably a later version that may work too, but for now I'll be using beta revision 4406 until this gets hopefully gets squared away.  Again, thank you!

 

 

1) DO NOT rely on the older betas.
I only meant for it as a last ditch effort to see if by any chance you could resurrect the the files that appeared to have gotten corrupted

2) POV changes, make all the POV changes you want, but do not save the table, instead click FILE > EXPORT > POV
and save it as tablename.POV
Then when you close the table, chose NOT to save the changes.
The POV will be used for the table, regardless of VPX version, and the POV will remain, even if the table is updated later, as long as you keep POV and table names the same

 

That will keep your table in original 10.6 form

Too many data structure changes, and data structure fixes from .6 to current .7

Editing one in .7 and loading it in .6 wont break anything, but the table will be a sterile white stanley kubrick looking table, it will run though

but allowing .6 to then save it again, is most likely to break the table as it does not understand the data structure it is looking at, plus it is going to write now fixed bugs back into it

and will probably corrupt the table entirely

 

If you accidentally do one, i have found that the older beta can in many cases return it to a .6 compatible table, as long as you do not let .6 do anything to the table before hand.
but i would not rely on doing that as there could be unforseen errors in doing so, i would not recommend making a habit of using the older beta exe's to flop back and forth except as a last ditch effort if an accident has happened

otherwise you may find next month that you have hundreds of heavily errored tables.

 

3) No images in editor only happens if you directly launch a table and then exit to editor
If you right click a table, and pick edit, you can go back and forth all day long from playing to editing and have the images shown

 

Myself, i much dislike the 10.6 layers
can not rename, stuck with a max of 11, can not show or hide individual objects, can not drag and drop between layers, and of course i can not put the layers panel over on a 2nd screen

 

Lastly "This" is not something that will be "squared away"

10.7 created or edited tables are not going to be backwards compatible with 10.7

Too much of the data structure has been fixed, changed, improved etc.
It is akin to trying to load XLSX files in MS Excel 97

It is an excel spread sheet, but it is no longer any kind of animal that excel 97 understands

[toxie]

Just added Pull for LightSequence flashers.... I have only just realized your change was in the whole time I was doing that, so just tested and perfect.

 

And merged.. Thanks!

 

I have a script error, when in the scritp it talks about Controller.B2sSetData, and when i use the commandd : for each x in GI (for example) when it says that :"Line 1 : Index was out of range. Must be non negative and less than the size of the collection. Parameter name index."

It was working with the rev 213

 

and not with the last rev 225

not test between them.

Tested with the Guardians

more than weird.. i don't see anything that we commited that could've caused this..

[chepas]

 

Just added Pull for LightSequence flashers.... I have only just realized your change was in the whole time I was doing that, so just tested and perfect.

 

And merged.. Thanks! 

 

Nice, I'm happy that's in before final.

[jipeji16]

 

Just added Pull for LightSequence flashers.... I have only just realized your change was in the whole time I was doing that, so just tested and perfect.

 

And merged.. Thanks!

 

I have a script error, when in the scritp it talks about Controller.B2sSetData, and when i use the commandd : for each x in GI (for example) when it says that :"Line 1 : Index was out of range. Must be non negative and less than the size of the collection. Parameter name index."

It was working with the rev 213

 

and not with the last rev 225

not test between them.

Tested with the Guardians

more than weird.. i don't see anything that we commited that could've caused this..

 

Arrrrffff.... Another time... Not very lucky... Thanks very much @Toxie

I think i will install all again... pffff

 

Thanks again to all of you

JPJ

[jipeji16]

 

 

Just added Pull for LightSequence flashers.... I have only just realized your change was in the whole time I was doing that, so just tested and perfect.

 

And merged.. Thanks!

 

I have a script error, when in the scritp it talks about Controller.B2sSetData, and when i use the commandd : for each x in GI (for example) when it says that :"Line 1 : Index was out of range. Must be non negative and less than the size of the collection. Parameter name index."

It was working with the rev 213

 

and not with the last rev 225

not test between them.

Tested with the Guardians

more than weird.. i don't see anything that we commited that could've caused this..

 

Arrrrffff.... Another time... Not very lucky... Thanks very much @Toxie

I think i will install all again... pffff

 

Thanks again to all of you

JPJ

 

Srcipt error resolved !!!

 

There was a windows 8 compatibility checked in the VPX exe... (pfff)

without that it works well again with the last revision It hasn't resolved my find option's bug

But i can go on working on Alien

 

Thanks @Toxie 

 

JPJ

Edited by jipeji16, 11 July 2021 - 02:05 PM.

[toxie]

Thanks for the quick tests/feedback

[chepas]

Is this new? codeview.SaveToStream. 

Save externally loaded .vbs script also to .vpx table?

The message while saving was pretty annoying after half an hour and it's always a No

 

Edit: Must be something to do with updating from 10.6. I think I had an external script window loaded somehow. A VP.7 table was loaded but the script was using 10.6 table.

 

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

 

Recent file list names are limited to 78 chars, or at least that's what it looks like. 10.6 file menu expands wider so it could be clipped. After I looked I have no idea to fix that.

Edited by chepas, 12 July 2021 - 12:14 AM.

[Pinballman]

 

 

 

 

 

Thank you for your response and suggestions, really appreciate it!. I've been using VP7 pretty much exclusively for over a year. It appears that any table that I've made changes in POV or images are the ones affected (I'd say several hundred as I prefer tables tuned in a certain way). My only two reasons for switching back to VP6 for a bit is I don't like losing the ui image in the image manager after a table is played, requiring to close and reload it, and I find the layer option easer to use when up in the table options rather than down at the bottom. Dumb reasons, I know!!

 

Thank you for sending me beta revision 4356 - however I have the same problem with it as well. Fortunately instead of clicking OK I went into task manager and ended process and table was fine. However I did find a beta revision 4406 in my files and have confirmed that this allows compatibility from VP7 to VP6 without a problem. There's probably a later version that may work too, but for now I'll be using beta revision 4406 until this gets hopefully gets squared away.  Again, thank you!

 

 

1) DO NOT rely on the older betas.
I only meant for it as a last ditch effort to see if by any chance you could resurrect the the files that appeared to have gotten corrupted

2) POV changes, make all the POV changes you want, but do not save the table, instead click FILE > EXPORT > POV
and save it as tablename.POV
Then when you close the table, chose NOT to save the changes.
The POV will be used for the table, regardless of VPX version, and the POV will remain, even if the table is updated later, as long as you keep POV and table names the same

 

That will keep your table in original 10.6 form

Too many data structure changes, and data structure fixes from .6 to current .7

Editing one in .7 and loading it in .6 wont break anything, but the table will be a sterile white stanley kubrick looking table, it will run though

but allowing .6 to then save it again, is most likely to break the table as it does not understand the data structure it is looking at, plus it is going to write now fixed bugs back into it

and will probably corrupt the table entirely

 

If you accidentally do one, i have found that the older beta can in many cases return it to a .6 compatible table, as long as you do not let .6 do anything to the table before hand.
but i would not rely on doing that as there could be unforseen errors in doing so, i would not recommend making a habit of using the older beta exe's to flop back and forth except as a last ditch effort if an accident has happened

otherwise you may find next month that you have hundreds of heavily errored tables.

 

3) No images in editor only happens if you directly launch a table and then exit to editor
If you right click a table, and pick edit, you can go back and forth all day long from playing to editing and have the images shown

 

Myself, i much dislike the 10.6 layers
can not rename, stuck with a max of 11, can not show or hide individual objects, can not drag and drop between layers, and of course i can not put the layers panel over on a 2nd screen

 

Lastly "This" is not something that will be "squared away"

10.7 created or edited tables are not going to be backwards compatible with 10.7

Too much of the data structure has been fixed, changed, improved etc.
It is akin to trying to load XLSX files in MS Excel 97

It is an excel spread sheet, but it is no longer any kind of animal that excel 97 understands

 

Thank you for all your guidance and suggestions.  I'm going to stick with using the latest VP7 beta and not look back.  The more I thought about my reasons for switching back and forth the sillier I felt about it, but glad I did as you helped educate me on some things. Thank you again sir!!!

[chepas]

Bug deleting an empty layer? When a layer has no objects and you delete the layer, then it will delete another layer.

[toxie]

Is this new? codeview.SaveToStream. 

Save externally loaded .vbs script also to .vpx table?

The message while saving was pretty annoying after half an hour and it's always a No

 

Edit: Must be something to do with updating from 10.6. I think I had an external script window loaded somehow. A VP.7 table was loaded but the script was using 10.6 table.

 

This is new functionality with VPX10.7. If one uses the vbs side loading, then the external vbs is shown in the script editor, so the obvious thing on doing changes to the table is to ask if one wants to actually save the (script) changes to the table itself.