The first time I ran across this puzzle – a paper and pencil afffair – I had to do it backwards to get the answer. That is why I provided the map – so you were playing by the same rules that I was

gryff

http://dl.dropbox.com/u/9694847/maze.png

You are either looking down a short or long corridor and you you should know the last gate you passed through – not difficult to figure out where you are. It is not one of those twisting and turning dungeon mazes where your place on the map would be helpful.

The map is there for a different purpose – to help you figure out “how to turn around” – to find away to approach the gates from a different direction. So for example, the blue gate at the top of the starting vertical corridor you approach from the south when it is active, how can you approach it from the north when it is active? That is a gate you have to approach from the north side to solve the puzzle.

Without the map – you might try for days to figure that out.

gryff

“btw do you use Time.deltatime for your movements?”

The player movement is just the same basic Gabriel Williams movement script – tweaked variables and a few bells and whistles added (speed change, show map).

The rotating vortex in the gates is just a very thin box with the vortex texture and a tiny script with :

“transform.Rotate(0, 0, spin);

in the Update function. (“spin” is a public variable set in the Inspector.)

That means of course it is frame rate dependent – so I should probably make it time dependent. (Which is probably why you asked about “Time.deltatime” )

This was just a little divergence from my thrashing about with an inventory GUI.

To me it was a learning exercise for interactions between the player, the red and blue gates, and the GUI display.

I find the best way to learn is to do something with this scripting stuff – then try to work out why some bits don’t work!

Cheers,

gryff