Project Reality Forums

zangoo wrote:Unless you can manage to import something that is 1m in real life into the game, But i dont see any way of doing that...

Ha, yeah that would be a nice trick wouldn't it?

Here is an idea.
Take the M4 rifle in game that has a known velocity, and fire it at a target that is of known distance from the shooter. Say 500 or 1000 meters.

First calculate the time in milliseconds it takes for the projectile to reach say 500 or 1000 meters in the real world. Then Setup the target at 500 or 1000 meters in game. Fire at the target and adjust the velocity up and/or down until the time it takes to hit the 500/1000 meter target in game is EXACTLY the same as in real life. I don't know much about fraps, but you could record the session and use fraps to possibly determine the EXACT amount of time it took for the round to hit the target. Of course you will need a timer that measures in milliseconds. Just using whole seconds won't be close enough.

Using distance over time could be a way to determine scale. If the time to target is the same in game as in real life using the real world values then you know it is pretty close to scale after all Might be able to use a weapon that has a slower projectile speed like the HAT or TOW. The only debate at that point would be; which clock do you use? The in game clock or a real world stop watch? Keep in mind that the longer the distance for the test the better.

Sorry, now I'm rambling on

Waaah_Wah wrote:They were barely visible with optics, but when using iron sights there was VERY hard to see them. On maps like Kashan, they would be invisible because of the bright surroundings. So unless your using an LMG or have a scope, you wont see your own tracers on 1024x768

That is why i would need to adjust the size of the tracers so they are still visable on lower resolution settings.

Rico11b wrote:Ha, yeah that would be a nice trick wouldn't it?

Here is an idea.
Take the M4 rifle in game that has a known velocity, and fire it at a target that is of known distance from the shooter. Say 500 or 1000 meters.

First calculate the time in milliseconds it takes for the projectile to reach say 500 or 1000 meters in the real world. Then Setup the target at 500 or 1000 meters in game. Fire at the target and adjust the velocity up and/or down until the time it takes to hit the 500/1000 meter target in game is EXACTLY the same as in real life. I don't know much about fraps, but you could record the session and use fraps to possibly determine the EXACT amount of time it took for the round to hit the target. Of course you will need a timer that measures in milliseconds. Just using whole seconds won't be close enough.

Using distance over time could be a way to determine scale. If the time to target is the same in game as in real life using the real world values then you know it is pretty close to scale after all Might be able to use a weapon that has a slower projectile speed like the HAT or TOW. The only debate at that point would be; which clock do you use? The in game clock or a real world stop watch? Keep in mind that the longer the distance for the test the better.

Sorry, now I'm rambling on

This doesnt mean the meter is off, This just tells us that the velocity setting isnt giving us a true m/sec value. I will do a test shooting 1000m with a projectile going 100m/sec. I will post the results soon.

After doing this test i have found something very interesting. The bf2 velocity setting works just as you would think and is the same as in real life. But the interesting part is that i was shooting a tracer round and I didnt need to increase velocity, Instead when i had increased it to make the tracer round go 100m/sec the tracer instead shot at the full 133.33m/sec. Now i am going to try to find what caused this but this might mean we can have ballistics!

Excellent Lets not get our hopes up just yet but it sounds promising!

After testing the tracer bug doesnt happen when the tracer interval is set to 1, So it wouldnt help us at all. But it did mean that i messed up my original test with realistic ballistics as the bullets were going 33% too fast.

zangoo wrote:This doesnt mean the meter is off, This just tells us that the velocity setting isnt giving us a true m/sec value. I will do a test shooting 1000m with a projectile going 100m/sec. I will post the results soon.

Well it has to be one or the other. Either the in game meter IS off scale. Or the velocity settings aren't giving a true m/sec value. Since you were using such a low speed value, It would probably be better to use a greater distance. That way any degree of error within the game engine would be magnified.
Sounds like you have made some nice discoveries. The rabbit hole is usually always a lot deeper than we first realized


Glad I could help.

Well the test showed that the bullets were traveling within 100±10m/sec, And i think it would be safe to assume that it is traveling the correct speed. You also note that for jonny's formula to calculate the correct angle to zero the guns, bf2's velocity would have to be true or the zero would be off, And from the tests shooting the m40a3, The zero was spot on.

zangoo wrote:Well the test showed that the bullets were traveling within 100±10m/sec, And i think it would be safe to assume that it is traveling the correct speed.

Within 100m/sec???

It won't be safe to assume that if the difference is about 100m/sec ±10m. That's a pretty large difference in speed measurements. 100m/sec is a large difference is huge. Fire two bullets from the same rifle with muzzle velocities being 100m/sec apart, and you will see that there is a BIG difference between those two shots.

If you would have said a difference of 100 FEET per second, then I would agree that they are fairly close, but not 100 METERS per second. 100 m/sec converts to 328ft/sec, and that's a big difference, especially for a rifle bullet.

hes saying its 100 meters per second more or less 10 meters per second, so ti could be 90 meters per second or it could be 110

Rico11b wrote:Within 100m/sec???

It won't be safe to assume that if the difference is about 100m/sec ±10m. That's a pretty large difference in speed measurements. 100m/sec is a large difference is huge. Fire two bullets from the same rifle with muzzle velocities being 100m/sec apart, and you will see that there is a BIG difference between those two shots.

If you would have said a difference of 100 FEET per second, then I would agree that they are fairly close, but not 100 METERS per second. 100 m/sec converts to 328ft/sec, and that's a big difference, especially for a rifle bullet.

Thing is we dont need to measure the time of flight, Jonnys program Assumed that bf2's velocity was correct, It would zero the guns perfect. So if this was off the guns wouldnt be zeroed Even if the velocity was off by only 10%. So i Can assure you that bf2'2 velocity is correct and there is no diffrence from real life. The only issue in bf2 is the models as those are the only things that can be scaled.

I have been messing around with the ballistics and i have created ricocheting bullets like seen in the videos demoing the tracers. There are some bugs that happen on a local server but im not sure if they will happen on a dedicated server. I will try to get a video up soon, Right now i am just having too much fun shooting the saw.

I also recreated the deviation for marksman and assault rifles, I am trying to get the files for kashan night and when i do i will try to setup a test to demo all of these new features.

excellent! Ricochiting bullets amazing

ricochet = no good cus u ll go around on for example kashan, and like suddenly lose 30% of your "health" (bleed time...) and u bleed painstakingly out, and u think... wtf... i didnot hear the shot at all.

bouncy bullets are IMHO quite lame.. think CQB.

Exactly how do the ricochets work?

This stuff sounds amazing, mate! Keep up the good work!

As long as the ricochets wont be ridiculous (bouncing back at you from sand, etc) go for it

It would be hilarious to see a bored player shoot the wall he's next to and get headshotted by the ricochet

And he's back But yeah, I've always wanted to see tracers bounce off etc, looks v cool

Some awesome stuff going on in here!

After more testing it looks like there is no bugs, But i do need to adjust alot of settings for alot of diffrent materials if i want these to look realistic.

Over all the richoets work like you would think, If the impact of the projectile with the surface has a low angle a ricochet will occur, But right now i have set the settings too high and they are gaining speed after a richoet....

Here are some screen shots of the ricochets, Note i have attached rpg effects so they are seen, Plus if i use tracers they dissapear after impact. Dont worry about that i have a fix.