868 replies to this topic

[fuzzel]

 

Here's a crash dump from 2505:
 
crash.txt
https://dl.dropboxus...62327/crash.txt
 
crash.dmp
https://dl.dropboxus...62327/crash.dmp
 
I was working on a GI light on Sinbad when it happened.
 
 
Best Regards,
Kruge99.

Thanks. I have added some checks to the next version to hopefully prevent this from happen again but the crash dump wasn't that clear so it's more guessing than real fixing
 

 
Is it related to the crash.txt (without the dump file that I reported but missed previously?)  or is it a different crash because I didn't get the same error message this time.
 
Best Regards,
Kruge99.

The crash dump helped but what I saw in there was a bit strange and didn't point to a simple mistake in the code. So I had to guess what went wrong and I fixed some possible wreak spots in the code.

Oooookay!
 
I 100% figured out what what causing that error message while loading a table
mentioned in my previous post.
 
It was the new (and awesome) ball image override setting in the video options.
I had originally chosen an image and then changed my mind later.
To remove the image I just selected / deleted the path in the box.
 
Apparently it did not like that.
 
I put the image back in, bam. All is right in the world.
It was definitely this that caused the error.
I've removed the image, error message again, put it back, fixed.
 
When you delete the path from the box and close VPX, the next time you open it
check the box again, there will now be some strange unicode in there. 
 
Am I just overlooking a proper way to remove an image path from there 
and have been doing it wrong?

Oh thanks for the investigation. Indeed there is a bug in the code and I'm going to fix it asap

[kruge99]

OK fuzzel here's another crash dump.  It happened after working on the script for Sinbad and I tried to close a VP9 table I had open to compare the script with.  It may be the same problem with 2505 so I hope this helps track it down.  After this I'll stop submitting them until you put out a new version.

 

https://dl.dropboxus...62327/crash.dmp

 

https://dl.dropboxus...62327/crash.txt

 

 

Best Regards,

Kruge99.

[fuzzel]

Oh one known issue is that you shouldn't have VPX and VP9 running at the same time. If you do that you will get strange UI behavior or crashes.

[allknowing2012]

Anyone finding the new editor to be a problem? Could that be triggering crashes? It starts actiing funny for me all the time. Highlighting weird portions and not allowing inserts/deletes. Crashing all the time ..

[fuzzel]

Yes the script editor has some issues and I hope brandrew can fix them.

[kruge99]

Oh one known issue is that you shouldn't have VPX and VP9 running at the same time. If you do that you will get strange UI behavior or crashes.

 

Sorry, to be clear, I only had VPX open and using it to view the script of a VP9 table.  So what I had was VPX running, opened a VPX table (Sinbad WIP) and a short time later I opened a VP9 table to look at the script.  When I attempted to close the VP9 table, VPX crashed.

[chepas]

Fuzzel , this: import/export physics settings in xml format

 

It can be used as the table is loading or anytime before editor? You can specify which xml to load?

 

Will it possible at any time for some collections, more importantly like walls-ramps-rubbers?

 

Would only really want the friction/elastic/scatter/falloff values and would be up to author to make sure the collection is consistent with one type of object.

 

rubbers.xml, rubbers2.xml, walls.xml

 

Dreaming?

[fuzzel]

Fuzzel , this: import/export physics settings in xml format

 

It can be used as the table is loading or anytime before editor? You can specify which xml to load?

 

Will it possible at any time for some collections, more importantly like walls-ramps-rubbers?

 

Would only really want the friction/elastic/scatter/falloff values and would be up to author to make sure the collection is consistent with one type of object.

 

rubbers.xml, rubbers2.xml, walls.xml

 

Dreaming?

the physics settings are the ones Toxie added in VP9 at some time. Where you can define a couple of different physics settings for flippers and playfield. These settings were saved in a simple text file and I would like to align that to use the same format I used for the POV import/export thing. You can use that at any time even if no table is loaded. The idea is to have a kind of a library for differen flipper/playfield types and you can overwrite the table defines ones.

 

The other settings for walls/rubbers and so on isn't a big deal but what is the benefit of having such feature?

[chepas]

At times it would be convenient to edit some common physics values outside of VP. Like presets that could be thrown in and override the current collections values.

 

When adjusting/testing physics, you could change your values outside, run table & exit without touching the editor.

 

Also I think it would help towards anti-cheat if these values could be forced.

[fuzzel]

hmm good point...I'll take a look later.

[chepas]

Awesome, no rush...I am late to trying this build as it is.

[fuzzel]

rev2513 is up:

 

- add sorting to material, sound, image and collection manager (by clicking in the column header)
- import/export physics settings in xml format (under Preferences->Physics Options)

- fix bug when nothing was entered in overwrite ball image dialog under Preferences->Video Options)

- add some checks to prevent crashing reported by kruge99

- add new platforms (vbs scripts ironballs.vbs and mac.vbs, core.vbs has changed too)
 

Edited by fuzzel, 19 February 2016 - 08:56 PM.

[chepas]

Dunno if you forgot to add the extension on export physics? It's ok to save "filename.xml" but for importing?

[fuzzel]

The extension is vpp that's the default but you can use xml as extension as well. You have to enter *.xml in the filename text field. But I have to admit a switch for filtering all files and not only *.vpp files would be nice. I don't want to name all files with a xml ending because someone could get confused and when you load a wrong one strange things can happen

Edited by fuzzel, 19 February 2016 - 09:36 PM.

[ClarkKent]

It would be nice if copy, past and delete would be in the context menu, too. And it would be nice if rotate, scale, etc. would be in the edit menu, too.

[chepas]

The extension is vpp that's the default but you can use xml as extension as well. You have to enter *.xml in the filename text field. But I have to admit a switch for filtering all files and not only *.vpp files would be nice. I don't want to name all files with a xml ending because someone could get confused and when you load a wrong one strange things can happen

 

Yeah I got it eventually. I built VP earlier, but when I couldn't see the options there either, I thought it can't be in yet still

[RYSr]

The extension is vpp that's the default but you can use xml as extension as well. You have to enter *.xml in the filename text field. But I have to admit a switch for filtering all files and not only *.vpp files would be nice. I don't want to name all files with a xml ending because someone could get confused and when you load a wrong one strange things can happen

 

Will the old .vpp files saved in previous versions still work?

Are any new physics settings added to this change?

Rich

[kiwi]

If it were possible to have a smooth transition of the ball in the kicker, with the box "Fall through" selected.

 

Thanks

 

Max

[fuzzel]

The extension is vpp that's the default but you can use xml as extension as well. You have to enter *.xml in the filename text field. But I have to admit a switch for filtering all files and not only *.vpp files would be nice. I don't want to name all files with a xml ending because someone could get confused and when you load a wrong one strange things can happen

 
Will the old .vpp files saved in previous versions still work?
Are any new physics settings added to this change?
Rich

No the format has changed you have to export them again and no other settings were added.

[toxie]

Just hold back a bit, as i will add some more of the currently not exposed parameters.

 

btw: Its now also possible to use the 64bit build in the same dir as the 32bit build, as i finally found a sane/convenient way to allow for renaming the dlls.