SLADE Discussion - Latest: v3.1.12 (26/May/2020)

[Gez]

With a size of 256, that means your images are 16x16. That's too small for a Doom flat, so they're identified as something else. Proper flats should be 64x64 (4096 bytes).

[sirjuddington]

3.1.12 is up, with a bunch of fixes and minor improvements.

[Hexereticdoom]

I have updated two days ago to version 3.1.12, and I've been working with it without any major problems... until today.

When I have opened it up some minutes ago to continue editing my mods, Windows Security Defender has jumped up of a sudden telling me that a trojan horse has been detected in the Slade executable file, and then it has removed the shortcut and moved the exe file to quarantine byself. WTF?! What's going on here?

Here is the report message in Windows Security program:

Code: Select all • Expand view

Trojan:Win32/Fuery.C!cl

Nivel de alerta: Grave
Estado: En cuarentena
Fecha: 01/06/2020 18:43
Categoría: Caballo de Troya
Detalles: Este programa es peligroso y ejecuta comandos de un atacante.

Elementos afectados:

startup: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\SLADE\SLADE.lnk

file: C:\Program Files (x86)\SLADE\SLADE.exe

file: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\SLADE\SLADE.lnk


Is somebody else affected by this problem? May be a false positive or what? Please let me know, I need to continue working with Slade tool...

[Blue Shadow]

I got the same thing as you just a few hours ago. Even though I've been using that version of SLADE for a few days now.

[Hexereticdoom]

Phew, good to know it has been not just me! Anyway, I hope SirJuddington can fix this as soon as possible...

At the moment I have reverted to previous version (3.1.11) and seems it is totally clean.

[Enjay]

There's a very good chance this is just a "false positive" from defender. i.e. 3.1.12 is probably totally clean too.

[JPL]

I run into this regularly with software I distribute (Playscii). Basically every time I post a new build with a slightly different signature (hash of the program's contents, however they define it) it trips a new false positive.

I submit my software to this page https://www.microsoft.com/security/port ... ubmit.aspx and it's usually confirmed as a false positive within 1-2 days, and the next round of Windows Defender definitions that goes out stops flagging it. It's a pain, but it's been a consistent process so far.

One thing that might be tripping it in SLADE's case is having an embedded Lua interpreter - Defender seems twitchy about any program that can execute arbitrary user-provided scripts (my software can exec() Python scripts), as apparently various kinds of malware do that.

[Gothic]

Hopefully the syntax highlighter will recognize all Decorate functions for the stable 3.2.0, as there are functions and flags that are not recognized yet by the text editor.

[Hellstorm Archon]

Well, this seems to now happen every time I load up a sprite or texture (or any sort of graphic):

This happened both before and after I updated to the latest version of SLADE, and I recently updated my Intel drivers.

[Gez]

If it happened also before you updated SLADE, that means that it suddenly started happening in a version that worked for you before, so it's not a regression.

Perhaps it was that driver update? What if you rollback?

Also you can try the 3.2 beta.