Jump to content
SpesoftPinballXConvert-It

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 donating by either clicking this text or the Patreon link on the right.

Patreon

mpad

Basic Member
 View Profile  See their activity

  • Posts

    120

  • Joined

  • Last visited

 Content Type 

Everything posted by mpad

  1. mpad

    Tapatalk change

    mpad replied to MNMax21's topic in Social Club

    Shit... I think I am getting used to it! On a tablet in landscape still unusable though. To much left right eye movement...
  2. mpad
    The nukelauncher calls the steam.exe not the games pinballfx2.exe. So if you have the legit version go where steam.exe is. If you have a pirated version because you scratched your dvd go where the games exe is.
  3. mpad
    I'm at a loss, too. Did reset everything to standard clocks when you first suggested it. But didn't help. Some other things bugging me so maybe I just do a fresh start with win7 and get finally get rid of stupid win8.1 on the way... Now that I know how to set everything up it should be done in 2 hours... Or so Just don't forget the backups!!!
  4. mpad
    Happy bday
  5. mpad
    Glad it worked. That dialog sounds like a Windows uac prompt. Disable it for God's sake (if you feel save with computers)!!! --> google how to Also it is best to run apps like pinballx nukelauncher etc. as administrator - right click on exe and go to properties
  6. mpad
    ok, thanks Jeff for clearing that up. I will definetly try the joy mapping, but for the moment I have xpadder running fine after disabling the internal plug in in pinballx. Last thing I am confused about is the exitemulator function in pinballx. This doesn't work for me when set to the same key, let's say "esc". So far I understand it has a similar kill function which interferes with nukelauncher. It exits to pbx before nukelauncher can rotate back and everything gets messed up. So for now I have to set this to an extra button to use with VP only.
  7. mpad
    Yes sure, but I won't have much time during the week as holidays are over now. [emoji24]
  8. mpad
    ok, thanks for the info and thanks for providing the plugin at first place!!! It did work a couple of times but suddenly not, or only for one of the programs, no idea what caused it. I don't think it has anything to do with the emulator software or nukelauncher, as xpadder should work independently. maybe it doesn't get the right info which system pinballX is calling, so it doesn't change the profile? I am fine with the built in profile changer of xpadder atm, but if you ever feel the need to update it I will gladly test again. thanks p.s. just noticed the headline "party"? lol, should have been partly party on...
  9. mpad
    thanks for sharing... this is waaaay more complicated than expected. I was hoping to get rid of all that scripts. what I found is that the pinballx xpadder plugin did't work for me all the time, so it't maybe not the best thing to use that atm. had it activated a while ago and forgot about it :-P standard xpadder auto profiling (it detects the program running and selects the key layout accordingly) seem to work fine. other thing is that you cant't use the exitemulator function and the exit key of nukelauncher with the same key. this messes things up. so exitemulator seem only to be needed for VP. to bad.. would have liked it on the same key as this is easier to rememeber :-)
  10. mpad
    hi, which log you need? are threre any settings that have to be made in xpadder for your plugin? disable autostart or sth? at least I have pinballx nukelauncher etc. now working with the xpadder standard autoprofil function. what exactly is the advantage of your plugin over this feature (if I only need one profile per software)? log.txt xpadder.log.txt settings.xml
  11. mpad
    hello, after having spent several our getting my exit emulator to work with nukelauncher (with no success so far) I cam tho the conclusion that the xppadder plugin is not working at all times. it seems to work for pinball arcade, but not for fx2 and VP. help.
  12. mpad
    as stated before I am too lost when it comes to the EXIT program strategy. All that button combinations go over my head. my contoller send out a button press, let's say "JB1". this can be recognized by pinballX as "JB1" natively. now I use x360ce to map "JB1" to a gamepad button like "X". Now fx2 can read this as "X". but I can use Xpadder to assign "JB1" to Keypress "ESC". This can be read by PinballX as "ESC" and "JB1", by fx2 as "ESC" and "X" an d by nukelauncher as "ESC". and so on... so If you guys could be more precise which combination works for you? I want to use one button to exit out off all programs, like fx2, tpa, VP, ... so for VP you have to use the exitemulator key. but for nukelauncher it is the wron one, because then the timer comes an pinballx goes to the wrong rotation, etc... I wonder if pinballX reads both keyboard an joypad press when running a program like fx2? or only joypad? real mess in my head. and so far I did't get it working for all cases. EDIT: I think it is the fact that xpadder or the pinballX xpadder pluigin is not working correctly. so no wonder that it won't exit when I press the button which I assignet to "ESC"... also it seems it doesn't play well with the 6 sec exit timer of pinballX. @Jeff: would it be possible for NukePA/FX to read joypad inputs directly? I have no ipac or keyboard, so the only way to send a keyboard input is with xpadder, which seems not to recognized correctly atm.
  13. mpad
    try to run pinballX in windowed fullscreen mode. just a wilod guess, but there seem to be some conflicts between pinnballx and the games lately. [Display] Monitor=0 rotate=270 Windowed=False ... FullScreenWindowed=True
  14. mpad
    what are all the keybindings in nukePA and nukeFX for? only need KB_Escape to kill the program...
  15. mpad
    Interesting. I may go for the non-steam version. They already got my money...
  16. mpad
    So for all you guys the timing is working? It is so darn inconsistent on my rig. One time it works one time it doesn't. Could you post your timings and maybe a brief system specs like cpu, ram, hard-drive? Would be interesting to see what works for you...
  17. mpad

    Tapatalk change

    mpad replied to MNMax21's topic in Social Club

    I hope they read and take the app store ratings seriously and assign a bunch of people to new tasks.
  18. mpad
    Good you got it working. It worked for me either way. PBA windowed fullscreen OR pinballX windowed fullscreen. Could't use the first option becaus eit creates an error with steam on my system And PITA yes, took me like 6 hours to find that workaround and I allmost starved that day I wonder when I will find time to finally PLAY pinball again...aaah hobbies. OK cool, maybe Tom has an idea what is causing the trouble. But if you plan an update of NukePA please consider adding a setting on how many "enter" presses it does to select a table. I think I only need one because it registers as two presses most of the time. and maybe another separate screen delay to fine-tune the timings like this: start screen - (Startdelay) - main menu - (screen delay 1) - table list - (screen delay 2) - table
  19. mpad
    DMD for old LED segments look great! Now you can read it You still have the distortions in the background, but imo this gives it a nostalgic touch. The alternative if you wanted it super clean would be a total black background - or repaint it dot by dot Also great that you did videos! Like it
  20. mpad
    @frodus: Hi there, it doesn't sound exactly like the issue I had, but try to set pinballx and/or TPA to windowed fullscreen instead of exclusive fullscreen. Worked for me. @jeff: Big thanks for the Media pack update!!!Will test on the real DMD and send you a pic later. About the autostart: sorry but I might have been imagining things , but when the overall timing is wrong, then it autostarts the table no matter what. and thanks for the insight in what nukepa does. I did notice the skipping and having to do doubble keypress in TPA as well. edit: does nukepa do a dubble keypress before it calls autostart? I think when timing is not perfect (which varies on dayly basis) it registeres the second keypress when already in the table, so it does autostart no matter what. I guess nukePA ist just fine and I totally blame TPA for everything , because it behaves very very odd! No consistency with loading times at all! and the keypress/controller issue was driving me nuts in the past (especially when reading table instructions or entering initials). but Farsight have to sort out too many things...why would they bother. Maybe they will introduce a new UI soon (has been in the making for 1 year) and thing may get better (or worse) As postetd yeasterday everything worked fine with super low delay setting all of a sudden and even autostart = false was OK, it did't do another keypress and the table was waiting in the start screen. and then suddenly BAM, long loading times and not working anymore... I did some testing and I came to the conclusion that the loading/delay time of TPA is 1) super fast when I selct a table at the beginning or end of the list (bigh shot, black hole, white water, who dunnit...) = nukepa working fast and reliably with low delay timings 2) slow when I select a table out of the middle (fish tales, gorgar, funhouse) = nukepa NOT working, or only with high delay timings Could it be something with the guessing engine? Sorry just wild guessing here, at least that is what it is doing on my system. timings that work in standalone don't work when launched by pinballx. so there seems to bee something going on here, too.
  21. mpad
    OK I found the issue: it is sweetFX !!! it makes the tables look so nice, but obviously it is creating some sort of fuss with pinballX interface, because it is listening for keyboard inputs. pfffffff. I removed all sweetFX files and game now regains focus after ingame/pause. can anybody confirm or did anybody use sweetFX and not run into this problem? still won't pause at keyboard input, only joypad. is this intentional to avoid conflicts?
  22. mpad
    edit2: I found out that no matter what keyboard key I assign to the ingame puse function it won't do anything. it only takes the corresponding joy input? does anybody use the pause with a keyboard / ipac / xpadder?
  23. mpad
    one more thing about the table autostart feature. as reported it doesn't work for me to disable it with "false". In addition I noticed it had massive influence on the timing on my system. when set to fasle the game starts slow, especially when selcting tables in the middle like "gorgar" or "harley davidson" and it won't work at all (stuck at attack from mars). strangely when I set autostart to "true" it is way more fluent and every table works. maybe I can even lower my timing now... can you explain what the autostart does? is it not just another "enter" keypress? EDIT: call me crazy, but I had it running with StartDelay = 2000 ScreenDelay = 800 MovementDelay = 50 and it seemed the lower the screendelay, the lower the loading time of TPA. Even Autostart=false worked all of a sudden. BUt after 4-5 tables it all got stuck again and stopped working.
  24. mpad
    hey jeff, thanks for the offer. I never used teamviewer, but I will keep this as a last resort. for now I will see that I can fix it or just keep it that way. the problem is I have so many extras done, there are too many suspects and I don't have the nerve atm to rule them out one by one or do a fresh install. most likely nvidia driver settings (which I have maxed out in a lot of things). I have had an issue with pinaball arcade like forever, that is very similar. when I run it in windowed fullscreen it crashes after I exit, details show problems with steam overlay render.dll. so I have set TPA to fullscreen. I have steam overlay deactivated, but with no success. NukePA worked that way too, with pinballX set to fullscreen and TPA to windowed fs. but I could't do that because of TPA crash, so pinballX is windowed fullscreen for now. so it seems my system has a problem with two apps trying to get exclusive fullscreen at the same time. Additionally I have the weird issue that I cant use the build in pause/return to game method of PinballX because the game (window) looses focus on don't react to keyresses anymore. only after a mouse click it reacts again. seems to be connected somehow. One thing I wanted to ask is what is the best method to exit a game? I don't mean the kill-method nukePA uses, but more like what kind of key mapping logic you guys use in combination with all the programs. if I want to go into the pause/options menue in TPA for example the esc key is normaly used to navigate out of it, but that will exit the game with nukepa, so I have to remap here. Or what is with all the options pinballX offers? exitemulator key with 6sec delay can't be used I guess. the pause function of pinballX and then exit game / or return to game won't work too, or is there a way? do you map the same keys ion nukepa/fx and pinballX? I am kind of confused here what is the best solution... so sorry for spamming this thread with my problems :-) I am sure NukePA works great for most people and is real treat! Thanks again for this Jeff!
  25. mpad
    @andyco: I thought so @jeff: OK, I got it working for now. can't talk about long term tests, but it selected 10 tables in a row, so I am very confident atm. only thing that doesn't work is the autostart disabled, it always does another keypress after a short time (screendelay) which starts the table. Thanks to andycos nukepa.ini i tried a much lower startdelay, and that did the trick. I did use the default xml though, so renaming the tables to the actual file names is not cecessary (in my case). EDIT: And you should definitely add to the documentation that pinballX should be in windowed fullscreen mode. stange that it works for allt he others (fx2, vp,.. in fullscreen). but it is TPAs fault. they only did that half baked porttrait support. zen had its native porttrait in in no time. maybe one day... Timing seems to be very delicate though, here is what works for me: StartDelay = 2000 ; Default: 15000 - for time between launch and first keystoke, mine works as low as 5000 ScreenDelay = 4000 ; Default: 1500 - for time between screen changes, mine works as low as 900 MovementDelay = 70 ; Default: 100 - for menu movement speed, mine works as low as 10 AutoStart = false as you can see startdelay is very low, but screendelay is high. this is because it recognizes the firs button press very fast, but than takes long to go to the first menu with seasons / my tables. After that when you enter the table selection list it could go faster. so for an improvement it would be cool to have a screendelay1 = 4000, and a screendelay2 = 1000, so table selection would be faster.
×
×
  • Create New...