Quote from: Scipi on January 25, 2014, 11:24:40 pm

6257: You create your own linguistic language and share it on Omni (1)

And how is that a sign?

Simple. It shows that any project of interest you have you share on Omni regardless of relevancy to calcs. (Omni is an excellent community for many topics, really)

Hello everyone.

It's been a few years since I last actually released a project here on Omni. However, recent events have had me revisit one of my old projects.

This is System Crash 2, the second iteration of my 2D Shooter. The original can be found here.

In its current state, the game is still more of a tech demo than anything else. It plays the same as the original version, however there are some changes.

Primarily, there are now two kinds of enemies:
Dumb Bots, which merely move towards the player at a low rate, and
Smart Bots, which are controlled via a Recurrent Neural Network.

As the game progresses, Smart Bots become more adept at killing the player through the application of a genetic algorithm. After each round, smart bots will be chosen either for being able to survive the longest or for dealing more damage to the player than other bots. These bots will then be used to populate the next round, with each offspring being mutated to create potentially new behavior.

As previously stated, the game is still a work in progress. However it is playable. It just doesn't have all the niceties the original had, like a high score or menu.

Controls:
   WASD/Arrow Keys - move
   Space - Sprint
   P/O - Pause/Unpause
   Esc - Reset
   RMB + CTRL - Select Bot to render Brain
   RMB - CTRL - Clear Bot Selection

Here are some ingame screenshots:





The Game is attached to the post.

Known Issues:
    -Title says HuntingBots
    -Weapons not properly balanced
    -Selected Bot does not clear unless player moves

Funny, yesterday I had wondered why the image for my emoticon suddenly broke (since it's just a link to an attachment somewhere).

Yay

Quote from: Scipi on January 20, 2014, 06:19:26 pm

Code: (java) [Select]

double dist = Math.sqrt((xPos - b.xPos)*(xPos - b.xPos) + (yPos - b.yPos)*(yPos - b.yPos));

if(dist < 0){
   dist = .001;
}

Erm, distance from a sqrt shouldn't give you a negative... I don't believe that if conditional will ever be fulfilled.

Good catch, that was supposed to be ==.

You can use the dot product of the viewing direction vector and the vector between the two bots. The direction vector should be <cos(viewangle), sin(viewangle)> and the vector between the bots should be <b.xPos - xPos, b.yPos - yPos>. The dot product of these two vectors, (b.xPos - xPos)*cos(viewangle) + (b.yPos - yPos)*sin(viewangle), is equal to the magnitude of the two vectors times the cosine of the angle between them. The magnitude of the first is 1, and the magnitude of the second is the distance between the bots. So you can divide the aforementioned dot product by the distance between the bots and get the cosine of the angle between the view direction and the other bot. Then, you can just compare it to the cosine of half the field of view. Hopefully this all makes sense.

I was given a similar solution a few days ago by a colleague. I have an attempt to implement what he said under this code:

private boolean inFOV(Bot b, double uAngle, double lAngle){
double x1 = Math.cos(Math.toRadians(uAngle));
double y1 = Math.sin(Math.toRadians(uAngle));
double x2 = Math.cos(Math.toRadians(lAngle));
double y2 = Math.sin(Math.toRadians(lAngle));

double uDist = y1 * b.xPos + -x1 * b.yPos;
double lDist = -y2 * b.xPos + x2 * b.yPos;

return (uDist > b.radius && lDist < b.radius);
    }
I'll recode it to try and implement what you suggested. Seems like what I need.

Edit:

Calc84's method solved my issue. Damn, I really need to take a look into vectors >_<

Here's the working code:

private boolean inFOV3(Bot b, double angle, double FOV){
double x1 = Math.cos(Math.toRadians(angle));
double y1 = Math.sin(Math.toRadians(angle));
double dist = Math.sqrt((xPos - b.xPos)*(xPos - b.xPos) + (yPos - b.yPos)*(yPos - b.yPos));
double dx = b.xPos - xPos;
double dy = b.yPos - yPos;

if(dist == 0){
    dist = .001;
}

//(b.xPos - xPos)*cos(viewangle) + (b.yPos - yPos)*sin(viewangle)


double dotP = (b.xPos - xPos)*x1 + (b.yPos - yPos)*y1;
double dAngle = dotP / dist;
double halfField = Math.cos(FOV);

return (dAngle >= halfField);
    }

There are some cases where only part of a circle is "visible," so the buffer is the angle to increase/decrease the view by to cover any circle overlaying the view at a given distance.

Here:

Build a smaller one

I lost my subatomic ball machine somewhere

Guess what time it is