ehagendorff

You probably already know/checked this, but you would have to go into the controls menu in game, and select the joystick column, then hit load profile, and browse to the Input folders n apply the profiles 'in game'. Then do the same for the throttle quadrant, rudders or any other peripherals you have. Just copying the folder won't bind the controls in game basically. Sorry if that was obvious/you've looked at that already, but didn't see it mentioned and figured I'd try and help out. The control bindings should still work fine..no reason those backup files wouldn't be able to be used/applied. Hope you get it working!

**RESOLVED** Thank you for all of your time on this, I really appreciate it. Sounds good. I had been thinking it was related to FreeTrack for a while because it was the only thing I could think of that changed, but I had used it in DCS when I first installed it. Either way I uninstalled it and deleted all the reg keys for it (I think), so was scratching my head again as to what would be causing it. I will go through my system again when I get home looking for anything related to FreeTrack/joyIDs FFB etc. Thanks again for all of your help so far. **RESOLVED UPDATE** It was FreeTrack remnants causing the issues. I had uninstalled it a while ago when I started having issues and thought I went through and deleted all the extra folders/registry keys when I did so. Turns out I missed a couple. Deleted the leftover registry keys and folders, reboot and DCS launched without issue. I feel silly for having missed those files and bothering you now, thank you again for all of your help. Attaching current known good Logs.zip for anyone who may have this trouble in the future to compare.) I am unsure how to edit the thread title to add RESOLVED, but if any mod is available to mark this resolved I appreciate it. Thanks again, Eric Resolved_Logs.zip

Never played at max settings, was always a bit reduced. Usually set to high or medium most things. I would drop all settings to low if I could launch to the menu. I immediately receive the error though. :( I can go through and modify the options and graphics lua files manually in notepad if necessary though.

I deleted everything out of the Scripts folder in the DCS Saved Games folder, same result. I removed the entire Scripts folder from the DCS Saved Games folder, same result. Also, earlier today, I completely removed the DCS Saved Games folder, to allow the game to recreate it on first run, same result. Nothing was generated in that folder except Logs and Config. :( Sorry.

Sorry about that, I had realized the 360 controller was plugged in last night when I began troubleshooting again today. My nephew must have been playing something. Previously I had tried without the 360 controller plugged in, and did so again earlier today as well. Please see attached logs. I also moved the DCS folder out of Saved Games entirely, and launched DCS just now (nothing but kb/mouse). I attached those as Clean_Logs.zip. The Logs from earlier today are Logs.zip attached to this post. Logs.zip Clean_Logs.zip

Thank you for the quick reply. I knew I forgot to mention something in there. I receive the error with nothing connected but the keyboard and mouse as well. I had tried it with nothing plugged in. I even unplugged my USB hub as well, and had just the keyboard/mouse plugged in to the back of the PC. Unfortunately no change. I have also tried running setup and the game itself as Administrator with no change. I will see if I can disable FF outside the game somehow. I assume it is a true false value in one of the .lua? UPDATE: After searching a few of them I have not been able to disable it or get it to make a difference. I found a forceFeedback entry in the "DCSWorld\Config\Input\Aircrafts\Default\joystick\default.lua" here is the entry: return { forceFeedback = { trimmer = 1.0, shake = 0.5, swapAxes = false, invertX = false, invertY = false, }, After that it gets into the key commands section. I tried putting trimmer and shake to 0.0, no change, and tried adding false in after 'forceFeedback =' no change. Although, I assume that's probably just not how that setting/file works (that seems to be the settings for BS2). I returned that section to the default values after troubleshooting. I opened "\Saved Games\DCS\Config\options.lua" and the forceFeedback setting was set to true in that file. I marked it false, and unfortunately receive the same error. I will double check more options settings and Input lua's in the Saved Games folder. Weird as I had removed those folders so they would be created with a clean install/default values as well.

Hello, Sorry for the book, wanted to offer as much information as possible. I rarely post issues on forums, but I have been unable to resolve or find any information anywhere online related to the error that developed recently with my DCS install. I am currently under Windows 10, FX8320 Processor, GTX 780 Graphics Card 8GB RAM. Running the 'stand alone' (non steam) DCS. I had been playing the 1.5 beta fine until the last major update under beta. After updating I began to receive the error in the attached screenshot. Troubleshooting performed over the last few weeks: 1. Attempted Repair w/DCS_updater. 2. Attempted to rollback to last known good 1.5 version w/DCS_updater. (also manually uninstalled modules with DCS_updater) 3. Uninstall/Delete reg keys perform clean install. (I also updated/reinstalled DirectX, Video Drivers, and Visual C++ Redistributable) 4. Repeat x3. (deleting and downloading install files from torrent/ftp/http sources on website) a: uninstall/delete reg, etc FreeTrack (even though was working with it prior) 5. Uninstall/Delete standalone, Install Steam version (beta). 6. Repeat 2x. 7. Install non beta (1.2) Steam version. a:. Same overall result, but with no error message, process starts and closes in Task Manager in 2-3 seconds with no indication it is running/crashing. 8. Now that 1.5 is out of beta install clean Steam version (non beta opt). No change each time. I do not get a prompt for module install or anything (obviously with the new version module management I wouldn't receive that until DCS:W fired up). I also deleted the 'Saved Games' folders (well cut/paste them to a different location) on some of those reinstall attempts. I have searched the forums, reddit, and google (not necessarily in that order) and could not find anything surrounding this error message. I have attached a screenshot of the error, my system specs, and DCS logs from both the openbeta and DCS folders. The reason for both, is the openbeta logs are from 12/23, (1.5.0.45208) and the DCS logs are from 1/2 (with 1.5 out of beta 1.5.2.48726). Maybe you will find something different in the two log sets? Please let me know if you need more information or would like me to perform anymore troubleshooting I may have missed. I apologize I forgot the exact version numbers of last known good 1.5 install and the first version that threw the error. (I did most of that troubleshooting mid December and got busy with the holidays here in the US). Thank you in advance for any assistance. Beta_Logs.zip Logs.zip ehagendorff_spec.zip

The TF-30 engines are definitely interesting. I have recently started reading and learning more about the F-14 in detail and have learned a lot about the engines and flight characteristics from my reading. The loud knocking described earlier and the subsequent stall is modeled in Aerosoft's version of the A model. They also model hot starts and engine fires, so if you don't start the aircraft properly from C&D you can kill the engine just trying to start it. The way to do this is to advance the throttle early (basically right when you hit crank) before the engine is spooled and it dumps a bunch of jet fuel in and then when it ignites you get an engine fire and can lose the engine. You can also get hot starts as well which is a more mild version of this same scenario, (you skip the engine fire and melted blades.) You'll see this in the gauges, the TIT (turbine inlet temperature) gauge will rise before the RPM gauge (quite a bit actually). If you see this you know to expect a hot start or possible engine fire. In flight you can cause compressor stalls a number of ways as well, throttle movement as described earlier, as well as aero (high aoa, sideslip, altitude/mach) or poor management of the aircraft can induce them as well, (typically when the throttles are lower or below 80%). You can sometimes get hot starts and engine fires recovering/restarting after a compressor stall as well. I am very much looking forward to Leathernecks version of the F-14 and look forward to breaking the aircraft as much as flying it! I believe it will be leaps and bounds better than any other simulation of the F-14 to date! Also here is a bit about compressor stalls with the Aerosoft F-14X. Here is a bit about hot starts/engine fires. I thought I saw something where it covered all the problems you could have in one video but I guess not. Can't wait for the full fidelity DCS F-14A/B!! :pilotfly::joystick: