Jump to content

htamas

Supporting Member
  • Posts

    219
  • Joined

  • Last visited

About htamas

Recent Profile Visitors

2801 profile views

htamas's Achievements

Rising Star

Rising Star (9/14)

  • Very Popular
  • Dedicated
  • Reacting Well
  • First Post
  • Collaborator

Recent Badges

239

Reputation

  1. 😀
  2. Thank you. It would be nice to have an option in the F12 menu to hide the side rails for cabinet users. In fact, that should be a default option for all tables... or even better, hiding them automatically in cabinet mode.
  3. I can't get the PuP working either. Not sure what am I missing, because every other PuP pack works fine. I'm running the latest PuP Player 64-bit beta version (but using only the Player, not the entire PuP System setup if that matters).
  4. Very nice update, thank you - however, how can I get rid of the rails in cabinet mode (no VR)?
  5. Thank you for the update. Latest version (1.1) still has the wrong left flipper friction value (0) 🙂 To me, value 1 (instead of the suggested 0.9 for both) seems to work better. Easy fix - thanks to XVector for the tip -, just wanted to mention it so this could perhaps be fixed in the next upload (if there will be any). Also, it would be nice to have an F12 option to hide the cabinet rails in non-VR mode. I just replaced those rail images with a black one, but the option control would be welcome for all tables, not just this one.
  6. It looks great, thank you. However, for the sake of authenticity, would it be possible to get the cab art say 'Gold Wings' like on the real table?
  7. It looks great, thank you. However, for the sake of authenticity, would it be possible to get the cab art say 'Gold Wings' like on the real table?
  8. Thank you for the update, it's appreciated. However, I somehow find the flipper physics to be off... it's, how should I say it, Future Pinball-like? At any rate, I'm having a harder time than usual to make certain shots, especially ones starting close to the tip of flippers. The scatter seems to be too big or something, I cannot quite put my finger on it. Also, the flippers seem to be a little too strong to me or the playfield friction is too low, something along these lines. Other tables with nfozzy physics don't behave like that. Or is it just me who feels this way?
  9. What a great table, thank you very much. I enjoy this a lot, and it plays very well. Physics are great. The only thing I changed was setting the top kicker hole's hit accuracy to 0.26 to avoid the "magnet pull" feel when the ball was dropping into the kicker. Now it's much more realistic. Another thing I noticed is that most VR elements (such as cabinet legs, rails, backbox and so on) are defined as collidable, many even have a hit event . Now, I'm not a VR user or table developer and don't know if this is needed for VR, but wouldn't it be better to define these as non-collidable or toy, to get better performance? (not that I really experience any performance hit with this table, but still... maybe this is more of a general question about tables).
  10. Excellent upgrade, plays and looks great. Thank you. For those playing in a cabinet who are not stretching the table sideways to the full width of the screen and want to get rid of the score showing next to the table: disable EMReels in the backglass settings.
  11. Great work as usual, thank you so much. I was wondering: is there any way to display this in a 3-screen cabinet, so that the grill appears under the backglass (like the second screen shot here) and the DMD screen shows the cab art? I have a 1600x1200 backglass monitor and using a .res file it is no problem to show the glass area with proper dimensions, but this leaves a pretty tall black bar below where I would like the speaker grill to appear. I couldn't figure out yet how can I do this.
  12. According the the description, the update was the addition of the altsound.csv file and some other changes.
  13. I checked my setup and apparently, the minimum DMDExt release for this update is not 2.3.0 as it's mentioned in the description above, but 2.3.1 I had only 2.3.0 installed and after updating to 2.3.1 this new version started working.
  14. Hmm, thanks for the update, but for some reason, this new version is not working for me, while the earlier one from March is fine. Anyone else with this problem?
×
  • Create New...