Flow

jackmckay, did you really think that atomizing is breaking a molecule apart ? If yes, well then look into how a diesel engine works, and try to light diesel on fire with a simple gas lighter. Also, that would close this thread, seriously.

Tell me if I'm wrong, but would't AAR be damn dangerous if it would ignite that easily ? Plenty of videos with fuel spray going on the plane and through the turbine, and not a sign of ignition. Example : https://youtu.be/BZV3Ffm2qIQ?t=2m52s Edit : also to add "some fuel to the fire", for an engineer, not many hard facts backed with calculations. Just guess work.

If you are having TARGET issues, this might help. Description of the issue : TARGET Script takes a long time to load, and the physical joystick and / or throttle are still connected and functional after the script is loaded, on top of the virtual "Thrustmaster Combined" controller. Warning : The script has to be properly coded and both joystick and throttle need to be included for the explanation below to be valid. Concerning the USB ejection issue during script loading : This process is handled by "DeviceManagementApp.exe" located /Thrustmaster/TARGET/x64 This can be blocked by various processes, like for instance the TeamSpeak Joystick add-on, but not only, and even Windows Kernel processes might be the source of the issue. One solution is to remove or rename this executable, and the TARGET script then won't eject the joystick and throttle, but will still add the virtual controller "Thrustmaster Combined". You can then map only that last controller in the game, and ignore the buttons & axis of the physical joystick and throttle. If the above is not satisfactory, we need to take it one step further : Discovering the process at the origin of the issue : 1 - What are the game controllers connected to the computer Start menu -> Execute (depending on which version of Windows you have, I'll let you handle that one) Type in "joy.cpl" and execute This is the list of the game controllers connected to your computer. YMMV. Now launch the TARGET script. If it takes time to load, like below, there is probably an issue : Once done : Now look at the connected game controllers again. Two options : only Thrustmaster Combined (OK) or Thrustmaster combined and joystick and/or throttle (Not OK) Script worked : Script did not work (could not eject a physical device) : 2 - Finding the process preventing TARGET to eject the device Start menu -> Execute (depending on which version of Windows you have, I'll let you handle that one) Type in "eventvwr" and execute Now go to Windows Journals -> System There you should have some errors on top of your list. Select the first one and see what it says. In the description you should see what process is preventing the ejection. See what it is linked to and if it can be killed or not.. Then use CTRL+ALT+SUPPR or simply quit the application, I'll let you handle it from here on. Example of the TeamSpeak Joystick add-on making trouble : In that preceise case, quit TeamSpeak, run the script, and reload TeamSpeak. Good luck on the troubleshooting !

Remove them from the Device manager and force re-install. See if that takes care of the issue ?

Look into the DEVCON tool. You can make yourself a script to virtually delete and reconnect a device without actually doing it physically. For the TM warthog for instance, the command is (if the devcon.exe is on your desktop) : C:\Users\%USERNAME%\Desktop\devcon.exe restart "USB\VID_044F&PID_040*" This restarts all the USB devices from Vendor 044F (Thrustmaster) with product ID 040 something (2 is joystick, 4 is throttle). To download DEVCON : http://www.itworks.sk/storage/devcon.zip It is a Microsoft tool, so no worries :) As for finding the right VID and PID of your devices, use Windows' device manager. That *should* take care of your problem.

Sennheiser PC373D here, very happy about it :) Very comfortable, open ear design.

CPU seems to have the same performance as your actual computer. Moreover, DCS is more about MHz than threads, so your overclocked 2500k might even do better than a non overclocked 7400 : http://cpu.userbenchmark.com/Compare/Intel-Core-i5-7400-vs-Intel-Core-i5-2500K/3886vs619 Just get a 1060 for your computer and call it a day IMO.

Good to know :) Thanks.

It would be great to share the solution. It is sad to see you come here to ask for help, but do not return the favour ?

Some indicate pitch and roll inputs (ADI and HUD), others relative glideslope position (HSI).

Patch worked perfectly for me :)

Such a bad time to buy a GPU though, with the 2080 around the corner, and the miners driving the prices up.

1080Ti in SLI ? That isn't supported by DCS, right ?

Show / hide pilot's body : RShift + P Only the HUD is translated. Are you talking about the Su-25/27/33 modules ? Why are you assuming this ? In Russian aircrafts, units will be metric. What module are you talking about ?

I always miss using CCRP somehow. Cannot get the diamond perfectly placed...

Unguided bombs, using CCIP :)

I don't, I reinstall from a drive image, to save a lot of time :) PS : thanks for the answer.

Hi - I know about that point system for DCS World activation, but do not find the information anymore ? I am moving from a SATA M.2 drive to a NVME M.2 drive, so the main hard drive of my computer will change. Should I de-activate my modules and re-activate them with the new hard drive after the copy or should I leave it as is ? Thanks :)

Nice fight Frostie ! Very interesting to watch. If you have the TRK file, I would be interested :)

I kind of solved the issue by preventing all the Thrustmaster USB controllers to go to sleep. Since that the issue seems gone

M.2 is just a connexion type. M.2 SATA SSD will be as fast as a normal SATA SSD M.2 NVME SSD will be a looooot faster than a SATA Let’s not get confused here. I have a SATA M.2 and it reads and writes at 580 MB/sec. A Samsung NVME M.2 would get me to 3000MB/ sec or some figure like that.

Bumping this thread. I have the same issue. Every now & then, when I start my profile, I have the Thrustmaster combined input, and the stick & throttle still there too. This is creating issues inside DCS. Is there any solution that has been found ? I've been looking all over, but nothing was really conclusive. I updated TARGET, made sure that windows cannot put the USB devices to sleep. Help is appreciated :)

35690, France :)

You need to setup a voiceattack profile and program your HOTAS well, and you'll be golden in VR.

I don't remember the key assigning for this function, but why would you need it ? Nothing is clickable in the FC3 planes.