cabzi

All I'm saying is that the problem is not just "fixable" but totally fixable. My trackir in DCS and other supported games is now smooth as the baby's bottom. In the end, after many hours of trying to get the problem sorted out, I can't really blame ED or Natural Point on this. There is an endless amount of different hardware, software and other end-user configurations.

This is how I fixed the jittery trackir on my comp. These settings may or may not work for you, but seeing most of you guys have tried so many ways to fix the problem, you might as well try one more.. Graphics.lua=default Nvidia Control Panel: GSYNC selected only for fullscreen mode NVCP (program settings for dcs.exe) Pre-rendered frames ahead = 1 Display = G-SYNC VSYNC = Use application setting Power mode = Maximum power Refresh rate = Maximum available (=144 on my Asus ROG PG279Q) In-game settings: Disable Aero Interface = unchecked VSYNC = unchecked Fullscreen = checked CPU affinity (set with Process Lasso) DCS.exe Single threaded performance mode (=disable HT cores) I/O priority = high Trackir.exe = all cores used / no changes --- Do NOT left alt+enter after entering the cockpit. This is not necessary anymore and was fixed some time ago. There is a super easy way to confirm whether you need to alt+enter or not: If you have a keyboard with sound volume control wheel, roll it up or down a bit after entering the cockpit. If you see a volume indicator/bar pop up on your screen -> alt+enter to enter true fullscreen. With my settings, the game has launched in true fullscreen mode (in-cockpit) for some time now. But this was not the case for years, so ED did something to fix this. Ofcourse, if you alt-tab while gaming, you have to alt+enter after getting back to cockpit. Again, volume indicator is your friend. If you don't see it, you are 100% in fullscreen mode.

AD, are you familiar with a program called Reshade? There is a filter called ”deband” which helps quite a bit with gradient skybox.

That is probably the case if deband is the only shader used with Reshade. I also use LumaSharpen, Clarity and Vibrance combined with in-game settings for antialiasing (MSAA *2 and SSAA *1,5) and I honestly don't see any problems with target spotting or quality of terrain textures.

Hmm.. that is strange. I am using with default settings and the difference is very noticable = no more ugly, gradient skybox.

Here too. Reshade's deband feature is pretty much mandatory with DCS. Can't figure out, why it is not hard coded directly into the graphics engine.

Ok, that sorted it out. Thanks Hollywood!

Hi, anyone else got problems with keywords database (after the latest update)? When I start VA, it prompts "keywords database was updated: apply FINISH steps.." Ok, so I follow the instructions like many times before (Ctrl+A, DEL, Ctrl+V) and when I click OK, I'm getting a pop-up window which says: Invalid Multipart Command Multipart commands cannot contain any blank entries. Please remove any blank entries. I can't figure out, what I'm doing wrong.. Hollywood, can you help with this, please?

Thanks Mustang! I like this version too. Also, many thanks for moving away from that hideous, malware spamming Mediafire. :v:

Have you tried ”approaching to refuel”? That works for me. After that when you are closer to tanker ”ready pre-contact”.

It is still not fixed 100% on beta. Many IA missions still get no debrief at all.

Hi, this has been a bug for months. Like many other threads on this side of forums, mods/devs don't seem to bother tagging bug threads as "reported". Use "fog of war" setting in options for time being (icons are bugged with off and my a/c).

Yep, got the same problem here. Noticed it right after patching. Couldn’t give two thoughts for it, because the lack of feedback from ED to original bug report on the matter.

Tbh, ED's current beta-release patch cycle is not very customer oriented way of doing things. Those of us using the beta put time and effort into testing and reporting bugs, only to find out they get zero acknowledgement from the developers. Then a week later ED just releases the same version as a stable version. I don't expect that every reported bug get squashed during the open beta-release period, but at least ED should have the courtesy to update the patch log with known issues. Now, release version users just keep reporting the same bugs as before..

I see what you did there, but I meant the official ED testers/team responsible for some level of QA before patches are released.

Missing debrief screen is definitely a bug. One so obvious that makes you wonder, how this wasn't noticed/reported by beta testers.

This. And there is also a slim chance ED might release something on Friday.

Definately not the only one! I'm frequently checking if there are any updates to this thread and your other mods. Love your work and truly appreciate the time and effort you put in to helping others.

Keep on flying, free weekend has been extended to tomorrow.

Just hop in the cockpit. Free weekend has been extended to tomorrow (2nd Oct).

Patch log released

Still bugged.. My question to moderators/devs is, how many bumps/posts do you need, before you have some courtesy to acknowledge/report this?

Ok, then it sounds like a must-download like all the previous versions. :thumbup: Thanks Mustang!

First post shows ver. 1.10. Ninja update? What is new in this version?

Wow, Kegetys to the rescue! While I don't own VR gear yet (waiting for next gen), I can only imagine you guys are in for a treat. This guy is a true talent and THE WIZARD of modding (you would know, if you ever played OFP or ARMA). I really hope ED will pay attention to what he brings to the game.