Moxica

It has been explained that the FCR find and assign targets, and loading them into the hellfire. But the hellfires still scan, find and choose target when they get "closer" Therefore they can not see the difference between a dead tank and a live AAA as they both represent a huge lump of metal. What I find contradictory, and don't understand in this context, is why then, do they miss when INU is out of whack? And with miss, I mean going 50-100 feet off target, and hitting empty ground. What selects that sorry specific point? Is it downloaded coordinates, or does the built-in agm radar hallucinate?

Thanks again, Raptor! -Much appreciated.

I understand what you are saying, Raptor, and thank you for patience and time. What I find "illogical" (according to the descriprion about prioritzing), I can explain with an example: Six targets in a PF. I fire six missiles in quick succession after a single scan. FCR skip to next target after I fire, and I wait for solid square before firing again. (I cant separate single targets in that cluster on the FCR screen, overlapping each other) Three missiles hit same target, leaving two AAA units unharmed. In other words; FCR prioritize same target thrice. Unless, of course, it is the limas themselves going for that metal chunk. But then again; Why do they miss completely when the INU is out of whack? I guess it will be easier when the link function become available. ..and the target could be lased?

Than what is the point of marking target with an "X"? Just to fire next one on the same spot, when there still are some unmarked, live AAA just nearby? I don't get it. I've seen three out of four hellfires hitting the same spot seconds apart.

Does not make sense. Is this the reason it prioritize a dead radar over a live AAA? Sending several missiles on the same dead target in same salvo? Because the missile may have been shot down? -Not a smart design decision, considering the price of a hellfire alone.

Not 100% sure, but it looks a lot like Bodø with "Saltstraumen" to the left. One of the strongest tidal currents in the world.

Glad to hear!

Current DLSS is the nvngx_dlss.dll version 3.5.0.0 in DCS There is a new version 3.5.10, and I just tried it; It is no revolution, but it makes for some improvements on ghosting. Or.. ghosting turns out a little different. If you like it, you keep it. If not, keep the old one. It is in the bin, and the bin-mt folder. You find it here: https://www.techpowerup.com/download/nvidia-dlss-dll/

Thanks, and happy new year, Flappie! None of these are relevant. I have disabled the hot plug a long time ago. Problem is so random, and not consistent. But most typical is the communications menu in AH-64 bound to the "left coolie" on the Thrustmaster throttle. Second, the trigger. I don't use any scripts that I am aware of. I have also seen this in a mission I made myself, using no scripts. Most controls are connected to a USB "Icy box" with its own power supply, but this one is connected through the USB on the monitor. I'm not excluding this as a possible weak point. (It has a short "leash" so I'm just a little hesitant to reorganize.)

Only in Beta: DCS need a reminder for my control bindings during missions. Many buttons dont't work until I open controls, press the button that takes me to its assignment, and I press OK. -Now I can use it again. Vanilla version does not show this behaviour. Not sure if bug/known/unknown/config error. Pls halp! Or smth..

I for one miss high value targets in black SS uniforms/leathercoats

FYI: I had a previous B21 in the aircraft folder, because that's what I had to do to make it work once upon a time. Problem solved. Now I just need to find the Hesco barriers and festival toilets. What asset pack was that?

I understand. I am restoring necessary ones only as i write. Folder looking neat now. Thx a lot!

Thank you. I tried, and it worked. Now I just have to move them back one (or five) at the time until I find the conflict. Sorry, I did not see that solution, because I figured it would be more work than it actually is. Plus, I will only reconstruct the ones I like and need.

Why would I "Delete everything you have under DCS/Saved Games/mods" (As if all other mods make it crash) I use most of them in my missions. Today I copied mentioned folder, and it crashed. I removed it; no crash. -Do you mean th CH mods? They all reside under "tech"

I know what causes the crash: It is the content of the mentioned folder. (CH Military Asset Pack USA 1.0.0) If I remove it, I'm good to go. But I really want to use those assets.

I get an error and no start with CH Military Asset pack USA 1.0.0: 2023-12-27 12:39:36.644 INFO SOUND (Main): Added sound path: C:\Users\nnnnnn\Saved Games\DCS.openbeta\Mods/tech/CH Military Asset Pack USA 1.0.0/Sounds 2023-12-27 12:39:36.664 INFO SOUNDER (Main): Loaded 60 sounders. 2023-12-27 12:39:36.732 ALERT Dispatcher (Main): Error running db_scan: ?:0: attempt to concatenate a nil value 2023-12-27 12:39:36.733 INFO APP (Main): application shutdown

Priority and No Fire Zone Data Transfer listed in green -"delivered" in the roadmap.

Fixed in recent update:

I'm trying to send fire zones to my AI wingman, but I get "NAK" every time. Need I search/learn more, or is this just not implemented?

Creating two "NF" zones did some trick today, and I could kill all main targets in one "salvo" of four missiles. Happy days! :)

Tied to replicate. One of the missiles goes haywire, most of the rest goes for the tank it seems: FCR.trk

Whaddya mean "clutter"? They are going for "clutter" now" They are way more picky/precise when lazer designated, and I have never seen them go for tank carcases like that before. Even less to just empty field spots. They be like "F*ck this spot in particular" Thank you for responding, Grennymaster! Thx, Bignewy! I figure, but I'm hesitant, because then FCR will reassign AND prioritize the old kills. I've been pounding "dead" tanks a lot that way.

I just don't understand how the FCR can lock target, but the missiles goes all over the place. Yes, I realigned INU, but still it looked like some fireworks factory on fire. Only the two first missiles hit. Then "Pew pew", randomly far off to the left. There is nothing there. Never was. What are they going for? How do they get assigned to those empty spots?

I find it a bit weird how there are registered a number of targets. (Each with registered coordinates?) And nothing in the system knows which targets are engaged and which are not; FCR locking on former missiles' target again and again. Seem like a very disagreable design decision.