rockyrocket

It has been years since I set this up so things may have changed, but the page linked should still have working files. DOF has nothing to do with future pinball you need macro`s DLL.... http://www.shaunroot.net/pinball/LEDWiz/readme_FP_LEDWiz_Setup_Instructions.html

Real mix of stuff - some NSFW, but that stuff is tagged as such. https://www.reddit.com/r/SciFiRealism/

Hhmm, Not sure of the purpose of this whole site/ruse?. Clever though apart from the blog. http://www.magicleap.com/#/home

Does the PC version have any benefits over the dreamcast version?, it is running fine for me in nulldc on 64bits win 7. If yes then I will upgrade. . EDIT: just checked and have it running under project 64 also.

Prices are up..... http://www.vpforums.org/index.php?showtopic=32549&p=322907

You actually have a number of options for this. First you have the built in LED plug-in although I can not seem to find the documentation for this?. Then you have this option.... http://www.gameex.info/forums/topic/13252-working-ledwiz-with-pinballx/ And http://vpuniverse.com/forums/files/file/3018-shineon-release12rar/ And LEDblinky... http://www.ledblinky.net/downloads/Install%20and%20Config.pdf

Just to clarify are you asking if the PacLED64 controller can be used for an attract sequence in the front end?, the Direct Output Framework bit confused me a bit. I know many others use the LED plugin to great effect with a LEDwiz for attract shows and have not heard of the PacLED64 not being supported?. Personally I use ledblinky in my cab for lighting effects whilst in the menu, it even has support built in for PinballX and fully supports the PacLED64 http://www.ledblinky.net/ledblinky.htm

Going to be tricky I think, as you are going analog wheel to digital keypress. But I am a huge fan of Xpadder - maybe a large dead zone would work?.

Can not see it but this is clever....

Can`t seem to find any pics, but someone did one inside a wardrobe once - just looked like any normal hardwood bit of furniture stood up. Will keep looking was probably Here somewhere?.

Hallelujah!. vpauto.exe automatically clicks through the nag screens Pinmame throws up whenever you play a table the first time. If you do not mind opening new tables up once outside of PBX to Ok the boxes then removing vpauto should not be an issue (correct tom?) , PBX will still send a command to it anyway but should be fine I am assuming. Have not added a new table in a while and Pinmame has changed a lot lately, do we still even get the nag screens?.

Or by .PNG/.JPG?

Bugger

Try it, but really I was concluding that db2s was the cause, but if it is not enabled then I do not know. Are the BG`s a static image?.

The burning question for me is do you still have focus loss with this config and PinballX?.

This just gets This just gets more puzzling does it not?. I was going to suggest This test software but am now really out of all Ideas?. Do you have another PC to test your set up in?. one with 3 monitor support via the gfx card maybe?, or have you tested in just a two screen configuration.

Did you enable Db2s in the frontend?, not sure if PinballX reads the screenres.txt file and resizes the Db2s screen to cut off the grill. Think I may of saw this myself and returned to just using a static image in the front end?, others can probably comment on this better?.

Steve and myself have been bashing away at this in the background via PM and in the name of transparency and to get some more eyes on the problem I thought we would let every one know where we are at. So using AHK to run a winactivate command to activate the VP window after a 7 second wait does indeed pull focus back to VP long enough to coin up but then somehow focus is again lost later?. However if we then add a second Winactivate after another 7 second sleep this fails?, adding a loop to keep activating may work but is no solution and who knows how game play will be affected. This I think though can probably rule out PinballX?, so we started to suspect something grounding out and producing unwanted key press`s, or a rogue input device sending ghost inputs. This though leads to the question as to why only when loaded through PinballX?, unless the extra windows opened are what is being clicked maybe?. Steve has now upgraded his nudge device and still has focus woes so any other input is most welcome. One thing I am unsure of Steve is if you are using your new nudge device for buttons aswell or do you have a separate encoder?. Also can you see any ghost inputs firing when the onscreen keyboard is active or anything under joystick properties?. Wondering also if any signal(usb) lines are running too close to power lines or alongside contactors or the sub maybe? What happens steve if you unplug all usb inputs ledwiz aswell and then plug in a external keyboard?, this would rule out noise then?.

Well I now know what sunday holds in store for me .

Hey Han, mark hamil plays a charactor alongside Gary oldman and others in the SC campaign mode....

I so love to hate the movie . Lots of new Star citizen footage.....

Damn that video sealed the deal I am defo getting one now. Russ only lives 3 miles from me so think I will PM him now.

I noticed this once and it was because some of the names that the games manager was using had illegal chars for an XML (spaces I think) so would not save - manually editing the media files and XML solved things. Should really of filed a bug report - sorry everyone . Hangs head and hopes tom reads this.

Maybe have a look at your PinballX.ini file, under the [FuturePinball] section and check that the last entry is..... MouseClickFocus=True And also that FP is running as admin can not hurt.

Yes thank you tom!, personally I really appreciate this update . Edit and ben aswell of course .