1622 replies to this topic

[mjr]

 

 

First things: The game type (SS/EM/ME) are not being displayed.

 

Are you looking in the "Information" box?  Main Menu -> Information.  It should be displayed there, under the "Manufacturer, Year" line.  If you were looking for it in the popup box that appears automatically, it's not meant to be there; I could add anything else there that people are interested in seeing, obviously, but just didn't want to over-clutter it.

 

The black info boxes for each table as you scroll through. I swear in earlier builds that was displayed? I feel it would be useful to have the initials right after the Manufacturer/Year. I'm still trying to slog through your highly complex source code along with learning Standard C++. Might get there by this time next year :-) Can you tell me what source file the variables and method(s) are for doing this? Application? Thanks!

 

That's in PinballY/PlayfieldView.cpp, PlayfieldView::SyncInfoBox().  And nope, the machine type has never been displayed there, just in the full info box that you can call up with the menu.  But it would be easy enough to add, the only issue being the aesthetics of whether less is more or more is more, which is certain a subjective judgement.  I think maybe the thing to do is add some options for what's in that box so that everyone can adjust it to their liking.

 

 

 

 

Are the high scores working?

 

They are for me.  If you're asking, I assume they're not for you - let me know what doesn't seem to be working.

 

Let me check the correct NV files are being referenced with the tables. Mine are not being displayed.

 

 

Yep, that's exactly the thing to check - the full info box (the one you call up through the menu) shows the NV file.

 

 

 

My videos are displayed upside down in attract mode. Is there something I can set to fix that?

 

Could you clarify what you mean by attract mode?

 

 

The main "wheel" menu where the videos or images are displayed as one cycles through. I've seen a lot of people call that attract mode, referencing real tables running their light shows to attract people passing by to play.

 

Okay, so basically all videos are upside down?  Is it all videos in all windows, playfield videos only, backglass windows only, some other combination?  How about still graphics?  And how about the other graphics, like the menus and such?

 

When you look at the source material (videos or stills) externally in a video/photo viewer, how are they oriented?  The canonical orientation is "sideways", with the bottom of the playfield at the left end of the screen.  If that doesn't look right, the capture must be creating them in the wrong orientation, otherwise they must be getting displayed in the wrong orientation - it would be good to know which it is to know where to look next.

 

(The reason I needed clarification is that I've been using "attract mode" to mean the screen saver-ish mode it goes into when you don't touch the controls for a while.  I didn't figure that's what you were talking about since there wouldn't be any technical reason the videos would look different in that mode, so I wanted to make sure we were talking about the same thing.)

Edited by mjr, 20 August 2018 - 08:34 PM.

[mjr]

PinballY is crashing right after it starts when I enable Auto or On for a real DMD.   I have a PinDMD3 and use it without issue in PBX, VPX, FX3, etc.      

 

It looks like the crash is happening down in the DLL, and looking at the stack trace you posted and the DLL source, it looks to me like a bug in the DLL.  I'll contact Freezy and see if he agrees.

 

As a workaround, the problem is due to colorization being turned on in your global settings.  If you turn that off, the crash should go away.

 

 

 Also,  Is there a way to disable DOF?  I am also getting an error with Failed to Initalize DOF Framework.

 

There's not; I could add that as an option, but if the reason you want to turn it off is the error, I'd very much rather fix whatever's causing the error.  Do you have any more information on the error from the message you're getting, and/or a DirectOutput.log file (which should be in the main PinballY install folder)?

Edited by mjr, 20 August 2018 - 06:21 PM.

[STV]

 

 

 

That's in PinballY/PlayfieldView.cpp, PlayfieldView::SyncInfoBox().  And nope, the machine type has never been displayed there, just in the full info box that you can call up with the menu.  But it would be easy enough to add, the only issue being the aesthetics of whether less is more or more is more, which is certain a subjective judgement.  I think maybe the thing to do is add some options for what's in that box so that everyone can adjust it to their liking.

 

 

 

 

YES!   I for example would love to see the filename.vpx right there without having to select 'information'.

[hlr53]

 

 

 

 

That's in PinballY/PlayfieldView.cpp, PlayfieldView::SyncInfoBox().  And nope, the machine type has never been displayed there, just in the full info box that you can call up with the menu.  But it would be easy enough to add, the only issue being the aesthetics of whether less is more or more is more, which is certain a subjective judgement.  I think maybe the thing to do is add some options for what's in that box so that everyone can adjust it to their liking.

 

 

 

 

YES!   I for example would love to see the filename.vpx right there without having to select 'information'.

 

 

If ya want to make it an option on showing EM, ME or SS that's cool but I would like to have it because sometimes there are certain types of games I like to play (Pre 1979) and it is helpful to have it there. I don't think having 2 letters next to the year is too obtrusive. My 2 cents :-)

 

PinballY is crashing right after it starts when I enable Auto or On for a real DMD.   I have a PinDMD3 and use it without issue in PBX, VPX, FX3, etc.      

 

It looks like the crash is happening down in the DLL, and looking at the stack trace you posted and the DLL source, it looks to me like a bug in the DLL.  I'll contact Freezy and see if he agrees.

 

As a workaround, the problem is due to colorization being turned on in your global settings.  If you turn that off, the crash should go away.

 

 

 Also,  Is there a way to disable DOF?  I am also getting an error with Failed to Initalize DOF Framework.

 

There's not; I could add that as an option, but if the reason you want to turn it off is the error, I'd very much rather fix whatever's causing the error.  Do you have any more information on the error from the message you're getting, and/or a DirectOutput.log file (which should be in the main PinballY install folder)?

 

 

I have a PinDMD3 and when I enable, PinballY pops up on the DMD. The DMD plays fine in my Future Pinball DMD games. Haven't tried VP games yet. I am not running the latest, is it  v1.7? I'd have to check my version. It has been a long time since I installed.

Edited by hlr53, 20 August 2018 - 10:10 PM.

[hlr53]

 

 

 

First things: The game type (SS/EM/ME) are not being displayed.

 

[snip]

 

[snip]

 

 

Are the high scores working?

 

They are for me.  If you're asking, I assume they're not for you - let me know what doesn't seem to be working.

 

Let me check the correct NV files are being referenced with the tables. Mine are not being displayed.

 

 

Yep, that's exactly the thing to check - the full info box (the one you call up through the menu) shows the NV file.

 

I have to do some more testing. It is still not being displayed. Pinemhi works at the command line and when I play a table its NV file high score is updated. I made sure Visual Pinball is pointing to the right directory and nvrom. I only had time to play with JP's Black Pyramid. Maybe I have something set wrong. Dunno? Recommend me a table you have and it's rom to check. Something SS.

 

 

My videos are displayed upside down in attract mode. Is there something I can set to fix that?

 

Could you clarify what you mean by attract mode?

 

The main "wheel" menu where the videos or images are displayed as one cycles through. I've seen a lot of people call that attract mode, referencing real tables running their light shows to attract people passing by to play.

 

Okay, so basically all videos are upside down?  Is it all videos in all windows, playfield videos only, backglass windows only, some other combination?  How about still graphics?  And how about the other graphics, like the menus and such?

 

When you look at the source material (videos or stills) externally in a video/photo viewer, how are they oriented?  The canonical orientation is "sideways", with the bottom of the playfield at the left end of the screen.  If that doesn't look right, the capture must be creating them in the wrong orientation, otherwise they must be getting displayed in the wrong orientation - it would be good to know which it is to know where to look next.

 

(The reason I needed clarification is that I've been using "attract mode" to mean the screen saver-ish mode it goes into when you don't touch the controls for a while.  I didn't figure that's what you were talking about since there wouldn't be any technical reason the videos would look different in that mode, so I wanted to make sure we were talking about the same thing.)

 

 

The image and videos are all oriented to the right outside of PBY. Now here is the strange thing. I was screwing around with flipping and rotating the display today. After getting PBY back to normal portrait mode I ran some video captures. The playfield images/videos are now right side up but the capture time remaining dialog box is upside down?  I have to mess with it some more. 2 monitors with primary in portrait with the second next to it on the right in landscape per Windows display settings.

 

Also, Future pinball captures now work after adding Future Pinball.exe to Process. Thanks!

 

Also, The Internet look up works. OPERATOR HEADSPACE at my end.

 

Sorry, my multi-quoting really sucks. I'm old. Don't judge me :-)

 

It is bad enough doing all this on a single thread.

Edited by hlr53, 20 August 2018 - 10:07 PM.

[mjr]

The image and videos are all oriented to the right outside of PBY. 

 

This is one of those cases where a picture is going to be worth literally 1000 words...  here's the "standard" orientation that all playfield media (Table Images, Table Videos) should have:

 

 

"Bottom of the table at the left side of the screen" is the way I describe this, but I know that can be read a few ways so hopefully the picture removes all doubt.

 

(All of the other windows (backglass, DMD, topper, instruction card) use the "normal" image orientation every other program in the world uses, with the bottom at the bottom.  The playfield is the only one with the sideways turn.)

 

It *sounds* like you're saying that your pictures are coming up in the opposite orientation, so that might be the source of all of the problems.

 

If you right-click on the playfield window, do you by chance have "Mirror Image" and/or "Flip Image" selected?  I'm thinking that maybe you "rotated" your playfield with those options instead of using the "Rotate" option.  If so, try this:

 

- Un-select both of those options

- Right click -> Rotate Display, repeat until it looks right

 

The capture process takes the rotation into account.  It doesn't take the mirror/flip into account.  The mirror/flip were meant for unusual situations where you're looking at the playfield in a mirror, not for ordinary monitor rotation.  Now that I think about it, the mirror/flip probably ought to be taken into account for the capture anyway, since ultimately you always want the same transformations (in reverse) for capture that apply to the image.  But if you could check your current settings, that might explain the weirdness with the inverted video and give you an immediate solution.

Sorry, my multi-quoting really sucks. I'm old. Don't judge me :-)

 

Heh, I totally judge the forum software.  You have no idea how much time I spend trying to wrestle it into the right format, and then half the time it still gets it wrong after I hit Post and I have to go back and edit it.

Edited by mjr, 20 August 2018 - 10:45 PM.

[martymoose]

Yeah, I can see why you’d take that as a PBY error message. But I’m just about sure it’s not. I don’t think it has anything to do with Pinscape, either. I think it’s coming from some other device entirely. Do you by chance have a DMD of some kind? I”m trying to think of what other device interactions could be triggered by bringing up the opyions dialog, and that’s the only one that comes to mind.

have a pintoodmd and pinscape and thats it

strange it works fine error only comes up after saving options in pinbally

i click close and it still plays fine

nothing in logs

Edited by martymoose, 20 August 2018 - 11:36 PM.

[hlr53]

 

The image and videos are all oriented to the right outside of PBY. 

 

This is one of those cases where a picture is going to be worth literally 1000 words...  here's the "standard" orientation that all playfield media (Table Images, Table Videos) should have:

 

 

"Bottom of the table at the left side of the screen" is the way I describe this, but I know that can be read a few ways so hopefully the picture removes all doubt.

 

(All of the other windows (backglass, DMD, topper, instruction card) use the "normal" image orientation every other program in the world uses, with the bottom at the bottom.  The playfield is the only one with the sideways turn.)

 

It *sounds* like you're saying that your pictures are coming up in the opposite orientation, so that might be the source of all of the problems.

 

If you right-click on the playfield window, do you by chance have "Mirror Image" and/or "Flip Image" selected?  I'm thinking that maybe you "rotated" your playfield with those options instead of using the "Rotate" option.  If so, try this:

 

- Un-select both of those options

- Right click -> Rotate Display, repeat until it looks right

 

The capture process takes the rotation into account.  It doesn't take the mirror/flip into account.  The mirror/flip were meant for unusual situations where you're looking at the playfield in a mirror, not for ordinary monitor rotation.  Now that I think about it, the mirror/flip probably ought to be taken into account for the capture anyway, since ultimately you always want the same transformations (in reverse) for capture that apply to the image.  But if you could check your current settings, that might explain the weirdness with the inverted video and give you an immediate solution.

 

OK, I did what you asked in bold and did another image/video capture. They were both definitely captured with the bottom of the table to the right side. They showed upside down in PBY. I rotated the image in the Media folder 180 deg and it displayed correctly in PBY.

 

I jacked so much around on the 32 bit I'm not sure where I am? Tomorrow I will install a fresh 64 bit and immediately try another capture and see what happens? All the time I have until after work tomorrow.

[mjr]

OK, I did what you asked in bold and did another image/video capture. They were both definitely captured with the bottom of the table to the right side. They showed upside down in PBY. I rotated the image in the Media folder 180 deg and it displayed correctly in PBY.

 

At least that narrows it down to the capture being the issue - it's just capturing with the wrong rotation, so naturally they're going to look wrong when displayed.

 

It might be 1000-word-picture time here.  If you could send me the following, I think I'll be able to sort out what's wrong - it could well just be the ffmpeg parameters I'm generating for your particular screen rotation.  Here's what would help:

 

#1 - a diagram showing your screen orientations like below

 

#2 - the following Settings.txt lines

 

    PlayfieldWindow.Rotation = ???

    PlayfieldWindow.MirrorHorz = ???

    PlayfieldWindow.MirrorVert = ???

 

#3 - the ffmpeg command line from the log file for a new capture (I know you've posted a couple before, but it would be good to do a fresh one just to make sure everything is using the exact current settings)

 

The diagram I'm looking for is a simple sketch showing your monitor orientations, with the Windows vs pinball orientations.  Something like this - hopefully this will make sense:

 

 

That should tell me what the rotation parameters all should look like, so I can compare them to what you have in your settings and what I'm generating based on that for ffmpeg.  I'm pretty sure something in there will explain it immediately once I can see all of the pieces.

 

 

I jacked so much around on the 32 bit I'm not sure where I am? Tomorrow I will install a fresh 64 bit and immediately try another capture and see what happens? 

 

If you ever want to declare Options Bankruptcy, it's super easy to reset to factory defaults.  Just delete Settings.txt in the main install folder.  All settings are stored in there, so deleting the will expunge all vestiges.

have a pintoodmd and pinscape and thats it

strange it works fine error only comes up after saving options in pinbally

i click close and it still plays fine

 

I think there's a 99% chance it's the DMD DLL.  Try this:  right-click on the playfield -> Real DMD -> Disable Always.  Or, equivalently, set the same option (Disable Always) on the Real DMD page of the options.  Now try going in and out of options and see what happens.

[tspeirs]

Sorry, please ignore this post.

Edited by tspeirs, 22 August 2018 - 05:05 PM.

[hlr53]

 

OK, I did what you asked in bold and did another image/video capture. They were both definitely captured with the bottom of the table to the right side. They showed upside down in PBY. I rotated the image in the Media folder 180 deg and it displayed correctly in PBY.

 

At least that narrows it down to the capture being the issue - it's just capturing with the wrong rotation, so naturally they're going to look wrong when displayed.

 

It might be 1000-word-picture time here.  If you could send me the following, I think I'll be able to sort out what's wrong - it could well just be the ffmpeg parameters I'm generating for your particular screen rotation.  Here's what would help:

 

#1 - a diagram showing your screen orientations like below

 

I'm remoting into the cab (RDP) because wife is on a conference call and took over basement (hate it when that happens).  In lieu of a diagram my orientations are for 2 monitors with a real DMD in between. Monitor 1 is always in Portrait Mode 1080x1920 and Monitor 2 is always in Landscape 1920x1080. Orientations like your sketch below except rotate the word Windows to face like Pinball in playfield box. In Windows Display Settings #2 is to the right side to #1. 

 

Started with fresh 32 bit Setting.txt and left all the PBY windows open this time except Topper and Instructions. I put the DMD and Backglass windows on monitor 2. Rotated PBY so it faced me in portrait mode on Monitor 1. That was all I did.

 

Playfield image/video still upside down in PBY and table bottom to right in standalone images/videos after these captures:

 

#2 - the following Settings.txt lines

 

    PlayfieldWindow.Rotation = -295,669,1005,1445 (that is minus 295)

    PlayfieldWindow.MirrorHorz = 0

    PlayfieldWindow.MirrorVert = 0

 

#3 - the ffmpeg command line from the log file for a new capture (I know you've posted a couple before, but it would be good to do a fresh one just to make sure everything is using the exact current settings)

 

Tuesday, August 21, 2018, 4:50:32 PM: Media capture: Capturing Playfield Image: launching FFMPEG
> "C:\PinballY\ffmpeg\ffmpeg.exe" -y -loglevel warning -probesize 30M -thread_queue_size 32  -f gdigrab -framerate 30 -offset_x 0 -offset_y 23 -video_size 1080x1857 -i desktop   -vf "transpose=2" -vframes 1  "C:\PinballY\Media\Visual Pinball X\Table Images\Cavaleiro Negro (Taito do Brasil, a division of Taito, Japan 1981).png"

 

+ FFMPEG completed: process exit code 0

 

Tuesday, August 21, 2018, 4:50:33 PM: Media capture: Capturing Playfield Video: launching FFMPEG
> "C:\PinballY\ffmpeg\ffmpeg.exe" -y -loglevel warning -probesize 30M -thread_queue_size 32  -f gdigrab -framerate 30 -offset_x 0 -offset_y 23 -video_size 1080x1857 -i desktop -f dshow -i audio="Stereo Mix (Realtek High Definition Audio)" -c:a aac -b:a 128k -vf "transpose=2" -t 30  "C:\PinballY\Media\Visual Pinball X\Table Videos\Cavaleiro Negro (Taito do Brasil, a division of Taito, Japan 1981).f4v"
Guessed Channel Layout for Input Stream #1.0 : stereo

 

Past duration 0.661842 too large
Past duration 0.737923 too large
Past duration 0.869118 too large
Past duration 0.977776 too large

+ FFMPEG completed: process exit code 0

Skipping audio capture but it ran OK

 

+ FFMPEG completed: process exit code 0

+ Media folder doesn't exist, creating it: C:\PinballY\Media\Visual Pinball X\Backglass Images

Tuesday, August 21, 2018, 4:51:36 PM: Media capture: Capturing Backglass Image: launching FFMPEG
> "C:\PinballY\ffmpeg\ffmpeg.exe" -y -loglevel warning -probesize 30M -thread_queue_size 32  -f gdigrab -framerate 30 -offset_x 1099 -offset_y 707 -video_size 1170x394 -i desktop    -vframes 1  "C:\PinballY\Media\Visual Pinball X\Backglass Images\Cavaleiro Negro (Taito do Brasil, a division of Taito, Japan 1981).png"

 

Backglass was oriented correctly but was scaled way too large for monitor. Didn't match the pinball B2S size.

 

+ Media folder doesn't exist, creating it: C:\PinballY\Media\Visual Pinball X\Backglass Images

Tuesday, August 21, 2018, 4:51:36 PM: Media capture: Capturing Backglass Image: launching FFMPEG
> "C:\PinballY\ffmpeg\ffmpeg.exe" -y -loglevel warning -probesize 30M -thread_queue_size 32  -f gdigrab -framerate 30 -offset_x 1099 -offset_y 707 -video_size 1170x394 -i desktop    -vframes 1  "C:\PinballY\Media\Visual Pinball X\Backglass Images\Cavaleiro Negro (Taito do Brasil, a division of Taito, Japan 1981).png"

+ FFMPEG completed: process exit code 0

+ Media folder doesn't exist, creating it: C:\PinballY\Media\Visual Pinball X\Backglass Videos

Tuesday, August 21, 2018, 4:51:36 PM: Media capture: Capturing Backglass Video: launching FFMPEG
> "C:\PinballY\ffmpeg\ffmpeg.exe" -y -loglevel warning -probesize 30M -thread_queue_size 32  -f gdigrab -framerate 30 -offset_x 1099 -offset_y 707 -video_size 1170x394 -i desktop -c:a none   -t 30  "C:\PinballY\Media\Visual Pinball X\Backglass Videos\Cavaleiro Negro (Taito do Brasil, a division of Taito, Japan 1981).f4v"
Past duration 0.950905 too large
Past duration 0.841179 too large
Past duration 0.853920 too large
Past duration 0.829445 too large

.

.

.

.

.

Past duration 0.869957 too large

+ FFMPEG completed: process exit code 0

 

Skipping DMD stuff

 

The diagram I'm looking for is a simple sketch showing your monitor orientations, with the Windows vs pinball orientations.  Something like this - hopefully this will make sense:

 

 

That should tell me what the rotation parameters all should look like, so I can compare them to what you have in your settings and what I'm generating based on that for ffmpeg.  I'm pretty sure something in there will explain it immediately once I can see all of the pieces.

 

If you ever want to declare Options Bankruptcy, it's super easy to reset to factory defaults.  Just delete Settings.txt in the main install folder.  All settings are stored in there, so deleting the will expunge all vestiges.

 

I keep forgetting I can nuke Settings.

 

What is Past duration 0.xxxx too large mean?

Edited by hlr53, 21 August 2018 - 09:42 PM.

[mjr]

 

In lieu of a diagram my orientations are for 2 monitors with a real DMD in between. Monitor 1 is always in Portrait Mode 1080x1920 and Monitor 2 is always in Landscape 1920x1080. Orientations like your sketch below except rotate the word Windows to face like Pinball in playfield box. In Windows Display Settings #2 is to the right side to #1. 

 

I think I tracked it down - your orientation is what I expected based on what I found in the code.  For that situation it was doing the rotation backwards, thus the upside-down display.  I think it should be fixed now (in the new Alpha 13).

 

 

 

Backglass was oriented correctly but was scaled way too large for monitor. Didn't match the pinball B2S size.

 

I assume you have the PBY backglass window covering the same monitor area as the B2S window?  It sizes the video area based on that.  Does 1170x394 sound like the right window size for that?  It looks suspicious to me.  That's the size of the capture area in the log you posted.  What does this line in your settings files say?:

 

BackglassWindow.Position = ...

 

 

 

What is Past duration 0.xxxx too large mean?

 

You're guess is as good as mine.  It's coming from ffmpeg, and it's just a warning.  How can you tell it's just a warning?  Because it wasn't an error.  If it had been an error, the whole capture would have failed.  My experience with ffmpeg is that it generates a ton of these things on any nontrivial encoding work, and that they can essentially always be ignored if the overall encoding job finishes successfully.  Some warnings probably affect the encoding quality in a more or less subtle way, but not so that I've ever noticed; when it rises to the point of being noticeable, it rises to the level of being an outright error, which will make ffmpeg abandon the encoding job and bomb out with a failure message.  PBY detects when that happens and shows you a "capture failed" status in the final results.

 

(The exception is that ffmpeg sometimes generates advisory warnings saying something like "random parameter foo is too small, you need to increase it with -random_parameter_foo", and those are sometimes useful.  It might be worth monitoring your captures until things look reliable, and if you see anything like that, let me know and I can add it.  The other time to pay attention to the warnings is if you do a capture that nominally succeeds but has quality problems on playback.  If that happens, you can go back, redo the capture, and make a point of figuring out what the warnings are trying to say.  There might be something in there on this occasion that explains the quality problem.  But I haven't really had that come up in practice; even when it's generating lots of warnings, ffmpeg usually seems to manage to come up with a decent result.)

 

 

 

I keep forgetting I can nuke Settings.

 

Yeah, I know I'm throwing everyone for a loop by not conforming to standard Windows coding practices and scattering settings over every hidey-hole of the registry and file system.  Sorry about that.

Edited by mjr, 21 August 2018 - 10:28 PM.

[hlr53]

 

 

In lieu of a diagram my orientations are for 2 monitors with a real DMD in between. Monitor 1 is always in Portrait Mode 1080x1920 and Monitor 2 is always in Landscape 1920x1080. Orientations like your sketch below except rotate the word Windows to face like Pinball in playfield box. In Windows Display Settings #2 is to the right side to #1. 

 

I think I tracked it down - your orientation is what I expected based on what I found in the code.  For that situation it was doing the rotation backwards, thus the upside-down display.  I think it should be fixed now (in the new Alpha 13).

 

 

 

Backglass was oriented correctly but was scaled way too large for monitor. Didn't match the pinball B2S size.

 

I assume you have the PBY backglass window covering the same monitor area as the B2S window?  It sizes the video area based on that.  Does 1170x394 sound like the right window size for that?  It looks suspicious to me.  That's the size of the capture area in the log you posted.  What does this line in your settings files say?:

 

BackglassWindow.Position = …1091,676,2277,1109

 

Come to think of it I didn't fit it to the monitor. Too concentrated on playfield.  I'll check that tomorrow. 

 

Yeah, I know I'm throwing everyone for a loop by not conforming to standard Windows coding practices and scattering settings over every hidey-hole of the registry and file system.  Sorry about that.

 

Yeah, like what kind of programming practice is that?   

 

Down the road are you going to add a batch mode for captures? 

 

Next for me is PINemHi as it doesn't appear to be working but I have to investigate across both systems before posting.....

Edited by hlr53, 21 August 2018 - 11:17 PM.

[mjr]

Down the road are you going to add a batch mode for captures? 

 

Seems like it would be nice to have, so yeah, definitely something to add once the basic capture is solid.  It shouldn't be much of a stretch to automate it across multiple tables, since that's just a matter of iterating what it's already doing per table.  The main addition would probably be a UI to select the tables to include in the batch.

[Tempest43528]

 Also,  Is there a way to disable DOF?  I am also getting an error with Failed to Initalize DOF Framework.

 

There's not; I could add that as an option, but if the reason you want to turn it off is the error, I'd very much rather fix whatever's causing the error.  Do you have any more information on the error from the message you're getting, and/or a DirectOutput.log file (which should be in the main PinballY install folder)?

 

 

I do not haved DOFLinx installed so there is no DirectOutput.log created.  That is why I was wondering why I would get the DirectOutput errors

[Tempest43528]

@mjr - I was able to fix the directoutput error.     I do not have DofLinx installed but there was a old registry key still there that was pointing to the DOF Com object.   I nuked the registry key and the error went away.      

 

 

Great looking work so far,  now that I am passed that hope to really check PinballY out.      Hopefully the PinDMDV3 coloroization issue is an easy fix for Freezy.

[mjr]

@mjr - I was able to fix the directoutput error.     I do not have DofLinx installed but there was a old registry key still there that was pointing to the DOF Com object.   I nuked the registry key and the error went away.      

 

Great!  I wouldn't have thought of that.  There's always some new trick to figure out with DOF...

 

 

Great looking work so far,  now that I am passed that hope to really check PinballY out.      Hopefully the PinDMDV3 coloroization issue is an easy fix for Freezy.

 

I added a small change to the Alpha 13 that I'm hoping will work around the problem, without the need to turn off colorization globally.   But if that still doesn't fix it, it should work for now to turn off colorization in the dmd-extensions.ini file.  I filed the dmd-extensions issue on github (https://github.com/f...ions/issues/125) but Freezy hasn't responded to it yet.

[bord]

I will have specific feedback eventually but want to chime in quick and let you know I've been using this for the last few weeks. Love where it is going. Keep up the good work!

[STV]

"Me too".    I've left the "X" behind completely at this point.   Thanks mjr!

[Tempest43528]

 

@mjr - I was able to fix the directoutput error.     I do not have DofLinx installed but there was a old registry key still there that was pointing to the DOF Com object.   I nuked the registry key and the error went away.      

 

Great!  I wouldn't have thought of that.  There's always some new trick to figure out with DOF...

 

 

Great looking work so far,  now that I am passed that hope to really check PinballY out.      Hopefully the PinDMDV3 coloroization issue is an easy fix for Freezy.

 

I added a small change to the Alpha 13 that I'm hoping will work around the problem, without the need to turn off colorization globally.   But if that still doesn't fix it, it should work for now to turn off colorization in the dmd-extensions.ini file.  I filed the dmd-extensions issue on github (https://github.com/f...ions/issues/125) but Freezy hasn't responded to it yet.

 

 

Same error persists using Alpha 13 release.    I will disable color tonight and see if that gets things working.    I saw the fix request on GitHub.  Thanks!