cabzi

Ok, thank you Hollywood! I was nearly going crazy here!

Hi, I have big problems with the latest version. My game controls are gone (totally empty controls menu) if I have VA running and launch DCS (latest open beta). The problem stays if I run DCS a second time without VA. Everything is back to normal after I run DCS repair and launch DCS without VA. The problems started today after updating Vaicom. All was good last night.

Yes, ICLS mod works with F-14B.

All you need to know ->

Thank you for chiming in Victory. So, I take it should show "11" while on ab? I can't understand why it does not work on my end. There is a similar problem with F.F indicator. While on full MIL power it sits around "7". After I engage ab, it doesn't move one bit higher. Surely, it should considering ab consumes a lot of fuel..?

Not necessarily related, but does anyone know, if ENG RMP indicator is supposed to go past ”10” -> ”11” when afterburner is fully engaged? I could swear, it moved to 11 in release build but not anymore (after first hotfix patch).

Did something change in the hotfix patch regarding Engine RPM indicator? If I recall correctly it went from 10 -> 11 after engaging afterburner. Now, the RPM stays at max 10 while on full ab.

The option won't stay selected, but Jester will give landing callouts, if you have contacted ATC for approach. Just tested this in Caucasus Dogfight IA-mission and it works (didn't re-select option after DCS restart).

Same for me too.

Ok, I don’t own Viggen so wasn’t aware of that. Tbh, kind of an immersion breaker for me.

Hi, using trackir and there seems to be a problem with cockpit boundaries = you can move your head through the canopy glass. Never experienced this with other modules.

Hollywood, after today’s Vaicom update I can’t access configuration menu. Any clues, please?

Brilliant, thank you!

Hi Starway, any chance you could upload the package to Google Drive or some other faster and safer site than Mediafire?

I had this problem a couple of months ago. Reset keywords from control panel and restart VA. Copy-paste should work after this.

Yes, it does. On a side note, haven’t come across a mod, that wouldn’t work.

No problem, Goa. Had a frustrating day at work, so I also slashed back unnecessarely strong. Sorry man.

Maybe you should read more carefully and try to understand what you read. I never said you can't use NVCP vsync with gsync. I said you should never enable vsync from INGAME settings. Howtogeek and Blurbuster articles explain the very same thing (hint: page 14, Blurbusters article). If I have to keep correcting your writings at this pace, could it be, that maybe it is you, who don't have a clue? Besides, last time I checked, I am not the one with jittery/stuttery trackir problems..

I also use MSI v2 to set negative IRQs. I did a little experiment last night and tried different MaxFPS (graphics.lua) configurations. Other settings were as I posted earlier. - 180 (default) = no stutter - 60 = stutter and actual fps dropped from 60-70 fps (in-cockpit) -> 45 fps - 240 = seemed even better than default 180, but might be placebo After this I tried different TrackIr settings to induce stutter - Light Filter Threshold = 120 - 150, no noticable effect, no stuttering - Light Filter Threshold = 30 (min), lots of stuttering - Light Filter Threshold = 253 (max), lots of stuttering

Thank you for fast response. I should have been more specific with the problem. If I lock an enemy plane with radar (STT) and give radio command to engage my target, nothing happens (even the verbal command is left out). AFAIK, this works ok with other aircrafts (F-15, Su-27, Mig-29, M-2000).

F-18 wingmen do not comply with "Engage My Target". - Wingman, engage bandits -> works - Flight, engage bandits -> works - Wingman, engage my target -> no response - Flight, engage my target -> no response

If you are using a GSYNC monitor you should never enable VSYNC from ingame settings: https://www.howtogeek.com/270672/how-to-enable-optimize-and-tweak-nvidia-g-sync/ In short, the rule is: Leave VSync enabled in the NVIDIA Control Panel, but disable it from within games. Only disable it for an individual games in the NVIDIA Control Panel if you really need to reduce input latency as much as possible.

Awesome, thank you!

What phrase are you using? What works for me is "Tanker (wait for blip-sound), approaching to refuel." When close "Ready pre-contact".

Ok, I think I understand your point of view now. But, I can't agree with the statement that trackir needs to run with stable 60 or 120 fps to get stutter-free experience. I get 60-70 fps sitting in the Hornet looking straight ahead. If I look up to the sky, my fps jumps to 100-110 fps. I don't know what gives, but my trackir is stutter-free even the fps fluctuates by a large margin. *shrug* Anyway, just wanted to share my view on the matter and correct the wrongly stated fact about "always leftalt + enter".