I’m a Glock guy. Drop once, twice, thrice, and on. Good site picture and trigger control - voila - tight grouping in the a…hole of a rabbit at 25 yards.
Latest posts made by mikemadmax
-
RE: Ff you could have one thing in the next update it would be…
-
RE: YAME64 suite
You’ve got to roll back WIN 10 and Nvidia drivers and, then permanently disable future updates until there’s a suitable fix.
-
RE: Ff you could have one thing in the next update it would be…
The 99 year lease reminds me of GTMO and the Panama Canal Zone.
-
RE: Ff you could have one thing in the next update it would be…
A few posts back (#2091) I suggested a good update would include HUD Only display with TrackIR and/or other head tracking devices. You guys pointed me to the empty cockpit shell and I’ve been using it ever since. Thanks again. It gives that extra sense of immersion with my modest pit. However, if the HUD frame and the AOA and NWS Indexers could be statically fixed to the front of the empty shell (replacing those four fins) - of course keeping the HUD projection centered as it is now - that would be cool. Just a follow-on thought.
-
RE: YAME64 suite
I don’t how that smiley popped up but, it’s the Superbug I was referring to.
-
RE: YAME64 suite
Hi Varhn:
That’s exactly how I had my system set before YAME crapped out on me a couple of weeks ago and, now post recovery - after reformatting my main Drive and starting over. Its funny because having I reached out to Wicked last night to offer some help on the same issue, I went into Desktop Display and moved my fourth display (dropping it down and to the right, adjacent to my other monitors) and voila, the YAME grid filled the entire 4th monitor screen as well. Its all about setting the right coordinates so that all the displays you want to use fall within the grid so that you can position the gauges wherever you please. I’ve got it running perfectly again. In fact last night, I flew my first campaign mission since getting back in the pit. I fragged a 12 ship package, an OCA Strike out of Seosan targeting NK Haeju AB. SEAD took out the SAMs, Escort dealt with MIGs and, my AI Wingmen and I dropped our GBU 24’s and obliterated Haeju. TRaclIR, Voice Attack, Jet Seat, TM MFD’s and, my recently acquired Viper Gear ICP - all worked flawlessly. It was total immersion and fantastically gratifying. I still have figure out how to fine tune my aging Cougar TQS - maybe a Hall’s update. We’ll see.To Roccio and Fd:
I really do feel Win 10 and/or Nvidia auto updates are wrecking havoc on YAME and Helios. Since reformatting my main drive and restoring to Win 10 V1703 Build 15063.966 and Nvidia Driver 382.05, I haven’t had any problems. Note that I permanently disabled future Win and Nvidia updates. FYI: although I’ve got Helios working again, I haven’t set it up. I’ve decided to table it for the time being pending release of your next YAME version. If you guys can replicate most of Helio’s extractions and, create a functional stand-alone turn-key F-16 (and F-18) pit, it would be beyond awesome. It would be a game changer. Again, I would be honored to help you test the beta. -
RE: YAME64 suite
Hi again Wicked: I don’t know if the following provides a solution for you. Hell, I don’t even know if it even makes any sense (whether its intuitive or counter-intuitive).
Obviously YAME will layout your grid and gauges you’ve selected to run based on the X, Y coordinates you’ve set in YAME’s Client/Windows/Edit screen. Now, I ran into the same problem you describe when I set YAME’s Width to 3440 and Height to 1440 (mirroring that of my main display - Dell 34" Curved 3440x1440) and the x coordinate to 3440 and y coordinate to 0. What I encountered was that, when I set the x coordinate to 3440 and y coordinate to 0, it was only picking up my main display(edge-to-edge and not my other three (3) displays and Android Tablet (Left to Right as in ICE’s Window’s Display Settings layout). Initially what I didn’t account for, was the combined Width and Height of my other displays. I also noted that if I set my y coordinate to 0 and, populated the gauges I selected, dragging from the main display and placing them in position on my second display (LG 32" 1920x1080), when I ran YAME and then Launched BMS I was getting a black screen on all of my displays (no gauges at all on any of my displays). )
This result stumped me for a bit. Then I ran Client/Windows/Edit again but, this time I ticked Border with Visible also ticked (I left Fullscreen, Masked and, Antialiasing un-ticked). I then dragged the White Boarder showing at the top of my main display down to the bottom of the main display (just about the top of my second display below the main) and dragged/placed my gauges on the second screen accordingly. When I ran YAME and Launched BMS, the gauges were pretty much close to where I wanted them and, BMS was showing fullscreen on my Main display. A little tinkering was needed (moving, resizing the gauges and, un-ticking Boraders) but, I got what I wanted. Note, that YAME changed the On Monitor window (in the Clent/Windows/Edit interface) from On Monitor 1 to, 2. At first, I had tried making the change manually but it wouldn’t take. I also had to putz around with my Width and Height settings. I still have to troubleshoot these setting because only a fraction of the YAME Grid is showing on my third display (set up as Portrait and Inverted in Win 10 Desktop Display Settings).
Whether you call it intuitive or counter-intuitive, what I’ve concluded is that, if you set YAME’s y coordinate to 0, YAME is going treat the Top of your main display as its uppermost point of reference and its going overlay and mask BMS from showing up on that main screen (single, extended double or, triple main screen setups). BMS will be running but, its running underneath YAME on the main screen. If you review my Pos Y coordinate in my #1443 Post above, you’ll see that I changed it from 0 to 1403 (just a few digits under my Main display’s pixel height of 1440). So what I would suggest is that you set your Y coordinate to whatever your Main displays pixel height is and make adjustments from that number up or down. In short, you want your main display to run BMS’s graphical renderings independent of your YAME gauge layout which would be dedicated to your second, third and/or fourth monitor(s).
Per the YAME start and stop extraction issue. I don’t have a clue about what’s happing there. Way above my pay-grade. However, I would consider Varhn’s advice regarding BMS’s MFDE extractions. I’d try anything once, twice, thrice, ad-infinitum, if it’ll make this sucker work as desired.
Let me know how this quest turns out. I’m sure we can help each other in this effort.
Best regards,
Mike -
RE: YAME64 suite
Wicked: I hear what your saying. When I laid out my monitors in Display Settings as ICE suggested I was having the same problems. However, when I laid them out in their physical placement configuration I was able to set the coordinates to get my YAME gauges to populate my second monitor just as I wanted them using the drag feature. I don’t know if the following pics will be helpful, but its what I did to get my layout setup and I’m not experiencing a start and stop extraction problem. A you coined it - its running as smooth as silk.
Display Settings.
YAME Settings.
Gauge Layout.
-
RE: YAME64 suite
I’d be honored to give it a shot - as time permits. However, understand that I’d be learning as I go and would need guidance…
-
RE: YAME64 suite
Understood. YAME is awesome right now but, what you’re projecting for the next YAME version would be beyond fantastic. I’m a YAME fan and I wish I had the expertise to pitch in and lend a helping hand. When Helios crapped out on me, I was vexed. When YAME stopped working, I freaked the hell out. On behalf of myself and, I would hope everyone else in the BMS community running YAME, you’re the best. My deepest and sincere thanks for your continuing great work.