KulleAeyd

Hey @currenthill just as an addendum to my poste before, I was able to get that DCS-DTC mod to work. As it is now, you can add emitters to a text file, and then have the utility upload them as MAN entries to the HTS/HAD function. You must have the mod EXE running in the background with DCS, and it seems that when you "upload" the emitters the app will just run a macro to punch in all the codes to the UFC. You can even see the buttons being pretty quickly in the background when you do this. As this app works in the background on a running DCS, i guess there is no way to just update the SAM tables on the HTS/HAD before you fire up DCS, but you have to do it each time you run a mission. I guess it's a bit better than having to punch them in manually though. Also, it seems the only way right now is to add your new emitters is to manually add them to his text file. I've told him about your new emitters and gave him a link to your HARD RWR page so he knows the codes. Not sure if he will add all those new emitters though. I did ask him to provide a way to add new emitters through the app UI instead of having to add them manually in the text file. We'll see what happens

Coming at this from the outside, the file path in your mod zip isn't entirely clear, as there is no distinction between the save game folders and the core folders. It just starts with SCRIPTS and works it way down. Both the save game folder and core folders have SCRIPTS, so it's not easy to tell. And although the core game file structure only has AIRCRAFTS, it's not really clear if that should be created in the SAVE GAME tree, as you are creating other folders inside of the MODS directory. Anyway... I'd kindly suggest that you make this distinction in a readme that's included in your ZIP and on your FAQ as well so the user knows the put it in the core game folder if that is where it needs to be PS - initially i didn't put the file in the core game folder. I put the folder in the MODS/TECH folder like all of the other mods. Although I didn't test all radars, for sure the S-350 did display the "28" in the RWR, so maybe putting it in the MODS/TECH still allows it to work? PPS- just now I added "529" to the LIST/HTS and the NASAMS radar still did not appear on the RWR, but it does appear on the HTS/HAD. When I added "509" and "510" to the LIST I received the indication on the HTS/HAD for the S-350 (and it also appears on the RWR). Regarding the DTC mod, I tried that yesterday. Unfortunately, there doesn't seem to be a way to add new radar codes. It has several pre-added, but I can't figure out how to add new ones like your S-350 and NASAMS codes. I've put a message on their Discord, but so far no reply

Hi - for clarity, the FAQ on CH''s site says only to put the assets in C:\Users\yourname\Saved Games\DCS.openbeta\. There is nothing about putting them in the core game directory. @currenthill ? But to confirm, i also placed RWR LUAs in the core game directory too. I received the same result - the CH version of the NASAMS didn't display on the RWR. I tried the CH S-350 as a control and it did appear there too with a "28". Both SAM systems did not appear on the HTS/HAD as was my original issue, but CH said this wasn't possible as far as he is aware. @currenthill from my earlier post, are there any LUAs you are aware of that allow you to update the codes for radars for the HTS/HAD? Thanks

Appreciate the heads-up. I've tried this too with the community's "high digit SAMs", and i guess they are up against the same issues, as their radars don't appear on the HTS/HAD either. I really wish ED would put a priority on the DTC - I haven't seen any updates on this in forever. I think there is a community mod DTC which I'll check out and see if it works. Also, do you know if there is a LUA text file where the codes can be entered and be more permanent? When I looked at the chaff/flare program update, i know there is a LUA file where you can set the burst quantities, delays, etc. and they will stay between missions, but it gets written over with each update, but at least there is something were you don't have to go into the DED each time to update the jet.

HI CH - thanks so much for all the hard work you put into these asset. I really enjoy using them. I think I have identified an issue, but i am not sure it's been reported before. I created a simple mission where I have an F-16C with HTS trying to attack a Patriot site. I have used the latest version of your USA asset pack (1.0.0), and I have installed the RWR/HARM pack (1.3.1). What I notice is that while your three versions of the Patriot radar appear on the RWR, they do not appear as a possible target on the HTS/HAD display. When I swap out the Patriot radar for the default DCS Patriot radar asset in the ME, then the "P" will appear on the HTS/HAD. Let me know if you've seen this as an issue. Also, just to verify I have installed the RWR/HARM folder correctly - I have installed it in the same MOD/TECH folder as I've installed all the other mods you've made. I mention this as it seems the subfolders are a bit different in this particular mod, so just wanted to make sure it's in the correct location. I should also mention that in a subsequent test of your NSAMS assets, while I was able to get the ARAAM-ER to fire on me, the radar never showed up on my RWR, and I never get any indication of the radar on my HTS/HAD. Thanks.

Addendum to my above message - it seems now that the F-14 is silky smooth on the Nevada map. No changes to my settings, only a new DCS M.2 installation drive. I'll try the others maps just to be sure. In a way though, if the drive was the issue, it would be a shame for those who still have mechanical HDDs. I still can't imagine that my setup was too different from the norm these days. Anyway, it's a big relief to know that was money well spent.

Hey BA - thanks for the reply. While I'll try anything, I'm not sure this will work. 1) this is the same setup that MW used in his video explaining the F/A-18 video options/control set up and my rig is fairly similar, 2) I've been using that setup for all my other planes and it works just fine, and 3) if those two items where at fault, i would be getting generally lower FPS across the board, not only when i start to turn. Note: this happens in the F-14 no matter what map i am using - even when i am out to sea or on Nevada with nothing near at all any my other plane's FPS is running 100+. It's an odd issue for sure, and since there are aren't a lot of people complaining here I'll have to assume there are some things underlying and undiscovered. Just switched to an M.2 for my DCS directory. Hope this helps. i really do want to purchase the F-14, but until I can explain what is going on I think i'm going to have to leave it in the oven. Snacko

Hey guys - I'm using the current free period to test out a lot of the planes. I had my eye on the F-14, and I am glad I have been able to test it as the performance is pretty poor. Here's my numbers: CPU: i7-9700K CPU @ 3.60GHz GPU: Nvidia 2070 running at stock 32GB RAM Hardware-Accelerated GPU Scheduling TURNED ON *See below for my in-game settings. I ran the test mission that someone posted above: F-16 - FPS ~79 (varied between 72 and 88 when in TrackIR) F/A-18 - FPS ~74 (varied between 73-83 when in TrackIR) F-14B - FPS - ~68 (varied between 63-69 when in TrackIR) One might think that the above F-14 FPS rates are pretty good, and they are when you are just sitting on the ground. Unfortunately this mission is not a good indicator of performance. You need to get the plane up in the air fully understand my hit on FPS. The problem i am having is that I am getting very noticeable and frankly unplayable FPS numbers when I am flying the F-14. When i am flying strait and level and looking forward I am getting a decent 60+ FPS. The problem is when I start to turn the plane or my head using TrackIR. The FPS will often just bottom out dipping to 13 FPS or lower sometimes. I am not seeing this behavior is any other plane - only with the F-14, so I am fairly certain my base settings aren't too far off the mark. I do find it odd that there aren't more comments like mine as I have a fairly basic PC setup. Possibly some F-14 configuration somewhere affecting this, but I am at a loss. Eric Marlow aka "Snacko"

Never touched that option in the past. I looked at it at he said "always on". Double checked that the a/b wasn't working. It still wasn't. But i changed the option to "always off", and it worked (?!?). a/b is now working as it should. Maybe the most recent update changed the default setting, and the ""off" position is where it should be? Thanks for the help :)

Hi all - i thought something was strange when I flew around in my F-16 this evening. I get no higher than 102% power, and the plane never kicks into afterburner, even though I'm pushing the throttle to the firewall. I'm running 2.5.6.55960, and I have your basic Thrustmaster Warthog joystick and throttle. I thought at first it was the calibration, so I made sure that was fine. I also checked the afterburner in the F-15, MiG-29, and Su-27 and all are ok there. It only doesn't work on the F-16. I don't have any other aircraft to test it against. Anyone else having these issues?

For those of you that have been around for a while - what's the typical pattern for ED sales? This current sale is good through December 7. Will they also have a Christmas sale? Is there a sale where the discounts are deeper?