Jump to content

twgin

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

6 Neutral

About twgin

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

358 profile views
  1. Hello to all, going through some stuff at home, came across these, contact me on twgin((at))me((dot))com if you are interested... first come first serve ! media mail postage in the USA will be on me, if you are international, probably ask you to pay postage ! Terry
  2. Gambit21's missions for this plane are outstanding, incredibly atmospheric ! The book is: The Forgotten Five Hundred, by Gregory Freeman... I got it at the library, need to read it before its overdue ! Terry
  3. Agree with Rjel, swapping out the "input" folder, while inconvenient, works pretty well. Would be nice to have a button to Exit game to the desktop, right now a lot of clicks just to quit (I bounce back and forth between VR and non-VR for various reasons, this would be very nice in those situations). Would be nice to be able to map the "Escape" key, especially for VR flying. In a perfect world, the tech talk would read out in appropriate units, for instance, flap extension in degrees rather than per cent, prop RPM setting in degrees rather than per cent, throttle in ATA rather than per cent... and so on...
  4. interesting links: https://aviationglossary.com/kollsman-window-altimeter/ https://www.boldmethod.com/blog/lists/2017/05/the-5-types-of-flying-altitudes/
  5. I dialed up a BOM campaign mission... given in the briefing was departure airfield elevation of 151 meters (called an altitude in briefing !) and atmospheric conditions of 764 mmHg. In the cockpit (Ju-88), I chose the "nearest airfield" option and both cockpit altimeters dialed themselves to "0". This is expected behavior. Switching to bombsight view, the reference altimeter read 151 meters (this is correct airfield MSL elevation, as LukeFF said, this altimeter is reading MSL despite the setting on the cockpit altimeters) Back in the cockpit, I then chose the "standard atmosphere" option and the cockpit altimeters dialed themselves to a Kollsman window value of 1013 millibar, resulting in an indicated airfield elevation of only 111 meters (wrong elevation, some 40 meters too low, see below). Switching to bombsight view, the reference altimeter still read 151 meters, or correct airfield elevation ! So: I think LukeFF is correct in that the reference altimeter on the left in the bombsight view always reads actual MSL altitude regardless of cockpit altimeter settings. Bomb drop to be dialed in on the right will always be the altitude indicated on the reference altimeter on the left MINUS the target elevation reported in the briefing. Answered my own question, I did... For those interested, the "standard atmosphere" option for the cockpit altimeter is useless... in this case local pressure as reported in the briefing was 764 mmHg (millimeters of mercury). The cockpit altimeters of the Ju-88 (there are two of them !) use a different unit system: millibars. A local pressure of 764 mmHg should translate into a Kollsman window value of 1019 millibar. In fact, when the "standard atmosphere" option was chosen the Kollsman window adjusted to 1013 millibar (and a wrong indicated elevation of 111 meters). 1013 millibars is equivalent to 760 mmHg is equivalent to 29.92 inHg; all are representations of atmospheric pressure on a "standard" day. It would make more sense for the program to set whatever local pressure is specified in the mission briefing; although this might be problematic and individual missions may not specify a value for this... So: In game I would set the altimeter option to "nearest airfield", the altimeter will read correct AGL altitude above your airfield for the balance of the mission. Use of the "standard atmo" option means that whatever is indicated on your altimeters is off by some unknown amount, unless local atmosphere just happens to be standard.
  6. This is kind of why I asked the question... Inkompetent says that (what I call) the reference altimeter in the bombsight (in the bombsight view, the altimeter on the left) reads what I called "bomb drop" directly, regardless of any other setting used. This says whatever value shows here should just be dialed in over on the right side of the bombsight. But what does "dialed in flight altitude" mean ? If an accurate description, this really is kind of boring... LukeFF on the other hand, says that this reference altimeter (in the bombsight view, the altimeter on the left) always shows MSL altitude (regardless of other settings ?) which must be modified by the target elevation to get a "bomb drop" number to dial in over on the right side of the bombsight. Which, if either, correctly describes the behavior of IL2 ? How to find out ? a little aside, airfields, targets, i.e. things on the ground, do not have altitudes, but rather elevations... a pretty small point but using more precise language might clear up confusion on these matters...
  7. I have read most of the material on Level Bombing but still have some questions... I'm flying the Ju-88 mostly but questions would apply to any of the bigger bombers... I have read some (older) comments that the "units" setting in the game could affect things such as differences in what the cockpit altimeter reads vs. what the reference bombsight altimeter reads, i.e. preferences are set to Imperial, but flying a German bomber that uses Metric, discrepancies between the cockpit altimeter and the reference altimeter in the bombsight view happen. As of now (October 2017), it seems the best setting available in preferences is "airplane dependent", and any old bugs due to this issue are now dead ? In campaign missions information given includes elevation of departure airfield, elevation of target, and local atmospheric pressure in millimeters of mercury (mmHg). Elevations given are understood to mean MSL (height above Mean Sea Level). For setting Altitude in the bombsight, the particular altitude we are concerned with is ALWAYS "above ground level" or AGL in real life parlance. In other words, how many meters or feet will the bomb fall after leaving the plane until it hits the ground. It seems to me it would be clearer to not call this an "altitude" but rather refer to it as something like "bomb drop". Is this a true statement ? Two ways of setting the cockpit altimeter: 1) At nearest airfield - when selected (and sitting on the ground at departure airfield) will basically set cockpit altimeter to "zero" regardless of actual atmospheric pressure, cockpit altimeter then reads AGL above the departure airfield for balance of mission. Value for bomb drop can be calculated using the difference between the departure field elevation and the target elevation. For instance, assume departure airfield elevation is 100 meters, target elevation is 200 meters, planned altitude for bomb run is 3000 meters. If before taking off you select "nearest airfield" for the cockpit altimeter, eventually level off at an accurate 3000 meters as indicated on the cockpit altimeter, bomb drop would be 2900 meters as the target elevation is 100 meters higher than departure field elevation. This could be set in the bombsight at any time and the reference altimeter in the bombsight view can basically be ignored. 2) Standard atmosphere - I have seen comments that say using this will set the Kollsman window of the cockpit altimeter to 760 mmHg (the atmospheric pressure on a so-called standard day, equivalent to 29.92 inHg in the US, or 1013 millibars in Europe) regardless of whatever local pressure is specified in the mission. If this is in fact true it is indeed a spectacularly useless setting; I can't see any way it gives any useful information. It would make more sense if, when using this setting, the cockpit altimeter is adjusted to the local pressure specified in the mission. In this case the cockpit altimeter would reliably read MSL altitude and bomb drop is easily calculated with target elevation. Real life pilots set their altimeters in this way every time they get in an aircraft, and after doing so the cockpit altimeter will indicate field elevation (in the example above, after setting the cockpit altimeter to local pressure, the cockpit altimeter would indicate departure field elevation of 100 meters). For a bombing instance, if target elevation given as 200 meters, after setting local pressure before takeoff, bomb drop would be whatever the cockpit altimeter reads minus 200 meters. Again, if the aircraft is accurately leveled off at 3000 meters as indicated by the cockpit altimeter, bomb drop is 2800 meters, which can be set in the bombsight at any time, and still not using/ignoring the reference altimeter in the bombsight view. So I guess the questions would be: Anything written here wrong ? What is set on the altimeter when using the Standard Atmosphere option (the Kollsman window is visible but tiny in game, perhaps I can check this...) ?
  8. Re-awakening this thread... I fly VR with a Vive. When starting up the game mouse cursor is there to choose all menus and options, etc. but when inside the cockpit no mouse cursor or function... when I switch to outside view I can use mouse for free camera rotate and up and down, zoom in and out, but nothing in cockpit. Is this as it should be ? had a mouse and a track ball, unplugged the trackball, went into il2.exe properties and checked the "override high DPI" box (windows 10, 64), no change in game behavior... Terry
  9. yes, thanks, that was it, one of the checkboxes under custom realism... still no joy on the altimeter ! thanks again, terry
  10. Something is buggy with the plane... RSHT + P has no effect, also I notice that switching the altimeter from reference pressure to nearest airport does nothing either... so at least two controls are non op for some reason... something in settings ? Terry
  11. thanks, flying with a Warthog Hotas stick and throttle, I'll give this a try... so far RSHT + P has no effect, i.e. the blue icon for "auto propeller RPM" doesn't go out as I think it should, hence the switches I have mapped to increase and decrease RPM have no effect. Hanford ? I'm in Madera ! Terry
  12. I'm spinning my wheels here... I am beginning to fly the JU 88 in BOM. After starting up a mission I have a blue engine management icon with a prop in it that says "auto propeller RPM". This is fairly straightforward so far. Is it possible with the JU 88 to turn this off (i.e. manual RPM controll) and if so, how to do? Thanks, Terry
  13. Done 3 of the 5 so far, absolutely enjoyable VR flying experience. flying through the dogfight/ground battle in #2 amazing... night flying in the driving snow and getting "coned" by the enemy searchlights, wow... I went into #3 and edited Pelican Lead speed down to 225 kph, was much better as I could keep up without maxing out the engines... Thanks for this incredible set of missions ! Terry
  14. I think VR Zoom is the only "zoom" for VR.... I haven't found any others that work along with the other cockpit camera controls... The camera you want is "external free camera at player plane" with which the mouse will pan around and you can get closer/farther with <right mouse button + move mouse> Terry
  15. Thanks Black_Sab, that worked just fine. I wrote a couple of two line batch files, first line to change directory, second line to start IL-2 with the commands. Thanks ! Terry
×
×
  • Create New...