Jump to content

=VG= SemlerPDX

  • Content count

  • Joined

  • Last visited

Community Reputation

3,220 Invaluable

About =VG= SemlerPDX

  • Rank
    Lieutenant Colonel
  • Birthday 07/03/1978

Profile Information

  • Gender
  • Location
    Portland, OR
  • Interests
    Camping, hiking, shooting, and fast gaming computers
  • Occupation
    Scruffy looking Nerf Herder

Contact Methods

  • YouTube

Recent Profile Visitors

28,264 profile views
  1. Time to brag

    Yea, with a ping like that, I wonder if she's some kind of emergent sentient a.i. like Binary or something... Are you, Alaura? Are you a bot? Is this why you asked me all those questions about my personal preferences and asked me to choose an update schedule? (j/k) haha
  2. Project Reality VIP Rescue Event

    Server has been setup for you @=VG= TEDF - GS9 Port 16587 -- didn't copy over the complete VG coop python, just the key parts like death time, etc. You will need to adjust kits and loadouts if needed, these are default COOP settings. If you need me to change these to match COOP, I can, but you'll likely want to edit them for your custom missions so I left them default for now. Let me know. Any issues, contact me. Cheers! *current banlist, admins list, and the Fly South Crash bug fix have been put in place, as well.
  3. Time to brag

    Personally, I prefer https://testmy.net/ because I can set parameters, have a better choice of servers, etc. etc. Also tests Up and Down separately. If you need to troubleshoot your Twitch live stream, you don't use Ookla Speed Test, you use testmy.net
  4. I got a Ban

    UNBANNED *(afaik will take effect next time the server changes map or restarts) /locked
  5. I got a Ban

    You were banned by FastJack for massive teamkilling. I can see why he perceived this as end of round teamkilling, an apology was not apparent, and it was swiftly followed by yet another teamkill. RULES: [16:15:18 T2 SQUAD 1] =VG= deathdealer203: !setnext kaz coop std [16:15:21 TEAMKILL] TF47OR-6Hausmann [usrgl_m4ugl] WARDOG WARHAMMER101 [16:15:21 TEAMKILL] TF47OR-6Hausmann [usrgl_m4ugl] Arthya [16:15:23 GLOBAL] =VG= Kavelenko: !setnext Kol coop std [16:15:24 TEAMKILL] wellleeee [c4_smallexplosives] Colt1001011 [16:15:25 T2 SQUAD 1] =VG= deathdealer203: l [16:15:25 TEAMKILL] TF47OR-6Hausmann [killed] WingnutDX9 [16:15:37 TEAM 2] =VG= Fastj@ck: !b hausmann tking massive [16:15:37 DISCONNECT] ' TF47OR-6Hausmann' disconnected [16:15:39 TEAMKILL] wellleeee [ushgr_m67] bao-y0000u [16:15:39 TEAMKILL] wellleeee [ushgr_m67] Cel_Coronel-Everton [16:15:39 TEAMKILL] wellleeee [ushgr_m67] WARDOG WARHAMMER101 [16:15:40 T2 SQUAD 1] =VG= deathdealer203: !setnext koz coop std [16:15:42 GLOBAL] =VG= Kavelenko: !setnext koz coop std [16:16:22 GLOBAL] =VG= Kavelenko: you ok with that one FastJack? [16:16:27 T2 SQUAD 2] =VG= Fastj@ck: stop that fucking teamkilling [16:16:41 TEAM 2] =VG= Fastj@ck: stop tking or get banned [16:16:47 TEAM 2] =VG= Fastj@ck: no [16:16:55 TEAM 2] =VG= Fastj@ck: i'm not ok with that tking Please be patient as we wait for the banning admin to post up. You have no history of bad behavior on our server that I saw, and if you can follow the rules, and be careful to make sure people know when a mistake has happened (text chat helps), you may be allowed back on the server. Again, we will wait for the recommendation of the banning admin, FastJack.
  6. The hardest Vietnam ever that can be

    Consider yourself warned. /locked
  7. Campaign Challenge Level

    Yes, it had crashed. Thanks for the report - I've restarted to the last auto-save, it's running now. P.S. I've not had time yet to work on the campaign file yet, but it's on the list and I've got plenty of free time coming up starting as early as this weekend or next week. I expect it to be that way through New Years, so looking forward to get some more regular flights in as well. See you around!
  8. Hacks or bug/feature

    omg - it's still a secret even if the person doesn't confide it in anyone lol
  9. Profile for VoiceAttack by =VG= SemlerPDX Description: These commands use VoiceAttack to translate the in-game on-screen radio menus from AWACS through Tanker into natural and intelligent voice command phrases that will fire keypress macros to help keep hands on the throttle and stick, and maintain immersion. As an additional option, these commands can be locked behind a push-to-talk mode bound to your UHF/VHF transmit buttons in-game, allowing any other VoiceAttack command unrestricted access if needed, while still restricting these BMS radio command macros. Finally, this single advanced control profile is extremely easy to edit or integrate into other profiles. At VETERANS-GAMING, we fly with friends or AI Pilots, or a mix of both on our 24/7 Public Korean Campaign in Falcon BMS. We may go out with an AI wingman only to have a friend take their place mid-flight. For this reason and others, I created this VoiceAttack profile based around restricting when the computer can execute keypress macros that match voice phrases, having to first check if that pilot was set to a human pilot and therefore disregard commands for that pilot. Thanks to user requests during the beta, there is now an optional mode to reverse the Human Pilots system, to assume all pilots are humans unless told otherwise, and also a system to choose a different keyboard layout than QWERTY. I have also added an optional Audio Feedback Mode to play a short radio cue sound when a command is successfully recognized. Included is a single profile that handles every callsign and radio command variation in Falcon BMS, with instructions on how to add any custom callsigns to the single profile. The focus of this profile is only on the in-game Radio Menus, and creating an immersive interaction layer through VoiceAttack that is easy to manage and update, or integrate into other Voice Control systems for Falcon BMS. My goal was an intuitive system, so there is no user manual - only a few infographics and quick reference pic of all the radio commands. I personally keep that final pic on my tablet for reference when flying, to find radio commands I seldom used in the past when they were more difficult to access while busy with HOTAS in the pit. Say goodbye to the keyboard, and enjoy the immersion! Cheers! Features: *Push-To-Talk mode disabled by default. Say, "Turn On Push To Talk Mode" to enable **Follow Instructions inside profile to set Push-To-Talk buttons to match BMS UHF/VHF keys Download: (Click Here) Tips for this profile: *On first import, you should say, "Initialize Profile" - after first time, this is automatic. Any attempt to use commands before this will trigger auto-initialization. If you get errors from my profile, Launch VoiceAttack and open Options (wrench icon in lower right): -Under last tab on top, System/Advance, check box next to "Use Nested Tokens" as in image 1 below -Unless absolutely required, during testing it's recommended to uncheck "Allow command segment info for composite commands" Open the profile - if not already done, group commands by category and consolidate multi-part commands as in image 2 & 3 below Click on the Description tab at the top to help sort commands further (see image 4) Read a semicolon ";" as the word "or" and look at long commands as having many options like saying "2;Two;Too;To;Wingman" (read as "2 -or- Two -or- Too -or- To -or- Wingman") Commands Reference: *Replace the word "Human" with "Computer" when All-Humans Mode is ON Normally, this profile assumes all pilots are Computers, use All-Humans Mode to invert this
  10. v1.1 Patch has been released A bug has been identified and removed. This issue prevented the entire Human Pilots Registry system to function and should have been caught before the final release version. All apologies to everyone who has been trying to use this new voice program. In addition to this, I've decided to not use a wildcard to catch the name of the BMS program to send keypresses to, and have gone for the "Falcon BMS.exe" method. Still, this will not catch every user, and players will need to test to be sure commands go through initially, and refer to VoiceAttack troubleshooting (and those tips we've highlighted already) to get commands to fire in the correct window. I'm happy to help new users, and the community has been helpful as well. Any questions, feel free to ask! Patch Release v1.1 Changelog Nov2019 Fixes/Improvements: -Changed common Send To default from *Falcon BMS* to "Falcon BMS.exe" to avoid conflict with open PDF's, etc. with Falcon BMS in name -Fixed Human/Computer Pilots Registry system - last minute addition of a mode check was to blame, has been removed for now Download: (Click Here)
  11. Time to brag

    I live in a major city and I pay around $90 a month, it was over $100, but I added Cable TV and the price went down... Yep. Down.
  12. Hacks or bug/feature

    I asked, it is a bug. A very rare bug. Seems to be known, asked but did not get recommendation to report it off the bat so like they can't jump at every little thing, just the things that break things, those that come up often, etc. If you can actually reproduce it, like Fastjack said, consistently, it would not be in the very rare category, and attention might be devoted to fixing it, and so reporting it and the method to reproduce would help. But if it's just another one of those things we see a few screenshots of and laugh, and never see again, no problem letting the Dev's relax and/or work on more important things. Thanks for the report, nevertheless!!
  13. Re-introduction (and a call for help, I guess?)

    Hello and welcome (back)!! I'm not sure about the mouse cursor thing.. if one of the guys doesn't post up with a tip or fix, consider posting up on the PR Forums website, the Dev's are helpful and of course, know tons of fixes from issues over the years. Best wishes and see you around!
  14. Rewatched this one for Halloween - funny as hell

  15. Mumble crashed

    Fixed and tested... Sorry about that guys, it had not come back up properly after the scheduled Server Maintenance today. We also spent some time testing it to get it to not do this again, will let you guys know if we have success. Thanks for your patience and understanding!