Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

25 Excellent

About Redglyph

  • Rank

Recent Profile Visitors

819 profile views
  1. That link is not working, here is the correctly link below. However, I downloaded it (again), it's from 2015 and is completely outdated, I almost don't even recognize the game, so I'm not sure it's necessary. Since then I have to guess how it should work, which is really not great... It's fortunate some people in the community publish videos and alternate documentation, but I hope there is a real intention to update the official one at some point.
  2. It seems the thread with the call for help will be ignored, so I'm copying those two issues here: Brief description: typos in map names (Rheinland Summer 1944) Detailed description, conditions: (it's possible some of them were fixed in the mean time) Additional assets (videos, screenshots, logs): Your PC config data (OS, drivers, specific software): IL-2 version 3.201 ---------------------------------------------------------------------------------------- Brief description: missing airfield Detailed description, conditions: Additional assets (videos, screenshots, logs): Your PC config data (OS, drivers, specific software): IL-2 version 3.201 PS: editor made a mess of my two posts, hopefully it's still understandable
  3. Thanks for the tip and screenshot, Therion and 56RAF_Stickz! That's very misleading though, it's not an axis but a button and we have to guess we can configure two buttons in one entry. I suggest to at least have a more suggestive label?
  4. Brief description: mapping of trim (aileron, elevator, rudder) don't work on P-51 when mapped to controller Detailed description, conditions: The aileron, elevator and rudder trim work with the pre-defined keyboard mapping, but if they are also mapped to a controller (joystick hat for ex), using the controller doesn't do anything. Using the keyboard mapping still works. Additional assets (videos, screenshots, logs): Version 3.201 EDIT: same problem with P-38
  5. I think that even a simple set of procedures for the startup, take-off and landing would already be enough. Part of the information is in the brief panel and it's probably not the place to add more. A simple text file would be great, or maybe another alternative suggestion, an additional brief panel for the procedures? Thankfully it should be quite short and easy to do since it's not a full in-depth system modelling. Hopefully the support will read this. @JimTM Thanks, I know Requiem's great videos. Thankfully he did one pretty quickly, and sometimes other people will post information as well. But it's not really the point of my post, the vendor has this information and it would be possible to give it to us with little effort, thus avoiding people wasting time with trial and error, or guessing how things should work For ex, I had the time to install the patch, and check the Me 262. I tried the standard procedure and it failed, I thought it was improbable this would be a bug, so I looked everywhere for clues, found none, restarted the mission, checked the controls, saw a new ignition control and tried it a few times (restarting the mission every time). Finally I gave up since I was running out of time. If I had had this simple procedure, I could have enjoyed that much more
  6. Hello, First I'm really excited with the new release 3.101, and in particular the Me 262! It's really a new era to explore. But it also points out the obvious problem which has been there all along: the absence of any documentation on how to operate those airplanes. For most of them it's pretty simple, for early two-engined planes like the Bf 110 it's getting sometimes complicated, because of the faulty startup procedure in cold conditions (the user has to know he must start each engine individually to avoid a stall). Some late aircraft get even more complex, like the P-47. And each time we have to guess how they start, how they taxi, how they take off. Sure, the flight limitations are shown in the summary/brief panel, but it's simply not enough most of the time. And for the 262 it's getting puzzling, I see there is an ignition control, but when exactly must the pilot press it, and how long? Can it be used with the 'E' auto-start, or should we use individual engine start? (always better IMHO). What's the maximum speed on ground, depending on the type of terrain? How to restart in flight? There was a manual years ago, I'd suggest to update it with the current aircraft, that would be most helpful
  7. There is an aerodrome near Namur that is not on the map, but which was active from 1944 to the end of the war in 1945, as a US military airbase. It was then abandoned and re-opened in 1946 as civil airfield, which is still there today. I'm joining a document in French, including a crude map but if there is an interest I'm willing to translate the relevant parts. Since it's not too far, I can probably check if they have more historical information. From the map, the runway had the same orientation as today (06/24 with current magnetic variation) and is at 502917N 0044608E and elevation 594 ft (all info on today's EBNM airport on the AIP pages here). As a short summary, an US reco Piper Cub landed there in October 1944. It was still a large meadow but they were looking for a spot to build a temporary airfield near Namur, where general Bradley had his HQ. They removed all fences, tree stumps, poles, on a 40-hectare zone (hectare = 10000 square metres) levelled the ground and built a runway a little longer than 1 km. It was operational after the Von Rundsted offensive. The code name was "Gangway advanced", and held a large number of various aircraft. A main role was the evacuation of POW with C-47s, night and day, but damaged fighters used to land there too. EDIT: there's obviously a lot of info to process in the thread and that'll take a while. I can't monitor this every day so just PM me to confirm, if more info is needed. temploux.7zip
  8. No map yet, but several typos: - Niverlles (unreadable, maybe another letter), B-75, is actually "Nivelles" - Floidchapelle, SW of A-78/Florennes) is actually "Froidchapelle" - Auwaille (South of A-93/Liège, East of Spa) is actually "Aywaille" - Chievres (A-84) is actually "Chièvres" - Bierset-Liege (A-93) is actually "Bierset-Liège" or more commonly "Bierset" - (to confirm) Le Culot (two places, B-68/Y-10) is actually "Culot", we generally don't put determinative in front of city/town names in Belgium the Beauvechain airfield was indeed called "Le Culot" (from the name of the area)
  9. Since there is no real up-to-date documentation, I'd advise you to watch "The Air Combat Tutorial Library" channel on youtube, it shows a tutorial for each plane, fight and attack techniques, and other very useful information! https://www.youtube.com/channel/UCwV5RLX7mkaDy5gTIiuwGmg
  10. Brief description: graphics artefacts, white contours around cockpit features and other planes Detailed description, conditions: Best seen in the screenshots, there are white contours around the cockpit frame, the wings, engine, and other airplanes. They really stand out over ground and forest by contrast. Most are also visible at night which makes night mission very bad. Those artefacts change with time, depending on the angle, so they are very distracting. I haven't noticed those artefacts before, or not to that extend, it seems very recent, probably with 3.009. Anti-aliasing is not disbled in the nVidia driver, those are the standard settings (decided by the application), and antialiasing is set to max in the IL-2 options (see screenshot). It doesn't seem to work very well, though, most contours and features like antenna wire, for ex. in the main game screen in rotation around an airplane, show very visible aliasing as long as I can remember in IL-2. Perhaps both issues are linked even if the reported issue is more recent? Additional assets (videos, screenshots, logs): - 3 screenshots emphasizing the artefacts - screenshot with graphics settings Your PC config data (OS, drivers, specific software): - version 3.009 - screen resolution 1920x1200, full screen - extra hardware/software details in sig
  11. Brief description: AI bomber pilot doesn't close the bomb bay doors after run Detailed description, conditions: - A-20B bomber mission 5 of "Havoc over the Kuban" (for example) - equipped with internal bombs and extra bombs attached to the wings - the AI drops the bombs over the target, but forgets to close the bay door, it remains open all the way back to base Additional assets (videos, screenshots, logs): screenshot Your PC config data (OS, drivers, specific software): - version 3.009
  12. I've just completed "5. Dawn Patrol" and didn't encounter any issue, no crash. I've followed the leader all the time, except over the target area. I usually don't use labels, except when I have a big doubt when identifying a fighter (friend/foe). It seems that when I had occasional crashes in the career mode, it was linked to switching the labels on the way back of a long flight to check for potential stalkers. Perhaps that's the difference? I noticed on the log that three Lagg-3s crashed on the way back, all over the sea at about the same time. Out of fuel? Or is that on purpose (removing planes appear on the log as crashed planes)? PS: flying over these mountains was great! Really enjoyed this one
  13. Mission 3 complete, and this time one cargo went down (would have been earlier if I hadn't forgotten to open the bay. Damn!). There are a lot of things going on, it's really fun and alive! I checked the log, 3 planes were lost just because of the relief. I witnessed one perfectly healthy Havoc hitting the hills west of the airfield, when I was taxiing back after landing... so much for respecting pattern altitude, they should rather enforce a right-hand pattern to avoid that (I suppose it's hard-coded). Two other fighters crashed earlier into the hills on the way back too, not far from the base. I don't know if they were trying to destroy the AA or just not paying attention. Despite what was said recently in the fix logs, there's still an awful lot of AI crashing into the ground and into buildings, even if there's no relief. Just a note but I'm not sure there's anything that can be done: in mission 3: there are a few vehicles messing around at the end of the runway, they steered in front of me and cut the way when I was taxiing after landing (the short bit of "taxiway" at the end of the runway). I could brake in time but it was close, after that they went on, driving on the runway then back into the fields.
  14. I think it's this file, you have do double-click and confirm (it will set a flag in your registry so the OS will ask confirmation): IL-2\data\EnableErrorReporting.reg Then run the mission again, good luck! I also have crashes with long missions in IL2, though I only had that in career mode so far, but I'm not at mission 5 yet.
  • Create New...