Tailhook

I've requested a start from "Ground" option multiple times that still hasn't been added. With an aircraft mod, you can trick the sim to thinking your aircraft is a Harrier though which allows you to place it anywhere.

With the ever growing number of skins for each aircraft and different skins per squadron, there should be a sort by squadron drop box now as well.

Colors on both are wrong. The navy blue and gold only looks brighter in direct sunlight.

Removed cause irrelevant. Original functionality was restored. See latest version.

Removed. Latest version available on GitHub.

I upped to 4xx months ago and saw a 20% loss across all games. Rolled back to 399.24 and haven't touched any new ones since. I am wondering if you guys see an increase now compared to the decrease noticed by numerous people on various forums trying the early RTX drivers.

What version did you upgrade from?

Is there a simple way to do it without calling variables from multiple other files? I'm trying to add a simple text hyperlink button to a Special options page but I can't seem to understand it, or it's just staring me in the face. I have the text button already formatted, calling the named variable info from cdata, and placed where I want in the dialog file but I haven't achieved any luck getting it to open the link I want in browser outside of DCS. I've looked at how the developer links in module manager and LINK button under news tab work but both have led me to a brick wall trying to understand all the call functions.

I get Malwarebytes warnings while running torrents all the time, including while updating DCS. While I'm glad the connections are being blocked, it may just be a false positive.

Got an email earlier telling me I'm one of the 100 that won beta access. Just waiting for a code now.:D

DCS (I think) is still programmed to only use two cores but Windows doesn't know that. I've tested only 1 and 2 cores and you get a drastic loss of FPS, and when running on more than 3 the FPS starts decreasing very slowing but runs more stable. I feel 3 cores works best on my system since I have 6 cores and like to stream. Anyone with a CPU with 8 or more cores should and can set DCS to 4 cores and may have a boost in certain situations. There is very little difference in DCS between using 3 and 4 cores, any more and you're just wasting CPU for other tasks. I don't know how project lasso works but I assume until you command it to manage core usage for a program it won't do anything else to other Windows processes.

Not true.

DO NOT USE AN EXTERNAL CORE SELECTOR, IT CAUSES INSTABILITY. Instead, create an autoexec.cfg file inside the Config folder in the Saved Games folder and use the command "affinity_mask = xx". Replace xx with number found using this website. http://store.fsxtimes.com/cal-cam.php DCS runs best confined to 3 cores, with hyper-threading. Performance per selected cores will vary depending on CPU. I have a 6 core and use "828" so it is using cores 2, 3, and 5 including the HT thread for each.

It's been a good ride.

Turn MSAA off, turn SSAA to 1.5x. You're welcome.

Developing high fidelity modules like the F/A-18C and A-10C takes years. Then don't buy 3rd party. None of the failed development of 3rd party's is related to Eagle Dynamics and the development of it's own modules. DCS has crashed on me less than the number of fingers on my hand in the last 5 years. Any crashing is caused by either a buggy mod that you installed or an unstable OS with weird background processes. The only self-induced crashing I get is when I accidentally click inside the window while joining multiplayer lobbies.

Thread was also started here - https://forums.eagle.ru/showthread.php?t=215875 ED did something to help but it wasn't enough. What I want to see is the cursor completely unlocked from head movement and possibly an input function for re-centering cursor. For an example, I want to be able to look at the cockpit flood light dial, select it, and be able to look around and still be able to use scroll to adjust the brightness. The mechanics behind this cursor extend back to Ka-50 and I think was designed for TrackIR users. I don't know why it was coded to be tied to head movement in the first place, it was extra work on top of writing the whole input functionality framework. Basically the whole extra chunk of code should be scrapped. Also anyone commenting saying we would lose the cursor in the cockpit, no that isn't even a thing currently. The cursor is confined to a virtual 16:9 box slightly larger than the UI window which is adjusted via re-centering view and therefore we can't simply lose the cursor somewhere behind us.

If it boots, then yes it probably defaulted to 1333 and you wasted the extra cash on MHz you can't use.

https://www.intel.com/content/www/us/en/support/articles/000007058/boards-and-kits/desktop-boards.html?productId=51997&localeCode=us_en

Then specify such in the original post. All you said is you want that cursor removed entirely, which won't happen.

That cursor appears for VR users. So no, it should not be removed.

Just be patient and don't click anything. It helps to preload some of the most used models in the encyclopedia.

Change the numbers in this line near the bottom. scene.cam.transform:lookAtPoint(x, y, z)

That's a lot of extra data to push to every client in the event of a skin change. NO

Would be nice if they could suppress the carrier engine sound to just the back end so all we can hear is the wind with canopy open.