616 replies to this topic

[chepas]

Seems to do it on all tables.

https://www.dropbox....bv/noscript.jpg

[fuzzel]

Hmm that's new. Does it happen directly after you loaded the table or did you play the table or any other table before without closing VPX?

[GInsonic]

Seems to do it on all tables.

 

Could your script window eventually be located on another screen ? Then the behaviour is like that. Try to get all windows to your active screen (most multi monitor tools can do this using a hotkey combination).

Edited by GInsonic, 19 June 2017 - 08:40 AM.

[toxie]

True.. Sometimes one also accidentially can move windows out of all screens so that one cannot reach them anymore.. (see f.e. https://www.technipa...ck-onto-screen)

[chepas]

Whoa that was it, thanks. I still haven't had multiple displays hooked up yet but I may have by accident pushed windows + ArrowDown on the script window.

 

Actually if you do Windows + down on the editor window you kind of get the same result.

 

Maybe force the window to restore on click when hovered over in task bar.

[toxie]

on other news: we have crossed the 350(!) unique VPX table count (e.g. not counting the various MODs, etc), at least in my folder.. 

[Rajo Joey]

on other news: we have crossed the 350(!) unique VPX table count (e.g. not counting the various MODs, etc), at least in my folder.. 

350?

I have only 289 with mods. So I'm missing many tables and have to search for.

[Thalamus]

297 here ... hmm

[kiwiBri]

Hi,

I see in the release notes for VPX 10.3 there is mention of "Support for Pinscape" added.  Can anyone expand on this ? Wasn't Pinscape support added in v9.9 of VP ?

 

thanks

[toxie]

???

 

that one was just backported to the new PM5 build.. VP in general already has that in since 9.9.1..

[jpsalas]

I have been using the editor a lot recently and I find it very unstable, much more than it was before. It crashes much often than it used to do. I attach here the crash dump files:

 

 

The crash happened while I was editing the table. I was selecting a bumper and 3 primitives using the mouse, and as soon as I released the mouse button, then it crashed.
A few things give me some hints when something is wrong and I use to save the table and restart VPX. For example: When I change the light state in the editor to test it, the state doesn't change, I mean I choose blinking, but the editor reverts to offline. Another hint that something is going wrong happened when I was editing the materials, so I change some of them, run the table, then I went back to the materials and all of a sudden all the materials had the metal option on (?!) then I knew I had to quit Vp and run it again. These are what I recall now.

 

I'm not sure if the reason is Windows 10 or the editor itself, since I have moved to Windows 10 LTSB edition a few weeks ago. We got that version at work, and I thought to give it a try at home. I find this Win10 LTSB version quite stable, without apps, cortana, edge, windows store, it is like Win7 with a minimalist interface and it doesn't "attack" the disks as Win7 used to do.

 

Greetings
JP

 

PS: I really like this VPX, I still can make tables even if I haven't a clue about 3D modelling

[toxie]

Weird.. maybe Fuzzel must provide a debug build though, to be able to get more informations, cause the dump itself does not provide any hint.. :/

[toxie]

or here :

debug is a real debug build, but maybe you should start with the releasewithsymbols one first and try to get some dumps from that, please.. thanks!!

Edited by toxie, 23 June 2017 - 07:22 PM.

[jpsalas]

Thanks, I'll try releasewithsymbols first

[wrd1972]

I have been refreshing my Bride of Pinbot table and the editor crashes routinely. I really dont recall this issue back when the table was created in VP10.0 - maybe 10.1

 

But now I have to save like every minute or two or lose work. I believe its something with that specific table and we have not been able to find the root cause. Man its so freaking aggravating. But thankfully, the table play perfectly regardless.

 

There other tables that never crash the editor period. SO I am convinced that there is something in my table that just no longer plays nice with later VP10. If anyone wants the table for analysis to try to find the root casue, I can send it. That problem could likely be prevalent in other tables too. I would really love to see this table more stable in the editor.

[fuzzel]

You should use the releasewithsymbols build and try to reproduce the crash. Maybe we find the problem that way

[wrd1972]

Not sure i understand. Can you elaborate?

[fuzzel]

Simply use the exe Toxie posted above and load/run/edit your table with that version. If VPX crashes post the dump files so we can try to find the bug

[kiwi]

or here :

debug is a real debug build, but maybe you should start with the releasewithsymbols one first and try to get some dumps from that, please.. thanks!!

Does this debug build save dump files in Win XP?
Most crashes are due to the same reason JP said, a few minutes ago VP crashed, I save the table every time I make a rubber.

[fuzzel]

 

or here :

debug is a real debug build, but maybe you should start with the releasewithsymbols one first and try to get some dumps from that, please.. thanks!!

Does this debug build save dump files in Win XP?
Most crashes are due to the same reason JP said, a few minutes ago VP crashed, I save the table every time I make a rubber.

 

Not sure if WinXP supports that or if the crach dump system is compatible with such an outdated system. There seems a bug somewhere maybe it comes from the Win32++ conversion..