335 replies to this topic

[darquayle]

Gauntletlover,

 

Excellent job.  My five troublesome tables are all now working perfectly.  I also like what you've done with the automated exiting routine.  It has worked correctly on all of the tables I've tested.  Also, I've only tried a couple of color changes and they too seem to be working great.  This really makes a huge difference on cabs with three monitors. 

 

THANKS!

[gauntletlover]

That's sounds like whats happening Open6l , If you manually launch, the dmd doesn't know what table you have loaded. You need to pass it the table name with your front end

table="%tableName%"

 

or on the command line c:\(your path) Future Pinball.exe table="Tron Legacy" close=1

 

Bruins or Blackhawks?

 

@Darquayle, no problem, that's great to hear!

[open6l]

LEAFS!!!!! but actually in this case the Hawks... can't stand the Bruins.

 

Edit - Yeah I figured once you posted whether I was using Hyperpin and I looked at the syntax and realized what has happening (or rather not).

Edited by open6l, 20 June 2013 - 01:37 AM.

[ClarkKent]

Transformers does not show a DMD via FutureDMD at all. Stays dark.

[gauntletlover]

Hey ClarkKent, It only supports 128X32 displays. If you edit the table and resize the 128X16 dmd to 128X32 dmd it will work.

[ClarkKent]

OK, thank you! Would this be an option for a future release of FutureDMD to include an option for auto-resize?

[gauntletlover]

At this point I have no plans to look at other sized dmd's. But I won't say no for sure

[ClarkKent]

Nevertheless FutureDMD is working THAT well that it's even more fun now to use Future Pinball on a cab!

 

Thanx for releasing this gem!

[MagicPinball68]

@gountletlover

Finally i had time to test. When correctly started thru hyperpin, everithing is now working perfect for me. WOW! Thank you again so much for this fantastic DMD programm. I love it, and gives my cab what i have so long waiting for.

[ClarkKent]

I only noticed some flickering at some animations of STTNG (looks like the ending of some animation is mixed with the beginning of the next one), no other problems until now.

 

Would be interesting if older tables with LEDs could also be somehow redirected to the FutureDMD in one of the next versions? Redirectling LEDs should use the same technique, shouldn't it? Would be just great to also have LED support so that ALL tables would have a full screen backglass and a separate DMD/LED display...

Edited by ClarkKent, 26 June 2013 - 07:47 AM.

[Ashlon]

I am also getting the (All Pipe Instances Are Busy) when I try to start Future DMD.I can run FP without crashes, I just keep getting that same error message.Future DMD does work for me on my other PC that has 1 monitor.

[aupton]

I noticed that BigBangBar won't draw to FutureDMD v1. I checked and the DMD and it is correctly set to 128x32. Is anyone else experiencing the same ?

[ndz]

Am I the only one getting major ball stutter once this is running?  FP runs smoothly otherwise.

 

Specs:

Win XP SP3

core i3 3.3Ghz, 4GB ram

Nvidia GTX 550ti driving two monitors

USB to VGA for 3rd screen DMD

[gauntletlover]

Ashlon, sorry I am having trouble reproducing that error without running multiple instances of the program (which you can't do), I will do my best to fix it up if I can find it.

Aupton. I am running Big Bang Bar without issue? What version are you running? I will try it on my Cabinet.

ndz: no studder here but I am using an i5 (don't know speed off hand) with Nvidia GTX 660ti running all 3 monitors through hdmi/dvi with the newest drivers. And just out of curiosity are you Mel Gibson?

[aupton]

@gauntletlover - Thanks for the reply, I'm using "BigBangBar PHYSICS 2.5" from "pinsimdb.o*g/pinball/table-5237-bigbangbar" (Sorry for the malformed URL, I hear that there are some rather childish rules about posting links to other sources around these parts)

 

 

@ndz: I'm using an old AMD Dual Core Opteron which is older than an Intel i3 without much impact on performance, if any. I'm using a Geforce 560 on Windows 7 x64 for the play field and backglass and a older geforce 6800 for the VGA DMD. If you aren't already, try to run each screen at their "native" resolution, I noticed that improved performance significantly on all screens. For example, I can drive 1900x1200 on my backglass screen, but the native resolution of it is 1366x768. There's no benefit to driving the screen at a higher resolution since the backglass images don't benefit from it and going higher only increases the CPU and GPU processing demand. So with that said, try that on your USB based VGA interface. You may be driving a high resolution that's saturating the performance of the USB bus.

[ndz]

ndz: no studder here but I am using an i5 (don't know speed off hand) with Nvidia GTX 660ti running all 3 monitors through hdmi/dvi with the newest drivers. And just out of curiosity are you Mel Gibson?

 

CPU stays around 60% utilized with FPDMD on or off so that's not it.  A friend with similar specs has the same issue.

 

Is anyone having success (no stutter) with these:

- Windows XP

- Nvidia 270.61 driver

 

Me Mel?  Nah, but thanks for the compliment.....    mate.

[Ashlon]

When you said multiple instances that made me think because the first time I try to open futuredmd nothing happens ,so I wait a few seconds try again and then I get the error.Do you know anything I can try for toubleshooting?

[aupton]

@Ashlon - If you have any antivirus software enabled, try to disable it prior to running FutureDMD to see if that resolves the problem. I've read reports of Norton AV causing that same error message for other applications.

[gauntletlover]

@Aupton

 

I just tried that version Big Bang Bar. It loads 2 dmd's at 128x32 but only DispDmd1 is sent any data through the script. Make sure the dmd you left at 128X32 is the one named DispDmd1 not the one named DispDmd12. Or for sake of clean up you can just delete the one named "DispDmd12" because the script never tries to call it and there is no need for it on the table.

[gauntletlover]

@Ashlon

 

What version of Windows are you running? How are you opening FutureDMD? (double clicking, windows start up or through a front end?) If you are using a front end can you post the script you are using to load and unload futuredmd. FutureDMD opens a pipe when it starts up and if not closed properly Windows may not be terminating the pipe. The second time you open, it can't create the new pipe because it is already open. Can you elaborate on "first time I try to open futuredmd nothing happens" Have you had it running some tables, or you have never had any tables working because of the error? When you start it do you see the drawn pixels in the off state or does it not open at all? Any details you can think of may help me re-create it.

 

Thanks

 

 

I almost forgot, If Aupton's solution solved it for you, please let me know so I can let anyone else know that has this issue.

Edited by gauntletlover, 29 June 2013 - 01:09 AM.