Project PLASMA FPS 2004: Thread 3

Blitz3D Forums/Blitz3D Programming/Project PLASMA FPS 2004: Thread 3

Implementing doors and other interactive things as door.bb might not solve the problem since such things, eg. a door requires several interfaces to the core:

-initialisation in the level loading procedure
-call(s) in the main loop
-including of the function(s)

Personally I am not sure if it's a good idea to use a high number of Include Files. So when you see a function call, how do you know in which of the 100 Include Files you have to look for that function if you want to edit it? Further you need to load all 20 Files in the IDE whenever you want to work on the Engine.

LOD, HFR and VIS is a thing that will complicate this massively. There is no good and working example of a homebrew HFR around yet. Please tell me which complete Bitz Game! is using a HFR. I suggest you load the walktrough demo I provided with the demo level and check the camera range setting. You'll see the range is max. 50 blitz Units. THere is no need for HFR IMHO. At least if we make this Engine for Indoor Levels.

I don't want to start too many things with this, I am still afraid this will suddently die when we start too many things at the same time.

Instead of saying "yes, we implement interactive Items the one or the other way, but let's talk about VIS" we better should decide ONE way to implement items and then proceed. I will not start on the level editor as long as there is no decision about this kind of stuff. There is a reason why I ask this, it's not only spontanous nonsense.

and anyway, Frank, you are looking for a level editor in the general forum - I also don't start with the edition of the csp editor for plasma when it is not a clear decision that we want to use it. you know these situations, somebody asks for some Sourcecode, then you write an example for that newbie, but he never uses it - that's scaring.