Home Forums Game Integration [Solved] ISE crashes on ED:Horizons start

Viewing 15 posts - 1 through 15 (of 30 total)
  • Author
    Posts
  • #4378
    Jon Burgin
    Participant

    I just got the eye tracker, seems great. However, when I start horizons, ISE simply closes.

    Also note that it ‘forgets’ the location of the eliteDangerous64 executable each time I run it. This makes me suspect I might have a permissions problem?

    I tried the substitution of the freetackclient dll as suggested in other entries, it had same behavior, so I put it back.

    I looked through the logs found at [local app data]/tobbi Interaction/InteractionLog, here are some of the entries:

    
    2016-02-13 20:58:51,797 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    ProcessInfo GetProcessInner, read file version, Could not access executable (pid: 5820) 'C:\WINDOWS\system32\DsmUserTask.Exe'
    
    2016-02-13 21:03:59,021 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 8820, error: System.ComponentModel.Win32Exception (0x80004005): Access is denied
    2016-02-13 20:58:53,499 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    ProcessInfo GetProcessInner, read file version, Could not access executable (pid: 4776) 'C:\Windows\System32\RuntimeBroker.exe'
    
    2016-02-13 20:58:53,583 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 604, error: System.ComponentModel.Win32Exception (0x80004005): Access is denied
    
    2016-02-13 20:58:58,126 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    ProcessInfo GetProcessInner, read file version, Could not access executable (pid: 420) 'C:\WINDOWS\system32\DsmUserTask.Exe'
    
    2016-02-13 20:59:34,034 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 10008, error: System.ComponentModel.Win32Exception (0x80004005): Access is denied
    
    2016-02-13 20:59:34,361 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 8520, error: System.ComponentModel.Win32Exception (0x80004005): Access is denied
    
    2016-02-13 20:59:34,362 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 8360, error: System.ComponentModel.Win32Exception (0x80004005): Access is denied
    
    2016-02-13 20:59:34,678 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 7308, error: System.ComponentModel.Win32Exception (0x80004005): Access is denied
    
    2016-02-13 20:59:39,339 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 2004, error: System.ComponentModel.Win32Exception (0x80004005): Access is denied
    
    2016-02-13 20:59:39,339 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 4428, error: System.ComponentModel.Win32Exception (0x80004005): Access is denied
    
    2016-02-13 20:59:40,910 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 0, error: System.ComponentModel.Win32Exception (0x80004005): The parameter is incorrect
    
    2016-02-13 21:00:14,554 [38] INFO Tobii.EyeX.Interaction.Foundation.States.EyeTrackingScreenBoundsProvider - 
    Tracked Screen Bounds set to X: 1920.000 Y: 0.000 Width: 1920.000 Height: 1080.000
    
    2016-02-13 21:00:14,557 [1] DEBUG Tobii.EyeX.Interaction.Foundation.States.EyeTrackingScreenManager - 
    EyeTrackingScreenManager: Update screen bounds to 1920,0,1920,1080
    
    2016-02-13 21:01:12,932 [38] DEBUG Tobii.EyeX.Interaction.EyeXInteractionTutorialLauncher - 
    Received request to launch intro after creating profile Jon No Glasses
    
    2016-02-13 21:01:13,003 [38] DEBUG Tobii.EyeX.Interaction.EyeXInteractionTutorialLauncher - 
    Successfully launched intro.
    
    2016-02-13 21:01:14,531 [1] DEBUG Tobii.EyeX.Interaction.Core.TouchEmulation.TouchInjectionRunner - 
    TouchInjectionRunner Reset
    
    2016-02-13 21:01:14,570 [1] INFO Tobii.EyeX.Interaction.Modules.TouchPad.TouchpadService - 
    Failed listing Synaptics devices: System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {F418EBA0-6A10-4482-AC2B-2D10C807073A} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
       at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
       at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
       at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
       at System.Activator.CreateInstance(Type type, Boolean nonPublic)
       at System.Activator.CreateInstance(Type type)
       at Tobii.EyeX.Interaction.Modules.TouchPad.TouchpadService.ListSynapticTouchpads() in D:\build\f1f54cb3c64ad990\Source\Modules\Tobii.EyeX.Interaction.Modules.TouchPad\TouchpadService.cs:line 59
    
    #4382
    Henrik [Tobii]
    Participant

    Also note that it ‘forgets’ the location of the eliteDangerous64 executable each time I run it. This makes me suspect I might have a permissions problem?

    We’re investigating this bug atm. Try exiting ISE (by clicking the Infinite Screen Extension systray icon and selecting “Quit”) directly after you’ve configured all your settings. The settings should then be preserved when ISE starts.

    I tried the substitution of the freetackclient dll as suggested in other entries, it had same behavior, so I put it back.

    ISE currently uses vJoy and not FreeTrack for sending gaze data to E:D the changing the freeetrackclient.dll will not make any difference.

    I looked through the logs found at [local app data]/tobbi Interaction/InteractionLog, here are some of the entries:

    Tobii Interaction is a different component of the software stack and has nothing to do with ISE (unless it somehow crashes the engine service that ISE depends on). ISE erros are logged in %PROGRAMDATA%\Tobii\Tobii InfiniteScreen\Logs

    Are you logged in as an admin user or a normal user?

    #4385
    Jon Burgin
    Participant

    Thank you for your prompt reply.
    I am a regular user. Should I run infinite screen application as admin?

    Here are the errors from the infiniteScreen logs:

    
    2016-02-13 22:44:45,957 [VJoyAccumulativeHidMapper Thread] ERROR Version:1.0.2.317 System.AppDomain - 
    Application Unhandled exception
    System.ArithmeticException: Function does not accept floating point Not-a-Number values.
       at System.Math.Sign(Double value)
       at Tobii.Oem.Gaming.InfiniteScreen.Core.HidMapperSettings.SensitivityTransform(Double value)
       at Tobii.Oem.Gaming.InfiniteScreen.Core.AccumulativeHidMapper.Map(TimeSpan timeDelta)
       at Tobii.Oem.Gaming.InfiniteScreen.Core.HidMapper.ThreadLoopProcedure()
       at Tobii.Oem.Gaming.Common.LoopedThread.ThreadLoop(Object state)
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart(Object obj)
    
    2016-02-13 22:55:46,274 [DirectInputKeyboard Thread] WARN Version:1.0.2.317 Tobii.Oem.Gaming.Common.Input.DirectInputKeyboard - 
    Could not get keyboard state! SharpDX.SharpDXException: HRESULT: [0x8007000C], Module: [SharpDX.DirectInput], ApiCode: [DIERR_NOTACQUIRED/NotAcquired], Message: The access code is invalid.
    
       at SharpDX.Result.CheckError()
       at SharpDX.DirectInput.Device.GetDeviceState(Int32 arg0, IntPtr arg1)
       at SharpDX.DirectInput.CustomDevice

    3.GetCurrentState(T& data)
    at Tobii.Oem.Gaming.Common.Input.DirectInputKeyboard.ThreadLoopProcedure()`

    #4387
    Henrik [Tobii]
    Participant

    I am a regular user. Should I run infinite screen application as admin?

    Yes, ISE currently needs to be run as administrator.
    Try following the steps in this post:
    http://developer.tobii.com/community/forums/topic/some-feedback/page/2/#post-4333

    #4388
    Jon Burgin
    Participant

    Thanks again for the quick reply.
    Unfortunately I’m a little stuck at step 5 of the post you mentioned.
    While I enabled the Administrator account, I cannot seem to find where its profile is kept in windows 10.
    Can you please suggest how to locate: <ADMINUSERLOCALAPPDATA>?
    It does not appear to be in the users directory.
    Thanks again for your time and patience.

    #4389
    Jon Burgin
    Participant

    OK, I manually create the profile directory and that seemed to allow me to proceed.
    Is it correct that I will no longer need to run the ISE as admin after this procedure?

    #4390
    Jon Burgin
    Participant

    So now, when I start horizons I get root element missing on ISE.

    #4405
    Jon Burgin
    Participant

    Any help with the “Error: Root element is missing” from ISE, the moment Horizons starts up?

    Other fact to note is I do have a full ch products setup(throttle, stick, rudder).
    My binds look like the following (What is DeviceIndex?)

    
      <HeadLookPitchAxisRaw>
        <Binding Device="vJoy" Key="Joy_YAxis" DeviceIndex="0" />
        <Inverted Value="0" />
        <Deadzone Value="0.0" />
      </HeadLookPitchAxisRaw>
    
      <HeadLookYawAxis>
        <Binding Device="vJoy" Key="Joy_XAxis" DeviceIndex="0" />
        <Inverted Value="0" />
        <Deadzone Value="0.0" />
      </HeadLookYawAxis>
    #4428
    Henrik [Tobii]
    Participant

    So now, when I start horizons I get root element missing on ISE.

    That’s odd. “Error: Root element is missing” indicates a corrupted config file. What does the first two lines of your Custom.x.x.binds file look like?

    Take a look at this thread:
    http://developer.tobii.com/community/forums/topic/infinite-screen-extension-step-by-step-troubleshooting/#post-4393

    If that doesn’t fix your problems then please contact the Tobii support.

    #4468
    Jon Burgin
    Participant
    <?xml version="1.0" encoding="utf-8"?>
    <Root PresetName="Custom" MajorVersion="1" MinorVersion="8">
    ...
    
    </Root>
    #4469
    Henrik [Tobii]
    Participant

    I would advise you to do a remote session with the support.

    #4480
    Jon Burgin
    Participant

    Thanks Henrik,

    What are their hours of operation?

    #4483
    Henrik [Tobii]
    Participant

    I believe should be open between 08.00 and 17.00 CET (UTC+01:00)

    #4537
    Jon Burgin
    Participant

    During our live session, we were unable to get the ED launcher to verify the installation files. I finally got it to do this (took a really long time, maybe 10 minutes or so).

    Afterwards, ISE crashes when ED:Horizons starts.

    The hud log contains the following

    
    2016-02-24 21:54:40,798 [WinEventWatcher] DEBUG Tobii.EyeX.Interaction.Core.Processes.ProcessInfoFactory - 
    Can not access process: 10332, error: System.ComponentModel.Win32Exception (0x80004005): Access is denied
    #4573
    Henrik [Tobii]
    Participant

    The latest version of ISE should hopefully resolve all the problems you’ve been experiencing.

Viewing 15 posts - 1 through 15 (of 30 total)
  • The topic ‘[Solved] ISE crashes on ED:Horizons start’ is closed to new replies.