slikbaz

Kudos to ED for the performance improvements recently that allow me to fly VR smoothly online on my laptop.

Basically you can either use in-game PTT buttons or SRS PTT buttons. In my opinion it is better to just set them through SRS because otherwise you have to individually bind them for every module and search for the relevant controls which will be different for the F-18 and Huey for example. Then you can set SRS to "ALWAYS allow SRS hotkeys" and disable "Allow INCOCKPIT DCS controlled PTT" and the controls you set in the SRS controls tab should work. Another thing I do is "Radio switch works as PTT" enabled in the settings, then I map radio 1, radio 2 etc. Otherwise the radio buttons work to select the radio, and you have an additional PTT button. As a side note I also disable the transmission effects because some people already have poor quality microphones. With these settings you will still be able to tune the radios using the in-game radios of modules with your mouse, and can use the overlay for combined arms or FC3.

Yes I think he is wrong, it should work fine. You may need to re-assign your controls by clicking "load" or whatever it is in the input assignment and selecting the correct files.

Seems they have vanished from SkateZilla's post http://forums.eagle.ru/showpost.php?p=2548018&postcount=4 Anyone happen to have a list?

As someone already mentioned, this exact same issue existed on the F-18 just a few months ago (firing 120 in TWS gave an instant RWR warning). It took a long time to get fixed as well. The conspiracy theory is ridiculous, just wait and it will be fixed. There are hundreds if not thousands of bugs that need fixing and it takes time.

IMO Jester is not too bad. There are people that are successful using him even on PVP servers. There are some annoyances, for example when using TWS there's no way to force him to IFF a target or to tell him to change the Phoenix launch order, but hopefully heatblur will continue to improve him. Certainly it does not compare to a real RIO, but I think it would be a bad business decision to make the aircraft completely un-flyable without another person.

You sure you are actually in afterburner (checked F2 view or fuel flow of 250+)? Or maybe too heavy or raising flaps too soon?

In the F-18 I have found that the communications menu keybind (default of \ I think) will not work after take off with easy comms off. What works instead is the COMM 1 or COMM 2 bind.

So I'm pretty sure I saw some video a while ago where the datalink contacts on the HSD were also repeated on the radar page, like in the hornet - has this been removed? If not, how to enable it?

Thanks for the reply, I did verify already and it found 1 file to fix, but the crashes continued. I'll try a larger pagefile and hopefully either the DCS patch or Windows update today will help.

Log attached. It doesn't happen every time, but most times. Other than that it seems to run fine. - On latest open beta - Windows 10 is up to date - Tried various nvidia drivers from the last few months - Tried validating files - Tried deleting fxo and metashaders dcs.log-20200414-203856.zip

If you guys did not already, try to roll back Nvidia drivers to early 442.x or the latest 441.x, helps a lot. The 445.x is much worse for DCS performance.

PTCL internet huh? :lol: :helpsmilie: But yes it probably won't be more than that, if I recall correctly from when I switched. At the time I had Caucusus and PG.

Post a screenshot of your DCS graphics settings. The extra ram might help - I have a friend who went from 12 to 32 and it made a huge difference. Also the current beta has a lot of performance issues. It can be helped somewhat by going to 442.xx nvidia drivers, but for the rest we'll have to wait for a patch (or go back to stable).

I rolled back to 441.87 and they got a bit better. Not as good as DCS 2.5.5 but much better than 2.5.6 with the new nvidia driver.