Jump to content

LCtrl+RCtrl+End = TARGET Script Editor Crash


Glow

Recommended Posts

L Ctrl + R Ctrl + End = TARGET Script Editor crash

 

To replicate:

 

Start TSE and use you keyboard:

Press L Ctrl and hold

Press R Ctrl and hold

Press End and hold

Release End

Release R Ctrl

Release L Ctrl

Press L Ctrl and R Ctrl = CRASH

 

Is it a TSE bug or is it something wrong with my system?

 

EDIT: Solved! Go to post #8


Edited by Glow
Link to comment
Share on other sites

This issue start from a running scrip that crash SE. Then by elimination I get to crashing it by simple pressing keys on my keyboard with no script loaded... I think my system need fixes/ updates. When I check an Event Viewer I found KERNEL.DLL as a source of this crash.

 

For a 1s I thought that's maybe well know SE bug.

Thanks for response.

Link to comment
Share on other sites

  • 2 weeks later...

I'm after Win10 updates. This issue still exists and I'm run out of ideas. I check on my other (fresh-test) partition with Win10 and TARGET SE is working fine. I suppose that TARGET need some windows services that are not running on my sim system but I can't tell witch ones.

 

This is weird... :helpsmilie:

 

steps taken:

 

- Win10 updated 1903 latest

- TARGET reinstalled, HOTAS not even plugin to PC, no script running

- start SE, press keys and crash

 

- Event Viewer pointing at: KERNELBASE.DLL / NET Framework 4.0

- Reinstalled .NET Framework (turning off and on in Windows features with restart)

- Microsoft .NET Framework Repair Tool - only warnings in a log

 

- .NET Framework Cleanup Tool - all looks ok

https://blogs.msdn.microsoft.com/astebner/2008/08/28/net-framework-cleanup-tool-users-guide/

 

- NET Framework verification tool - 4.0 and up all good

https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-guide/

 

- Visiual C++ libraries repaired/reinstalled from 2010 up

 

 

Event Viewer errors:

 

#1 .NET Runtime

 

Application: TARGETScriptEditor.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ArgumentOutOfRangeException

at System.ThrowHelper.ThrowArgumentOutOfRangeException(System.ExceptionArgument, System.ExceptionResource)

at System.Collections.Generic.List`1[[system.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].RemoveAt(Int32)

at ScriptEditor.KeyboardHook.CheckKeyStates()

at ScriptEditor.KeyboardHook.HookCallback

 

----

 

#2 Application Error

 

Faulting application name: TARGETScriptEditor.exe, version: 3.0.18.328, time stamp: 0x5abb580b

Faulting module name: KERNELBASE.dll, version: 10.0.18362.418, time stamp: 0xfba22159

Exception code: 0xe0434352

Fault offset: 0x000000000003a839

Faulting process ID: 0x1a6c

Faulting application start time: 0x01d589065e61f1ba

Faulting application path: C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETScriptEditor.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: 6c75be09-e7c2-43a1-8496-3f2e4c0cb72c

Faulting package full name:

Faulting package-relative application ID:

 

----

 

#3 Application Error

 

Faulting application name: TARGETScriptEditor.exe, version: 3.0.18.328, time stamp: 0x5abb580b

Faulting module name: KERNELBASE.dll, version: 10.0.18362.418, time stamp: 0xfba22159

Exception code: 0xc000041d

Fault offset: 0x000000000003a839

Faulting process ID: 0x1a6c

Faulting application start time: 0x01d589065e61f1ba

Faulting application path: C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETScriptEditor.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: 20e8280b-58c9-4de3-bd81-4fcb8b777c22

Faulting package full name:

Faulting package-relative application ID:

Link to comment
Share on other sites

[solved]

 

I found it! I think it's a Script Editor bug.

 

Option menu > General tab > Windows mode hot key.

There is a key combo for stoping a scrip in emergency - when this is Enable, it crash my editor by LCTRL+RCTRL+END, LCTRL+RCTRL press.

 

I haven't changed the Ctrl+Alt+Pause combo. Only enabled this for some reason and forgot about it.

 

Disabling this solving this issue. DO NOT USE!

 

 

Grate... at least I refreshed and updated my win10.

 

Thanks SGT Coyle for rep. You can try to crash your editor to see this.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...