I would like to hear your opinion on what is the more effective solution to implementing a bullseye for a shooter.
I have a couple of ideas, but would like to learn of others experience implementing a solution. The specific escenario is a 3rd person flying shooter.
What sort of ideas do you have? Why not share with us rather than us retreading ideas you already have.
A forum is a give and take⦠give us something, weāll join the conversation.
Also⦠define bullseye more specifically. Do you mean like a dart board? Or do you mean a target? But these are just āthingsā⦠art them up, done.
This is the ācoding/scriptingā section, what do you want code wise in relation to a bullseye? Like are you asking how to give a player the ability to shoot a bullseye? Determine IF a player has shot a bullseye?
I believe the original post was explicit, as Iām looking for known the specific implementations for a bullseye in a 3rd person flying shooter, but if helps additional details, Iām interested in the technique to move the bullseye in 3D space for long and short distance objects having a constant size for the bullseye image, so the crosshairs is not necessarily at the center of the screen; and I do not want to skew the responses with my opinions as I have not tried to code it myself yet.
Nobody knows what you want, and nobody is going to code your stuff for you.
Assuming if by bullseye you mean crosshairs, do not have crosshairs move separately from the view port, it will be nauseating. Do what -every- other shooter does and just draw an X in the middle of your screen.
lordofduct, Zero response is perfectly OK, what is not acceptable is to have zero value added responses from people like yourself that believe they are the center of the world and pretend to apply such a shortsighted criteria to blast my interest for learning.
Neither your original post nor your subsequent posts have any actual value either. That isnāt the reason behind a lack of suggestions though. Youāre not receiving suggestions because we donāt have any actual details about the game. One suggestion may work great for one game but be completely useless in another.
We need more information or itās a complete waste of time on our part.
Kind of like you, who believe you are the center of the world, and want your code written for you?
Take criticism better, the us telling you that we -simply need more information- to help you IS helping. Define your problem more precisely, for both us AND yourself. Donāt get short with people who are helping you (and have no obligation to do so) because they donāt do it the way you want.