[Multithreading: Flipping between F10 and F1 Causing intense, and lasting screen-tearing in VR]

Please consider the findings in this video as well: 

It investigates and speculates on the effects of multithreading, heavy parallel IO and the number of cores available.

[2.9 Peterovich AI cannot correctly identify the target]

11 hours ago, FusRoPotato said:

He is extremely slow to find targets with ATGM as well, close targets out in the open. Eventually, after maybe a minute, he will spot 2 of 10 targets just 200 meters away. ATGM just became useless as solo pilot. 

I can confirm and described it here, too: 

 

[2.9 Peterovich AI cannot correctly identify the target]

11 hours ago, KoN said:

Can confirm while in the Grayflag servers. 

Petro can't lock or spot targets . Over and over search areas and he does not see or lock any targets with a good time limit . I can see the targets right in front of us . 

When you roll away from ground fire he locks on the roll . Very odd . 

Lots of stuttering also . 

We are so close to ground targets that missiles won't matter . 

This Petro man needs training ...lol . 

Bug report . 

I can basically confirm this, also from the Grayflag servers.
Petrovic seems to find air targets quite well, on the ground it is very much hit or miss. Infantry seems to be basically impossible, ground targets are sometimes picked up fairly well, sometimes the ground unit *already engages me* with its gun and he can't lock it up.
Unfortunately the Hind crewed with the AI gunner has lost much of its effectiveness.
I understand that there should be a difference to George (from the AH-64), who has much better sensors, but when I as a pilot without a zoomable periscope can spot targets then Petrovic should be able to find them easily. And in particular if these units are already firing their weapons. If tracers or missile smoke is coming from a unit it should be trivial to find for the gunner, in my opinion. I really hope this mechanic get's properly adjusted. I find it to be very much overdone in its current iteration.

[Interact with Airport stockpiles through scripting.]

Pleeeeeeeeeease.  It would add a lot of depth to long-running, persistent campaigns.

[Bombs and Rockets won't drop off pylons, Crosshair won't work sometimes]

Cunning Fox, I had a bug before that on mission start the jet was already in DG/DM. I could have sworn that was patched at some point though.

 

 

 

When you get in, select Return to Search mode or whatever it's called even if it looks like you're already there.

 

Had the same problem in the bombing training mission, this was the solution. For whatever reason the radar (although off/stdby) had the piper in DG/DM mode. Return Search reset the piper.

[Can listen, but can't talk to AWACS]

If "IC" means some kind of installation check like Steam's "verify installation" then I assume the answer is No.

[Can listen, but can't talk to AWACS]

I came across a patch or mod to put the AWACS and JTAC options into the KA-50.

 

After closely looking at the files included in the little mod I made out only two lines of code that actually include the menu items. By adding them to my Huey's config I got both AWACS and JTAC to work.

 

You need to do the following:

 

1. Find the file called "comm.lua" in your Huey's config. It is located inside DCS here: "\DCSWorld\Mods\aircraft\Uh-1H\comm.lua".

2. Make a copy of the file for backup. It is ok to make a copy right in the same location.

3. Open "comm.lua" with a text editor.

4. Scroll to the very bottom of the file where you find bunch of lines starting with "utils.verifyChunk(utils.loadfileIn( ...".

5. Add the following two line to the end of the file:

utils.verifyChunk(utils.loadfileIn('Scripts/UI/RadioCommandDialogPanel/Config/Common/JTAC.lua', getfenv()))(9)
utils.verifyChunk(utils.loadfileIn('Scripts/UI/RadioCommandDialogPanel/Config/Common/AWACS.lua', getfenv()))(10, {tanker = true, radar = true})

This will add the JTAC menu as F9 and AWACS as F10 items.

6. Save and close the file. Done.

 

As with all other radios in the Huey you have to make sure to be on the right frequencies on the right radios to get a response. AWACS works as usual, for JTAC to show up in the menu make sure you have weapons loaded (took me a while to figure that out :lol: ).

 

I attached a little mission to test this out.

 

I assume this "mod" would work on all aircraft in this manner.

My understanding is that the two lines of code simply chain load two other config snippets that implement the JTAC and AWACS menus.

 

Have fun! :joystick:

Fast Mission AWACS Test.miz