Sending text or commands via Torch GUI chat causes application crash. about torch

[Varaxian]

Yup. Doesn't matter. Run the compatibility tool.

…

On Jul 28, 2017 2:04 PM, "kurazarrh" ***@***.***> wrote: @Varaxian <https://github.com/varaxian> I'm already running the .exe with the "Run as Administrator" box checked (which is what running the compatibility tool for access permissions will turn on), and I've tried running it in compatibility mode for everything available in the list: WinServ2008R2SP1, Vista, VistaSP1, VistaSP2, and Win7. I've been doing some more digging, and it does appear to be related to making a call to the window manager. The important part of that stacktrace is right at the top: System.InvalidCastException: Unable to cast object of type 'Microsoft.Windows.Themes.ClassicBorderDecorator' to type 'System.Windows.Controls.Border'. I'm thinking this was developed on a Win10 machine that supports that typecast action, whereas older OSes may not. Either that, or the issue lies in the Server version of the OS, which has a less-advanced window theme manager. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#51 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXurF5HpA5GLcXKxnwDPig2kFJaB-ph8ks5sSjC6gaJpZM4Okqph> .

[XeroCreator]

Did you have essentials on a mod-list? I can't re-pro this.

[kurazarrh]

I just checked the SpaceEngineers-Dedicated.cfg to be sure, but no, the Essentials mod isn't included. I also cleared out my mods folder entirely before migrating from SESE to Torch.

In case it helps, here's my current mod list. Or, I can upload the full log if you need to see it.

<Mods> <unsignedLong>646796262</unsignedLong> <unsignedLong>753102087</unsignedLong> <unsignedLong>899070352</unsignedLong> <unsignedLong>473571246</unsignedLong> <unsignedLong>682707915</unsignedLong> <unsignedLong>806331071</unsignedLong> <unsignedLong>678678053</unsignedLong> <unsignedLong>861361363</unsignedLong> <unsignedLong>595665128</unsignedLong> <unsignedLong>570033657</unsignedLong> <unsignedLong>652337022</unsignedLong> </Mods>

Edit: I'll figure out how to format this eventually...

[kurazarrh]

Just to make sure I wasn't crazy, I fired up a new server, no mods. I create the new server in the vanilla DS application, created a new installation of Torch in another folder, and pointed it at the fresh DS world, and got the same crash. I've finally got attachments working, so I've attached the full log file.

One thing I'm noticing is that it seems to be related to the Windows, er, window manager. Could this bug be caused by running Torch on Windows Server 2008 R2? It doesn't have any of the advanced window styling capabilities that the non-server SKUs have, which would naturally cause any calls or typecasts requiring those methods to fail.

GitHub
Torch-2017-07-27.txt

[Varaxian]

I've been having no issues with this. I'd suggest running Windows compatibility tool for access permissions. Fixed me up on a couple of things.

[kurazarrh]

@Varaxian I'm already running the .exe with the "Run as Administrator" box checked (which is what running the compatibility tool for access permissions will turn on), and I've tried running it in compatibility mode for everything available in the list: WinServ2008R2SP1, Vista, VistaSP1, VistaSP2, and Win7.

I've been doing some more digging, and it does appear to be related to making a call to the window manager. The important part of that stacktrace is right at the top:

System.InvalidCastException: Unable to cast object of type 'Microsoft.Windows.Themes.ClassicBorderDecorator' to type 'System.Windows.Controls.Border'.

I'm thinking this was developed on a Win10 machine that supports that typecast action, whereas older OSes may not. Either that, or the issue lies in the Server version of the OS, which has a less-advanced window theme manager.

[kurazarrh]

@Varaxian Already did. Didn't help.

[Jimmacle]

What version of Windows are you using? This seems like some kind of .NET incompatibility.

[kurazarrh]

I'm running Windows Server 2008 R2. (6.1.7601)

.NET version is 4.7.02053.

Please let me know if there is any other information I can provide to help debug this!

[Jimmacle]

See #68, it appears to be an issue for people using the Windows Classic theme. Working on a fix.