Jump to content

33LIMA

EDITOR
  • Content count

    3,403
  • Joined

  • Last visited

  • Days Won

    7

33LIMA last won the day on June 29 2017

33LIMA had the most liked content!

Community Reputation

785 Excellent

About 33LIMA

Profile Information

  • Gender
    Male
  • Location
    Belfast, NI
  • Interests
    Military history, AFVs, infantry weapons, flight/flying, airsoft.
  1. Thanks - found them now. Another reminder I've just had, as to how good BoB2+BDG is...I was tootling east along the coast after a circuit at Tangmere, when I came to Brighton and saw the famous pier. 'A graphics glitch', I thought, seeing the section of pier missing. Then I remembered, they disconnected the ends of such piers from the coast, to deter the Germans using them during landings. Now, THAT'S attention to historical detail!
  2. "Hmmm...now, why can't MY boys maintain a nice tight formation like those Rolands?"
  3. The same scene, from the viewpoint of one of a formation of AEG G.Vs brave enough to venture out on a daylight raid:
  4. A Bristol Fighter gets a nasty surprise, in the form of an Albatros D.V firing air-to-air rockets... ...actually of course, it's just an optical illusion from a plane going down in the distance :) The Brisfit is one of the many essential planes for FE/FE2 that's available courtesy of the A Team Skunkworks.
  5. Thanks Sky High - have had a quick trawl through the 'Subscriber modifications' thread at A2A/BoB2 looking for mods, seems you have to find the post there with the link to the mod and that there's no 'mods master list'. anyway will look out for the stuff you are recommending.
  6. Thanks for the tips guys. I got an Alt+X CTD last night with Buzz73's settings and graphics options at medium again as a baseline, so I figured if I'm going to get crashes, I might as well get them at high settings. I also applied the recommended lines to BDG.txt to get autogen trees, and found that 8x anti-aliasing plus 4x sparse grid supersampling in Nvidia Inspector kills the shimmering on distant terrain. I also killed the compatibility settings on BoB.exe and reverted to 'Run as admin' only, much as per Dustbag's original post...and I have had two takeoff training missions on a row without the Alt+X CTD. So I will stick with that and see how I get on. I had forgotten how good Battle of Britain/BoB2-WoV was - is - with the BDG patches and Multiskin. The RAF airfields look to be very faithful renditions of the real ones at the time, well furnished with blast pens, emplaced AA guns and all the rest. And the sheer variety of authentic aircraft schemes and markings - including different RAF fin flashes and various undersurface treatments - is very impressive if not unequalled. Heck, I can even fly 11 Group boss Keith Park's Hurricane, complete with the Old Man's personal squadron code and the man himself in his distinctive white flight suit. I can see why established BoB2 players call this one a 'time machine'.
  7. Thanks for the encouragement Strikeagle. That A2A thread I saw, it goes cold after Buzz73 posted his settings as also on Steam. The Buzz73 posted on both forums, several months after his first settings post on A2A, that they were still working for him, implies he had found a stable solution. Last night I got several normal mission endings with his low-medium in game settings, but another Alt+X CTD when I pushed most of them up. The plan now is to stick with medium settings for an extended period, to see if that works consistently, and then try one high setting at a time, starting with the ones that I find most important, like aircraft textures, horizon distance and weather/cloud. Will report back.
  8. I suppose A2A Simulations' forums are the place to ask this, but the question appears to be hanging in the air, there and elsewhere on the net, so I'll pose it here... Has anyone got BoB2 working fully in Windows 10? I've been spurred to try for myself for two reasons: 1. My Vista 64 box's mobo gave up the ghost so I now have a newer replacement which has Win 10 Pro. With which I've got the vast majority of my sims working fine, mostly from the old HDD which is now installed in the new box to complement the fast-but-just-120GB-capacity SSD that came with it; and 2. The arrival of Wings over the Reich prompted me to renew my acquaintance with sims of the classic Battle, in which I have always been very interested. As I posted 'in another place', I was keen to see WoTR's arrival, but deterred from jumping in when it arrived by a number of issues, including: very small German formations ('Minor Skirmish of Britain', anyone?); bombers way too widely spaced; UFO Bf110s; few flyables; very limited variety in aircraft skins (only slightly better now); and quite seriously for the defender, little or no representation of Ground Controllers. It seems the most recent patch has endeavoured to fix some of these issues eg the really tiny incoming raids, but others remain. I also tried a CFS3 ETO freeware mod which covers the Battle, based on the ETO expansion...but it just reminds me why I always reckoned CFS3 was ok at what it was designed to do (tactical air ops)...but not much else. So back I came to A2A's makeover of Rowan's classic. Despite making my own map-based BoB wargame back in the '70s, I never really appreciated BoB/BoB2's 'flight sim within a wargame' approach. But while WoTR provides the conventional squadron-based SP campaign I prefer (available to an extent in BoB2, if you follow the available guidance on workarounds), BoB2 scores in about every other respect - except that the graphics are not quite so modern as (or more dated than) WoTR's. Even just playing BoB2's included set historical missions, though all seem to be air starts, provides a good recreation of the Battle via many of its hightlights, complete with the ability to fly in several of the participating squadrons or Gruppen (including as air gunners in the German bombers), Ground Controllers are on the air, the R/T chatter is great, the AI likewise, and the formations often positively scary. As is taking the role of one of the air gunners in a Do 17 of 9/KG76 in the famous low-level raid on RAF Kenley, one of the historical missions. Anyhow, back on topic. After a re-install, I have BoB2 mostly working in Win 10, complete with the latest 2.13 update from the BoB Development Group and Multiskins - which gives every plane in every unit accurate squadron/gruppe and individual aircraft markings. The problem I was left with was that the game CTD'ed when I quit a mission. Alt+X being the default keys; remapping them didn't help. Likewise, no joy quitting from the 2d map, paused or not, instead of the 3d world. The consensus online seems to be that differences in the way DirectX handled some things in Win 10 was the likely culprit. Win 8 is likewise problematic, and while 7 is apparently fine with BoB2, I'm not going there, having got most all else going on an OS which will be in support a fair bit longer. Today, I seem to have reduced the Alt+X CTDs from 'very common' to 'rare', by applying the settings posted by Buzz3 on Steam, here... https://steamcommunity.com/app/63950/discussions/0/1471968797464997938/ ...except that I have just begun to increase the recommended low-to-medium in-game graphics settings, to see how far up I can push them, while isolating the item or items I can't. 'Quite a way' seems to be the answer. But I fear that over the days ahead I will have the same experience reported by others on A2A who thought and posted that they had found an answer, only to discover they were just having a good patch and that the law of Alt+X averages caught up with them - and the regular CTDs were back. Some seem to have spent ages trying to find the BoB2 Win 10 Holy Grail, in vain, and I've tried anything I can think of that they haven't reported trying. I can live with the dated but serviceable graphics for the sake of BoB2's very considerable superiority over all other comers as a simulation of the Battle. At a push, I will be happy being able to play the many historical missions, interleaved with the numerous training sorties, and accept a rude, debrief-free ending and an inability to play campaigns, if I must. But if anyone has discovered settings which reliably eliminate the Alt+X CTD in Windows 10, I (and likely others!) would be very glad to hear of it!
  9. As regards current preferences, after a while almost exclusively on train sims, I'm back with First Eagles 2 here. Am appreciating the ability to 'warp' to near the mission location, the feeling of flight (and stalling!), the greater air activity, the better representation of AA fire, the light touch squadron management, the excellent dogfight experience, etc etc IE all the reasons I still rate it, on balance and with available mods, quite on a par with RoF and WoFF. FE/FE2 also has a unique vibe from being nowadays so much a product of its modding community, still active and unfettered by commercial considerations such as which planes will sell, and which won't. Not interested in Flying Circus as I have no desire to go beyond, or leave behind, my significant investment in extra flyable RoF planes, for the sake of what to me are relatively modest improvements. Besides which, there are no 'general purpose' two seaters. Now, that's really as bad as a Battle of Britain sim with no bombers, and an unpardonable sin for me. Terrain is at the lowest level (!) in terms of what matters to me, I would like better but am quite ok with the stock FE landscapes, let alone the modded ones.
  10. Thanks Crawford; as I mentioned I think the problem was introduced with Geezer's replacement pilots (like the one seen below, sandwiched between two stock air gunners in the AEG), which all had their shadows set to TRUE. I eliminated the 'shadow rope' when either I set that to FALSE in each new pilot's .ini file, or disabled the new pilots altogether, so the sim defaulted back to the stock ones. The AEGs seen here are at about 10,000 feet because I recently hand-edited most of the default mission height settings in MISSIONCONTROL.INI (as well as dropping the cloudbases a bit, tho I'm not sure if this edit works in FE2 as it reportedly doesn't in SF2), so that I am now getting some missions well above the maximum of about 3,500 feet I usually got before.
  11. VonS, you are a veritable treasure trove of useful tips!
  12. Thanks for the tips, I will seek out your FM mod. Yates's alter ego Cundall is stated to have 'done one hundred and sixty-three jobs, totalling two hundred and forty-eight flying hours' all with 46 on Camels, while Yate's Wiki entry says 110 and 250 respectively; so he (and Cundall!) obviously knew a thing or two about them too, based on service machines. The FE2 Camels I'm flying now all seem to need no more than some right stick at higher revs to counter torque and the tendency to roll left. Don't know if I can vary fuel loads in FE2 (my loadout screen CTDs for some reason I must try to troubleshoot some day) or if the sim models the CoG effects of fuel consumption.
  13. Many thanks Trotski, that was spot on, took a bit of time tracking down all the offending pilot .ini files, but once amended, problem solved! Hi Wrench. These were stock FE2 planes (Camels, Albatros D.V etc). When I temporarily renamed the mods/pilots folder to prob-pilots after reading Trotski's post, the stock pilots were defaulted to and re-appeared, and those shadow ropes disappeared. So I edited the pilot .ini files in the Mods/prob-pilots folder and after restoring the subfolder's name, Geezer's pilots were back less the shadow ropes. Haven't checked every affected plane yet but seems that was the problem. Like I say I do recall seeing it before years back, that probably the problem you are describing.
  14. Anyone know likely causes of this dark line which links my plane to its shadow like a control line model? Seems gone at height but persists around 1000 feet or so. Not visible from every angle but affects multiple plane types, all I have checked so far. Vaguely recall seeing it years ago but can't recall of find anything on it. Only thing I can think of is that have noticed it since changing to Geezer's new pilots, but that is probably just a co-incidence, since I did not notice it playing two new Alb D.III campaigns on the Flanders map.
  15. When I first saw this, I thought it was a poll about planes, and of course, I was about to type 'AW FK8', 'LVG C.V or CVI' and 'Albatros CX or C.XII' followed by 'pretty please', when I saw it was about FMs not planes...oh well... :) Was it Clausewitz who said something to the effect that the enemy usually has three options, of which he will choose the fourth? Applying that principle, I choose the Sopwith Camel :) Not just because it is such an important plane, worthy of the attention, which it is. Because it doesn't seem to match the real Camel that well in one or two important ways. I recently finished reading 'Winged Victory' for the first time (I tend to avoid fiction even such as this) and while written years after the event and only semi-autobiographical, I believe Victor Yates when he describes the Camel as unstable and very tail heavy. Many will have read this before but it's such a lovely description that I cannot resist quoting it here. 'Camels were wonderful fliers when you had got used to them., which took about three months of hard flying. At the end of that time you were either dead, a nervous wreck, or the hell of a pilot and a terror to Huns, who were more unwilling to attack Camels than any other sort of machine except perhaps Bristol Fighters...Huns preferred fighting SEs which were stationary engine scouts more like themselves...They knew where they were with SEs, which obeyed the laws of flight and did as properly stabilised aeroplanes ought to do. If you shot at one, allowing correctly for its speed, you would hit it: it would be going the way it looked as if it were going, following its nose. A Camel might be going sideways or flat-spinning, or going in any direction except straight backwards. A Camel in danger would do the most queer things, you never knew what next...and in the more legitimate matter of vertical turns, nothing in the skies could follow in so tight a circle, so that, theoretically speaking, all you had to do when caught miles from home by dozens of Huns was to go into a vertical bank and keep on turning to the right until the Huns got hungry and went down to their black bread and sauerkraut, or it got dark: the difficulty was that you might run out of petrol and have to shoot them all down on the reserve tank, so that it might be as well to shoot them all down at once, as recommended in patriotic circles.' ...But it was this instability that gave Camels their good qualities...a Camel had to be held in flying position all the time, and was out of it in a flash. It was nose light...and was rigged tail-heavy so that you had to be holding her down all the time. Take your hand off the stick and it would rear right up with a terrific jerk and stand on its tail. The same with the half-roll. Nothing would half-roll like a Camel. A twitch of the stick and flick of the rudder and you were on your back. The nose dropped at once and you pulled out having made a complete reversal of direction in the least possible time." Even allowing that the author is obviously indulging in a certain amount of tongue-in-cheekery, or even an element of hyperbole - and that the better AI pilots in FE can get some wicked turns out of their Camels - the current FMs (strock and Peter01s) don't seem to match the 'out of it [level flight] in a flash' and the 'terrific jerk and stand on its tail' aspects. Not saying I want to spend the stated three months learning how to avoid killing my virtual pilots in the FE/FE2 Camel, but something a bit more like these points in Yates' description might be good - I recall the RoF Camel (like most RoF planes, perhaps more so than others) was very tail-heavy.
×

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..