335 replies to this topic

[gogo69]

max's error message is called : All Pipe Instances Are Busy

Edited by gogo69, 13 June 2013 - 06:14 AM.

[max37170]

Thanks gauntletlover and gogo69,

 

i´ve done some more tests. After i ran "futuredmd" the "future pinball.exe" crashes all the time, still without futuredmd.

The error report said its the ntdll.dll.

I´ve done a complete deinstallation with registrycleaning, and after that  a new installation and future pinball works fine, without any errors - until i run futuredmd.

Same errors as before, same procedure as before. A clean new installation of future pinball solves the problem.

 

I´m sad - futuredmd doesn´t work for me. I hope gauntletlover finds a solution.

 

max

[gauntletlover]

Thanks gogo,

 

Max

 

I haven't heard of this one yet. Is it happening only on a specific table while you load the table? Everytime you run Future Pinball.exe (without a table)? When you say "until I run futuredmd" do you mean everything works until you copy the files into the new future pinball directory and then run? I'm trying to find where to start looking. The Dmd is seperate from the dll capturing the data for it. Neither writes to the registry so you shouldn't have to clean the registry or reinstall future pinball. No files are modified. I suspect it is the openGL.dll causing the issue. It uses pipes to communicate with the dmd part. If you try it again and you receive an error. Try taking the opengl.dll out of the directory and try to run Future pinball again. It should start back up without re-installing. Almost forgot to ask, how are you starting the app? before loading future pin, after future pin or with a script?

 

The ntdll.dll is a Windows file. It can report numerous types of errors or could be corrupt itself. If I can find a way to re-create what is happening I will patch it up.

 

Thanks for any info.

 

 

One last thought. have you re-booted at all? If the program terminated unexpectly and didn't finish properly it could have left a pipe open which is now locked. A simple re-boot will remove the pipe.

Edited by gauntletlover, 13 June 2013 - 05:03 PM.

[max37170]

Hi again Gauntletlover thanks for your advice,

 

Here is my procedure:

1. Load and run FutureDMD - the requester "All Pipe Instances Are Busy" is popping up - i quit this with ok

2. Run Future Pinball - nothing unexpected happened

3. Load a Table (doesn´t matter witch one) - all seems normal

4. Hit "Play" - Future Pinball.exe crashes, the black FutureDMD-Window is right in position until i quit it

 

And from now on Future Pinball crashes every time til i hit play and it doesn´t matter if futuredmd is running or not.

But on the second try of starting FutureDMD and Future Pinball the requester "All Pipe Instances Are Busy" doesn´t pop up.

 

With your new information i removed the opengl32.dll - and you are right, Future Pinball starts normal without a new installation.

Now i´m ready to try a lot of more things with futuredmd.

 

thanks a lot

max

[open6l]

gauntletlover: for the tables that are not working for you (but work for me) try doing what I am doing. Launch BAM and run the tables through BAM. My BAM fploader executable has been renamed to Future Pinball.exe in the BAM folder and I launch that. As I mentioned earlier all those tables that crash for you run for me this way (Avatar, Goonies, Indy, Jurassic Park).

 

Hold tight guys I'm working on a few updates that will change how some things are done based off all of the great feedback I've received from everyone, I will put out version 1 soon and I will include instructions for hyperpin ahk. I have added a shutdown flag as well that will close fp after the table closes (thanks magic), customized colors are ready to go via ini files for each table or a default ini if no custom settings are available. Sparky, as far as I know you shouldn't have any problem installing the 3.5 run-times with 4 installed.

 

I am currently trying to track down a bug causing some tables to crash so bare with me. And sorry max, I don't speak german either :/

 

If you have tables crashing right at the end of the load screen please let me know which ones and what you are running on your system. It could help me track it down a little quicker... Thanks everyone.

[gauntletlover]

Thanks Open6l. You have definitely helped me, but maybe not how you intended . When you use Bam you aren't seeing the whole picture. FP sends out two layers for every frame.  A font layer and an image layer. When you use bam for some reason, futuredmd isn't getting the image layer. You may be getting some graphical display because one technique for animating is to make custom fonts of multiple images and then run them quickly so they animate instead of using the image list.  Now I know that the non-working tables have images or textures that the program can't handle causing the crash. This will definitely get me rolling. And I now have an extra task!

 

Bam looks really good on the tables I tried. Now I have to figure out how to get image layers from it 

Edited by gauntletlover, 14 June 2013 - 06:25 AM.

[MagicPinball68]

@ gauntletlover

Can't wait to test the new version you are working on. I tested now so many tables, FutureDMD works perfect for me.

On some Tables with just a 128 x 16 DMD it didnt worked, but you can chnge it easy to 128 x 32 DMD on the backglass editotr, works perfect.

Can't wait to see what is coming soon.

[cparedes]

Thanks again for future dmd, it's great for our cabinets!

I have a problem with it, though. I have the direct acces in the startup folder and, as I use a soft to hide windows, it doesn't work. I would need if someone could help me adding the call to the .ahk to execute future dmd when I play a future pinball table.

Thank you very much.

[Mark4par]

Is there a way to close this program inside pinballX? I can get it started but not close it without clicking on the screen. Or is there a way to open and close it automatically along with FP?

[MagicPinball68]

@ Mark4par

Hi, as i know, actually you need to "kill the task" of the FutureDMD when FP is closing, this is donne by adding a command to the FPlaunch.ahk in Hyperpin, but gountletlover said, in a future version there will be a command to close it or maybe a automatic routine.Hopefully gauntletlover will add it soon.

[Mark4par]

O.k. Got it working in Pinballx.

 Download or create a kill.vbs file. Like this

taskKill = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & taskKill & "\root\cimv2")

Set processlistFull= objWMIService.ExecQuery _
("Select * from Win32_Process Where name = 'FutureDMD.exe'")

For Each killPro In processlistFull
killPro.Terminate()
Next
 

Save and change txt to vbs.

 

 Now just direct pinball x in Future Pinball settings to open FutureDMD at launch and open Kill.vbs after launch.

Also DMD must be dragged off translite and not created new on backglass for it to show up.

[max37170]

i´m sorry to tell you, that the new version 1.0 still doesn´t work an my computer - sorry.

max

[aupton]

Just saw that 1.0 was released, can't wait to test it out tonight after work, thanks for this update! 

[MagicPinball68]

First thank you so much gountletlover for the verry cool adds to V1. I am shure it was a hard work, many hour's.

 

The new release works fine, exept the color mode for different tables. In my case, DMD is working great with the (default) setting in the ini file, in any color, but if i try to configure a special pin Example *Attack from mars* a Green DMD, the only thing that happens is that the DMD in this table is not working anymore, tryed with several Tables, all the same, no sucsess. The rest works like it should as i can  see. Can anyone confirm that? Thanks.

[open6l]

In my case I tried the TRON table with the same name [TRON] as the filename TRON.fpt in the ini and set it to blue. I got a DMD but it was still amber/orange. I didn't spend much time troubleshooting as I had to step out so I can't say for sure it didn't work as a result of user error or a result of a bug. I'll have to try again later.

First thank you so much gountletlover for the verry cool adds to V1. I am shure it was a hard work, many hour's.

The new release works fine, exept the color mode for different tables. In my case, DMD is working great with the (default) setting in the ini file, in any color, but if i try to configure a special pin Example *Attack from mars* a Green DMD, the only thing that happens is that the DMD in this table is not working anymore, tryed with several Tables, all the same, no sucsess. The rest works like it should as i can see. Can anyone confirm that? Thanks.

Edited by open6l, 19 June 2013 - 07:23 PM.

[gauntletlover]

Sorry guys, I'll double check a few things when I get home. I haven't had any issues on my cabinet or dev system with the ini file but I did only test a couple of tables so far myself. Tron being one of them. I thought it was working fine. Magic, did you change the number values under the [default] to get different colors? If it fails to read the the ini file to get a custom setting it is hardcoded to use the orange color.

[open6l]

hmm - some more tests. Tried TRON and Goonies. Changed colors of both those tables (named TRON and Goonies) but it stayed as orange. Tried changing the [Default] from Orange to just Blue (Red=0, Green=0, Blue=255) and it worked but when I try the individual tables it doesn't change. Tried different colors too for each table and still remained as Orange. I closed FutureDMD and restarted it (ran as Administrator under win7 64bit) but made no difference. Tried naming the tables Tron.fpt and Goonies.fpt in the .ini but still no go.

[gauntletlover]

Thanks Open6l, That's a big help. I will have a look tonight to see what went wrong.

 

 

 

 

-sorry max, I haven't been able to re-produce your error to learn how to correct it. The only way I can get an "All Pipe Instances Are Busy" message is if I try to open more than one instance of FutureDMD because the pipe is busy with the first instance. If you have it in your start up folder and it starts running at boot up without an error and you also have an entry in your Hyperpin AHK it will fail. It is not designed to run multiple dmd's. I can't seem to produce the error on the first loading.

Edited by gauntletlover, 19 June 2013 - 09:39 PM.

[gauntletlover]

Everything seems to be working on my end? Did you guys overwrite all of the files with the new ones? Are you guys loading from Hyperpin?

 

;********* start future dmd **********    
        Run, "%emuPath%\FutureDMD.exe" close=1 table="%tableName%",,hide UseErrorLevel

 

The "close=1" tells the dmd to close after you exit the game.
The "table=" pass's the table name to FutureDMD so it can check if you have entered a custom color in the FutureDMD.ini file

 

These tags can be incorporated into another front end but need to be there if you want the features.

 

Let me know, If I need to keep digging

[open6l]

I'm launching manually for testing by running the FP executable (and also testing through BAM again manually). I have overwritten all the files. I will keep trying later tonight after the hockey game.

Everything seems to be working on my end? Did you guys overwrite all of the files with the new ones? Are you guys loading from Hyperpin?

;********* start future dmd **********
Run, "%emuPath%\FutureDMD.exe" close=1 table="%tableName%",,hide UseErrorLevel

The "close=1" tells the dmd to close after you exit the game.
The "table=" pass's the table name to FutureDMD so it can check if you have entered a custom color in the FutureDMD.ini file

These tags can be incorporated into another front end but need to be there if you want the features.

Let me know, If I need to keep digging

Edited by open6l, 20 June 2013 - 12:32 AM.