Jump to content


  • Posts

  • Joined

  • Last visited

1 Follower

About Spool

  • Birthday August 1

Personal Information

  • Flight Simulators
    DCS - Hornet is primary module
  • Location
    United States
  • Interests
    Flight sims, Naval Aviation
  • Occupation
    Career E-2C/D Hawkeye NFO, CVN 74 Mini Boss 2017-2019
  • Website

Recent Profile Visitors

1370 profile views
  1. CVW-8 had VA-52 with them, so good chance we'll use that squadron when the Intruder comes out. But, I am partial to VA-145 and VA-165 personally. My step-dad was with the Swordsmen and I babysat for Boomer DHs when I was in high school lol. VFA-15 and VFA-87 were both A-7 squadrons before they were Hornets, so we're already set there!
  2. Hello again, Hoss, I hope all is well! On the tailcode, our squadrons are VFA-87 and 15, as well as VF-31. You are right, VFA-97 is a west coast squadron, but for us, we are east coast based, hence the AJ tailcode. You've got a lot of VA time there in your career (I actually moved to Whidbey in '79...but I was three years old, so I doubt we crossed paths - my father flew Station SAR there in CH-46s)...You must be looking forward to the Intruder module! Only two weeks away, right? Take care, shipmate! V/R, Spool
  3. RECRUITING STATUS UPDATE: F/A-18C All Categories: CLOSED F-14B Cat Other Drivers: CASE BY CASE F-14B All Categories RIOS: Open
  4. Perhaps...but DiCE doesn't have a line in the export.lua, so that is why it is confusing to me. No big deal though DiCE is a great program, but I have a modded countermeasures lua used through OvGME at this point, so I don't need it.
  5. The saga is complete! It was DiCE that was causing the problem. Removed DiCE and now TX Link works exactly as it should. Good stuff. I wrote Vaicom and suggested they put a note in their install notes about the DiCE conflict. Not sure why a countermeasures mod would impact comms, but it did!!
  6. As I said...I appreciate your help. I have tried all the things you have suggested, as well as contacted Vaicom directly. I am beginning to suspect it was DiCE that was causing the problems. I have uninstalled it, completed a clean and repair, and will reattempt. I don't want to give up, as others in my Wing are successfully using the TX Link as it was designed for MP operations...so, it has to be something in my setup. Hoping that DiCE is the issue. We shall see.
  7. This is only happening when IN the Hornet. Works fine outside the aircraft. I am about ready to shelve it and waste the $20 because it shouldn't be this difficult to get something working. I'll just have to make due with Voice Attack alone. I appreciate your help. I used the Search Topic function to find what I found in here...makes sense to have it all in the same place, in my opinion!
  8. Posting another log so I can clearly show what is happening. Starting at the bottom, this log shows when I am in the aircraft. I say "arm seat" to test the Hot Release bypass function. It works properly. I then press Comm 1 for the first time. It "should" open the VIACOM listening function (it does this when I am NOT in the aircraft in DCS) I say "kolkhi". VA recognizes the word, but because VIACOM is not listening, it is rejected with the red block. I key Comm 1 a second time and say "kolkhi". VA recognizes the word. But VIACOM is still not listening, so it is rejected. I key Comm 1 a third time and say "kolkhi". This time, VA recognizes the word, and VIACOM is listening, so it awaits further input. I key Comm 1 to close the VIACOM listening window. I repeat the process. It takes three keys of Comm 1 for VIACOM to listen for the command again. I am thoroughly stumped. Works as it should outside the aircraft...once inside the aircraft...takes three activations.
  9. I have not changed it from the default selection of NORM. Also, it does this in SP or MP, so that does not seem to matter...
  10. Separate issue...REALLY hoping this one is an easy fix. Working to get the TX Link function working so I can use VIACOM with MP. Have the VA commands set up as per the manual for TX Link. Function works as advertised BEFORE getting in the Hornet. Even while in the DCS menu, a short press of the Comm 1 switch on throttle opens up listening, a second short press mutes listening. However, once getting in the aircraft...it now takes THREE short presses of the Comm 1 to get VIACOM to start listening for commands. A fourth short press will make it stop listening. Then, another three are required to get it listening again. Has anyone dealt with this? I cannot figure out why it works the way it is supposed to BEFORE I get in the jet...then after I'm in it...it takes three activations of the Comm 1 to get it to start listening. Also, why does the log look like it is actually resetting itself, listing me entering the module multiple times...I was just sitting in the aircraft the whole time in this log. The double blue box "Listening resumed" followed immediately by "listening suspended" is messing things up. But again, I can't understand why it is behaving differently once I am in the pit, but works correctly outside the aircraft? AH! Thank you for your patience and additional instructions! I was missing the part about using the arrow keys rather than the mouse...I have my GUI back, THANK YOU!
  11. Well Max, unfortunately no dice. The menu comes up when I press LAlt Space, and when I click Move I get the four way arrow...but when I click anywhere on main display, nothing happens. Of note, when I press LAlt+Space, the menu comes up on the right edge of the main display, but the Config GUI is not there, or on the second monitor to the right of the main display. I suspect the only way to resolve this will be a complete reinstall of VIACOM...and since I can find the GUI through maximizing the window via Task Manager, I don't feel like going through that pain. thanks for the help though!
  12. Thanks Max, I will give it a try. I have tried the move selection with a right click in the task bar, but when I click the desktop, it does not relocate. So, hopefully your method will yield better results!
  13. Has anyone figured out how to deal with the bug when your Config GUI will no longer display on your screen? You get the taskbar window showing it is open...and if you go to task manager, you can maximize it...but I seem unable to get just the small sized Config menu to display anymore. I believe it happened after I dragged that GUI over to my aux monitor. It worked fine while it was open...but after closing out that session...it has never come back up. Just the tab in the task bar. I have searched and found a couple others who have experienced this...but have not seen a fix. Hoping there is one out there...but at least I can still access it through the maximize function, I guess. Very strange bug.
  14. It's possible! I did my U/I Mini training on Nimitz during her 2017 deployment, so you might have seen me there... -Spool
  15. Hey JackJack, so during my last deployment on Stennis as the Mini, we had low level blue floods aft of the island. Forward had low ambers...you're right forward and aft have different settings for when Boss yells "SET RECOVERY LIGHTS". The low level blues are so low that they are worthless if you come topside from underneath the ship and your eyes haven't adjusted...but if you're in the junkyard pre-flighting a Hawkeye (like I used to do...) they are JUST enough to not trip over tie-downs...most of the time!
  • Create New...