[RESOLVED]1.5 Startup Error: "Element introuvable"

[ehagendorff]

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

Edited January 6, 2016 by BIGNEWY
tile

[BIGNEWY]

This crash looks like a force feedback issue,

 

try unplugging your controllers, just to see if it makes a difference, if it does and you are able to get into the settings untick force feedback for now in the ingame options.

 

 

# -------------- 20151223-173359 --------------

 

# 0EEDFADE at 79D61F08 00:00000000

00000000 00000000 0000:00000000

79D61F08 0014E140 0000:00000000 RaiseException()+68

131DD416 0014E250 0000:00000000

131DD44C 0014E280 0000:00000000

134BABD3 0014E2C0 0000:00000000 TMethodImplementationIntercept()+25BC93

134ADB51 0014E2F0 0000:00000000 TMethodImplementationIntercept()+24EC11

134AF775 0014E330 0000:00000000 TMethodImplementationIntercept()+250835

134A8D6D 0014E360 0000:00000000 TMethodImplementationIntercept()+249E2D

134D39C6 0014E680 0000:00000000 TMethodImplementationIntercept()+274A86

134D2CB9 0014E6D0 0000:00000000 TMethodImplementationIntercept()+273D79

134D4899 0014E720 0000:00000000 FTProvider()+3B9

134D40D1 0014E770 0000:00000000 NP_GetSignature()+31

5060A57E 0014ECE0 0000:00000000 luaopen_Input()+589E

5060AE57 0014EE40 0000:00000000 luaopen_Input()+6177

505C3E25 0014EEF0 0000:00000000 ?isImmediate@ForceFeedback@@AEBA_NXZ()+505

505C3B0D 0014EFD0 0000:00000000 ?isImmediate@ForceFeedback@@AEBA_NXZ()+1ED

505CFDD3 0014F020 0000:00000000 ?initialize@Input@@SAXPEAX@Z()+A3

30AD3532 0014F0D0 0000:00000000

30B9B46E 0014F780 0000:00000000

30B9D365 0014F7C0 0000:00000000

7D1D8102 0014F7F0 0000:00000000 BaseThreadInitThunk()+22

7D59C2E4 0014F840 0000:00000000 RtlUserThreadStart()+34

[ehagendorff]

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.

Edited January 5, 2016 by ehagendorff
More Troubleshooting added.

[Flagrum]

Dubious:

0.809 INFO INPUT: Device created Controller (XBOX 360 For Windows) {97431A70-E54C-11e4-8001-444553540000}

00000.879 ERROR INPUT: setSpringAutocenter Controller (XBOX 360 For Windows) {97431A70-E54C-11e4-8001-444553540000} : Not implemented

 

00001.024 INFO INPUT: Joystick created[Controller (XBOX 360 For Windows) {97431A70-E54C-11e4-8001-444553540000}], ForceFeedBack: yes

 

Maybe somewhere a forgotten Xbox controller fell behind the PC or something? ;o)

[ehagendorff]

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

Edited January 5, 2016 by ehagendorff
Added Clean_Logs.zip

[BIGNEWY]

are you running a scripts folder from the saved games folder / dcs? if so clear it for now to take it out of the equation

[ehagendorff]

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.

[BIGNEWY]

No problem, are you running at max settings with 8gb ram or have you tried reducing the settings?

[ehagendorff]

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.

[BIGNEWY]

no problem, I will take another look at this in the morning with a fresh head, hopefully we will get to the bottom of the problem

 

edit:

 

was just digging around, and the FTProvider ref. in the crash most likely has something to do with freetrack. I will look into it some more in the morning

Edited January 6, 2016 by BIGNEWY

[ehagendorff]

**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

Edited January 6, 2016 by ehagendorff
RESOLVED ISSUE

[BIGNEWY]

Good to see you have it resolved :)

[tomekbrud]

Had the same issue with DCS: World but I sorted it out without loosing FreeTrack functionality:

 

In Freetrack folder I had to remove the file called ''NPClient64.dll'' which is necessary for BMS 4.33 64-bit to work. After removing it temporarily from the FreeTrack installation folder , DCS works fine!

 

Hope it'll help ;)