RTS354

Not all programs play nice together. Games based on the Unity engine are very core and hyper-threading sensitive. For example, if the Steam VR service happens to run on the same threads as the unity VR game, that it launched, the performance of the VR game will suck big time. Windows does not know which programs belong to which, but if a program launches another program, windows will run that program in the same thread. I use CPU Lasso to assign the steam programs one set of cores and the games that it launches to another set of cores and the gains in performance are dramatic! Many games do not work well with hyper-threading enabled, so turning this off in the bios can increase gaming performance as this allows turbo boost to run the non-threaded cores consistently at high turbo speeds. The less cores and threads that are running the less heat is generated on the CPU. I can maintain a 4.3 GHz across 10 cores without hyper-threading, but only 4 GHz when hyper-threading is enabled which gives me 20 cores. Another benefit of CPU Lasso is that you not only assign which process to specific cores, but you as assign the priority of those processes, but NEVER give a process “Real-time (Highest) priority as this is reserved for the Windows software and hardware systems. With everything that I just said, unless you know what your doing, it is best to just let Windows manage the processes.

Since the last update, the mission editor is taking up to 5 minutes to save over an existing mission file. It is also taking just as long on the load screen when loading the mission before the mission load progress bar appears. I don't have this problem with loading missions that I bought. Anyone else have this issue, or a solution to fix this? Thanks.

On my Thrustmaster HOTAS left throttle there is a red push button that is usually mapped to the auto pilot, and now it no longer works for any key map function. The Windows 10 game controller recognizes the button press as button 15 on the throttle, and the DCS controls setting interface recognizes it as a button 15 on the throttle, but when I assign button 15 to any function the function doesn't work, even though the button was recognized in mapping it to the function. At first I thought this was the A-10 autopilot bug, but I am having this issue when trying to assign this button to other aircraft modules. Is anyone else experiencing this issue?

I just purchased the Super Carrier mod, and I am impressed, so I decided to create a mission where I can practice and takeoff and landing a F-18C from a carrier using my own mission objectives. But I ran into a snag that I cannot figure out. I have the carrier doing a large orbit using four-way points, and I have the wind align with the recover zone of the carrier. I used the measuring tool to get the wind direction. With the combined speed of the wind and the carrier, I get the 30 knots across the landing zone. BUT this will change when the carrier turns east to the 2nd way point which will change the wind direction. I have a two-part question: Does the carrier automatically turn into the wind during recover 0perations? If not, is there a way to change the wind direction at each carrier way point so that the recovery operation can be simulation by just changing the wind direction?

Thanks for the info. Your suggestions worked. Is there a list that I can download that gives the correct naming scheme for all aircraft in the Kneeboard folder?

In VR, I need to reference many of the voice commands that I need due to not being able to see the keyboard, so I created some kneeboard pages for the A-10C and they work just fine. I'm placing these reference documents in location: C:\Users\MyUserName\Saved Games\DCS\KNEEBOARD\A-10C But the following locations do not work for these aircraft: C:\Users\MyUserName\Saved Games\DCS\KNEEBOARD\F-16C C:\Users\MyUserName\Saved Games\DCS\KNEEBOARD\FA-18C C:\Users\MyUserName\Saved Games\DCS\KNEEBOARD\P-51D This locations use the identical naming scheme in the DCS world mod directory. All of the research that I did indicates that I am creating the correct folders for the kneeboard documents. The documents are 768 x 1024 with the PNG extension. The name of the two documents are: 00000 - Kneebaord.png 00001 - Kneebaord.png Like I stated, the two documents work with the A-10C mod, but not with the other aircraft. Any suggestions?

Was checking out the option to show the pilot body, but had an issue where I needed to access a switch that was blocked by the pilot's arm. Is there a keyboard command to temporary make the body transparent or something so that I can access the cockpit switches? Never mind, I found it. Looks like I misspelled pilot in my search of the controls. Disregard this stupid post.

I just started learning how to play DCS and the A-10C module, and I was having issues with learning how to launch multiple mavericks at multiple targets using some of the tutorials on You Tube. Although the tutorials work, there seem to be to many buttons presses to do this. The technique that I use requires four button presses, and you don't need to change focus from the maverick MFCD. Note, if someone has already posted this, you the credit goes to you, not me. I just could not find this method in my search results. I think this is the quickest way to launch multiple mavericks at multiple targets. The first thing you need to do is to bind a control to the “Steer up” rocker switch in the UFC. I used my “Coolie Hat” switch down movement to activate the switch as I don't have a need to swap that left and right MFCD. Once you do this, you can just press the “Coolie Hat” switch to select the next steer point. So, the procedure after mapping the Coolie Hat down to the Steer up rocker switch is: 1) Center target in TGP, press TMS right short. Repeat this for each target you intend to shoot a maverick at. 2)Select MARK as the STEER PT option which is below the CDU. 3) Make the MAV MFCD the SOI (sensor of interest). Now you are ready to launch the mavericks. 4) Press the Coolie hat down to select the steer point you want to launch the first missile at. I usually start at “A”. 5) Press China Hat forward long to slave the maverick to the steer point. 6) Press the TMS up short to lock the maverick on to the target. Note that if the cross hair on the MFCD is not vibrating you may need to press the TMS button up short several times, or slightly move the slew button. This problem is usually eliminated if you created the steer point while pointing the TGP at the center of the target. 7) Press the Weapon Release button to launch the missile. Repeat steps 4,5,6, and 7 for each consecutive target. My original video got hosed, so I'm going to post a new video showing how to do this. Stay tuned.