First Problem:
This was just now being noticed in the engine. The main city, is populated by people, and their all having.. 'graphical' problems. I can't explain it using words, so I need to use a picture.

Basically, this is what happens. at ANY distance. I dont know why, because I've never noticed anything like that before. I'm guessing its how the model is built.. In MED at any distance, this problem doesnt appear. Only ingame, do parts begin dissapearing like that.
When at a close enough distance, the problem goes away

Question #1
I've always used W,A,S,D for my controls, because I couldnt use the arrow keys. Main reason, what would you put for the arrow keys in command?
I know for WASD, its key_w, Key_d, etc
Whats the command line for having the controls as arrow keys? O_o

Problem is, thats too close.

So im wondering if anyone knows what might be causing this to happen? Or a way to get rid of this problem, without rebuilding the models. ..Because all models are having this problem.

Problem #2 (.. i got a slew of problems, dont I )
I've done something horribly wrong. Which I find piculiar, because I havent edited this part of the code.
Code:

---

var dist_total = 400;
var cam_zangle = -7;

---

This is what I've been using for the camera, distance and what I thought was the Z direction location of the camera. The var cam_zangle = -7; part is whats bugging me. I thought it was changing the camera to be higher, but its not, no matter its changes.
Exactly what might I be doing wrong there?

Question #1
Ive always used WASD controls for player movements. I never actually knew, what are the "key_" lines for using arrow keys? O_o

I'm going out on a limb, but I think thats all my questions for right now. =P
Thanks in advance.

key_cuu = up arrow key;
key_cud = down arrow key;
key_cul = left arrow key;
key_cur = right arrow key;

Look in the manual for other key configurations.

As to your graphical things, I don't know, but if it's the shadows, it's a possible known issue (but I may be thinking of something else).

also, there is key_force.x and key_force.y. Key_force.x will return a 1 or a -1 if the left/right keys are pressed and return a zero if no arrow key is pressed.

for example,
my.speedY = 5 * (key_cul - key_cur);
becomes
my.speedY = 5 * key_force.x.

key_force.y works the same way with the up/down

there is also mouse_force.x and mouse_force.y which works the same way and is a good way to make the player turn via the mouse.

perhaps the problem with the models has to do with that whole z-buffer thing?
check this threadIf it is the z-buffer thing than the material talked about in this thread should solve it.

Righto, never actually took into consideration zbuffer.
My question now is:
Each NPC in the village are different models, and they all have the same problem, they all have their own script too. Does the Zbuffer script have to be applied to each individual script, or is there a global script, that will affect all objects?

You have to put the line my.material = mt_vegetation (or something like that) in the action, so if they all have their own action, then yes, you have to put that in there everytime as far as I know.

Well, I've tested that code over and over. Nothing happens, the few times it did manage to load without error, its task was never done, it basically was a pile of bulk.

The code just isnt preforming its action, and if I modify the vegitation part, it only encounters errors. It usually gets replaced with the [ACTION player_action] seeing as the players script is Function player_action
That still wouldnt do what I need though.

This script doesnt act as a global script, it only seems to be able to act as a script to modify the buffer on one specific function, all objects tied to that function.
O_o

More a less, wouldnt a script work that resembled something like;
Code:

---

{
my.transparent=off;
my.flare=off;
}

---

(that doesnt actually do anything) There must be a more simplified command line for the zbuffer on a global status.

convert the models skin to a 24 bit texture. you get the sort problems when you have 100% opaque areas and semi-transparent areas within the same skin image with an alpha channel

Texture was already 24bit, still having problems. It doesnt seem to be anything with the texture, but the model itself.

When an object is behind an unsolid object, the unsolid becomes invisible, and the solid behind it, can be seen. The problem is eliminiated when the camera is close to the model.

I'm assuming it is infact the zbuffer, but the script for my zbuffer doesnt do anything.

sounds then like either flipped normals or an open mesh ( unless your applying some shader to the model that might mess up the rendering sort)