Friday Update, June 08, 2012

[Freycinet]

Originally Posted by zapatista

BlackSix, a question plz: can you please check with Luthier that he has also addressed the lack of correctly being able to select a specific FoV setting that corresponds to our personal monitor size (as we could do in the late versions of the old il2 series). right now we are limited to the 3 settings of "normal", narrow and wide, instead of being able to select between 35 and 90 in 5 degree steps like we should be able to. the result of this is that all ingame objects (including planes, trucks, ships) either look to small or to large compared to their real life sizes we should see from a specific distance. please ask or this to be looked at as a matter of priority (reported in feedback thread before)

Zapatista, check out my latest five vids, you can set the exact FOV you want...

to get the smooth zooming in/zooming out, you have to go into:

Control options,
Camera,
And set "Hold to adjust view" to whichever button you prefer (keyboard or joystick)

- If you then hold down that button and move your mouse forward or backward it will change the field of view in a gradual way.

It is an ok option to have, but it would be much better if CoD allowed you to set a "zoom in"-button and a "zoom out"-button, as in - for example - RoF.

Hope this helps.

[zapatista]

Originally Posted by Freycinet

Zapatista, check out my latest five vids, you can set the exact FOV you want...

to get the smooth zooming in/zooming out, you have to go into:

Control options,
Camera,
And set "Hold to adjust view" to whichever button you prefer (keyboard or joystick)

- If you then hold down that button and move your mouse forward or backward it will change the field of view in a gradual way.

It is an ok option to have, but it would be much better if CoD allowed you to set a "zoom in"-button and a "zoom out"-button, as in - for example - RoF.

that is a very disorienting and clumsy way to do it, and not practical during normal flight or intense dogfighting situations

the point also is that we should be able to view the "in game" CoD world with the right FoV setting for our monitor size (for ex 55 FoV for a 27' monitor) so we can see all objects (planes, vehicles, ships) in their correct sizes, and then use a snap view KB/hotas control to zoom in (and aim at a specific part ) or get a wide view (to increase peripheral view and SA) briefly, and then snap back to a normal view which gives us instantly again the correct perception of object sizes and the distance we are from them !

trying to do that by a clumsy zoom in/out, which doesnt even have a reference point for what is "normal" for you monitor size, doesnt really help. people also use the magic zoom as a way to "game the game" rather then try and simulate a ww2 aircraft pilot experience

we need to be able to set a specific correct FoV setting for our respective monitor sizes, and then key bind the snap view settings we want to use for wide and zoom, which are settings used to try and replicate more closely issues like intense concentration on one object (zoom) or better peripheral vision and SA (wide view) and so represent what we would experience in a cockpit in real life, and reduce the limitations of watching a small screen in our livingrooms

we did already have this option in the old il2 series, where you could set it to any kb key at 5 degree intervals between 35 and 90 FoV, we need that same feature in CoD !

[Catseye]

Originally Posted by zapatista

that is a very disorienting and clumsy way to do it, and not practical during normal flight or intense dogfighting situations

the point also is that we should be able to view the "in game" CoD world with the right FoV setting for our monitor size (for ex 55 FoV for a 27' monitor) so we can see all objects (planes, vehicles, ships) in their correct sizes, and then use a snap view KB/hotas control to zoom in (and aim at a specific part ) or get a wide view (to increase peripheral view and SA) briefly, and then snap back to a normal view which gives us instantly again the correct perception of object sizes and the distance we are from them !

trying to do that by a clumsy zoom in/out, which doesnt even have a reference point for what is "normal" for you monitor size, doesnt really help. people also use the magic zoom as a way to "game the game" rather then try and simulate a ww2 aircraft pilot experience

we need to be able to set a specific correct FoV setting for our respective monitor sizes, and then key bind the snap view settings we want to use for wide and zoom, which are settings used to try and replicate more closely issues like intense concentration on one object (zoom) or better peripheral vision and SA (wide view) and so represent what we would experience in a cockpit in real life, and reduce the limitations of watching a small screen in our livingrooms

we did already have this option in the old il2 series, where you could set it to any kb key at 5 degree intervals between 35 and 90 FoV, we need that same feature in CoD !

Agree 100%.
I popped back into 1946 today and it was great selecting 60 degrees as my standard setting - flicking into gunsight view or wide as I needed and then returning to my default 60 degrees.

[Blackdog_kt]

Originally Posted by nakedsquirrel

It changed with the most recent build. If you put in IAS and altitude in the bombsight, it will not track correctly, but it will drop on target (you have to force it to stay on target with the raise/lower bombsight button while using bombsight automation You no longer need to convert metric to imperial.


With that... bombsight automation doesn't track correctly, your using IAS instead of TAS, the bombsight is fuzzy, and there is no indication when your bombs have dropped.

To top it off mode 22 has some strange habit of putting your plane into a shallow dive, only leveling out after you fly 100km or so

If it doesn't track correctly then the units (or the tracking code) are probably messed up again. What you describe sounds exactly like one of the methods i was describing before, where the player converts to imperial units for proper release and fights against the wrong tracking, but if i understand you correctly now it happens without even converting to imperial...sounds a bit confusing

I'm not doubting your observations mind you, just thinking out loud to see what the reason behind it might be.

As for the R22 autopilot mode, that is easy. It's probably more of a problem with the 111's engines not producing the expected power settings (they tend to be on the low RPM side, especially noticeable during take-off) than the autopilot itself.

Mode R22 is a wings level function, where the AP turns the aircraft by rudder only. So the general idea is to navigate and roughly line up the target with course steering mode (the one that uses aileron turns), then engage R22 mode from the initial point and fly the bomb run using that one.

I have tried it and it does in fact work quite well, as long as you don't overdo it with the corrections because the rudder will bleed off too much airspeed and you lose even more altitude.

The trick with mode R22 is to get to 300km/h IAS before engaging it, as that seems to be the speed for which it is calibrated. What i usually do is climb an extra 500 - 1000m above my intended altitude, then go into a shallow dive and engage R22. As the aircraft picks up speed and wants to climb i cancel out the tendency with elevator trim, until i'm flying straight and level at 300km/h IAS. Then it's time to enter the speed and altitude values in the sight and make any course corrections.

I have mapped course steering left/right to my < and > keys, so i just look through the bombsight and give it a tap or two to align the target. I let it stabilize between corrections and not overdo it, otherwise it's too aerodynamically inefficient and the speed/altitude drop.

Like i said, the dive probably has more to do with the 111's engines being a bit on the weak side and the fact that it reacts sluggishly to speed/trim changes. I haven't been able to test this in the 88 however, because its gyrocompass doesn't work.

About the bombsight textures now, that is because of the texture loading bug that appeared for most people with the latest test patch. If the PC can't handle loading the textures in one go, it loads lower detail versions of them.

The reason i say "most people" is that i've had this issue since release. I have an Ati 4890 1Gb graphics card and only 3GB of RAM, so i guess it's got something to do with how the textures are managed in terms of available memory.

However, the majority of players with better systems than mine were unaware of this until recently, where apparently the texture loading issue manifested on a wider range of systems. To tell you the truth, i was happy to see it mentioned because now it's a legitimate issue that is going to get looked at, instead of something that only happens at my end

Anyway, here's hoping we have another test patch by this time next week. It will be good to hop on the server and try some bomber sorties with your regular bomber pilots. What i'm expecting to see is a nice group of 5+ Ju88s on a proper high altitude sortie

[BlackSix]

To All:
Please, you have to write bugs here
http://il2bugtracker.com/
and your requests here
http://forum.1cpublishing.eu/showthread.php?t=28341
I won't find and take bugs and requests from this thread.

[Trumper]

Originally Posted by BlackSix

To All:
Please, you have to write bugs here
http://il2bugtracker.com/
and your requests here
http://forum.1cpublishing.eu/showthread.php?t=28341
I won't find and take bugs and requests from this thread.

hopefully this will stop the 80 pages of drivel we normally end up with.

[catito14]

Originally Posted by BlackSix

To All:
Please, you have to write bugs here
http://il2bugtracker.com/
and your requests here
http://forum.1cpublishing.eu/showthread.php?t=28341
I won't find and take bugs and requests from this thread.

Sorry for that B6, there i used the proper places to make the petitions.
Regards

[bw_wolverine]

Really looking forward to the patch! Thanks to everyone at 1C maddox!

[adonys]

Originally Posted by zapatista

that is a very disorienting and clumsy way to do it, and not practical during normal flight or intense dogfighting situations

the point also is that we should be able to view the "in game" CoD world with the right FoV setting for our monitor size (for ex 55 FoV for a 27' monitor) so we can see all objects (planes, vehicles, ships) in their correct sizes, and then use a snap view KB/hotas control to zoom in (and aim at a specific part ) or get a wide view (to increase peripheral view and SA) briefly, and then snap back to a normal view which gives us instantly again the correct perception of object sizes and the distance we are from them !

trying to do that by a clumsy zoom in/out, which doesnt even have a reference point for what is "normal" for you monitor size, doesnt really help. people also use the magic zoom as a way to "game the game" rather then try and simulate a ww2 aircraft pilot experience

we need to be able to set a specific correct FoV setting for our respective monitor sizes, and then key bind the snap view settings we want to use for wide and zoom, which are settings used to try and replicate more closely issues like intense concentration on one object (zoom) or better peripheral vision and SA (wide view) and so represent what we would experience in a cockpit in real life, and reduce the limitations of watching a small screen in our livingrooms

we did already have this option in the old il2 series, where you could set it to any kb key at 5 degree intervals between 35 and 90 FoV, we need that same feature in CoD !

you can do that using a 3rd party small programm (setjoy or something like that): you assign a key for hold to zoom in IL2CoD, then you're mapping mouse movements to joysticks hatswitch/buttons (same buttons as you assigned in IL2CoD for hold to zoom) pressed in the 3rd party program. that way, you can zoom seamlessly (as in old IL2).

The problem with objects rendered size is something completely different, and it is bad in IL2CoD. The natural size of the objects is rendered in game at around 30 FoV, which is a too small FoV compared to human normal vision's FoV to can be used all the time in game.

So, at this moment, using the human normal vision's FoV (which is around 60), you see the objects smaller and further away than they should be. The correct human vision size/distance for the rendered objects is when using the zoomed in FoV of 30 degree.

This is why, for example, when flying in formation, you don't get the feeling of closeness you're getting when you see WW2 formation flying pictures.

CFS2 was solving this by forcing the apparent size/distance of the rendered objects in normal view.