Jump to content

Wolf359

Members
  • Posts

    350
  • Joined

  • Last visited

Everything posted by Wolf359

  1. I love this idea, but am I able to "clone" the waypoints from the original aircraft, or do I have to set them up all over again for each plane?
  2. No, that didn't change.
  3. Working in the mission editor and have something simple set up for the F-18. Tried to edit and save as for each of my aircraft. The A-10C works fine, but the rest don't load the mission; they merely open the map as my primary view. The only changes I made were the aircraft and where they start parked. Then just saved as new title. One more thing: I was setting up nighttime versions for each, set the time to 23:30. But doesn't seem to work. Thanks for the help!
  4. You are absolutely correct and spot on! I believe it is Windows/driver issue, and found the workaround. My default sound in Windows is my speakers. Set windows default sound to my headset, click a tx button, then back to my speakers. Go into Viacom CP and reset redirect device. Then it works perfectly. May be a realtek driver issue. I'm sure if I left VoiceAttack open when I am not using the PC it would be fine. I'll try that, but too used to shutting everything down when not in use. Apps, that is.
  5. I had the audio redirect working last night, and now nothinig. I've tested in VA without DCS started up. This seems to be a VA related issue, or the Vaicom plugin. When I depress the TX buttons, I get the "kerplunk" prompt, but nothing comes through my headset. Of course, when I turn off the redirect, all works fine through my speakers. Any suggestions? Aaaand now it works. Have no clue. I did nothing.
  6. Speaking of comms, is there any way to lengthen the timeout for being logged into the forum. My log in times out before I can complete a post.
  7. Just to be very clear, he's not the only one with this issue. Unfortunately, it's a bit intermittent. I will be sitting on the ground, cold and dark, battery on, press \ and comms menu comes up. Tried talking to ground crew. Nothing. When I CAN contact ground crew I tried having them connect external power, then tried contacting ATC. Nothing. Started right engine, keyed in the frequency for ATC, can contact them. Request startup - it's a bit after-the-fact at this point. From here all is good until I am in the air - departing ATC frequency is assigned to com1, and destination ATC assigned to com2. I press \ and get nothing - no menu, nothing. Tried re-keying the frequencies and still got nothing. When I get home tonight I will test again and test if VoiceAttack has any effect on this. Forgot to mention: my issue is with the F-18. I haven't tested in the Viper yet.
  8. I'm experiencing similar issues in stand-alone mode - not on the servers. And this is since the update. Can't contact ATC for start up, etc. I found that I have to be partially started - right engine - and key in the frequency before I can get the clearance to start up. This wasn't the case before the update. I even tried having the ground crew connect external power first. Same result. This is in the F-18.
  9. Thanks for the info, gents. Pro it is.
  10. I know this is a passive vs active comparison, but is there really ANY difference that I would notice in performance, etc?
  11. Eh-hem... If I use the updater utility to switch between versions, do I have to install my modules every time?
  12. How quickly is quickly? It seems to want to download and install all over again.
  13. Nevermind. Found it.
  14. Nice! Where is this updater tool??
  15. That's what I was thinking also. I mean, open beta is stable as it is; they just happen to test more stuff out on it before bringing it over to the "stable" platform, right?
  16. Which version are most of you flying: Open Beta or live 2.5? Do you keep both loaded on your PC? I have both loaded now only so I can fly the Viper. I did not load any other modules into the open beta platform. Just curious.
  17. Great idea, Don! Thanks!
  18. Good to know! Thanks Emmy. Initially, I was starting from fast action, Cold and Dark.
  19. I just checked all three maps. Only Caucasus has an additional Blue airfield; the rest are Neutral. Nevada and Persian Gulf, only the start-from base is Blue; all the rest are Neutral. So you have extremely limited repair stations; other than Caucasus, return home for repairs.
  20. That explains it. I was on Neutral airfields. I was working on my navigation skills on the Nevada map. I think ALL those airfields are neutral. Thanks guys!
  21. When I land at another airfield, I have contact with ATT, but I haven't been able to communication back and forth with the ground crew for refueling, repairs, etc. Do I need to be at a specific area on the airfield? Thanks
  22. I'm running on an AMD RX 570 8GB. I see a lot of recommended setting for NVIDIA, but trying to find some for the AMD. Thanks!
  23. Qualification Missions I'm still learning the F-18. not rushing anything. When I fly any of the qualification missions, is there any notification of mission ending? I flew the navigation qualification for Caucasus and when I landed, nothing. I used Heading AP, and I didn't shut down the aircraft. Do either of those things affect the mission outcome? In other words, is there some type of reward/award attached to these types of missions? Thanks!
  24. I read some of those reviews as well, and it made me extremely hesitant. However, I noted the dates of the reviews and most were during the Saitek version. The Logitech (grey) versions seems pretty good so far. I like that the switches and switch guards on the throttle quadrant are metal, and they are toggle switches. That means they each can be bound to dual actions/commands. The throttle is smooth - no snags like the T16000m throttle. It is a bit stiff for my taste, even when loosened all the way, but I've read from other posts on the forum that this goes away after a couple of weeks' use. When I booted up DCS and went in to set up axis/curves, the stick was not centered on either axis. I went into the Logitech software and ran the calibration for each and issue resolved. I hope this helps you out.
  25. Good info, Bearfoot! If something doesn't crop up in three years, odds are they won't. Three years is a decent lifetime. Good thing is, REPLACE or REFUND. I'm good with that. That's like a three-year tryout in a worst case scenario. Maybe I get lucky, or maybe I have a refund to put towards the Warthog HOTAS. :)
×
×
  • Create New...