Skip to main content

Real VS Fake: lighting.

In a video game, what is real?

This is, strangely, a question that infects many discussions about making games, much more so that those about playing games.

Well, some things can be modeled somewhat realistically; ray tracing, shadow casting, physics, real time reflections, on the fly destructible or deformable terrain, goal orientated action planning AI... These are all "realistic" approaches" to making games, or you might say simulation based approaches. Other times people use tricks; pre-baked lighting, animated pseudo-physics, on-rails movement, scripted AI, matcap reflections... These are all cheats, to save development time and processing power. They don't simulate real word physics or behavior but simply try to mimic the results.

Players of games are rarely concerned with with such things. Everyone who plays a game knows deep down that it is not real, and they don't expect it to behave realistically. Sometimes they get annoyed with games which show bad faith, enemies which respawn inside a locked room. Guns with infinite bullets. Cars which don't dent or scratch when you crash them at 200MPH. Who wouldn't get annoyed? We've got used to better.

But in other cases things such as shadow casting lights... If you've played Diablo 3, a AAA modern game, you might not have noticed that there's only one shadow casting light in the scene, and that shines from above the player. None of the other lights cast shadows. How does no one notice that? Someone asked me today; "Why don't you make your lighting system better, more like Diablo 3?"

Actually right now my lighting system is much more sophisticated than Diablo 3. I have multiple shadowcasting lights in the scene, casting "soft" shadows, unlike the hard edges shadows of Diablo. But I wonder if I'm wasting my efforts there.

Look at the picture above.
It seems like there is a sword on the floor, glowing with light. Actually, the sword isn't glowing. It's just a simple plane with a texture that has additive type transparency. A trick that predates real time shadows, you can see it used frequently in games from the last century! If you move close you'll see that it doesn't illuminate the player, it doesn't cast shadows...

Diablo 3 is packed with tricks like that. simple 2d shaders, particle effects etc... But the basic lighting is very simple indeed. When people praise the lighting, they are really praising the fake effects, not the lighting setup itself.

So maybe I should just focus on adding more cheesy visual effects and shaders instead of trying to simulate real torchlight. In the end, who's going to notice it but me? If the game has a single unidirectional shadow lamp, no one is going to notice, and the result will be much faster on low end computers.

Comments

  1. Very simple comment from my distant past:
    "It is irrelevant how you do it, just as long as it looks right to you"
    So take whatever shortcuts, do whatever you need, and cut every corner to get it right :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Automating Level imports from Blender to Godot

  Recently I've been making some levels in Blender an importing them into Godot. There are only about 7 or 8 shaders for each level, not counting dynamic objects which will be added later. But to improve rendering performance, it can be a good idea to split the meshes up into sections. At that point you might be faced with a list like this: Or it might be even more chaotic, if you didn't use simple names for the objects in your level. So it can take a long time to sort out all the meshes, make them unique and add textures and so on. Blender imports with simple Blender textures, or with placeholder materials. This is sometimes OK, but if your Godot shaders are very different to those used by Blender, it means applying new materials to every mesh object in the level when you import the scene. I found that during the design process, I was importing and readying a level several times before I was happy with the final layout. So at first I was wasting a lot of time. In Blender, I us

Upstairs / Downstairs.

I've decided to make my prefabs multilevel. Later this should allow me to add pit traps and other great stuff. It also makes it easier to line up stairs so that you can exit them on the same co-ordinates where you entered them. The prefab editor is pretty much finished, it just needs some code for loading up prefabs from a saved dictionary, so that they can be checked or edited. The entries will need to be forwards compatible, so I'll be loading each tile and then translating the indexes to a new array, that way if I add extra indexes or extra info (like traps or puzzles) I'll be able to update existing prefabs to work with the new standard. Click for a video.

Advice needed on tilesets...

I need some advice on which is the best way to handle building the dungeon. Right now I'm using prefabs for my dungeon, they have a north south east and west section for each "room": The basic tileset. This has several advantages, and also several disadvantages. Firstly I can have curved rooms, I can have tunnels and other interesting shapes. The tilesets can look quite nice with a little work. On the other hand I can't easily get the navigation data before building the map and once the map has been built I can't make changes to the layout, like having active pit traps or believable secret doors. Although the rooms are interesting, they are quite repetitive, and it takes a lot of effort to make even a few different variations. Also rooms are constrained to one size. A newer version of the tileset with a lot of variant parts for making more interesting rooms. To create a tile set is a real headache too. Planning how to lay out the UVs, trying to cra