Forum Replies Created
-
Posts
-
I’ve got this exact same problem also. After you exit a Future Pinball table it appears you are on the desktop but if I hit a menu key the PinUp menu is still active and will display and scroll. I’ve just gotten into the habit of hitting my “e” button which is mapped to exit PinUp and then relaunching.
Sorry for the late response. No I never got this resolved. I just stopped using FP with popper. I suspect my system is too slow to load FP with popper in the background and something is timing out.
You need to login in order to like this post: click here
I just uninstalled vlc and reinstalled 2.2.8 just to be sure. No luck.
I got my hopes up when I saw that I had geforce experience installed, but uninstalling it and rebooting didn’t seem to make any difference.
I hate to say it, but I may install Windows 10 soon to see if it makes any difference. Probably on a different hard drive though. I hate starting from scratch.
You need to login in order to like this post: click here
Yep. pinupmenu.exe is the only one running as admin.
I am running DOFLinx. it runs on windows starup via startup folder I the windows start menu.
curlaunch.bat runs the last table I opened per your instructions. Below is what is in the file.
rem FUTURE DMD. Remove “rem” on next 2 lines if you are using FutureDMD. Change the directory to where you have FutureDMD installed.
cd “c:\games\Future Pinball”
START “” “FutureDMD.exe” table=”Knight Rider (p2.5) (DOFLinx)” close=1START “” “C:\PinUPSystem\Launch\VPXSTARTER.exe” 5 5 20 “Future Pinball”
rem This will load Future Pinball and your selected table using BAM (Better Arcade Mode).
START “” “C:\games\Future Pinball\BAM\FPLoader.exe” /open “C:\games\Future Pinball\Tables\Knight Rider (p2.5) (DOFLinx).fpt” /play /exit /arcaderender /STAYINRAM
You need to login in order to like this post: click here
I messed around with this briefly tonight. I didn’t see anything out of place in the launch script. I did go into the windows application logs and I see an instance of this crash every time I open FP from PinUp.
Faulting application name: PinUpDisplay.exe, version: 1.3.4.0, time stamp: 0x5b105c87
Faulting module name: libvlccore.dll, version: 2.2.5.1, time stamp: 0x38a93891
Exception code: 0xc0000005
Fault offset: 0x000814fd
Faulting process id: 0x2ad8
Faulting application start time: 0x01d3ffb3c02bc982
Faulting application path: C:\PinUPSystem\PinUpDisplay.exe
Faulting module path: C:\Program Files (x86)\VideoLAN\VLC\libvlccore.dll
Report Id: 0eb747f5-6ba7-11e8-86e9-7446a0c27483I am running version 2.2.8 of VLC.
You need to login in order to like this post: click here
Thanks guys. I’m running windows 7. I looked this morning before heading out the door if PinUp is set to run as admin. It is.
I’m less concerned with the recording since I don’t run that many FP tables and like Terry said, I can use OBS. I think I’ve done that in the past when the other recording solution didn’t work for me.
Is there something in particular in the FP post launch script should I be looking for? I don’t recall touching that when I set up FP in PinUp the other day. I didn’t have time this morning to look into it further.
You need to login in order to like this post: click here
Thank you guys for the help. I’m sorry to have wasted your time but maybe someone searching for help on this will see my mistake and this will help them. It appears that my Pinscape settings were configured wrong. I played around last night and discovered when I went to the Pinscape properties in Windows Devices and Printers (you know, where you can calibrate contollers and test buttons and such?) that my Pinscape only showed two buttons in the calibration window. Furthermore the top of the window said LEDWiz. My next step was to unplug the LEDWiz and voila, all the Pinscape buttons appeared in the calibration window and the window said Pinscape. This led me to uninstalling all my USB devices in device manager and reinstalling one by one. Unfortunately, as my last step of plugging the LEDWiz back in, the Pinscape reverted to only showing two buttons in the calibration window and the name of the window again changed to LEDWiz. One thing I did notice was if I unplugged my LEDWiz and rebooted the PC, PinUp recognized the button presses from the Pinscape buttons, but when I plugged the LEDWiz back in, the buttons stopped again. Not really knowing what to do next, I remembered a special DLL for LEDWiz that MJR put out. I was sure I had installed it previously but I tried it again. Unfortunately, still nothing. Finally I went back into my Pinscape software and looked closer at the LEDWiz stuff because I know the Pinscape does act as an LEDWiz and figured maybe a setting was wrong in there. That’s where I found my issue. In the setup it says to set the Pinscape as LEDWiz #8 if you have a real LEDWiz in your system. When I built my table last year, this is how I set it up. When you click that dropdown it gives several assignment #s for which LEDWiz you want your Pinscape to be. Near the bottom of the dropdown it also has something like Pinscape ID (something to that effect, I’m writing this from memory at work). Once I set the controller to this, I was able to finally use the Pinscape as intended and set the buttons in the PinUp configuration menu.
MJR, if you ever come over here and read this, perhaps you could add a little more clarity on how to set this part up in your software. Otherwise, thank you very much for what you’ve done.
I’m really surprised that my system has worked at all with my configuration being wrong this whole time and that PinUp was the only thing that balked at my mis-configuration. As a side bonus in figuring this out, My LEDWiz appears to be functioning better now. It was working before but it occasionally had a weird flicker, particularly with LED sequences that breathe in and out. PinUp is looking really good and I’ve already recorded several playfield, backglass and DMD vids with it and have 5 or 6 tables set up now. Thanks NailBuster.
TL;DR
If your Pinscape buttons don’t register in PinUp and you also have an LEDWiz in your cab, make sure you don’t have your Pinscape set as a secondary LEDWiz in the Pinscape Software. Set it as Pinscape ID something or other. LOL, I can’t remember exactly, but hopefully this will get you on the right track.
You need to login in order to like this post: click here
Same here. Did I see you post on VPF that you had some kind of error related to the buttons not working in PinUp? I’m not getting any errors with mine, they simply fail to register.
You need to login in order to like this post: click here
Yep. tried both xinput and direct x. No-Go.
You need to login in order to like this post: click here
Yep. Installed 1.3.4 on top of the base install. Also updated Pinscape firmware. I haven’t looked at direct x version yet. Will do that tonight when I get home from work. Thanks Terry.
You need to login in order to like this post: click here
This is the thread I was looking for! I set up popper yesterday. Followed Terry’s vids as well as followed the wiki. Love it so far but I too am getting no love from my KL25Z pinscape device. I hate to see anyone else have trouble, but it is a little re-assuring to know I am not the only one having an issue. I am getting zero response from my Pinscape device when I try to map my controller buttons. I get the window that flashes waiting for me to press a button but nothing ever happens unless I press a keyboard key or cancel out. I do have the DirectX Joydriver set as the driver. In my Pinscape settings, the buttons are all working fine. The Pinscape works fine as a controller in VPX as well as in that other frontend. I was able to use Anti-micro (sort of like joytokey, xpadder, etc) to map my controls as key presses, so I was able to get going, but obviously I would like to get this to work without a keymapper like that. Cameron, maybe we can compare notes and figure out what is causing the issue?
Here is what I got in my box. Not fastest or prettiest but it works. I hope maybe we can find something that is common to our set-ups that could be causing the issue.
I’m running Windows 7.
Re-purposed AMD A8 5500. (Yes its slow, I know, I know.)
16 gigs of ram.
250 gig SSD
Geforce 1050 Ti 4 gig
Teensy controller
SainSmart – eight channel
LED-Wiz
External USB 7.1 Audio Adapter
That’s about all I can think of at the moment. Hopefully we can figure something out.
You need to login in order to like this post: click here
Thanks Terry. I do look at that for reference. I really need to deconstruct another example to see how it all ticks. I’ll look at some of your other code to figure out how to do it. Baby steps, baby steps. I’m learning, Thanks!
You need to login in order to like this post: click here
I screwed around last night with the Elvis table. Terry, I copied your TOTAN PF Back Flasher MX code and re-purposed it with different colors and DOF assignments from the Elvis table. I wish I was more knowledgeable about this stuff. I learn by deconstructing something or having someone completely walk me through it, so bit of a learning curve here!
Is there any reason the letter I can’t be better centered in the DirectOutputShapes.png? It seems like all the letters would be better off if they were centered better, but maybe there is a reason why they need to be aligned to the left for some reason?
Here is a short demo. Too bad I have such a bad glare off the playfield glass.
Here is the PF Back Flashers MX.
S9 Red @flasherclo@ @LetterE@ L15/S22 Red @flasherclo@ @LetterE@ L16/S32 Red f200 @flasherclo@ @LetterE@ L17/W43 Yellow @flashercli@ @LetterL@ L18/S23 Yellow @flashercli@ @LetterL@ L19/S10 Purple @flashercli@ @LetterL@ L20/W41 Yellow @flashercli@ @LetterL@ L21/S9 Blue @flashercc@ @LetterV@ L22/S22 Blue @flashercc@ @LetterV@ L23/S20 Yellow @flashercri@ @LetterI@ L24/W42 Yellow @flashercri@ @LetterI@ L25/S17 Yellow @flashercri@ @LetterI@ L26/S10 Red @flashercro@ @LetterS@ L27/S23 Red @flashercro@ @LetterS@ L28/S43 Red @flashercro@ @LetterS@ L29
You need to login in order to like this post: click here
