3889 replies to this topic

[dark]

A basic version of something like this perhaps?

[gtxjoe]

Fading light object.  Is there a way to read the current intensity of the light?  Not the state of the light, but how bright it is currently, sort of like reading the flasher Opacity value

Edited by gtxjoe, 28 March 2015 - 04:52 PM.

[fuzzel]

You can use the IntesityScale for that.

A basic version of something like this perhaps?

Yes something like that. The only reason why it's not already in VP is that I don't have much time at the moment and I have to figure out how to add this into the current architecture.

[fuzzel]

rev1884 is up:

 

- add crash report and dump handling
- invert ctrl+mouse wheel zoom handling
- fix floating property window shrinks if you click on multiple objects
 

regarding the crash report: If VP crashes it tries to create a dump (crash.dmp) and a report (crash.txt) pack these files together and post them here. I hope we can find bugs like in Nascar much faster with this.

[chepas]

Does the crash dump work when it crashes before the VP Player screen?

[fuzzel]

That shouldn't matter because the crash report behavior is global for the whole application. Let's see how that works out

[chepas]

Motu crashes on launch in later versions of vpinballx. Had just tried it then, but no crash dump.

[Sindbad]

Okay, I just installed the newest beta and re-produced the crash in Nascar. Where should I look for the crash report?

[fuzzel]

it should be in the same folder where you have the VP exe. I don't know yet but maybe there is no crash dump if some other dll, like vpinmame or b2s crashes. I just tested the dumping feature by forcing VP to crash at certain points at I always got a crash dump.

Edited by fuzzel, 28 March 2015 - 10:37 PM.

[chepas]

The MOTU is using no controllers (pinmame, b2s) and no crash dump for that here.

[fuzzel]

Hmm strange but that crash is a bug in the collection group rendering introduced somewhere around rev1880.

[Sindbad]

Sorry,

 

no dump here. I'll check the system messages to see which module crashed.

 

Edit:

 

This is what I found in the system message journal (Sorry for the German, but you are firm with this language)

 

Name der fehlerhaften Anwendung: vpinballx.exe, Version: 10.0.0.0, Zeitstempel: 0x55170ce1
Name des fehlerhaften Moduls: vpinballx.exe, Version: 10.0.0.0, Zeitstempel: 0x55170ce1
Ausnahmecode: 0x40000015
Fehleroffset: 0x000e97a4
ID des fehlerhaften Prozesses: 0x61c
Startzeit der fehlerhaften Anwendung: 0x01d0699c9f80e00e

Edited by Sindbad, 28 March 2015 - 11:06 PM.

[fuzzel]

ok it seems the crash report stuff only works for really hard errors, like null pointers. Thanks for tests

[Sindbad]

Is the entry in the system journal helpful? It shows the offset where the problem occured. Can you compare that with the compile log?

 

Edit:

 

I compared all entries, the offset is always the same, so it seems it crashes always at the same code.

Edited by Sindbad, 28 March 2015 - 11:17 PM.

[fuzzel]

I can give it a try

[toxie]

I think i got it.. 

Some more testing needed though to see if its really the issue..

[chepas]

VPT/VPX 7z "TableInfo" extraction:

 

I'm about ready to give this a try again and will probably result to using the 7z.exe on commandline. (somehow)

 

The only way I can think of at the moment is to rename the tables extension first, extract info , rename back. Could be a slow process for all tables but should work.

 

Any easier way to get access to the table info outside of the editor?

 

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

Edited by chepas, 30 March 2015 - 05:29 PM.

[fuzzel]

@chepas: why you need to rename the file extension? 7z should eat all files as long as the file header is the right one.

 

@all: If VP crashes for you take a look for a crash.dmp file in that folder where you loaded the table. I thought it was the folder where the exe is copied but it's actually the folder where you loaded the table for playing

Edited by fuzzel, 30 March 2015 - 07:01 PM.

[chepas]

There is the crash dump in my MOTU folder! Lol , thanks!

 

http://pastebin.com/kMzzrGVf

 

If you check the picture I posted it was directly from a .vpt and not renamed.

 

Anyway, i can extract through the 7z GUI so I can get to it one way or the other.

7z.exe x Table.vpt -0c:\TableInfo TableInfo

7z.exe x Table.vpt -0c:\TableInfo GameStg\GameData

First command pulls the info and second is for script. Kicking myself not doing this ages ago!

 

The crash .dmp is 300mb!?

Edited by chepas, 30 March 2015 - 08:00 PM.

[fuzzel]

rev1893 is up:

 

- fix MOTU crash

- fix JP-Nascar crash (hopefully)

 

 

@chepas: yes the crash dump is always big because the whole process is dumped (dlls, data and so on). With this crash dump we can try to find the root cause of a crash because it's somewhat debuggable.