Leaderboard
Popular Content
Showing most liked content on 01/11/2019 in all areas
-
12 pointsI really like the look of the markings in the drawing! Might not be the most likely rendition but it looks cool... My original: CIA: FAR:
-
8 pointsNATO F-84F Thunderstreaks (The Mirage Factory's F-84F with updated lines, rivets, etc. Original skins by Pappychksix, Thierry-As, Sony Tuckson, USAFMTL, Carlo ´´Soulfreak`` Vecchi, WhiteKnight06604)
-
7 points
-
6 points..yes I wrote I wouldn't do one. But since Geezer is back and we'll get a Bleriot XI shortly (just kidding) I decided to go back into business. All the aces will be there no matter if it's historical correct or not: Arigi, Barracchini, Scaroni, Baracca, Fulvio Ruffo di Calabria, Brumowski. If you've a wish, e.g. a special ace that should be included, I'll do the skin and adapt the campaign rgds gt
-
6 pointsExcellent rendition! I love the more colorful one too, and great work on the others! Mandatory pic, WIP Donbass fighting...
-
5 pointsCool skins! Will they be made available for CUBA campaign?......................Hope so - Nice work! Mandatory pic & Credits: Thanks Wrench for the outstanding F-80C and Soulfreak for the fantastic skins! (tweeked for the F-80 'What If')
-
4 points
Version 1.0.0
151 downloads
As radar technology developed, a new Meteor night fighter was developed to use the improved US-built APS-21 system. The NF.12 first flew on 21 April 1953. It was similar to the NF 11 but had a nose section 17 inches (43 cm) longer; the fin was enlarged to compensate for the greater keel area of the enlarged nose and to counter the airframe reaction to the "wig-wag" scan of the radar which affected the gunsighting, an anti-tramp motor operating on the rudder was fitted midway up the front leading edge of the fin. The NF.12 also had the new Rolls-Royce Derwent 9 engines and the wings were reinforced to handle the new engine. Deliveries of the NF.12 started in 1953, with the type entering squadron service in early 1954, equipping seven squadrons (Nos 85, 25, 152, 46, 72, 153 and 64); the aircraft was replaced over 1958–1959. What's in: - a new plane - 12 RAF skins 12 - pilot, weapons, sounds - all planes built serials 100 Credits: - Vetro 2k: original T.7 model - Yakarov79: nightfigher upgrade - paulopanz: skins, decals etc Operations: - key 10 canopy open Enjoy! @paulopanz -
4 pointsIt's in the pipeline, but don't hold your breath as I have a lot of other stuff to finish first.
-
4 pointsWhat a brave man! Smokes at the controls of the airplane! Of course, Hubert Latham, one of the pioneers of aviation, lit cigarettes right in the air, but this is still the exception rather than the rule.
-
4 pointsIf I ever get back to the Spanish Civil War, I'll certainly make a Heinkel. But I've been neglecting the Real World since early November and there are things I need to do there. Also, to be honest, I want to spend some time flying in the Eastern and Italian Fronts.
-
4 points
-
4 pointsMaking good progress on the R11 cockpit, but need help with the instrument panel gauges. Could a French-speaking fan - maybe Coupi or Jeanba - help me out? I need a distinctly FRENCH WW1 engine tachometer, air pressure gauge, and water temperature gauge. Thanks ahead of time.
-
3 points
-
3 pointsDe Havilland Vulture S.1 - No.17 Squadron, RAF Germany, 1969 De Havilland's submission to GOR.339 came from their Christchurch team under the leadership of W.A. Tamblin who proposed the De Havilland Vulture, a radical design featuring a variable incidence wing with podded Rolls-Royce RB.142R Medway turbofan engines. Tamblin's design was slightly smaller than most of the other submissions to GOR.339 and, apart from the variable incidence wing, it featured supersonic drop tanks and a bulged conformal belly tank to help it achieve the range requirement. In addition, De havilland's experience of 'buddy' refuelling techniques with the Sea Vixen were incorporated into their design from the outset and the company pitched a minimum change version at the Admiralty for carrier-based interception and strike. Air Ministry officials were delighted at De Havilland's claimed 70,000lb all-up-weight and with a general correlation between an aircraft's all-up-weight and cost their design soon became favourite to win the GOR.339 competition and in early 1959 they were awarded a contract for 220 aircraft for the RAF and 80 aircraft for the Royal Navy. Entering service in early 1968 with No.6 Squadron in the UK the aircraft soon spread it's wings to become the backbone of RAF Germany with the Vulture S.1 eventually replacing all remaining Canberra and Hunter squadrons and reaching a peak strength of eleven squadrons in RAF Germany by 1973. Nice One Cocas!
-
3 points
-
3 points...and many more Link -> http://www.aviation-14-18.fr/aviation-française/instruments-de-bord/ Translation Engine Tach = Compte tours Air pressure=barographe..altimetres(?) temperature=jauge temperature
-
3 points
-
2 pointsView File Armstrong Whitworth Meteor NF.12 As radar technology developed, a new Meteor night fighter was developed to use the improved US-built APS-21 system. The NF.12 first flew on 21 April 1953. It was similar to the NF 11 but had a nose section 17 inches (43 cm) longer; the fin was enlarged to compensate for the greater keel area of the enlarged nose and to counter the airframe reaction to the "wig-wag" scan of the radar which affected the gunsighting, an anti-tramp motor operating on the rudder was fitted midway up the front leading edge of the fin. The NF.12 also had the new Rolls-Royce Derwent 9 engines and the wings were reinforced to handle the new engine. Deliveries of the NF.12 started in 1953, with the type entering squadron service in early 1954, equipping seven squadrons (Nos 85, 25, 152, 46, 72, 153 and 64); the aircraft was replaced over 1958–1959. What's in: - a new plane - 12 RAF skins 12 - pilot, weapons, sounds - all planes built serials 100 Credits: - Vetro 2k: original T.7 model - Yakarov79: nightfigher upgrade - paulopanz: skins, decals etc Operations: - key 10 canopy open Enjoy! @paulopanz Submitter paulopanz Submitted 01/11/2019 Category Meteor
-
2 pointsOf course. We are very lucky in such a relatively small community to have so many who are so talented. And generous.
-
2 pointsThanks, but Gtrel's maps and Stephen1918's large stable of aircraft make the sim what it is today.
-
2 pointsNow you see them, now you don't... Unfamiliar with how to get the best from BoB2’s radio command menus, I had ordered everybody to get stuck in, of their own accord. As by that time our four vics - three Hurricanes each - was closing with the German raid from behind, I sort of expected they might open out a bit. But – the shortest distance between two points being the straight line I was flying – that the boys would stay more or less with me. My plan, such as it was, being that we would all wade into the enemy formations ahead, more or less together, just not in rigid formation. Alas, a quick look behind revealed that this plan had pretty well evaporated. I was alone. The rest of 242 had spread out behind me, the dispersed specks and white contrails indicating that the escorting 109s had arrived and that a general melée was in full swing. The airwaves had already begun to fill with the usual excited chatter. What to do? I don’t think there’s a way of recalling just your own section (3-plane vic), BoB2 not having the nested commands enabling you to choose whether the order you want to give is to your wingman/section. to a particular flight, or to the whole squadron. And anyhow, it looked a bit late to recall anybody. Either I rejoined them, and pitched into the air fight behind, or I took the opportunity to carry on and come in behind the now possibly unescorted bombers. I considered briefly, then chose to carry on. Keeping a wary eye on my tail. I edged out towards the right of the mass of contrailing enemy aircraft, picking out the right-hand Stuka for my attack, from below and behind out of his gunner’s field of fire. As I closed in, I noticed that my chosen Stuka had neither fixed undercarriage nor cranked wings. I was closing in on a bunch of snappers – Me 109s to be precise. All on my own. Well they hadn’t seen me, so I decided I’d press on and try to clobber one of them before the rest woke up to what was going on. My target first knew I was behind and below him only when I pressed the t*t and let fly with a short burst at eight times a thousand rounds a minute. Evidently somewhat put out by this, the 109 broke down and right towards some clouds, with me hard on his heels. The cloud cover didn’t save him but it may have saved me from his friends, whose reaction I could not see. After some more hits, the 109 went down towards the North Sea minus a significant part of his outer right wing. No need to follow that one down, he’s out of the fight if not doomed. In the circumstances, it’s more important that I avoid target fixation. That need was sharply brought home when, looking around, I suddenly saw a falling Spitfire, just above and to my right, emitting gouts of burning fuel as down he went. I hadn’t seen any Spits to that point, nor did I see his attacker. Not wanting to be the next victim, I pulled up and broke hard right and towards the nearest clouds. Finding myself alone again, I pulled clear of the clouds. Heading south again, I saw ahead of me that the rest of 242 was still hotly engaged, about where I last saw them. I could still hear their radio calls, including a few reporting that they were pretty well out of fuel. They must have been my boys, as I think that in BoB2, as in Fighter Command at that period, it’s one squadron per radio net. But how could they possibly be low on fuel? Damaged, perhaps? Either way, hopefully they tried to get down onto terra firma somewhere, while they could. Catching a call for help, I raced over to the scene of the action; but broke hard when sharp plinking sounds indicated hits on my airframe, from an unseen 109 behind me. He must have been moving a lot faster because he promptly overshot me and turned left. With me now after him. I got a couple of good bursts into him before he drew out of range and saw what might have been his canopy fly off, before he too went down somewhere below. Again, on my own in a dangerous place, I had better things to do that try to confirm his fate. Soon after, I spotted a second lone 109 over on my left, headed towards the coast, and again tried to catch him. He was too far away and going too fast - I could not gain any ground. I don’t have manual engine control active, but nevertheless I was trying to keep my engine boost gauge in the red only for short periods, concerned at seeing my oil temps up near that gauge’s limit. Eventually the 109, now just a speck, joined up with three or four others headed south. Together, they disappeared into the upper reaches of a cloudbank and I grabbed this opportunity to take my leave of them. I levelled off and came back onto a northerly course, just out to sea, now much lower of course from where I’d started. Where was everybody? The airwaves seemed to have gone quiet, no more cries of ‘Shoot him!’ or calls for help. At this lower level, all this bloody cloud very much limited one’s field of view. Where indeed was everybody? After a bit, I spotted a bunch of distant specks, which looked to be the raid making its way back down to the south, perhaps a little diminished in numbers and with one machine trailing smoke. No point going after them, I was low on ammo and my concern now was for my boys. Time to order a recall, which I did. I orbited, but no-one showed up. A request to report in produced a response from Blue 2…then silence. ‘Go home’ I ordered, and then set my own course back to Coltishall, up to the north-west.It wasn’t a long flight but it gave me plenty of time to wonder what I had done with the rest of the Squadron. I made a careful half-circuit on arrival... ... and, as if in mockery of my recent, lamentable performance as a squadron leader, I made the best landing I had ever managed in BoB or BoB2, in which getting down without lots of rattling, bouncing and maybe even a nose-over is much more difficult than in about any other sim I have played. On the ground as I came in, I could see Blue 2, rolling very slowly towards the hangars amidst a cloud of smoke, with no help from the fire truck or blood wagon. So that was it, just two out of twelve had got back. Crikey! And all I’d got in return was a couple of Probables. The debrief confirmed we had lost ten aircraft and nine pilots, all for claims of three Destroyed and another three Damaged, all 109s. BoB2 provides other status reports and I consulted the Squadron Diary for 242, which added the shocking detail that we reckoned we'd been up against over a hundred 109s, more than seventy 110s (which I for one never even identified) and thirty Stukas. That’s a really big fighter escort, especially for such an early phase of the Battle – equal numbers of fighters and bombers might be more usual in July. No wonder we got hammered! Goodness knows what happened to the convoy. Worse still, a look at the overall summary of claims and losses (‘Review’) indicated that in the first three days – it was actually July 12th, not the 11th as I mentioned originally – we had lost over 120 fighters, nearly four times what we’d claimed shot down! Such extremes seem to indicate I had messed up more than merely running the campaign or a squadron. It’s as if I have invoked hidden AI skill settings so the Luftwaffe are all set to ‘Nazi Superman’, while the RAF are all at ‘English Nanny’ – a bad illustration perhaps since though unable to speak from experience, by repute one English nanny is a match for any number of supermen, Nazi or otherwise J Apparently older versions of BoB2 had a bug whereby 2d (campaign) results might not match what was experienced in 3d (flying), but that was fixed and seems not the issue here anyway. Odd things can happen if you load a campaign from an old version of Bob2 into a more recent one, which I don’t think I did, although I confess to restarting the campaign at least once, not following the manual’s advice on naming conventions when saving, and loading saves indiscriminately between the two default names offered (BoB and Savegame). Anyhow, disaster after days via massively lopsided losses not being commonly reported from players, there’s something amiss here which I will need to troubleshoot and fix. Perhaps deleting my saved campaign files and starting one afresh would be worth trying. I’ll make some enquiries over at A2A, before I resume campaigning. In the meantime, there is plenty for me to do flying BoB2’s historical and training missions. And as experienced players have advised, that’s really the best way to build up before you pitch into the deep end, actually flying the Battle itself.
-
2 pointsSee the video below - Lt. Jean-Francois Martin of Le Gendarmerie de Montagne is my choice for "Second Best Pilot"!
-
2 pointsNo one has yet been able to surpass "The Fateful Adventures of the Good Soldier Svejk in the World War" by Jaroslav Hašek
-
2 pointsMy whack at turning Cocas's fantastic "Blackburn Shark F.1" back into a Me-262 HGIII. My first time re-texturing. I may try giving it some camo later.
-
2 pointsI did a very quick review on the CR32 cockpit and it looks proper. I think Coupi had the default view zoomed out a bit, maybe for artistic reasons. I checked the cockpit position and it looked good. Also checked the gunsight alignment by firing a few rounds at ground targets and they hit within the small inner ring from probably a couple hundred feet. Here's what the default view looks like: I think the only other thing to check might be the depth of the upper wing fuel tank.
-
2 pointsLockheed F-113C Starflash - 119 Squadron, Israeli Air Force, 1973 Credits 3D Model: Cocas Skin: Nyghtfall And, yes, those are the pilot's size 12's poking out of the fuselage!
-
1 pointFlying a sortie in the RAF campaign This is my second mission report from my new (or at least, new-found) toy - A2A's Battle of Britain II - Wings of Victory. In case anyone's wondering, I didn't set out for them all to be called 'A bad day for...' - that's just how it's working out, so far. A bit of a give-away, or spoiler if you like, but I trust it won't last, and that future mission report titles will be a tad more cheerful. Anyhow now that I've made a start with a BoB2 campaign, I'm wondering why I didn't take to it years ago, when I first got Rowan's original, or A2A's remake. Especially since both are so much better with the BDG updates. Now, you can even play a more conventional campaign, as described in the comprehensive BoB2/BDG manual, which enables you to have a log book-carrying, squadron-based pilot persona. This uses the underlying dynamic campaign 'wargame' to generate your missions. But for now I'm doing a conventional BoB2 'commander' (not 'pilot') campaign. The main difference is that the commander version allows you to act as any and all of the Air Vice-Marshals commanding 10, 11 and 12 Groups, Fighter Command, plus jump in and fly any squadron scrambled or tasked to patrol, either on takeoff or on meeting the enemy. Also at other points but the latter is the most interesting, and enables the player to jump in just before the start of any air fight, in any of the aircraft in the squadron about to engage. I opted to start at the beginning of the first phase into which the Battle is conventionally divided - the channel convoy phase, starting 10 July 1940, just after the fall of France. Among the many options, you can set things so that the AI Luftwaffe you will be facing starts the battle mainly by attacking British coastal convoys ('historical' tactics), or using 'optimal' ones - which likely involves going for more beneficial targets earlier, like your airfields or aircraft factories. I opted for 'historical' and as expected, ended up with the RAF campaign AI flying standing patrols to protect convoys, plus scrambling squadrons to intercept raids as they come in. This campaign AI presents you with 'directives' which set rules your deployed forces will follow, and allows you both to vary these or create your own. It also takes decisions on what and when to scramble, abiding by these directives. The BDG manual gives excellent, detailed and illustrated advice on how to do all this, but the AI is quite good for the RAF anyway. I opted to accept all the defaults and let the AI fight the Battle, so that all I had to do was wait for something to happen and then dive in to any action that developed. As each campaign day accelerates and decelerates time as needed, you are not kept waiting staring at the map for long. And even while you are, it's a not uninteresting experience; you can watch convoys moving, patrols orbiting, raids developing and squadrons scrambling, while listening to reports as they come in. 'Hostile seven zero one is now a hundred plus' sounds positively sinister, even though spoken softly in the polite tones of an invisible but obviously efficient and very possibly pretty virtual 1940s WAAF at the plotting table. Above is my campaign map near the end of the first of three sections the campaign day is broken into - morning, afternoon and early evening. The aforementioned raid Hostile 701 is near bottom right, returning to base after attacking Convoy Jaunty (authentic convoy and squadron reporting names are a feature), which is the grey ship marker in the Channel between the headlands at Beachy Head to the west and Dungeness to the east. The blue and white markers are RAF fighter squadrons, either the convoy's standing patrols or those scrambled as the raid came in and now heading home. During this raid I jumped in with 79 Squadron as the leader (the top right blue/white marker) when it intercepted Hostile 701. Here I am contemplating the incoming raid, from a not-terribly favourable position... ...and here I am dealing with a Messerschmitt 110 which objected to our presence... But this mission report is about a sortie I flew the following day, 11th July. A convoy had left the dangers of the channel behind and sought safety off the North Sea port of Felixstowe. Not so safe, as it turned out, for Luftflotte 2 decided to have a go at them. Once again, we were up against a raid reported as 'a hundred plus'. Being keen, I accepted the first offer of combat that the campaign AI offered me, for the first squadron to sight the enemy in the air. This was no less than 242 (Canadian) Squadron, commanded by no less than Squadron Leader Douglas Bader. BoB2 being the stickler for unit-level historical detail that it is, it was no surprise when I therefore found myself in the cockpit not only of a Hurricane, and not only of one bearing authentic squadron codes ('LE') with each aircraft in the squadron with its own unique individual aircraft letter; but my mount was no less than the boss's own machine, LE-D, with my blue and red leader's flash below my starboard cockpit and the unofficial unit emblem, Adolph getting a kicking, adorning the nose. My Corgi diecast 1/72 has the leader's flash on the opposite side, the mirror image A (camouflage) Scheme, and is serial V7467 not P1966, but such minor details apart, BoB2's version is a pretty good replica. Would I do the illustrious pilot justice, whose flying boots this sortie had found me filling? Well, yes and no... ...to be continued!
-
1 point
-
1 pointLooks well worth the wait! Do what you have to do, and thank you. At this rate, I don't know whether we need to rename our game FE3 or First Eagles, Geezer Super Edition!
-
1 point
-
1 pointLast week we discussed the many aircraft projects that will be under development in 2019. Today, let’s look at some of the non-aircraft projects. As mentioned last week, we cannot promise that all of these will be released in 2019, but they will all be under focused development. Ships Although we released a greatly improved and free Nimitz-class aircraft carrier at the time of the Hornet release, we are also working on a separate Nimitz-class aircraft carrier module. This product will have an incredible level of detail and include such features as a detailed and operable LSO and Air Boss stations, detailed modeling of the hangar, animated deck crew, briefing room, and control of the carrier. Once this project is complete, the team will finish up the Arleigh Burke-class destroyer and then return to and release the updated Kuznetsov-class aircraft carrier. Combined Arms No combat environment is complete without a good solid ground game, and we continue to improve on and add to your abilities to control ground forces either from a commander position or behind the controls of a single unit. As with 2018, we will continue to address issues and look at new features to improve Combined Arms, based on your feedback, throughout 2019. We will continue to add new content in the form of new units both to the core sim and the WWII Asset Pack, as well as exciting new missions and campaigns. We are currently at work on new CA-related effects like main gun fire, dust trail, localized damage, and smoke grenades, while also working on improved ground unit AI like line-of-sight issues, pathing, and more intuitive control. Radio Communications The biggest radio communications task are the aircraft carrier communications that includes CASE I, CASE II, and CASE III for departure, marshal, approach, and the Landing Signal Officer (LSO). Once this massive task is complete, we will move on to an overhaul of the airbase radio communications. New Maps With 2018 we saw the release of the DCS: Persian Gulf Map. For 2019 we and our partners are working on two new World War II maps, a Syria map, a Falkland Islands map, and a new free map that we’ll discuss later in the year. In parallel, we will be finishing up the Persian Gulf map with the addition of Liwa Airbase and Ras Al Khaimah airport; Al Ain Air War College; ruins near Shiraz, Kerman, and Bam; and fix remaining bugs. Once complete, it will be the largest DCS World map as measured from airfield to airfield. Dynamic Campaign While a hangar of great aircraft is certainly a wonderful thing, having an engaging, exciting, and dynamic combat environment is equally important. We have been developing the inner-workings of a dynamic campaign system which will continue into 2019. Based on the strategic goals and tactical situations, the systems will create dynamic Air Tasking Orders (ATO) that players then join to help their side to victory. This work is non-trivial, but we believe the addition of this system should be exciting for DCS users. DCS World Multiplayer In the closing weeks of 2018, we made the Dedicated Server software available to a handful of trusted 3rd party online servers. Based on their feedback, we have been tuning and expanding the software to best suit customer needs. One aspect of the Dedicated Server we are also exploring is the availability of free maps to Dedicated Server hosts. In addition to this new Server software, the team has also been at work developing an integrated Voice Over IP (VOIP) system for DCS World which is based on the growing Web RTC standard. The first phase will allow users to use and create “rooms” and the second phase would integrate the VOIP into in-cockpit radio controls. As mentioned in last week’s newsletter about Modern Air Combat (MAC), we also plan to include leader boards, rankings, and other online statistics for DCS World online players. DCS World Foundation In parallel to all the above, the team continues to work on the foundation items of DCS World like air and ground artificial intelligence, performance optimization, more detailed damage models for all unit types, Vulkan implementation, improved VR optimization and improved Touch Controller support, aircraft wake turbulence. DCS World Steam Edition to DCS World e-Shop Transfer You can now transfer modules purchased on Steam to your DCS World e-Shop installation. Note that this only applies to Steam DLC that uses Steam protection, not StarForce keys. All DCS World DLCs released on Steam from 12th May 2017 can be transferred. Here are some modules released on Steam after 12-May-2017: DCS: M-2000C DCS: NEVADA Test and Training Range map DCS: Spitfire LF Mk.IX DCS: AJS-37 Viggen DCS: Normandy map DCS: WW2 Assets pack DCS: Su-33 for DCS World DCS: AV-8B Night Attack V/STOL DCS: F/A-18C Hornet DCS: Persian Gulf map Please see this link for complete directions Given that Steam no longer accepts our 3rd party license keys, binding of keys purchased on the E- Shop cannot be transferred to the DCS World Steam Edition. Hornet Missions of the Week In our quest to bring more and more great, new content to the Hornet, we are now providing a Hornet Mission of the Week! The first two missions can be found here: River Run Strike Fighter These missions will also be integrated into the Hornet Instant Action list of missions. Sincerely, The Eagle Dynamics Team
-
1 pointI understood you. In this case, you only need this program, as mentioned above. Hex-editor_XVI32.rar
-
1 pointFor safe and easy use thats correct. But it's not really needed, as the length actually _can_ differ. You just have to watch carefully, how the characters etc. are coded. The pattern in the picture is character, followed by "00" (the dots in the right column). Add those "dots" on the left side by typing 00....if you hit the "dot-key", you will get the hex-value of the actual dot, which is not "00". Follow this pattern and don't overwrite stuff other than "00" and it will work with longer or shorter names too.
-
1 pointTally Ho! Here we are, on a vector to the bandits. When I say 'we', I realise that I mean both 242 Squadron which I'm leading in LE-D, but also the chaps down below and to our right. The eagle-eyed will have noticed that these Hurricanes carry larger fin flashes and fuselage roundels - and different squadron codes: GN, indicating they are from 249 Squadron. I had thought from the campaign map when I took over 242 that we were on our own, ahead of the pack of three or so squadrons scrambled to intercept the raid on the convoy off Folkestone. Must pay a bit more attention to that map in future, I told myself, like pausing and zooming in (to uncover markers hidden beneath other markers). Before I jump into the hot seat. The BDG manual does recommend that when taking over a flight about to hit contact, you pause the game once in the 3d to re-orient yourself. In fact there's a setting that does that by default. As with any new sim, I have a lot to learn, perhaps more than most as, like Steel Armour - Blaze of War, BoB2's sim-within-a-wargame approach repays taking time to learn the greater number of ropes. Not jumping straight in, like me. My first inkling that this very lesson was going to be mercilessly drummed into me came when I got my first clear view of the raid, coming up from the south. Gave me a right good sense of what Dowding's boys felt like, that did; scrambled in individual squadrons to intercept raids of a hundred or more. Yes there were almost certainly others on their way but the sense of being outnumbered was brought home with a bit of a shock, when I saw that little lot up there. OK I've got a fully functional rear view mirror, but do I miss the dynamic shadows or higher-res cockpit textures of more modern sims? They're nice to have, but no, not really. As in IL2 '46, you have much more pressing things to be aware of and indeed, appreciate. Not least the 'Now, THAT'S what I call a raid!' moments, coupled with the sense that you are not fighting in the Minor Skirmish of Britain. Much more important. For a while, I flew dumbly on. There was Jerry, and there was I, wondering what the Hell to do about it. For a while, I couldn't think of anything better to do, than take some more screenshots. So that's what I did. While I climbed hard and watched this armada go sailing past on a reciprocal course, up above us. Wisely, 249 seemed to have decided to do something different, for they were gone. Straight home, if they had any sense. I was fearful of being bounced of course, but I recalled enough of my WW2 air combat tactics to know that turning in under a higher enemy to force him to make a head on-steeply diving pass was a defence in this situation. Here, I didn't even need to turn. But no attack came. Perhaps wisely, Jerry resisted the temptation and ploughed on. Feeling a bit less scared, and still climbing, I began to lead 242 around and after them. Soon, we were coming up behind the beggars, still with a bit of catching up to do. The Huns looked like single seaters, possibly Stukas, but likely also with 109s for escort. Very likely, since I could see some contrails peeling off to the left of the main formation. Probably snappers (fighters) turning to come in on us from abeam or astern. It was at this point that I finally had to admit to myself that I had not practiced nearly enough squadron-leading using the BoB2 radio command system. This is different but quite sophisticated, coupled as it is with what they call an 'auto vectoring' AI which aids control - after giving certain combat orders, you can actually hear yourself on the R/T translating that into some sort of drill or tactical response, which might be 'Pick your own targets - there's dozens of them!' Or something a bit more sophisticated. But of course I had read and dabbled, but not practiced sufficiently. So I basically ordered a free for all, and that's what I got. ...to be continued!
-
1 pointThanks for the link, love to learn this curious facts about aviation history. Maybe the drawing I posted is a bit colorized in order to be more attractive? On the drawing you can see the VA-34 markings on the tail not completely covered, so the blue is still visible, same for black numbers in the nose, and even the canopy is painted blue! Also the grey used is much darker so it gives the impression of being painted more crudely lol. Mandatory screen: Refugee extraction mission...
-
1 pointIf only there was a way to bring Snoopy back. Yeah he never fired the smoke rockets and all too often was shot down, but I can't be the only one who missed seeing that little O-1 orbiting a tank battle.
-
1 point
-
1 pointThe Greek skins are something I started long ago but never finished. The aircraft is MontyCZ's excellent Avia B-534:
-
1 pointI solved the issue and that is the merit of Crawford, who pointed out that replacing a fakepilot won't work, because a pilot LOD distance is limited (from its design) to 200m no matter what one would do, which didn't cross my mind until now. I had the same issue, in the past, with the SU-30SM canards and I abandoned then the pursuit for a solution. Now I applied this trick and it worked. I can see the canards from 2000m, without have them disappear. The same should work for the rotodome. I'll be back after testing with the results. UPDATE yep, it works, the rotodome is now visible all the way up to 2000m. Case closed.
-
1 pointThanks guys, Reinstallation worked first time. I've no idea what I mucked up before, must be out of practice! Changing subject, but still relevant, I'm re-reading "The Two-Headed Eagle" by John Biggins, a fictionalized account of the adventures and misadventures of Otto Prohaska, an Austro-Czech naval officer attached to the KuK Fliegertruppe on the Isonzo Front in 1916. Clearly grounded upon solid research into the period, it gives a dramatized but authentic picture of the Hapsburg Empire in its waning days. It is very far from dry though, with moments of farce and tragedy all narrated by the protagonist with a deep sense of irony. It is the third of four novels in the Prohaska series, all very highly recommended! Cheers Mike
-
1 pointYou should look for a place to land right after takeoff or have a personal refueler on the way to your targets. ;)
-
1 point
-
1 point
-
1 point
-
1 point
Important Information
By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..