• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Medo Mex

Vision Raycasting

2 posts in this topic

I'm currently developing vision raycasting for FPS game, I have few questions:

 

1. How many ray is accurate to detect vision from a tank?

 

2. How many ray for each character?

 

3. Should I calculate the distance against EVERY model and create rays at each model if it's close enough?

 

4. If the model is a character the ray will start from his eyes, however, if it's a tank, from where the ray should start?

 

5. How do I determine the exact ray target? (rayTo = target.position) --> I don't think this is good enough

 

 

I want to create something efficient and at the same time with high performance.

0

Share this post


Link to post
Share on other sites


1. How many ray is accurate to detect vision from a tank?

 

one from each station with an exterior view to each target in the station's arc of sight/fire within visible range. the type of tank will make a big difference. in a large WW1 tank, you might have 6 stations with exterior views, and FOVs of 30-45 degrees. in a newer tank, you might have something like a 90 degree FOV for the driver, a 30 degree FOV for the gunner, and a 360 degree FOV for the commander/spotter.

 


2. How many ray for each character?

 

one to each target in visual range. infantry has a 360 FOV.

 


3. Should I calculate the distance against EVERY model and create rays at each model if it's close enough?

 

that's what i do (sneak/stealth mode, fps/rpg game). but i only do the ray casting LOS/LOF (line of sight / line of fire) calculations if the player is in sneak mode (and undetected by hostiles).

 


4. If the model is a character the ray will start from his eyes, however, if it's a tank, from where the ray should start?

 

the visual orifice of the station. IE the driver's view slot in a WW2 tank, the persicope on top of the turret of a modern tank, the MG station's viewport on the side of a WW1 tank, etc.

 


5. How do I determine the exact ray target? (rayTo = target.position) --> I don't think this is good enough

 

for infantry, center to center may be good enough. to increase accuracy, you'd step up to something like checking 4 corners of a bounding box, or perhaps some type of bounding sphere type test. for tanks, if center to center isn't good enough (probably won't be), again you'd go BBox corners, etc. for a tank, bbox corners would be more accurate than bounding sphere.

 

with center to center vs bbox, almost half a target would be visible before the LOS/LOF test indicated so.

 


I want to create something efficient and at the same time with high performance.

 

by that i assume you mean accurate (hi performance) and fast (efficient).

 

accurate means bbox or the like. fast means...   well. write the code. if its not fast enough, then you optimize. of course, no harm with writing it with speed in mind from the get go... i think i just did a bressingham's kinda thing (step moving along a direction vector, checking for collisions with occluding objects/terrain).  speed was a concern, but i got it working ok. can't recall if i had to optimize. if so, must not have been much.

1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0