RickJamesBish

Solution for me, after looking on TrackIR Forums, was to run DCS at 120hz refresh rate, which matches TrackIR refresh rate. Thanks for the response. It was most noticeable vertically but still felt off in all directions. I did figure it out though after searching on TrackIR Forums. It is because I am at 144hz and TrackIR is locked at 120hz. I know I stated I tried all refresh rates in previous post but apparently I missed 120. Its like butter at 120. Should have put this in my original post of things I have done... I always test my camera before starting a game by using camera view in the TrackIR software to make sure LEDs don't cross each other in my range of motion. Thanks for responding.

Rolled back to a previous driver and still same issue. I also confirmed vsync is on and I have tried every refresh rate from 60 to 144. Maybe it has always been this way and I just don't remember but it caught my eye immediately. Best explained like lower refresh rate but displays shows correct rate, and as stated, if I turn off TrackIR and use num pad it is smooth.

Been a bit since I have played but fired up yesterday and noticed TrackIR movement, in particular vertical, is not smooth, almost like its skipping. I confirmed that it is only when looking around with TrackIR by using the num key to look and that is very smooth. Has anyone else noticed this or can anyone recommend something I might try to fix the issue? Made sure windows is updated as well as latest versions of Nvidia drivers and TrackIR software. RTX 4090 i7 13700k 64gb ram, all nvme drives. While waiting for responses I am going to try and roll back TrackIR software but this issue only seems to be in DCS.

Confused on FC3. I own it. It's listed in my account under modules. I have purchased and downloaded FC4 at the discount price but game keeps prompting me that FC3 is available. I click and it downloads and restarts but the prompt shows up again that FC3 is available to download. How can I get rid of this?

Thanks for the response. Now that you mention it, Those gauges will likely not be that useful and I think I would like to put the F16 RWR in that location instead. I will give it a shot once I have an understanding of how it works.

Is there a utility I can run in conjuction with my current SimappPro from Winwing, which runs my left and right MFD for F16, that will let me display an area of the cockpit on a 3rd usb display? My current setup is MFD with USB display on left, ICP Panet in center, MFD with USB Display on Right. I would like to add a 3rd USB display to the bottom below the ICP panel and have it show all the area as pictured in attached image. null

Does anyone know that ENGINE section in SimappPro is for? I have two WW MFDs configured, one for Left DDI and one for RIght DDI. They work correctly. I was trying to see what ENGINE displays so I designated one of the two displays to ENGINE, but it still displays the MFD. null

I posted here because it is specific to the F16. I have two WW MFD-1 units. Both are set up and working as they should as LEFT and RIGHT DDI. I was considering another MFD-1 to use for the ENGINE display for the F16. I have not idea what is actually displayed, which is why I wanted to test it and to see if it had any real benefit. So I took display #3, which was assigned and working on Left DDI, and moved it to the ENGINE. It applied successfully but when I run the game I still have the LEFT MFD being displayed. Any ideas?

I currently have two WW MFD1 configured for the left and right MFD in the F16 and they work as expected. I was considering a third display to use of the ENGINE display shown in SimAppPro but wanted to see first hand what it looks like and see if it would be a worth while addition. My LEFT DDI was set to 003 so I set that to null and moved it to the ENGINE. I applied and started up the game however the 003 display still shows the LEFT DDI information rather than whatever information the ENGINE is supposed to display. So what am I doing wrong? It is like a file is not getting updated with the new information and I don't want to go start deleting files not know which one is the likely suspect. Any recommendations?null

Just an update.. Since installing the DDT driver and enabling in BIOS, I have not had a single performance issue in DCS. I use to have at multiple occurrences per day. The Intel Application Optimization App does not seem to be required. It appears to be a performance enhancement app for some titles and DCS is not listed.

Yes I went to dicord first actually and made them aware of what we found.

Yes, both of these, although it is unclear if the Intel Application Optimization is needed or not. In the Reddit Intel group, the person that appears to be from Intel is vague with responses. The App has a list of tested / supported games that you can enable or disable as individually or as a whole, but also has an Advanced tic box, which by description makes it sound like it is for testing on games not listed. When asked about that, he states on multiple occasions that the advanced option is to try out the games in the list, which made absolutely no sense. He dances around that aspect quite well. The DDT driver is something Intel provides to the MB Manufacturers so I can't really link to it since there are so many but is referred to as DDT Intel® Application Optimization with Advanced Mode (as far as I know only available from Microsoft Store) Intel to roll out 14th Gen's game optimization software to older 12/13th Gen hybrid CPUs after all | PC Gamer Here is a link to MSI and you can see here they only mention the Gen 14, which in a video about the core issues, the person stated they reached out to Intel and was told they had no immediate plans to support 12 and 13 Gen.. but that obviously changed. (see link above). How to Enable Intel Application Optimization on MSI Motherboards For my Z790 ASUS MB, you enable it in BIOS under Advanced > Thermal Configuration > Intel Dynamic Tuning Technology Configuration. It would be nice if someone at ED reached out to Intel about this to get some details... And followed up with what they find, if anything.

Apparently Intel has released a driver to address this. It does not come right out and say it addressed this issue but it does distribute work load between P and E cores. It was initially only available for the GEN 14. I found a link that announced support had been extended to gen 12 and 12 so I checked the Asus Website for my Maximus Z790 and the new driver was there. Since installing and enabling in my bios, I have not had the performance issue yet. I am going to continue to test throughout the evening.

Last update.. Promise. We spent hours on this and narrowed down to a definite fix. It is unlikely the above fixed the issue, and more likely we made a change we were not aware of. This issue IS, without doubt, related to the callsigns and VA/VC. If you have user mission and use any of these callsigns for a flight, you cannot hear the Entity response to your radio command/request. All of these result in hearing static at start of entity transmission then again at the end, but nothing in between. We edited all of our missions made prior to the last DCS update and changed them ones not in the list. If you use VA/VC, run DCS repair and do not start VC / VA AT ALL because it immediately modifies files. However if you wish to use VA/VC, modify your mission to not use any of these callsigns. viper jedi ninja wild weasel wolf panther venom lobo rattler cowboy python

Yep in my case, and the people in my group, the fact they have used the buyers as pawns, has turned us away from their product and any future products they may come out with. In fact, this has put a halt on purchases other than those modules direct from ED.

We are in the trial period with two copies of Tacview. I connected to my friends session and we viewed the mission together. Loaded another mission and got missing data alert. I could only see grey surface with small x x x with some big X X X but no actual mission data. Tried loading the one we had just successfully viewed and it did the same thing. All missions loaded from the point on had the same result when connected to view together. We swapped so that I was hosting and same issue was present. We were about to buy the standard and glad we ran into this before we did. Would like to get this resolved before moving forward.

I'm sure you saw this post. OP has a point. Until they are actively supporting that product again, it is a dead project and should not be listed for sale. They state things will get worked out and don't mind taking in $$$ while they are ASSuming. null

So this appears to be associated with Vaicom and / or Voiceattack in some manner. This is what we know to be a constant between the 3 systems we experience this on. The same user mission is being used between all the computers to test. 1. Prior to update entity voices such as AWACS could be heard when they responded to your voice command or F menu keys. 2. After update starting DCS only (VA/VC not run at all after update), entities can be heard responding. 3. After update starting DCS again but this time with VA / VC, Entity cannot be heard responding to your command by voice or F keys. Only hiss at start of what would be their response and another hiss at what would be the end of their response. 4. After trying 2 and 3 in order, then starting DCS again without VC / VA, issuing command with F key, same results as #3.. hiss.. nothing... hiss. 5. In DCS Scripts/Speech, two files are being altered by VA/VC... speech.lua and common.lua. 6. Running DCS Repair fixes these two files. 7. Running DCS after repair without VA/VC entity voices are heard. 8. Launching VA / VC results in the aforementioned two files being altered immediately. 9. Run DCS with VA/VC or without it, and entity is not heard. Conclusion is that once VA/VC is run after the DCS update, something in the changes to the common. lua and speech.lua made by VA/VC is not compatible with the user made missions that were created prior to the DCS update.

Not sure what that is. The entity sounds work in all the training missions and all missions created after the update, so somehow all user missions created before the update got broken. I have a friend who has not updated yet. He is trying a mission he created, and one we played the night before the update, to confirm sound still works. Then he is going to update and see if it breaks. That will tell us something. Will update post after he is done.

I do have vaicom / voice attack, but it happens without these running. It also worked yesterday and we played into the morning hours. It stopped when we all updated. Log is attached. It may not be the update but its the only common factor we know of that changed. Also missions created after the update do not have the issue. dcs.log

I cannot say this happens on every user mission. 3 systems and after update, entities such as awacs and tower are not audible in any of our user made missions. Pressing the appropriate F key, for example request taxi progresses to the next option, request takeoff but you never hear them. Awacs also is not audible. Created a new mission and it works. Tutorial missions it works.

What CPU and GPU? Also if you are doing any type of overclocking of your CPU or RAM, Discord will do exactly what you described.

For those looking, and since it apparently is not important enough to put a sticky in the performance bug section, the issue was the Intel P-Core E-Core. My issue was resolved by disabling Core #8. I see this was hit upon a year ago and now it is pretty well know that the issue is the Intel Cores, so not really understanding why a sticky has not been made.

I have been hunting down solutions for sporadic performance on my 13700k and 4090. This ranged from sudden extremely long load times, that I could get to finally continue loading by simply opening task manager, to long freezes in the game, to very unresponsive menus after existing the mission that had the long freezes. I was just experiencing this, and it continued after killing DCS and restarting 4 or 5 times. After killing it the last time, I tried the trick of disabling Core #8 (same windows session not a restart) and I played from start to finish through a mission without the faintest hint of a freeze or studder of any type. I have a friend with a similar gen processor and 3000 series GPU that had the same symptoms that this core disable seems to have addressed right away. I have seen this issue referenced, and even the fix I tried and another temporary fix as far back as 2023, so why has it not at least been acknowledged by ED? Even if it is an INTEL issue, with affecting and ED product you would expect them to collaborate and find out what is going on. If they have acknowledged this, then I apologize, but I have not seen it.

Thanks for the suggestions. He ended up uninstalling and starting over. Went through the same process and it worked. Something just got jacked up along the way but its working now so all is good.