Pac-Man

Avantar, thank you for all your effort here. I hate the TARGET software from Thrustmaster. Takes forever to switch profiles. However, I'm having a little trouble with yours. Any "Button" that I assign to single press without "continuous" repeat on, doesn't register in the aircraft. Here's what is really weird about it though. It will register in the "edit controls" menu. For example: (Thrustmaster Warthog) I bind LShift + B to the forward Airbrake button LSHIFT + B Single Press Repeat Off Results: The airbrake doesn't extend Open "Adjust Controls" Push the Airbrake switch forward again The speedbrake extend command is now highlighted with Keyboard command LSHIFT+B. This clearly shows DCS is receiving a command. However, if I change the Single Press command and add "Reapeat + Continuous", the aircraft will register the command and the speedbrake will extend. I have also tried setting "repeat with "X - Times". Same result as before. Nothing from the aircraft, but the adjust controls menu registers the command. Now, in most cases setting commands to continuous isn't an issue. However, the speedbrake forward switch is a problem because as long as it's on DCS won't register any following commands. I am also unable to then bind a "Long Press" to that command. As if this wasn't odd enough, it only effects "Buttons". The toggle switches on the Hotas work fine with "Single Press and no repeat". But in order for any of the buttons to work, they must be set to continuous. Any ideas? Anything I can try? I appreciate your help.

Radar Tutorial for F-15C In today's course, we'll be going over the AN/APG 63 Pulse Doppler radar in the F-15C for DCS World using an amazing tool designed by AlephRo from TAW. Thank you very much for making this tool available to the community. Radar Tool by AlephRo from TAW: https://tawdcs.org/radar-f15/

Don't let the negativity and misinterpretation ruin you guys' day. In my opinion, the NS is a gift for aircraft that didn't have it by default. This SIM to me, is about era specific aircraft and what the pilots had to go through to operate these birds. The NS is not something they had available to them at the time these aircraft were in their prime. I own the NS, and from the day I purchased it I knew it was for the Mi-8. The fact that it now exists at all in other modules was a surprise to me. Yes, I'm aware that it was mentioned it MAY in the future become available to other aircraft. However, at no point did I think what I purchased would cover other modules. I was aware I purchased the NS FOR THE MI-8! You guys and your team have done great. Shake the BS off and enjoy your weekend.

Fair enough! I appreciate the feedback. LOL this is why I claimed to not be an expert at AAR in the Eagle lol. I'm just good enough at it to do what you saw lol.

Hope this helps out guys!

I know many pilots/DCS users don't quite understand how this works. So, I thought this may help.

I don't know if this has been posted already or not and I have 2 little ones tearing through my house so I don't have time to hunt lol. However, if you are experiencing the above, disable MSAA. MSAA and DS are once again clashing in their eternal battle. With MSAA disabled, visuals in the targeting cameras should be restored. Good Hunting!

I have two 960EVO's in RAID 0 with DCS on the installation. I have definitely seen a performance increase. Prior installation was M.2 NVME single drive. However, as they all stated above, its very expensive to do with a lot of risk should one drive fail. One NVME will provide amazing performance.

Set up the viewer part in your "viewer install" Copy me_3dview.lua to %USERPROFILE%\Saved Games\DCS.secondcopy_D Open the MissionScripting file of your second installation (D:\Program Files\Eagle Dynamics\DCS World_D\Scripts\MissionScripting.lua) and add the following lines after dofile("ScriptingSystem.lua"): me_3dview = {port = 46587} dofile(lfs.writedir().."me_3dview.lua") You missed this step. That's what causes the error.

Yeah, all the videos I could find on it showed it...

I was able to get passed this by unlocking and re-locking the throttle cutoff. Default key is RWin+T if i'm not mistaken. Forgive me if I am. :) Hope it helped.

To SLI any graphics card, they must be the same make and model. Example: GTX 1080ti SC2 GTX 1080ti FTW3 Can't SLI The issue is the clock speed is different right out of the box. The cooling system shouldn't make a lick of difference as long as all numerical specs and brand are identical. Although, given the price of the 1080ti, my recommendation is buy the exact same one.

You can use the TARGET software provided by Thrustmaster and send keyboard commands using the toggle switch Example: ENG L FWD = RALT+Home > starts the left engine

Training We typically train every Sunday at 2100 EST and a few members are flying pretty much every night

You may want to look here. Solved the same problem for me https://www.humancentric.com/

Yes, I did. I apologize for not responding sooner. Thank you for that!

Can we expect any support of these products in the future? It is a little shocking that DCS doesn't support these. These devices greatly enhance the immersion of the flight simulation. Especially, given the fully interactive cockpits? I know there is an amazing addon that was created by other users in which these panels will operate within DCS. However, the software only supports 4 aircraft. No F-5, or M2000C. I have noticed bugs with the Huey. Is ED planning on implementing compatibility of these devices?

Logitech Radio Panel and Mirage 2000 and F5 Has anyone been able to configure the Mirage 2000C/F5 to work with the Radio panel

Ok, is the ability to transport troops with the Uh-1H ever going to be reintroduced. It is one of the major functions of the Huey that made it so popular. This is an expensive module to not be able to do something so basic. I understand there are a bunch of LUA scripting utilities and such that will allow this functionality to work in the mission editor. However, I personally don't understand how to write in lua and feel like I honestly shouldn't have to given the price we pay for the Huey.... Can this please get addressed. I am trying to make a mission with my squadron involving multiple aircraft with multiple roles and the only one I can't complete is the Huey aspect of it which is picking troops up from a hot LZ. If anyone can offer some assistance I would greatly appreciate it. ED, any update on when this function will be returned to DCS would be nice.......... again, this is a very basic and highly used functionality of the Huey... I am regretting purchasing it.. :(

Glad to help, Guys!!

It's only the DeviceManagementApp that can be removed... still need the TARGET software for key mapping

So, I know this isn't the Thrustmaster forum. However, it is a very common problem and DCS certainly sees a lot of the Warthog and other Thrustmaster devices. Do you experience a problem when the Thrustmaster TARGET Software stops a script? Does it prevent your computer from successfully shutting down or restarting normally without having to press the reset switch? Have you spent hours on forums and testing different solutions your self? ALAS!!!! I have found the solution. I too have been dealing with the same issue. However, the problem isn't directly Win 10 or TS causing the problem. It's actually the Thrustmaster. Now, before we I tell you what to do, confirm the same symptoms. I was also noticing a coincidental timing between TARGET and TS. However not as frequent, I have been able to reproduce the issue without the use of TS. So, here are the steps: 1. Start the TARGET 2. Run Script 3. Stop Script until it fails/freezes 4. Open Task Manager 5. Navigate to "Details" 6. Sort by author/maker? (forgive me I'm at work while writing this and therefor don't have WIN10 to give exact verbiage) 7. IF, the issue is the same as mine you should see 2 services from Thrustmaster - FAST Service - DeviceManagementApp< this is the criminal who must hang for his crime against the SIM community If you attempt to stop this service, you will find that Access Denied slaps you in the face. This is the same service that is preventing safe restart/shutdown of our beloved SIM portals of joy. (or anger depending on how good you are) Next, we will discuss what and why. What is it? The purpose of this little devil is to reallocate the Thrustmaster USB devices back into individual units once the Script is stopped. Why is it being so mean to me? Essentially, it's not. My assumption is that this USED to be a required application. When it works correctly, you will see this service start and then immediately stop and disappear from the list. The problem is Win 10 already understands how to reassociate the devices once the script is stopped. So, its basically a race between WIN 10 and Thrustmaster on who will complete the task first. When Windows wins the race, the service hangs and thus our headache has arrived. When Thrustmaster wins, all runs as designed. What is the damn solution, already!?!?!?! Navigate to Program Files (x86)\Thrustmaster\TARGET\x64 and find the DeviceManagementApp and.............................. DELETE IT!!!!!!! ALL works well and the SIM world involving the Thrustmaster products resumes its enjoyment to the fullest!. Good Luck and hope this helped!

You have something else going on. I have been running the EVGA GTX 1070 since 2 weeks after its release. Did you make sure that you're AMD drivers were completely removed before installing the GTX 1070? They may be conflicting. I average 60FPS on the ground and 100+ above 20000 ft. with all three screens and graphic setting maxed on all options. This SCREAMS drivers to me. Also, what is the temp of the GPU when the framing starts? What is the version of the 1070.... FTW? SC? etc .... Rig: 3 X 27" 1920*1080 Samsung monitors Asus Z270 Prime -A motherboard i7 7700k 4.0ghz 32g Corsair Vengeance DDR4 EVGA GTX 1070