The Maze

Page: 1 2
ID:104647
 
Nov 16 2010, 4:57 am
Keywords: game, maze, testing
I've been bored and made very simple maze game. Currently it has only one level, but if there will be any interest I'll add more levels.

It uses dynamic lighting, meaning you won't see whole maze, it makes maze quite a challenge, though first maze is pretty easy.






Hub: http://www.byond.com/games/Ripiz/TheMaze
Nov 16 2010, 5:44 am
Pretty cool.
Nov 16 2010, 2:30 pm
It plays extremely slow for me. I think it has something to do with the lighting system.
Nov 16 2010, 4:10 pm
FYI: Pretty much unplayable on my semi-decent system. My CPU is at 50% while moving. Tried to do some video card profiling but I couldn't find anything useful.
Nov 16 2010, 6:41 pm
It was somewhat slow for me.. Though, I think it was really awesome. Work more on it! Oh man, this would be trippy.. If it was more fluid.

Imagine adding some creatures in it, and some other "tools".. Like types of lights, turning the lights off to avoid being seen, etc. I dunno, makes me want to make something like this... Haha. I think you could manage to make it creepy :D
Nov 16 2010, 6:55 pm
Please keep in mind, keypress only turns light, if it's not facing that direction, and won't move. Maybe some of you mistaken that with lag?
But generally yes, it is slow.

Chidori123 wrote:
It was somewhat slow for me..
It has to update a lot of objects, so yes, it is slow. I guess I could lower amount of objects, but shadowing quality would be lower quality too.

Imagine adding some creatures in it, and some other "tools"..
I'll think about it, but need optimizations first.

PopLava wrote:
Tried to do some video card profiling but I couldn't find anything useful.
Dream Seeker possibly uses hardware to render objects, but it cannot be used for lighting, or in some other way. So I have to use CPU to update ~6000 objects every step.
Nov 16 2010, 6:57 pm
Ripiz wrote:
Please keep in mind, keypress only turns light, if it's not facing that direction, and won't move. Maybe some of you mistaken that with lag?

I'm just holding down the right arrow button and it takes a few seconds between tile movements.
Nov 16 2010, 7:01 pm (Edited on Nov 16 2010, 7:09 pm)
Few seconds? Weird... According to profiling it's less than 0.2 seconds per step on my system. I have only 2.13 GHz processor.
Nov 16 2010, 8:26 pm
Only 0.2? It takes me 3 seconds to move 1 tile.
Nov 16 2010, 8:26 pm
What are your computer's specs?
Nov 17 2010, 4:31 am
Ripiz wrote:
What are your computer's specs?

dual geforce 8800
3g ram
Intel 2ghs

I think Kai has the slowest computer on the planet though. ;P
Nov 17 2010, 5:25 am
I have single GeForce 8800, 4GB RAM and Intel Dual Core 2.13GHz (E6400). Our PCs are similar so there shouldn't be such difference 0.o
Nov 17 2010, 1:24 pm
Ripiz wrote:
So I have to use CPU to update ~6000 objects every step.

Wait... what? Why? O_o
Nov 17 2010, 1:34 pm
I see how this effect could be useful, but for this application you'd get the same effect (and much better performance) from using the built in opacity variable to limit the player's sight.
Nov 17 2010, 5:41 pm
Forum_account
Effect won't be similar even if I set icon-size to 8 to match my current size. Opacity also has only fully visible or fully invisible option, AND it doesn't do different angles than 45 degree multiplier.

C_Dawg_S
To set correct shade depending on amount of light received.
Nov 17 2010, 11:12 pm
PopLava wrote:
Ripiz wrote:
What are your computer's specs?

dual geforce 8800
3g ram
Intel 2ghs

I think Kai has the slowest computer on the planet though. ;P

My computer sucks either way. :P

Nov 18 2010, 1:30 am
Ripiz wrote:
Effect won't be similar even if I set icon-size to 8 to match my current size. Opacity also has only fully visible or fully invisible option, AND it doesn't do different angles than 45 degree multiplier.

For the corridor environment in the game the effect will be similar enough. The purpose of the shadows is to limit what you can see. The quality of the shadows doesn't improve the gameplay.

If you want nicer looking shadows I suggest doing something like this. That way you have one object per turf to represent the lighting so you don't need to update as many objects.
Nov 18 2010, 2:56 am
It looks similar to what I use, except D4RK3 54B3R uses 32x32 blended dark shades, and I use 8x8 unblended shades
Nov 18 2010, 2:58 am
Right, and that means you can use one 32x32 icon per turf instead of 16 8x8 icons. Instead of updating ~6400 objects for a 20x20 view you'd update ~400 objects.
Nov 18 2010, 3:00 am
I update only what's in lights reach, not everything. My objects are actually on map, not players screen.

proc/gUpdateLighting()
    spawn()
        for(var/light/L in lights)
            for(var/lighting_sub/O in oview(L.distance + 1, L))
                O.Update()
Page: 1 2