Call of Duty 2

Post by **Neil** » Thu Jun 14, 2007 5:59 pm

Post by **LukePC1** » Fri Jun 15, 2007 6:18 am

Hi Niel,

thanks for the nice Screenshots. Most of them are quite good, but when I found one with a Crosshair (no 0051), it looked not right.

The crosshair is slightly in front of the target - unlike Laser Sight. I don't think this provides an acurate aim with higher seperation.
You have only one Crosshair, so it can't be acurate in all planes. This is exactly like with the Nvidia-Drivers --> if further planes are in focus, you'll get 2 crosshairs...

In Addition the arms and Weapon don't look right. They seem to be in the ground

I think i'll stay with Nvidia, not only because of the price

Post by **Neil** » Fri Jun 15, 2007 6:49 am

LukePC1 wrote:Hi Niel,

thanks for the nice Screenshots. Most of them are quite good, but when I found one with a Crosshair (no 0051), it looked not right.

The crosshair is slightly in front of the target - unlike Laser Sight. I don't think this provides an acurate aim with higher seperation.
You have only one Crosshair, so it can't be acurate in all planes. This is exactly like with the Nvidia-Drivers --> if further planes are in focus, you'll get 2 crosshairs...

In Addition the arms and Weapon don't look right. They seem to be in the ground

I think i'll stay with Nvidia, not only because of the price

Hello LukePC1,

Thank you for your input - I'm not sure what this feedback is based on.

It's important to remember that these drivers are in continual development and I think it's better to judge a driver with actual gameplay than a single image of a crosshair in one out of 55 screenshots.

I've played the game plenty, and I haven't experienced the impression that you have received. Remember, these screenshots had lower separation and were toned down for the audience. If you look at my previous screenshots, I play with much higher separation and convergence.

As for your last remark, I really don't understand what you are trying to say. They are just screenshots, and you are welcome to use whatever driver you want.

Regards,
Neil

Post by **Neil** » Fri Jun 15, 2007 9:10 am

Post by **LukePC1** » Fri Jun 15, 2007 1:31 pm

It's the same with these shots.
The aim thing of the weapon points at one point in the distance. This is ok. It is, where the Bottles are, so I could aim very well in this 'mode'.

But if changed to the single white crosshair, just one crosshair, but two bottles (one for each eye) are shown.

If I focused on the Stereo-Bottle in the distance with high seperation, the "nearer" white Crosshair would get out of focus.
Now I'd have to shoot between both resulting Crosshairs, when the bottle is focused.

The problem is, every shot (of the 65) with crosshair has just one of them at screen/menue Depth, whereas Laser sight proviedes 2 crosshairs. Each on rendered on the aimed object.

Some games have good Huds, which don't seperate. I think GTA SA or STALKER are doing this well (are those DX8 ones - could be possible, since they are based on old engines).

Yeah and last, but not least the Weapons look with Nvidia nearer to the observer than the ground - unlike iZ3D's. But I have to admitt, that my hud moves to the middle and out of the screen, which is not that nice...

I hope I expressed myself understandable

Luke

Post by **Neil** » Sat Jun 16, 2007 5:07 am

I think you are being a bit too scientific!

I just want to blow things up!

Many of the shots taken were done without using the gunsight. Open crosshair and gunsight are equally accurate.

I'm under NDA, so I can't talk about the driver's future plans. However, what I posted here is just a preview. This IS NOT the final product.

I'll get more screenshots up shortly.

Neil

EDIT: Thanks for the upload, by the way. I put it in the downloads section.

Post by **artox** » Sun Jun 17, 2007 2:33 am

Am i the only one who thinks that the weapon is appearing to be drawn behing the surroundings, meaning that there is a sort of the sky close sky in unreal engine effect. (the same can be observed in Fable and the sky in oblivion)

Other that that I have to say this - you can achieve a perfect ingame crosshair usage even with the nvidia drivers if you use so little separation as the one being used in these shots. If you are going for a 100% separation good luck on using the in-game crosshair (which gets really splitted into two) without boosting the convergence and making the pop-out eddect waay too strong to be comprehenced, unless using a projector and sitting far away.

Post by **Jahun** » Sun Jun 17, 2007 5:04 am

Neil:

He is justbeing honest and both Luke and Artox are right.

The crosshair is not accurate at all, it just isn't.
And the arms and gun are rendered in the back, like Artox is saying.

Think of it, there is 100% sure no possible way to use a gunsight with two eyes! Try it if you have anything looking like a gun at home (take a stick). There is 100% sure no possible way to use 2 eyes on a gunsight. The only way to fix this, is to render the gun in the distance. Which is done in this driver. For some reason your eyes don't tell you that right away.

Look at the images with crosshairs btw, the crosshair on the L and R image is rendered on for instance totally different bottles, whereas they should be on the same one (as Nvidia does).

It is not like we are trying to bash the drivers, they'll get better. But if they aren't released yet, it is best to speak up I'd say.

edit: I do like the interface sticking

Post by **Neil** » Sun Jun 17, 2007 7:35 am

Hi Guys!

I'm not at all offended - it just took me awhile to understand.

The COD 2 profile does need some tweaking. For example, the flame coming out of the gun is out of sync with the rifle (for example, the "bang" comes out a little to the left of the gun).

There are crosshair inaccuracies here and there. If you are up close to a wall, the bullet hole will be to the left, but the semi-close to distant shots are much more accurate.

I've forwarded your feedback to iZ3D - let's see what they come up with.

Post some NVIDIA screenshots too - I keep hearing about the gun in the ground, and I don't understand. Give me something to compare it to.

Remember, as revolutionary as the drivers are, it's the game developers that implement the crosshair that is rendered at the depth of the object it is pointed at - which means we still need the advocacy, and I still have a job!

Regards,
Neil

Post by **Freke1** » Sun Jun 17, 2007 7:46 am

When I play FPS games I adjust convergence every time I change weapon. If You want to hit anything You have to make sure the preferred aiming devise (crosshair or ironsight - not both) aims at the same spot in the distance. So the aiming device is double like the spot it is aiming at. This is not a driver fault but comes from using both eyes rather than just one eye. Neil chose to make the ironsight aim at the same spot/bottle which is my choise too. Some like the crosshair more and then that should be double. Alternatively You could close one eye when aiming.

Post by **Jahun** » Mon Jul 16, 2007 6:17 pm

Ok, no clue how that would work Freke1, can you please elaborate for dumb me ?

In that image, both ironsight and bottle are at the same place, so you can use it to aim. But the objects in between are shifted. That cannot be. If you have gun and bottle at same place, the area in between *must* be also in the same place. Unless you use some odd something.

Besides this image being physically impossible (any which way you turn it, you can't aim with 2 eyes), you say you use this aiming technique often, please let me know how you can have both ironsight and target at the same place (unsplit) and still have a 3D depth in your game.. it baffles me.

In this case (just checked it) the problem is solved by rendering the gun in the distance. Then ofcourse the gun lines up. (dunno what happens if you aim at something close)