Nightstorm

Hammer 1-1 linked a copy directly above.

It's the same issue as with the CJS mod that I replied to you here with.

There is a new version available on the downloads page: VSN_F105_V.2.7.12.23x_FC3_SFM.zip It has the weapons sub folder and the fixed LUA is already included. Folder: VSN_Mods Stable - filehorst.de @kahuuna

UPDATED 4/28/22 for DCS 2.7.12.23362 Open Beta

Mod updated for DCS 2.7.12.23362 Open Beta. https://www.dropbox.com/s/kbyluvauy3z25yg/CFT_Mod_3.0.2.7z?dl=0 Here's a copy of the FA-18C.lua file that I use updated today for the new OB. It includes the CATM-120C's and other training missiles. FA-18C.lua

Updated F-22A External Weapons add on for DCS 2.7.12.23362 Open Beta. There were changes to the entry.lua for new equipment. Also updated both the external weapons add on and the Single Player version for the new missile exhaust plume effect that ED implemented. The position needed to be adjusted. Links are the same in the first post.

I took the last version I was using, 0.6.3, updated the 64 bit DLL with the current one. Commented out the couple of lines in the ini file and installed the new version of the companion app v1.1. Everything works just as it did before but I have the new options and motion reprojection seems (slightly) improved. I don't know if this official branch had MR changes / fixes or not. So, the test I did could have been a one off. I still get the shimmering when I fly through clouds. With MR off though, it works just as well as before with no loss in performance. The additional post process options for vibrance, highlight, saturation etc are nice.

I read in the official branch instructions that if the opencomposite.ini isn't found it'll just use default settings. Whatever they are.

For those that do not want JTACS to show up on the RWR. Here's how to comment it out. You'll find the modified file, once installed, here: Open said file in your favorite text editor and place two -- in front of this line: ['us_jtac_infantry'] = 'S', or delete it. That is currently at line 241 according to Notepad++ subject to change in the future, but you can search for 'jtac' and find it. Save the file, done. No more JTAC on RWR.

Alright then. We'll just leave it as "S". It can always be removed easily enough if folks prefer.

Yes, I'm using the OXR version of this mod with the toolkit and companion app installed.

No problem. I've got the mod installed myself Let me know if the JTAC should show up as something other than "S". I looked at the type of RADAR used for it, but I didn't see any other references to compare. So I just went with "S" for search.

I added the EC-130, RC-135 and RC-135CB to the RWR mod and they show up fine. The us_jtac_infantry.lua has been added. Hopefully it will show up as "S". DCS RWR Symbology (digitalcombatsimulator.com)

They did fix several Radio related bugs. In the process I think they broke the filters. For FC3 based modules and related mods, like the F22, the filter has no affect currently. That's what I reported and it was confirmed. The Open Beta was then pushed to "Stable" a few days or so later. Any time there's a new release of a campaign or whatever, unless there are significant bugs that require a hotfix, you can bet OB will be pushed to "stable". I keep putting "stable" in "" because it's a joke in my opinion, to call it that. There's Open Beta, slightly less open Beta. In my opinion, there is ZERO advantage to run "stable". You might as well always run Open Beta and have access to stuff sooner, and, you can always revert back to the previous one if something gets seriously broken.

No, it hasn't. And that was confirmed in the post I linked. The radio filters still have no effect. And you have to turn off allied radio reports to silence them. AWACS still won't stop reporting constantly as long as there are contacts to report. You used to be able to use the filters and silence everyone except your wingman unless you were talking to them.

The file that stores your changes is called d3dx_user.ini and is located in the same folder with the 3DMigoto files. As @Fiztex said, if your DCS is installed in the Program Files folder, you will run into file access/permissions issues from mods because they will be unable to modify or create files in that location due to Windows security protections. DCS should be installed in another location, especially if you intend to mod it.

I believe he's referring to this: After updating to version 2.7.11.21408.1, the radio stopped working on all third-party mods. This is what the developers did. I hope it's not with malicious intent. Which I reported here and it was confirmed. The current Open Beta and "Stable" are the exact same code base. So the radio's are currently broken in both.

I'm going to put this out there because it seems odd to me. I have two version of the OpenXR Tookit Companion app. 1.04_DCS and 1.05. The current instructions in the first post point to the 1.05 version that was released earlier this month. I thought I'd try it again, and I lost 10-15 FPS with no other changes. I removed it and reinstalled the 1.04_DCS version and got the FPS back. What was done to that 1.04_DSC version that makes it custom to DCS? I didn't have a problem with 1.04_DCS so I'll stick with that and keep my 15 FPS thank you. Just seems odd.

As with everything related to DCS performance and tweaking "Your mileage may vary". Some things will work for some, that don't work for others. Several people in this thread had commented that they were able to resolve all of the motion reprojection artifacts from OpenXR by changing the runtime in Steam VR and then putting it back. I tried that four times with no affect. If I turn on MR I get the swimming effects in different places. All I can say is to try things out until you find something that works for you. We have examples of people with near identical hardware, yet they have different results. It doesn't make sense, but it seems to be the case. Personally, DCS has never run this smooth for me or looked this good. I'm really happy with it. And, I don't even have to start up Steam much less Steam VR. I'm hoping that the MR issues get resolved in OpenXR as I imagine that might improve things even more.

As I mentioned, having FSR enabled was causing the crashes I was getting. I went from everything worked, to crashing almost every time I ran DCS (sometimes in menu or loading or even during flight) to not crashing again. The reason, I turned on FSR at 0% and was trying to use the sharpness setting. I turned it back off, no more crashing. I use 3DMigoto for sharpening.

I also use the 3Dmigoto, however I adjusted colors in the OpenXR toolkit and use 3Dmogoto only for sharpening and haze reduction. I've tested with and without 3DMogito with those settings and I'm not seeing a performance hit but I can see the sharpening difference.

FSR is what was causing my random crashes. The log file / crash dump would show it was crashing in a couple of different video driver DLL's. Once I disabled it, no more crashing.

The time stamp on the post you're referencing is from November of 2020. That was three months before the new version of the F22 mod was released. = Necro post!

@Backy 51 I've updated my RWR database mod to include these aircraft. DCS RWR Symbology (digitalcombatsimulator.com) They will show up as EC (130) or RC (135's) on the RWR. The database also includes entries for many other 3rd party aircraft and missiles etc. Anything that isn't installed in your DCS installation won't impact anything. The purpose of the mod is to prevent the <U> unknown contact displays on western RWR when an entry isn't found.