The "How do I..." Thread

[VGA]

How do I disable SLADE autobackups? (I make my own backups)

[Coincident]

How do I disable SLADE autobackups? (I make my own backups)

Thumbs up for that question. Those .bak files are really annoying.

The OCD in me keeps deleting them over and over.
The clumsy in me sometimes deletes wrong files...

Don't get me wrong, I'm sure the backups were implemented with the best intentions. But a way to turn them off would be great.

[Ozymandias81]

How do I disable SLADE autobackups? (I make my own backups)

If I'm not wrong, I remember that some old Slade versions had disable options... but I'm not sure.
Also, you may try to contact Gez or sirjuddington for the purpose. Look at this.

[Gez]

They cannot be disabled.

[edward850]

Besides, it's all fine and good to say you don't need automatic backups, but then you're sort of missing the point of automatic backups. You're better off having them and not needing them, as opposed to not having them and shooting yourself in the foot.

[VGA]

They cannot be disabled.

Can you please add a toggle?

[Kostov]

Edward has a point. You should keep them.

[Coincident]

Besides, it's all fine and good to say you don't need automatic backups, but then you're sort of missing the point of automatic backups. You're better off having them and not needing them, as opposed to not having them and shooting yourself in the foot.

My point was; I have shot myself in the foot, for having them.

The only problem is where the backups are placed: exactly in the same folder as the .pk3 / wad you're working on (I presume that's VGA's problem too).
Anyone who wants to keep the workspace clean and tidy is going to have a bad time...

IMO, it would be better if they could be placed in some temp folder (e.g. the SLADE instalation folder).
That would be the best of both worlds: tidy workspace + automatic backups that nobody feels the need to delete

[edward850]

My point was; I have shot myself in the foot, for having them.

Sorry, you can't make a mistake of losing all your work via critical user error or generic data destruction by having them, hence the point. This is data/project integretry 101.
If your workflow is complicated by automatic background backups, it's time to readjust your workflow. Sure, put them elsewhere, but there is no feasible excuse to outright remove them.

[Zeberpal]

Hmm, whenever I try to tid Skybox Viewpoint, whole sky turns into white-lightblue striped once. UDMF.

[Graf Zahl]

On the line type 121 thing, ....

which means that you have to search and copy the 121 occurrences in the original first, and then apply to the conversion.

What's unclear from your post is what it does with the Line_SetIdentification args and comparablae info from other linedefs. Are those line IDs and flags preserved (i.e. copied to the actual line ID field) or do they have to be respecified manually?

[edward850]

Hmm, whenever I try to tid Skybox Viewpoint, whole sky turns into white-lightblue striped once. UDMF.

The skybox which a sector uses is determined by placing a SkyPicker thing in a sector with F_SKY1 on the ceiling and/or floor. Set the thing's first argument to match the TID of a SkyViewpoint and instead of seeing the sky texture in that sector, the player will see the skybox pointed to. You can use this to create a map with many different skies in it.

By setting a TID, you are implying it's a unique skybox, not the default one.

[Zeberpal]

By setting a TID, you are implying it's a unique skybox, not the default one.

Hmm, so in order to manipulate with skybox viewpoint (change position, angle, etc) I have to SkyPicker all the sectors with relative tid?

[edward850]

Yes.

[Zeberpal]

Thanks for that, it works. I keep messing with sky though. So i tid SkyboxViewpoint with 100, but I have to change pitch and angle for it

Code: Select all

ChangeActorAngle(100, 225, 0);
ChangeActorPitch(100, 90, 0);

For some reason it did nothing, really. It stays as it was. I wonder what could go wrong?