Hmmm is it possible the gameengine is calculating a lot more recoil and applying it than the game model is showing
Devs give us a few hint's on how your doing on some of the games problems please
- Thread starter Mickg
- Start date
It could be your sound. Maybe lowering soundsetting in the game
will be better the playing.
This post is just ignorant as hell. If the issue was THAT easy to fix it would have been fixed my point is the hit detection is an elusive issue that seems to plague this engine. Move on to another solution? What's that? Replace the engine? Yeah that'll take the time span of a few minutes for sure.Not to be rude or anything but what's your point? I don't think you can justify it by blaming the games' engine. If it's a known issue (which it apparently is with UE3) either fix it or move on the another solution.
As I said, they aren't doing a Rollercoaster Tycoon game but a (Tactical) FPS where the keyword is shooter.
What do you expect will happen to a game when the most important part is borked
The problem is at the moment when a gun is fired at a certain distance it shoots out a ray(also known as a hitscan or raycast) this is essentially a laser if the hitscan intersects with a hitbox it will instantly hit the target no travel time or anything like that. This only occurs at very close ranges after which the bullet turns into a physical object and has travel time and bullet drop as normal. This is done for server performance.
The ACTUAL issue is that something is wrong with the hitscan section or perhaps it's when the bullet stops being hitscan and becomes a physical object but generally this issue occurs at ultra close ranges, usually 5-10m. Where something that should have hit, doesn't. This is either because the raycast somehow goes off on a tangent or it simply doesn't occur.
Ignorant might be bad word, i'd rather go for downright logical...
Have games gone down the drain this much that we can't even expect the shooting part of a shooter to work properly?
It's not my concern how it's being delt with, that's not my job, it's my (and every other gamers) concern that it works.
And the entire server side hit detection is just as bad a decision as releasing it like this, it's a frikking game where 75% of the encounters are cqb ;/
Have games gone down the drain this much that we can't even expect the shooting part of a shooter to work properly?
It's not my concern how it's being delt with, that's not my job, it's my (and every other gamers) concern that it works.
And the entire server side hit detection is just as bad a decision as releasing it like this, it's a frikking game where 75% of the encounters are cqb ;/
Any news on server latency issues? Every server seems to ping everyone in 100-300 area, and it wasn't always like this.
Yoshiro just please tell us wether you're working on the historical issues as-well, it's one of the most important things a lot of us want to hear atm.
Again, thanks in advance for any response.
i think we need all the damage and crap fixed, performance uped...and we need large, open, spread out, combined arms maps.
i just think a LOT of the run and gun crap will be fixed with open maps and a tank that can lock down MILES of land.
RO1 also lanched to a shackey state. a lot of the tanks and stuff was not in RO1 at launch, the community MADE things for the game that TWI liked and made official.
I dont know..i think half the problem is the maps are geared twords "insert issue here".
i just think a LOT of the run and gun crap will be fixed with open maps and a tank that can lock down MILES of land.
RO1 also lanched to a shackey state. a lot of the tanks and stuff was not in RO1 at launch, the community MADE things for the game that TWI liked and made official.
I dont know..i think half the problem is the maps are geared twords "insert issue here".
I kinda want to see how you guys are testing that. Does one guy run into a room while the other guy tries to shoot him or something?
Simply
, thanks for ignoring his well formulated and logical point.