Browse thread
[Caml-list] OCamlSDL
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | John Max Skaller <skaller@o...> |
| Subject: | Re: [Caml-list] OCamlSDL |
Sven wrote: > >Yes, if they are clearly isolated, which is something that ocaml makes easier, >then this could be done easily. > This is actually very hard to do. In general, there is a tight integration between graphics and game-play engine. Mainly, this is because realtime behaviour demand it: even abstraction layers like D3D etc cause serious problems due to to inadequate coupling .. Diablo II is a pefect example of extremely bad interactive design precisely because it didn't lock the frame rate down, or phase lock the NPCs properly...the graphics were absolutely superb .. but they had no idea what to do about non-constant rendering times or how to synch the client and server properly in the presence of internet lag .. Blizzard sold heaps .. but their reputation is in tatters now .. -- John Max Skaller, mailto:skaller@ozemail.com.au snail:10/1 Toxteth Rd, Glebe, NSW 2037, Australia. voice:61-2-9660-0850 ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners