Jump to content

mdee

Members
  • Posts

    373
  • Joined

  • Last visited

Posts posted by mdee

  1. 1 hour ago, lester said:

    I wasn't able to reproduce it in singleplayer mission: both with hot start in the air and with cold start and take off, with my usual startup routine.

    But it's definitely reproducible for me in multiplayer. Unfortunately can't provide track because of that. This is how this effect looks like:

    Note that I didn't touch rudder pedals after switching to CPG seat.

     

    Yeah, that's exactly how it looks like.

  2. Hi,

    I have quite severe issues with George AI when hovering, the hover is unstable and makes operating from the front seat very difficult, sometimes impossible. The heli oscilates from left to right, 10-20 degrees each side. I have tried all George modes, doesn't make any difference. I have tried with an empty heli.

    I am using latest beta, I have triple checked my controls, no trim, no wind. I can hold a stable hover from pilot seat.

    Any ideas?

    • Thanks 2
  3. 6 hours ago, dburne said:

     

    All, right, so we don't know besides speculations. Fair enough, it's a bit of a shame though, VIACOM worked well for me for a good couple of years. Would be great to at least have an explanation from the dev himself, esp. that the software is still for sale. I really hope nothing bad happened to him.

  4. Hind and Viacom issue.

    I have an issue with getting Viacom to work with Hind properly. I have to say my command (using standard Viacom procedure) then press Hind specific radio trigger, otherwise command is recognized but not executed.

    Having comms menu displayed on the screen works around the problem.

    Any ideas how to solve this?

  5.  

    [...]

     

    It isnt (for DCS). And g-sync probably makes no difference whatsoever for DCS as very few people get frame rates that high.

     

    This is not true (just like the rest of your post which I removed, screen tearing is directly linked to GPU time/content frame rate and display device refresh rate). G-Sync (or free sync) will virtually eliminate all screen tearing, because G-Sync enabled monitor will adapt its refresh rate continuously to device/content frame frequency, so as long as frame frequency is reasonable (varies.. about 30 fps or higher works ok), there won't be any screen tearing. In practice, it works very well in DCS.

     

    I don't know about any large (45 inch +) monitors/TVs with G-Sync/Free sync, but I think there are a couple out there made by NVidia.

  6. I know it has been asked before but ED told me to reopen a new thread. I think we REALLY need an easy AAR option. It is easily the hardest part of DCS.

     

    It's already there. It's called "unlimited fuel". You will never have to refuel again.

  7. I have a separate ptt for discord, too. It is amazing how well SRS and VAICOM Pro integrate into the game communication system. I am an native American English speaker with a very neutral accent aside from a few southern words/phrases. My problems with recognition often relate to words with the same exact sound that require context to differentiate, so no amount of training will ever fix that.

     

    For example, if I say "two" <pause> "engage bandits" the command is recognized every time, but if I don't pause long enough it become "to engage bandits", which is unrecognized. Computers would have a much easier time understanding English speech if there weren't words with different spellings but exactly the same sound, "two, "too", "to". I also tend to speak fast, so I have to concentrate on not only the pause between the identifier and the command, but the speed at which I pronounce single words as well as the short pause between words in a phrase. Most of the time, I don't have to think too hard about it, but sometimes I hit a phrase or word that forces me to focus on what I am saying and how I am saying it.

     

    I'd try alternative VSPX processing, you don't need to pause between keywords. Works for me, although I turned it off because it doesn't allow for callsigns in the comms and I am used to it.

     

    I too have issues with words sounding the same.. I try to set up aliases when I can.

  8. Not sure if anyone else has this issue, but AOCS will only work on 284.00 AM in the hornet radios, comm-1/2.

    (2.5.5 or 2.5.6ob). If I try 071.00 or 142.00 the (:AM) doesn't show and is blanked out. Easy comms off.

     

    After trying on 071.00 for several attempts and much troubleshooting, thinking it was another problem, I decided to try the other two frequencies. That's when it manifested that only 284.00 worked. I'm fine with using only one freq, but I wanted to report my experience.

     

    Note: I've only tried AOCS in the F-18 thus far. Also, this is with manual tuning. I haven't tried setting up presets in the mission editor.

    Thanks.

     

    Edit: Just downloaded the latest patch and gave it a try. Now 142.00 is working as well, but not 071.00.

    So at least I now have two working frequencies to chose from, which is nice.

     

    I can't get AOCS to work at all, lately. Auto Briefing works, but "Crystal Palace, status/briefing" doesn't. I tired to tune to both 142.00 AM and 284.000 AM.

     

    Any ideas?

  9. Here is my experience:

    (This is more about Windows Speech Rec. than viacom) I am not native English speaker, but my accent is mild (been living in English speaking country for a long time). I've spent about an hour reading Viacom keywords/training speech recognition. No problems with VA recognizing me. I have 7 (yes, seven, I make music for fun and have specialized gear hooked up, plus 2 VR headsets, camera, headset) sound devices capable of recording, I just locked VA to my headset. No fumbling required.

     

    I know exactly what to say because I've read the manual and memorized phrases/protocols.

     

    I use Viacom with SRS and Discord at the same time. I have separate PTT button for Discord.

     

    I don't even know how to operate radios from keyboard. Total setup time was about 30 minutes, it took me about 2, 2-3 hours sessions to memorize most comms phrases, including JTAC interactions, by just playing the game.

  10. With a 2020´s GPU, CPU and lot of memory system... i don´t understand what the problem with clouds or smoke effects. Seems like the problem is to try to make improvements on too old effect with a old code that can´t extrat the best of modern systems.

     

    I could write about 4 pages about it, but just one random thing - translucency is a performance killer in VR.

  11. Problem is that ED can't make realistic flight modeling to F/A-18C or F-16C etc. They have in the agreement that they will nerf the aircraft real capabilities somewhat for security reasons.

     

     

    :lol:

    Yeah sure. A computer game is a security threat. This is one of my favorites when it comes to make believe, by the way. Local urban legend.

     

    I've heard AG radar is coming sometime this year. For now I just fly jets which have AG radar already available, if I fancy playing with it.

  12. I am done buying any modules for foreseeable future. Not only the goalposts are being moved as it suits ED, but also it's being announced in condescending way - I am tired of "we are special, therefore this is what you get" tone.

     

    Good luck on Steam. They can be quite effective in managing developers who don't deliver on EA or try to re-define EA.

×
×
  • Create New...