HR-Crumble

Hi all, Scenario - 2 ship of either hornets or vipers (makes zero difference) set to travel to waypoint X where the ROE changes to designated only and the attack group action is given. Target is either an SA-6 or SA-11 or SA-10. AI won’t fire on an inactive SAM site as we know so they are set to red state. ISSUE - AI will not fire unless target is exactly 47nm or less away. 48nm? No. 47nm? Yes. I chose three different Sam sites to test individually to see if it was something to do with detection signal of the larger Sam’s etc but that makes no difference. Despite target type, AI altitude, speed, heading and if the Sam site is in a valley or open ground the AI will not launch greater than 47nm. 47nm is fine for SA-6 and SA-11 but not the SA-10 as it has an approx 70nm launch range. Is 47NM the max AI launch range?

Nice one thanks mate.

Can we confirm the nothing is old or new clouds?

Where are you seeing the density setting? This option hasnt existed in Mission Editor for nearly a year? Maybe even more.

Negative on any lens effects or motion blur etc.

No DLSS is enabled - it looks horrendous for me. Just DLAA. Sharpening 0.31.

Evening All, Happy Holidays! SYSTEM SPECS: 5600x OC 3700Ti OC 64Gb RAM Gen 4 SSD 32” Curved 144hz Using MT release System can give me 144fps no problem. ISSUE: I’m struggling since 2.9 on DLAA V MSAA. For me DLAA is smoother and gives a better ‘image quality’ and ‘texture quality’ to my eyes on all panels, materials and terrain etc. BUT the ghosting is awful - bullet tracers look like hosepipe water, smoke is fuzzy, jets especially in F3 flybys ghost like a mother! Dials when they spin with numbers also blur and number counters also. MFDs also not as sharp as 2.8 days. Installed the latest 2.9 patch from a few days ago and the ghosting is slightly better on DLAA but after reverting back to MSAA this seems almost worse than pre-2.9 MLAA. Still have jaggies and the textures look flat compared to DLAA. I’ve got everything set to high/ultra etc as I always have. Now I’m torn between better looking visuals except for awful ghosting or no ghosting but flat looking textures and jaggies. What are your thoughts? Can I try a different combo of settings? Have you guys had a similar experience? Crumble.

Hey all, firstly what a great thread thank you to the OP and others for keeping it going. I’m new to this so I’m starting small - I’m looking at just doing a ‘half UFC’ at first - essentially just the Harrier key pad within a 3d printed frame and box and two rotaries on the bottom. Would someone mind pointing me in the right direction as to how I create/purchase the key pad board circuitry underneath? I’ve used the STLs in this thread to print the keys them selves. KR, Matt

@Strale where did you get the keys from for the UFC keypad?

I had this issue last night flying at night on Syria. In the Harrier random white strobe flash almost like a flashback or firework in the night sky.

Thank you very much for that. Much appreciated.

Hi all, Would this ME scenario work without script? I’m trying to work out how to get a reaper set to AFAC to search along a route (highway for example) and find targets and then it sends a message to the pilot with Lat and Long. I don’t want to do it via 9L. More a simple message. Crumble

Hi all, Im working on a few Gulf War period missions for my group and I’m looking at creating kill boxes and having a drone act as a FAC-A ghat players would switch to the FACS channel and get the drone to radio back the LatLong of any targets they find in their kill box. Anyone tried anything like this before. I have successfully got the Drone to move across a F10 User Draw box and cover it all in their flight path no problem. It’s the radio coms I’m looking for help on. I have a trigger to activate a radio menu add item “contact Trident”. When this is pressed how would I get the logic to radio back the latlong? Cheers! Crumble

+1 and also spawn statics on triggers.

I’ve raised this before in the forums as it often throws people in ME. Most airports in DCS have a ‘1st choice’ direction for TO and L - even if you set a few kts wind it won’t change AI jets or when you call ATC to take off into the wind. You need to set a minimum of 6kts wind to get AI to acknowledge an into wind TO and L. The exception to this rule is as mentioned by some users above - some airports have only ever a fixed active runway due to geographical or city restrictions. For example PG Map Khasab and some others I can’t remember right now on Caucasus map. Set 6kts and you can set the active with wind direction. Hope that helps! Crumble.

Hey PrestonFlying - glad the page file worked for you - can you share how you set it?

Hi Bignewy, Thanks for your reply - I have tried it with a fresh install as well on the same PC which doesn’t have any mods. KR, Matt

Hi ED, Another CTD since this update - happens mostly at night in a simple or complex mission. Have tried fresh copies without any mods etc. Have also checked temps and voltages and memory issues my PC - all within normal params. KR, Crumble Latest logs attached. dcs.log dcs.log.old

Happens on everyone’s DCS I fly with. katest OB achingly slow to load up from windows. Achingly slow to load into simple miz or training missions or online. Achingly slow and hands often on quitting the app. Worse in MT but also bad in ST. Is this being addressed for next update?

@Flappie this issue is exactly what I’m seeing on the latest patch from July 2023. On both ST and MT.

Hi Flappie - not sure why yon can’t see the video as it works for others. It shows the stuttering. As above it happens in both MT/ST. Cheers, Crumble.

Hi all, ever since the last three updates I’ve noticed when viewing externally F3 flybys and sometimes a second jet (wingman etc) in the background will flicker. It’s nothing else in the scene that flickers just the jet. I haven’t changed any hardware or settings in game. 5600x 3070Ti 32Gb Ram. Water cooled. 55C in game. Happens on all modules, all jets, all maps and on both ST/MT. No reshaders or image adjustments. Same monitor. FPS always shows 100+. RPReplay_Final1688498026.mov Attached is the issue from a replay. Anyone else had the same? Crumble

Okay so you have to look down and left as well and it’s not fully in view without doing that?

Hi all, it’s taken me about a month of filling around with FOV, camera angle, tracking IR settings and head position but I always end with the same issue: My view of the cockpit always cuts off the top of the engine RPM display so I have to almost lean down and forward to see the rpm. Anyone else have anything similar with the hornet?

Can’t really say much more than the title - since the last update the HMD doesn’t acquire targets in close range with the 9X as quick as it used to. Too many variables to say what/who/where/when/why. Standard engagement HMD not as responsive. ~Crumble