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

Any utility that assists in the creation of mods, assets, etc, go here.
Forum rules
The Projects forums are ONLY for YOUR PROJECTS! If you are asking questions about a project, either find that project's thread, or start a thread in the General section instead.

Got a cool project idea but nothing else? Put it in the project ideas thread instead!

Projects for any Doom-based engine (especially 3DGE) are perfectly acceptable here too.

Please read the full rules for more details.

Re: SLADE Discussion - Latest: v3.1.11 (04/Mar/2020)

Postby Gez » Wed Apr 08, 2020 2:06 am

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).
Gez
 
 
 
Joined: 06 Jul 2007

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

Postby sirjuddington » Mon May 25, 2020 6:33 pm

3.1.12 is up, with a bunch of fixes and minor improvements.
User avatar
sirjuddington
 
Joined: 16 Jul 2003
Location: Australia
Discord: sirjuddington#7496
Github ID: sirjuddington

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

Postby Hexereticdoom » Mon Jun 01, 2020 11:08 am

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 allExpand 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... :?:
User avatar
Hexereticdoom
Don't make me angry or I'll bite you! Heheheee...
 
Joined: 08 Aug 2013
Location: Spain

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

Postby Blue Shadow » Mon Jun 01, 2020 11:17 am

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.
User avatar
Blue Shadow
 
 
 
Joined: 14 Nov 2010
Operating System: Windows 10/8.1/8/201x 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: ATI/AMD (Modern GZDoom)

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

Postby Hexereticdoom » Mon Jun 01, 2020 11:32 am

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.
User avatar
Hexereticdoom
Don't make me angry or I'll bite you! Heheheee...
 
Joined: 08 Aug 2013
Location: Spain

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

Postby Enjay » Mon Jun 01, 2020 11:41 am

There's a very good chance this is just a "false positive" from defender. i.e. 3.1.12 is probably totally clean too.
User avatar
Enjay
Everyone is a moon, and has a dark side which he never shows to anybody. Twain
 
 
 
Joined: 15 Jul 2003
Location: Scotland

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

Postby JPL » Mon Jun 01, 2020 12:36 pm

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.
User avatar
JPL
 
 
 
Joined: 09 Apr 2012

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

Postby Gothic » Wed Jun 03, 2020 12:49 pm

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.
User avatar
Gothic
To be fair, you have to have a very high IQ to understand ZScript.
 
Joined: 17 Jun 2011
Location: Where it all began...
Discord: #1462

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

Postby Hellstorm Archon » Wed Jun 03, 2020 3:06 pm

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


This happened both before and after I updated to the latest version of SLADE, and I recently updated my Intel drivers.
User avatar
Hellstorm Archon
Will debase self for street cred.
 
Joined: 25 Oct 2010
Location: 404 Error- Location of User Not Found
Discord: Man of Doom#4046

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

Postby Gez » Thu Jun 04, 2020 1:39 am

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.
Gez
 
 
 
Joined: 06 Jul 2007

Previous

Return to Editors / Asset Manipulation

Who is online

Users browsing this forum: No registered users and 2 guests