This was reported in A7.07.

- Apply texture to block.
- Check Texture Lock.
- Move Block.
- Texture did infact stay locked.
- Build Block. (even cancel build dialogue before building)
- Click back onto Wed top view.
- Texture will shift back to unlocked co-ordinates, or scrambled co-ordinates.
- Built block will also be scrambled. (if you built it)

-- Work around remove texture lock before building.
Very frustrating if just spent hours setting up locked textures and forget to unlock, before build.

Jethro.

This was fixed a long time ago, according to the bug list - but maybe it reappeared for some reason. I'll check.

I've checked, but can not confirm the problem, at least not the way you described it. Texture Lock works fine. Make sure that you're not accidentally using an old WED that had this problem.

If you think that the problem still exists, can you give a step by step description how to reproduce it, starting with a blank level?

OK Found another bug whilst trying to simulate this from a blank level.

- Open Wed.
- New Level
- Add cube large
- Apply default texture to cube
- set texture lock on cube
- Move cube into y axis slightly
- rotate cube slightly
- texture is still locked.
- build simple map.
- Click back in top view, now texture does remain locked, this is where it normally gets corrupted ????
- However now if you Run Level, it CRASHES.
- May still be related to locking I dunno.

In above example texture did remain locked, but the simple map would not run to preview the cube.

I'll need to look further into lock problem, tomorrow, I need to get some sleep now.

Jethro.

In your second description, with "it crashes" do you mean WED crashes, or the engine crashes? What's the content of the log files - acklog.txt or wed.txt?

@jcl This is a very easy to reproduce bug...
Build an empty map WITHOUT saving it and then press run (=>exception in blablabla)

Obviously the engine crashes, when it tries to run untitled.wmb (just untitled.wmb, other non existing files are working).

The engine crashes if you don't do a "save as".
ie. If you run the level as untitled.wmb it crashes the engine.
It's OK after you "save as" something else and build and run.

In A7.07 you could run as untitled.wmb, you just got a warning, but it still previewed the level/map_ent.

As far as the texture lock problem, we tried this on 2 machines the other day, and It failed on both.
I was sure we were using 7.50.
I am unable to get it to fail again, sorry for false alarm if there is nothing wrong.

I'll let you know if we can re-produce it again, consistently.

Jethro.

Thanks - you're right, the engine crashes when running untitled.wmb. This will be fixed. You can not compile and run a level level without having saved it. I overlooked this in Jethro's description. But it's apparently unrelated to a texture lock problem.

OK I'm not going mad, here's how to reproduce texture lock bug in A7.50.
1. - New map
2. - add cube small
3. - add another cube small
4. - Place cubes next to one another butted together.
5. - Apply default texture to both cubes.
6. - group the 2 cubes.
7. - Set Texture Lock On, in object properties for group.
8. - move and rotate blocks.
9. - open build dialogue.
10 - Either build or cancel build it doesn't matter.
11 - Click in any WED window.
12 - You should now have jumbled texture allignment.
Tested on 2 machines with A7.50

Jethro.

Here's another texture Lock bug we found.
1 - Add a cube to a New level.
2 - Apply default texture to cube.
3 - Lock textures on Block.
4 - Move cube to the right, in top view.
5 - Unlock texture.
6 - Move block up and down in top view.
7 - Textures now move on the faces that are perpendicular (90 degrees) to the move direction.
8 - Before the texture was locked and Normally, these faces textures don't move, when moving the block in that direction.

Jethro.