Zyll

My realistic slew is definitely off, I've had it off since the feature existed. When I turned it on to test, the DESIGNATE freeze feature then worked.

Hi team, I noticed with the new SLAM-ER, the behaviour of freezing the picture to slew via TDC to the target does not work as in Wag's video, IF you have realistic slew turned off in the Special settings. You don't get the DESIGNATE indicator at all, per the screenshot below from Wag's video:

Do you guys still delete fxo and metashaders2 folders after each DCS patch?

i get alot of these type of messages in the dcs.log, i assumed they are symptoms of why it takes so long to load in: 2021-05-19 00:03:20.520 ERROR DX11BACKEND: Can't find precompiled shader model/def_material.fx:BLEND_MODE=1;DECAL_UV=tc1;DIFFUSE_UV=tc0;DIRECTX11=true;METROUGH_MAP;NORMAL_SIZE=3;SPECULAR_UV=tc0;TEXCOORD0_SIZE=2;TEXCOORD1_SIZE=2;USE_DCS_DEFERRED=1;. 2021-05-19 00:03:20.520 INFO DX11BACKEND: Compile shader: model/def_material.fx:BLEND_MODE=1;DECAL_UV=tc1;DIFFUSE_UV=tc0;DIRECTX11=true;METROUGH_MAP;NORMAL_SIZE=3;SPECULAR_UV=tc0;TEXCOORD0_SIZE=2;TEXCOORD1_SIZE=2;USE_DCS_DEFERRED=1; 2021-05-19 00:03:20.524 ERROR SECURITYCONTROL: Manifest check failed for file 'bazar/shaders/deferred/shadows.hlsl' 2021-05-19 00:03:20.524 ERROR DX11BACKEND: Can't open include file: bazar/shaders/_hmd.hlsl. 2021-05-19 00:03:20.528 ERROR SECURITYCONTROL: Manifest check failed for file 'bazar/shaders/model/functions/diffuse.hlsl' 2021-05-19 00:03:20.538 ERROR SECURITYCONTROL: Manifest check failed for file 'bazar/shaders/deferred/atmosphere.hlsl' 2021-05-19 00:03:20.545 ERROR SECURITYCONTROL: Manifest check failed for file 'bazar/shaders/deferred/shadows.hlsl' 2021-05-19 00:03:20.548 ERROR SECURITYCONTROL: Manifest check failed for file 'bazar/shaders/deferred/atmosphere.hlsl' 2021-05-19 00:03:20.552 ERROR SECURITYCONTROL: Manifest check failed for file 'bazar/shaders/model/functions/forward_def_ps.hlsl' 2021-05-19 00:03:20.552 ERROR DX11BACKEND: Can't open include file: /deferred/_hmd.hlsl. 2021-05-19 00:03:20.553 ERROR SECURITYCONTROL: Manifest check failed for file 'bazar/shaders/deferred/shadows.hlsl' 2021-05-19 00:03:24.999 ALERT DX11BACKEND: Error: Can't find precompiled shader for effect model/def_material.fx:BLEND_MODE=1;DECAL_UV=tc1;DIFFUSE_UV=tc0;DIRECTX11=true;METROUGH_MAP;NORMAL_SIZE=3;SPECULAR_UV=tc0;TEXCOORD0_SIZE=2;TEXCOORD1_SIZE=2;USE_DCS_DEFERRED=1;. Recompilation process will take some time, please wait (this situation should not occur on end user PC, if there is no manual shader editing)

i too run this version and get extremely long load times, much longer than I got in 2.5.6. I've been running Mustang's Caucasus terrain textures as well, but I don't think that's it, as the long load times affect other maps too. I thought that perhaps since 2.7 the habit of deleting fxo and metashaders2 folders after each patch was hurting me, so I don't do that anymore.

Right, that's a fairly recent change, within the past 5 patches or so. You can have either/or, not both.

Try the RECCE event hotas binding. That toggles the HMD on and off

we have a trk file for ED to reference, showing our challenges with the carrier during a full op. https://drive.google.com/file/d/1mytPiAUW911BzFbQWF4RkU_O8AcxhTX7/view?usp=sharing

Further to this, I think that the flight that has a member taxi off their parking spot first, is the first flight authorized to hook up to the cats. The next member of a different flight to taxi will make their flight be #2 behind the first group. This was the evidence that we saw during a recent op: Spawn order ENFIELD_Aly UZI_Spang ENFIELD_CannMan ENFIELD_SpencyD UZI_Zyll - first flight to taxi ENFIELD_Analogy - second flight to taxi DODGE_Reflex DODGE_Tero DODGE_CrimzN ENFIELD_Spency fail hookup to cat4 ENFIELD_CannMan fail hookup to cat3 ENFIELD_Spency fail hookup to cat2 ENFIELD_Analogy fail hookup to cat1 ENFIELD_CannMan fail hookup to cat2 * UZI_Zyll to back of boat, then succeed hookup to cat1 ENFIELD_Aly fail hookup to cat4 ENFIELD_Analogy fail hookup to cat2 DODGE_CrimzN to back of boat ENFIELD_Aly fail hookup to cat 2 ENFIELD_Spency fail hookup to cat1 * UZI_Spang succeeed hookup to cat3 ENFIELD_Analogy to back of boat ENFIELD_Spency to back of boat ENFIELD_CannMan to back of boat DODGE_CrimzN fail hookup to cat4 DODGE_Tero fail hookup to cat3 * ENFIELD_Analogy succeed hookup to cat1 * ENFIELD_Spency succeed hookup to cat2 * ENFIELD_CannMan succeed hookup to cat3 ENFIELD_Aly to back of boat DODGE_Tero to back of boat DODGE_Reflex fail hookup to cat1 DODGE_CrimzN to back of boat DODGE_Reflex to back of boat DODGE_Tero fail hookup to cat2 * ENFIELD_Aly succeed hookup to cat3 * DODGE_CrimzN succeed hookup to cat1 * DODGE_Reflex succeed hookup to cat3 * DODGE_Tero succeed hookup to cat1

You are using sensor select right (assuming the radar is on the right DDI) to lock?

a couple of post 2.7 bugfixes sounded like they were addressing this issue, but it still is not working as expected. Referencing the following from the patch notes: https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.0.5118/ HSI/SA are oriented track-up but color map is oriented heading-up - Fixed https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.0.4625/ Setting Map North Up for HSI makes it North for Map on SA Page - Fixed I'm just wondering if this bug is what's being worked on, as it has been 2 years and I was excited to see it might be getting addressed. Regards, Zyll

You need to switch to degrees minutes seconds decimal-seconds to be able to hit a vehicle in game

To further answer your question, JTAC is giving you degrees minutes seconds if it's ##'##'## format. If it were ##'##.## it would be degrees minutes decimal-minutes. Regardless, both are not accurate enough to hit anything smaller than a farmer's field. If you want to practice precise PP JDAM drops, you can get precise coordinates on the F10 map by cycling left-alt Y to get different coordinate formats, then place your cursor over a target and take down it's precise coordinates. Then go back into your jet and configure for PP.

are there any known issues using this with OpenBeta 2.7? Thanks in advance

Yeah what Bunny said. You may need to weasel your own HARM to get the SAM to emit and stay emitting until the missile reaches its target. I assume that's why there is information in PB mode about your ETA to target, as well as the missile's ETA. I find flying on the fringe of the radar range ring in the SA page is a good strategy, that way you can fly out of range if fired upon.

My advice, once you have managed to hook up with the basket, fixate on the sight picture of the pod on the wing of the tanker. Keep it the same size and at the same position on the top of your HUD. If it starts to drift, do minute adjustments to bring it back to the fixed position. If it's starting to get too big in relation to the top of the HUD glass, let a tiny bit of throttle off, then bring it up again. Doing it this way will even serve you well if the tanker starts to bank into a turn. Good luck! Sent from my SM-A715W using Tapatalk

I would only use night vision if I need to spot a sparkle, otherwise I would always prefer HMD. Sent from my SM-A715W using Tapatalk

Yep, rename your files so they sort in the order you desire. I use a numbering scheme like 010, 020, 030 Sent from my SM-A715W using Tapatalk

in today's openbeta patch notes, there is the following line: MP. New network predictor for aircraft. Safe to say that the change discussed in this thread have now gone live?

Our group likes to use the 7 o'clock position as a visual reference to know when to break. Our procedure is once you see your lead at your 7 o'clock, you are safe to kiss off.

Yep, that's what you would think, but give it a try, and I think you will notice that we need to give it just a few seconds buffer time for a proper alignment. Edit: in response to Brun's question

It does not break integrity check

I give it 100 seconds to be safe. If you switch right at 1:30 you will get an advisory warning and the alignment fails.

Are you running the OpenBeta?

My recommendation is to learn the laser Maverick with self lasing first, and that should (hopefully) correlate with what you are reading in Chuck's guide, and seeing in Wag's video. The JTAC is just adding more complexity to your situation, and understandable frustration. Working with AI JTAC is a whole other category of material to learn. So hop in a mission with easy to find ground targets, and load up with AGM65E and a litening pod, and then you should be able to follow the instructions. Good luck!