Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider becoming a contibuting member by either clicking this text or the Patreon link on the right.

Patreon

If neither of those of work for you, you can donate any amount by clicking here.

doogie2301

Basic Member
  • Posts

    19
  • Joined

Recent Profile Visitors

612 profile views

doogie2301's Achievements

Advanced Member

Advanced Member (2/5)

2

Reputation

  1. Does anyone know if this feature (random play of launch files) was implemented?
  2. For some reason this doesn't work for me, even with Show DMD set to Hidden. It seems like as soon as I launch the table from PinballX it blanks out the DMD immediately, even before the table and backglass are loaded. I have a PinDMDv3, so maybe it doesn't work the same way as PIN2DMD?
  3. Do you know if this is supposed to work with Real DMD images too? Even if I have Hide DMD unchecked, the image goes away once the game launches.
  4. OK I take that back, I haven't been able to reproduce the issue lately. I'm running all the latest beta versions of everything now (vpx, b2s, etc.), so maybe something got fixed.
  5. I can confirm the same issue. For some reason under certain circumstances the B2S server is not detecting the VPX process properly to get the table name to use when searching for the directb2s file. Not sure if it's a timing issue or what, but it only happens on certain tables, when running B2S server in EXE mode, VPX in fullscreen mode, and launching the table from PinballX.
  6. OK I just tested it again, it does appear to be fixed now, thanks.
  7. Tom, did you ever get a chance to look at this issue? Thanks.
  8. Try turning off "Auto Position DirectB2S" in Display Settings
  9. Update: The bug in VPM is being corrected, and I created a separate thread regarding the Shutdown bug in PinballX, so this thread can be closed.
  10. Verified both issues fixed, thanks.
  11. I seem to be having some issues with the latest version of the Game Manager. The ROM setting on all the games got wiped out somehow, and when I try to add them back, they seem to randomly get cleared again. It appears to happen when I change more than one at a time, and then save the list. Also trying to import media packs now gives an error (screenshot attached). See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.InvalidCastException: Unable to cast object of type 'System.Windows.Forms.VScrollBar' to type 'Game_Manager.UserControl1'. at Game_Manager.Form1.cmdImport_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8689 (QFE.050727-8600) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- Game Manager Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/PinballX/Game%20Manager.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.8670 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8690 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8670 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8681 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8670 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- Interop.VPinMAMELib Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/PinballX/Interop.VPinMAMELib.DLL ---------------------------------------- System.Web Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8670 (QFE.050727-8600) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
  12. Does anyone have "Real DMD Color Videos" for the FX2 tables, or know how to convert from DMD Videos?
  13. When the PinballX setting "Use PinMAME in Front End" is set to 'Yes', PinballX changes the VPinMAME setting "Use Sound" for a particular ROM while viewing the table in the front-end. It does this so the ROM sounds will not be heard in attract mode, and then it turns it back on when you launch the table, browse away from the table, or exit PinballX. I have provided evidence of this in a screenshot from Process Monitor, where you can see the registry value being set by PinballX. The bug is that the sound is not turned back on when choosing Shutdown from the PinballX menu, so the last table displayed will have the sound turned off permanently.
  14. I'm not so sure that it does function as expected. As an end user, I would expect if "Use Sound" is disabled, there should be no sound, regardless of the type of sounds that are configured. Sorry, I'm not familiar with vPinMAMELauncher, is that what PinballX uses to display the PinMAME DMD? Anyway, I do like this feature because I don't have to worry about recording or downloading videos, it will show the current high scores, and it just looks really good on a real color DMD. I don't mind the second or two for the ROM to boot up.
  15. OK then for #3 I will take it up with PinMAME to begin with, and determine if that was the intended behavior. What about for #2? What is the procedure for officially reporting this as a bug in PinballX?
×
×
  • Create New...