(The code's pretty weird right there. A function returns an int but is cast to float. That gets compared against 0.0 and then cast back to int for its last use. Maybe it dodges some bug with shots that would deal damage around 0 or 1 point? If not (and I suspect that's unlikely), it's unnecessary work that would be a 2-second fix for a programmer -- just initialize as an int and remove the casts back and forth. That, or it's a really weird decompiler error. Or that intermediate rounding isn't meant to happen after penetration, but then there are flaws in several pieces of code.)
Fixed! Returned an INT but stored as a float. Not clear why it was setup that way.
(The code's pretty weird right there. A function returns an int but is cast to float. That gets compared against 0.0 and then cast back to int for its last use. Maybe it dodges some bug with shots that would deal damage around 0 or 1 point? If not (and I suspect that's unlikely), it's unnecessary work that would be a 2-second fix for a programmer -- just initialize as an int and remove the casts back and forth. That, or it's a really weird decompiler error. Or that intermediate rounding isn't meant to happen after penetration, but then there are flaws in several pieces of code.)
Fixed! Returned an INT but stored as a float. Not clear why it was setup that way.
Being a programmer myself I can guess why it was coded like that...
"Why did you code it like that?"
"I... It was 3am, I was drunk, and it compiled. So I went with it."
"Well for the love of god don't touch it then, we don't have time to go back and fix that if it breaks. The end users will probably never see the code anyways."
(The code's pretty weird right there. A function returns an int but is cast to float. That gets compared against 0.0 and then cast back to int for its last use. Maybe it dodges some bug with shots that would deal damage around 0 or 1 point? If not (and I suspect that's unlikely), it's unnecessary work that would be a 2-second fix for a programmer -- just initialize as an int and remove the casts back and forth. That, or it's a really weird decompiler error. Or that intermediate rounding isn't meant to happen after penetration, but then there are flaws in several pieces of code.)
Fixed! Returned an INT but stored as a float. Not clear why it was setup that way.
Being a programmer myself I can guess why it was coded like that...
"Why did you code it like that?"
"I... It was 3am, I was drunk, and it compiled. So I went with it."
"Well for the love of god don't touch it then, we don't have time to go back and fix that if it breaks. The end users will probably never see the code anyways."
I feel the GUIDE is missing something. Wish BCPULL would do a little more homework. :*
A little more detail would be helpful... Turnaround time has been pretty quick when others have found issues or suggested changes, but I can't work off of "do more homework".
I feel the GUIDE is missing something. Wish BCPULL would do a little more homework. :*
A little more detail would be helpful... Turnaround time has been pretty quick when others have found issues or suggested changes, but I can't work off of "do more homework".
He probably means something to do with minimal HUD.
I feel the GUIDE is missing something. Wish BCPULL would do a little more homework. :*
A little more detail would be helpful... Turnaround time has been pretty quick when others have found issues or suggested changes, but I can't work off of "do more homework".
He probably means something to do with minimal HUD.
You could be right.
There are a few things (enemy weapons, for example, or details on the sway system) that are bare-bones or left off right now because we know the systems are going to be significantly changed with release. HUD is one such system that's being updated.
There's also much less behind-the-scenes detail to go into with the HUD. I wrote this less as a general guide for the beginning player and more for the people that already know the basics and are curious about the inner workings. That's why there aren't sample sight pictures or that sort of thing; that info is already extremely accessible.
Sorry for getting the topic on it's tracks again, but I've did a quick research and found a sniper-only penetration spot on Slums. (The concrete floor of the broken building.) http://steamcommunity.com/profiles/76561198046748844/screenshots/
This spot might have some practical value: you can shoot the bomb planter/defuser from above.
I suppose there are many/some more objects with similar properties, but they are not that easy to find (you basically have to search by hand) I'm lazy. If you want, I can try to get more.
Theory and reality are not that different. In theory.
Sorry for getting the topic on it's tracks again, but I've did a quick research and found a sniper-only penetration spot on Slums. (The concrete floor of the broken building.) http://steamcommunity.com/profiles/76561198046748844/screenshots/
This spot might have some practical value: you can shoot the bomb planter/defuser from above.
I suppose there are many/some more objects with similar properties, but they are not that easy to find (you basically have to search by hand) I'm lazy. If you want, I can try to get more.
If you're "fluent" in the full version of the map editor, you can open a map, find the AAPhysMats package in the content browser, and search for objects in the open map using the supplied material. The materials are named something like "0_WordWordWordMetal" and the number is a fast way to see their penetration cost. It's not perfect, but it's the best way I've found.
Sorry for getting the topic on it's tracks again, but I've did a quick research and found a sniper-only penetration spot on Slums. (The concrete floor of the broken building.) http://steamcommunity.com/profiles/76561198046748844/screenshots/
This spot might have some practical value: you can shoot the bomb planter/defuser from above.
I suppose there are many/some more objects with similar properties, but they are not that easy to find (you basically have to search by hand) I'm lazy. If you want, I can try to get more.
If you're "fluent" in the full version of the map editor, you can open a map, find the AAPhysMats package in the content browser, and search for objects in the open map using the supplied material. The materials are named something like "0_WordWordWordMetal" and the number is a fast way to see their penetration cost. It's not perfect, but it's the best way I've found.
Thanks for finding that spot on Slums
Oh my, I'm such an idi*t. I was googleing 'select based on physical material' (a lot earlier for myself) with no results, and there is a big shiny button what can do this (and many other stuff). Well, I'm completely self-learning the UDK editor, this method has it's drawbacks.
What I was doing is: select the Physical Material->list objects what reference to this object->it gives me Material names->copy-paste a name and search for it->select given material->list objects what reference to this object->it gives me a list of StaticMeshes. This is how I found that spot on Slums.
Thanks a lot for this tip!
Theory and reality are not that different. In theory.
Q. Are bullets affected by gravity?
A. Yes, bullets drop over long distances. You may have to aim slightly above where you want to hit for long-distance shots.
Q. Are bullets affected by gravity?
A. Yes, bullets drop over long distances. You may have to aim slightly above where you want to hit for long-distance shots.
Really ?
As mentioned, yes there is bullet drop over distance. However, you have to be on a very large map to see it's effect.
I know it's hard to see but in my signature the scope view shows the centre dot just above and ahead of the target who was moving towards the flag. This was on an early build of Keebler750's HUGE All Terrain UMM. I think it was 230 meters to the flag.
Comments
I love this community!
Fragmovie 6 | iNv Discord
FGNL Season 1 Champions
FN Season 2 & 4 Champions
Fixed! Returned an INT but stored as a float. Not clear why it was setup that way.
"Why did you code it like that?"
"I... It was 3am, I was drunk, and it compiled. So I went with it."
"Well for the love of god don't touch it then, we don't have time to go back and fix that if it breaks. The end users will probably never see the code anyways."
The truth, in this post...
Those Clueless to sarcastic humor
Please line up below:
_________________________
********Bam4D********BE ALL (THAT) YOU CAN BE!
________Army 1980_________
He probably means something to do with minimal HUD.
Fragmovie 6 | iNv Discord
FGNL Season 1 Champions
FN Season 2 & 4 Champions
There are a few things (enemy weapons, for example, or details on the sway system) that are bare-bones or left off right now because we know the systems are going to be significantly changed with release. HUD is one such system that's being updated.
There's also much less behind-the-scenes detail to go into with the HUD. I wrote this less as a general guide for the beginning player and more for the people that already know the basics and are curious about the inner workings. That's why there aren't sample sight pictures or that sort of thing; that info is already extremely accessible.
http://steamcommunity.com/profiles/76561198046748844/screenshots/
This spot might have some practical value: you can shoot the bomb planter/defuser from above.
I suppose there are many/some more objects with similar properties, but
they are not that easy to find (you basically have to search by hand)I'm lazy. If you want, I can try to get more.If you're "fluent" in the full version of the map editor, you can open a map, find the AAPhysMats package in the content browser, and search for objects in the open map using the supplied material. The materials are named something like "0_WordWordWordMetal" and the number is a fast way to see their penetration cost. It's not perfect, but it's the best way I've found.
Thanks for finding that spot on Slums
Oh my, I'm such an idi*t.
What I was doing is: select the Physical Material->list objects what reference to this object->it gives me Material names->copy-paste a name and search for it->select given material->list objects what reference to this object->it gives me a list of StaticMeshes. This is how I found that spot on Slums.
Thanks a lot for this tip!
A. Yes, bullets drop over long distances. You may have to aim slightly above where you want to hit for long-distance shots.
Really ?
As mentioned, yes there is bullet drop over distance. However, you have to be on a very large map to see it's effect.
I know it's hard to see but in my signature the scope view shows the centre dot just above and ahead of the target who was moving towards the flag. This was on an early build of Keebler750's HUGE All Terrain UMM. I think it was 230 meters to the flag.