Leaderboard
Popular Content
Showing most liked content on 01/19/2019 in all areas
-
11 pointsSomething different...a Northrop F-89J Scorpion of the 124th Fighter Interceptor Squadron, Iowa ANG unit based out of Sioux City Airport, circa 1969.
-
6 pointswicked, i just saw some pics of that on FB earlier this evening! mandatory screenie (tho a day late for a throwback)
-
5 points
-
5 pointsPlaying around with the water effects...flooded fields and a bit of train sim
-
4 pointsAgreed. A lot of talented people have made the sim what it is today. Speaking for myself, it's a fun hobby that delivers a lot of satisfaction.
-
3 points
-
2 points
-
2 pointsDefending the convoys again, on Day 2 of the Battle of Britain This was my first mission on 11th July 1940, the day after the RAF traditionally considers that the Battle began. At this stage in the BoB2 RAF campaign, as in the real one, the Navy is still insisting - in the face of some German-supplied evidence to the contrary - that Britannia rules the waves. And that this being so, coastal convoys should carry on, rather than shifting everything they're lugging about onto the already-busy railways. So the principal commitment of Fighter Command at this stage is flying standing patrols to provide air cover, with additional fighter squadrons on standby, ready to scramble if an incoming raid is detected by the Chain Home radar network. This is the balance sheet as of early that morning. From flying 252 sorties, many of which never saw a Hun, we have claimed eleven kills, all of them bombers, against seven Spitfires and one Hurricane definitely lost. Hopefully our over-claim rate is not high, as this is not a great exchange rate. However, having re-started my RAF campaign afresh, I am not so far seeing the very high and hugely imbalanced losses from first time around, possibly down to me messing up saves or something. You can see patrols 'changing shifts' over Convoy Bosom out to the west, while an incoming raid, marked up as Hostile seven zero one, strength sixty plus, has been detected over the French coast. As it happens, this raid's target is Convoy Whiskey, whose circular grey marker you can just about see to the centre right edge of the Review box, in the outer reaches of the Thames Estuary. Following the default Directives which I accepted, controllers soon scrambled four squadrons, a mix of Spits and Hurris, to join the one on patrol over Whiskey. Seventy-Nine Squadron - flying Hurricanes out of Biggin Hill south of London, squadron code NV - was the first to sight the enemy. So when offered, I accepted the chance to fly with them, opting to be Red 2 on the right of the squadron leader. This is me seen from his machine, in NV-B, as we climb gently in four, tight three-plane vics, going north over the coast near a town which might be Allhallows on Sea. I had hoped to be on the edge of the formation but mis-read the layout and ended up smack bang in the middle. Combined with the cloudy conditions, this was to have interesting consequences later. ...to be continued!
-
2 pointsHome, James, and don't spare the horses! Needless to say, I made the best of my Hurricane's turning abilities to get out of the Hun's line of fire! BoB2 gives very good 'shake, rattle (but no roll)' audible stall warning when you're on the edge, so I was able to hold her there quite happily. Another few circles and I was gaining on him. He was faster but I could turn tighter. I was a bit alarmed when a completely different Hun whizzed past. I didn't fancy a sustained low-level dogfight against two or more 109s, especially as there seemed to be no friendly fighters about to come to my aid, this time. So as soon as I was able to put a bit of distance between myself and the 109s, I bravely ran away. Discretion being the better part of valour, he who fights and runs away, and all that. The railway lines in BoB2 can be a bit badly laid in places, and this was one of those places. However, the woods look a lot better with autogen trees turned on, which is a very simple hand edit of your BDG.txt configuration file. And at low level, you can see that the lie of the land is reproduced, even though this is not so readily apparent from higher up. The red low fuel warning lights must have come on in those 109 instrument panels, for they made no effort to pursue me. So I was able to level off and call up Control, asking for my nearest landing ground. I could murder a cup of tea, I thought; no need to wait till I got all the way back to Biggin Hill. To be honest I'm not sure where it was, that got down. I just followed the bearing given, as it was only a few miles away. Compared to our sector airfield, the premises looked a bit on the Spartan side, and the grass field itself seemed a bit small. But I only bounced once, and then I was down and rolling up to the sheds, tapping the brakes with the elevators well up to keep the tail down till the speed came off, and wondering where the officers' mess was. Or even the NAAFI, if all else failed. If nothing else, the mission has got me hauling out the keycard (I have a copy of a 'big box' version of the Rowan original, which includes the old-style printed manual) and the modern BDG soft copy equivalent, which includes some new keystrokes and a tabular explanation of what each does. Not flying as a leader makes life a bit less busy, but there are still some basic skills and sim-specific drills I need to learn, to get the best of my BoB2 experience. Which so far - just in case you haven't noticed - I am finding lives up to the very best I've long heard about Rowan's classic in its A2A Wings of Victory form.
-
2 pointsRepublic P-72C Superbolts - 51º Stormo, Aeronautica Militare, 1948 Skin Credit: Charles
-
2 pointsThe shooting starts! As I approached the enemy, I wished I knew where the others were. I could have asked, but the R/T was silent and I didn't want to advertise my absence from formation. Some of the distant specks ahead started to descend steeply - Stukas! But I was too far away to help whatever it was they were dive bombing. So I kept my height and waded into the bunch who were by now twisting and turning up top,. This lot turned out to be the 109 escorts, who were in an air fight with some Spitfires, possibly from 54 Squadron which I recalled had also been scrambled against this raid. I went for a 109, only to see that he already had a Spit after him. By this point the airwaves were beginning to fill up with radio calls, so I reckoned that Seventy-Nine was in action now too, wherever they were. The skies below and all around me seemed to be filled with aeroplanes doing all kinds of things. It was all very disorienting. Every so often there was the roar of a Merlin as a Spit shot past somewhere, or the harsher whine of a 109's Daimler Benz, sending me into a break while I scanned to see where the beggar was and ideally, avoid being shot down. I latched onto this fellow as he flashed past on the tail of a Spitfire... I tried really hard to shoot the Hun off the Spit's tail, but his shells wacked into the RAF fighter, and down the latter went. I was furious of course and went for the yellow-nosed b*stard like a bat out of hell. However, one of the Spit pilot's mates got there first, and sent the 109 down in flames. Retribution having been meted out, I cleared my tail and got my bearings again, in a gentle spiral climb. I was well out over the Thames Estuary and the skies in my immediate vicinity seemed clear, but there was plenty of action going on. Time to get stuck back in. ...to be continued!
-
2 pointsTally ho! One of the things I have learned since starting seriously playing BoB2 is that if you don't opt to join a flight when it's taking off but instead do so for BoB2's equivalent of an air start, this generally happens at the moment the enemy is sighted. This is the point the leader gives the 'Tally ho!' report to the ground controller in the sector control room who is directing the interception. Anyhow it's a really good idea to pause things as soon as the 3d loads (or enable the setting which does that by default), and orient yourself - height, heading, location, position in formation, and of course, direction, numbers and heading of the enemy. This is where one of the things I hadn't learned bit me - enough keyboard commands. Un-pausing the sim, I tried 'A' to turn on autopilot, so that I could watch what was going on while my alter ego kept my place in the very tight formation - I have friendly collisions turned off but wanted to stay with the chaps. Sadly, in BoB2, 'A' is the quick radio command for 'Break!' Issuing this needlessly literally got me a testy rebuke on the R/T from my leader. Suitably abashed, I edged out of formation but still headed for the enemy, instinctively climbing a bit harder. The others didn't match this and I soon found them falling away below, to port. You can see my empty position in the formation, just to the leader's right. Perhaps because he'd already told me off once, and I was making an effort to re-join, he didn't snap at me again. At this point, the cloudy conditions took a hand. The others started dipping into and out of cloud, and the next thing I knew, I was ahead of them and on a diverging course, before they slipped out of view again. When I emerged into clearer skies, I found I had entirely lost sight of the squadron. By now, I was well out over the Thames Estuary. The town visible below and to port is I think Southend - BoB2 is excellent for VFR-type navigation, when you can actually see the ground of course. And in the map view, while the map itself is like an unlabelled version of the 3d world, you conveniently get your position displayed as so many miles N, S, E or W of some prominent place or landmark. Incidentally both Spit and Hurri in BoB2 feature the B Scheme, the A Scheme having a reversed or mirror image dark green and dark earth 'shadow shading' camouflage pattern. Apparently A was applied to the first aircraft of a given production batch, and B to the next, alternating thereafter. Wings over the Reich has the B Scheme on its Hurricanes but unaccountably gets the port upper wing's pattern wrong, missing a prominent area of dark earth. Having for the time being lost sight of my friends, perhaps I had better check on the whereabouts of my foes, I thought. There they were, just off Southend, a compact mass of dark specks. Instinctively, I steered in their general direction. As I watched, the compact mass expanded then began to break up. Some of the specks broke well off to the left. This all looked rather ominous, like a disturbed octopus spreading out its tentacles. I could feel the tension rising. What was happening? Stukas beginning to make their attacks on unseen targets down below? Their fighter escort, reacting to our presence? As I was soon to find out, what I was seeing was both of these things. ...to be continued!
-
2 pointsWhile taking shots for the Pfalz D3 intro screens, I accidentally caught some nice mood shots.
-
2 pointsCant remember where,but I showed how I make metal textures easily...like so for the P47 all I did was find metal texture images online and cut bits out and paste them in the jpg where the fuselage is mapped,then smooth out joins add panel lines,rivets,dirt wear and tear etc... First image for the Mig was same way bits of images cut etc..top middle bit on F7M is believe it or not metal corrugated roof panels...recoloured to make the nozzle interior texture.. Th fantail image is the same...texture of metal sheet with some lighting effect...usually spray painted in a vector layer.....game does rest with settings to give the polished metal look...and added bump map for theextra details such as dents,rivets etc.
-
1 pointWe all understand that the Me 262 was a superb aircraft at high altitudes. However, its' weak point was on the ground, and taking off and landing. To that end, the Luftwaffe instituted strict dispersal/camouflage procedures on-ground, and also instituted procedures for various piston-engine aircraft to "cover' the take-off/landing of the Me 262s. So, how about a landing/takeoff scenario at an Me 262 base? This would involve the 262s trying to land/take off, the "covering" force of piston engine aircraft, and Allied aircraft attacking the base and landing/taking off 262s. Allied aircraft get bonus points for 262s destroyed, in addition to 'covering' aircraft. Maybe two different scenarios: landing and taking off. I understand that this would be a very demanding scenario, utilizing the in-game AI for purposes for which it was never originally intended. Even so, a question unasked is never answered. Submitted for discussion
-
1 pointPanavia Tornado IS 'Bavandar' - No.28 Squadron, Indian Air Force, 1985
-
1 point
-
1 pointThanks. Again, Crawford was an immense help with researching details for this aircraft.
-
1 pointPlink! Plink! BOOM! Plink! At this point, I thought that maybe it was time to go home, with or without more than a Probable. While I was thinking this, someone else was thinking that perhaps I should do no such thing. My first warning of this was that plinking sound again, as his rounds hit me. Naturally, I did my level best to get out of his way. After a bit of obligatory whirling around at increasingly lower level, I managed to get out of his way so well that I was actually behind him, although quite a long way back. However, any thoughts I might have entertained that this, at last, might be MY 109 were rudely dispelled, when just as I was working my way closer, another Hurricane - possibly that chap from Thirty-Two again - decided that he could do better. Which he could, as it happened. After a few bursts from the other Hurri, the 109 started trailing smoke. Suddenly, the 109 blew up and disappeared into smoke and fragments! Thoughts of going home were put aside, knowing that we - if not necessarily me - seemed now to have the whip hand in this fight. Likely by now, the Huns were short of fuel and needing to make their own way home. I headed back out over the estuary, to where I could see an air fight in which I might be able to make myself useful, rather than leaving others to it. This turned out to be a deuced clever move, if I say so myself. I managed to do the sneaking up this time, catching an unsuspecting 109 and removing his port outer wing. He rolled left and fell like a stone right after this picture was taken. You'll do me! Looking around for any further trade, all I could see was a pretty serious ack ack barrage, quite a long way up and drifting away to the south. I thought of trying to get up to it, but at last decided that honour had been satisfied. So I headed home, back to base. Below me you can see the Naval dockyard at Sheerness, one of many historical sites and targets recreated in BoB2 and refined by BDG. And here's a view of the BoB2 map, zoomed in. I think the yellow line is pointing to the south-east and not south west towards my base at Biggin Hill, where I'm now heading, is because a programmed waypoint I have not flown to lies in that direction. BoB2's Sheerness, realistically, has its very own balloon barrage, which may be why the Stukas haven't paid it a visit. Anyhow, the skies down here look clear now, so I hold my course for home. The 109 you can see in the next pic curving in from below and behind had other plans for me, however. I woke up to this when I heard that plinking sound again, of bullets striking airframe! ...to be continued!
-
1 pointPlease sir, can I have one? Looking up, I saw another group of specks wheeling and falling from the sky, one somewhat ahead of the others. Stukas diving, maybe? But there was no ack ack. Friendly fighters chasing a Hun? Huns chasing one of ours? Having failed to save the Spit earlier, I wasn't going to wait until it was too late, to find out if a friend needed help, even though I wasn't conscious of somebody calling for it - which they do, in BoB2. Those aircraft seemed to drop like hail and as I tried to work out what I was flying into, the 'flying' bit nearly came unstuck. I suddenly realised I was diving steeply and the water was rushing up to meet me. I managed to pull out but lost track of the other aircraft. Instead, I now saw more specks at sea level, with another layer above, or perhaps further away. It took my brain a second or two to resolve what I was seeing. This was Convoy Whiskey, apparently at anchor. Of more immediate concern, a 109 was racing in from my left, skimming the wave tops. Here we go again! I tried to pick him up, but lost track of him as he slipped underneath me somewhere. Up ahead, a lot seemed to be happening - circles of white water where planes had gone in, others falling trailing smoke, and more specks, planes or AA fire I could not tell, further up ahead. I could have identified the planes by turning on labels, but I hate to clutter the virtual skies with the little beggars, and in BoB2, I find I can manage without them somewhat better than in IL-2, for example. Even if it leaves the element of confusion, that can help create the tension of uncertainly, that you're in a untidy air fight not playing a video game. Tracers off to my left revealed two 109s shooting up a Spitfire, which like the first one, went down before I could intervene! The 109s cut across me at an acute angle. Of course I went for them, but pulled up hard in a panic when something plinked noisily into my airframe. The 109, for of course that's what it was, had the cheek to come up after me. You can see on the bottom the text of an R/T message heard at that moment - Silvo squadron is us, so this is Blue Section's leader, stating the fairly obvious. How I got out of his way I have no idea, but I did, and then chased after another 109 that had yet another hapless Spitfire in his sights. This time I shot him off the Spit's tail. I should have knocked him down, too, but I was so keen to get a picture as my rounds delivered the coup de grace that I missed and overshot, leading to this interesting situation. More through luck than judgement I had rolled the same way as he did and I got onto him again. There was no visible sign of it but I fancy I had damaged him, which will have helped. Smoke and flames belched from the Messerschmitt. Got him! Or had I? At the last minute I'd noticed yellow tracers passing close to me and flying into the 109, as well as my own. Sure enough, I wasn't alone. Looks like I'll be sharing this kill. You can see that the other Hurricane is from a different squadron, no under wing roundels and code GZ - that'll be 32 Squadron. Oh well, this is a team game and they all count. Still, I do wish that, having gone to all this trouble, I'd got a 109 of my own. I'll need something to placate the boss when he tears strips of me back at base, for deserting my post. My chance would come soon enough. ...to be continued!
-
1 pointThis game has morphed into something very wonderful. To me, it always had great, and quickly accessible, gameplay. Now, it has developed a graphic beauty that rivals any of its competitors. People that know these things better than me suggest that the flight models rival much more modern attempts and that the AI is second to none. It's a great cooperative achievement between its original developer and its users. Untalented people like me can only say thanks.
-
1 pointLittle trick with max 2009 on windows 10...if it crashes a lot.....copy the max2009.exe and run from the copy shortcut....wont crash dont ask me why...lol you still having vertex animation problem?...I use it a lot and it can be a pain...when you map a part thats got animated vertices,animation will vanish no idea why...always edit \map before you animate vertices.
-
1 point@warthog64 I am in the possess of doing a full data file overhaul for the Falklands and the YAP Rising Sun ship data files. Falklands 82 ships should come first. Also that seems too weak for a US carrier due to US damage control.
-
1 pointTested the latest set of files for the Caudron R11, but the gunners didn't track targets, let alone fire at them. So, until I look through my backups for the earlier files - which DID track/fire at targets - I'm working on the Berg D1 and Bleriot 11. Crawford: Thanks for the research photos - they were a BIG help with the control wire pulleys!
-
1 point
-
1 pointAn old thread now but for anyone dropping by I just want to update my earlier lukewarm comments. Now that I have a system that can play BoB2 + BDG patch 2.13 acceptably at or near near max settings, and the patience to try the wargame side (if only so far as to generate dynamic missions I can choose to fly) I'm a true BoB2 believer, fickle or not. The scope of the air action dwarfs CloD and WoTR and is the only one I've seen that recreates this acceptably (not even modded EAW was close), the depth and accuracy with which history is recreated is unlikely ever to be equalled let alone exceeded (both as regards aircraft markings and ground object/terrain details); the amount of content (flyables and missions) is very high; and the air combat AI is superb. And with autogen trees enabled and other settings higher including terrain tile shimmer fixed, the landscapes look a lot better than in the screenies in my original post.
-
1 pointFor those who aren't following me, here's some recent operational testing. I've found to deal with just one Udaloy - just one - you have to have two brackets of four F-2As fire ASM-2s:
-
1 point
Version 1.2
316 downloads
From Veltro2K's Cargo Planes... All FM ini files are mostly the same... All credits to the original creators in the original readme (below)...I just polished it... v.1.0 New\Updated 4096x skins, Actual Decals & B52 Cockpit... Added 1920x Hangar, Loading & Loadout Screens... Actual Serial Numbers, Randomized... New sounds... v.1.1 Converted Command Wing emblems to lo-viz as pointed out by daddyairplanes - Thanks! Original skins with color emblems are optional in the "Extra" Folder... Fixed the wingtip NAV light positions... Reduced the size of the US AIR FORCE markings Moved the side door and emblems... Fixed loadout - has Jeeps and Pallets in the cargo hold... Used one tail decal from daddyairplanes Euro C-5A Galaxy (for his ecellent work see below)... * Please note - The INI files may be different, so you will get the INI files from the last pack you install. v.1.2 Added White over Gray MAC C-5A... Converted some skin markings to decals... ------------------------------------------------------------- Installation: ------------------------------------------------------------- >>> Please backup and delete in your mod folders: "C-5A" in \Objects\Aircraft and \Objects\Decals folders...or don't know what will happen... Copy the contents of the uncompressed "To_Mod_Folder" folder into your Saved Game mod folder. Overwrite any conflicts... Enjoy! Viper 01/18/2019 ------------------------------------------------------------- Original Readmes: ------------------------------------------------------------- SF2 USAF/NATO/Western Cargo Planes by Veltro2K 3/20/2013 -For SF2, Any and All- This is a re-release of these aircraft, as some have stated a desire to have them again. This pak includes all my reskins, decals, ini tweeks from the various "upgrade paks" I'd released before the aircraft were disappeared. This pak contains =ONLY= those aircraft used by the USAF, our Allies and other NATO powers. The Soviet/Warsaw Pact transports are someplace else.... Included in this pack are: C-141A Starlifer C-141B Starlifter C-5A Galaxy C-17 Globemaster III G-222 Spartan (called such in USAF service) Some may be more complete than others, with regards to decals and such. Some are fairly 'untouched', and will need further decaling, etc. Some hangar and loading screens are NOT in SF2 format, and will need redoing (meaning: I never got around to them!). All the original readmes from the Upgrade Paks (I could find!) are included within this main folder. I'd reccomend reading them, just for fun! Skin and some decal templates (again, when I could find them!) are included. The decal template is for the "ttag" decal, that is for USAF AMC usage. This pak is quite large, as the skins remain in their bmp format. You can convert to jpg at you convience. As always, fairly easy to follow, yet detailed install instructions are included. PLEASE read them!!! PLEASE read the "Notes" section for other important notations. Also, the Legal Statement has been changed with regards to this aircraft. For those that still have the original releases, you may not need to reapply this package. But, to be safe, PLEASE check over your aircraft to be sure. Thank You :). **These aircraft herein are released in "AS IS" Condition. There are/may be some issues with the LOD that may not/cannot be resolved. Period. Any and all issues/problems that cannot be solved via ini edits will exist forever, as new models are unlikely to be created. For now.** ------------------------------------------------ =TO INSTALL: As I always reccomend, unzip the "sf2_veltro2k_cargoplanes_pak.zip" to a temp folder or your desktop or somewhere else that's easy to find Then, simply, copy/paste the Objects folder supplied directly =OVER= your existing /Objects folder. Copy/Paste the supplied Sounds folder directly OVER your existing /Sounds folder You'll probably be asked "OVERWRITE?", just say Yes. I've already seperated out the various folders (Aircraft, Decals, etc), so they'll drop right where they're supposed to be. ---------------------------- Notes: Again, as these are considered "heavies", they are best left under AI control, even though they all have cockpits. What can be done with them, I've not too many clues...however, with the SF2 mission builder, they can be inserted into campaigns, single missions and a host of other opportunities that present themselves. Use you imagination. If there is a HUGE hugh and cry, perhaps I can be moved to locate all the Soviet transports Veltro did....if I can find where I put them! --------------------------------------------------------------------------------- Credits: Veltro2K for the aircraft me for varioius and sundry other stuff StephanP for the C-17 chaff/flare tweek Dels, iirc, for the c130 engine sound Sources: see the enclosed original readmes seriously --------------------------------------------------------------------------------- If you have any problems, questions, comments, I can be reached in the usual places; CombatAce, SimHQ, or via the email addy below. Happy Hunting! Wrench Kevin Stein kjstein@ca.rr.com -------------------------------------------- Legal BS: This is freeware, with limited/controled re-release; it CANNOT be redistrubuted, or posted on other sites even if the original readmes and all other pieces of the package remain intact. The names of all contributors, modders, suppliers, etc =MUST= be listed in any new readmes. This package may NOT in any way, shape or form be used in any payware additions. Bribes are accepted; ask for the day's going rates... ------------------------------------------- SF2 Upgrade Pack For Western Transports, Airliners and AWACs by Veltro2K 6/1/2018 = For SF2, Any/All (Full 5 Merged RECCOMENDED!) = This is a remod pack for Veltro2k's Western/NATO Transport, Airliner and AWAC aircraft. This package =ONLY= contains the data inis for the aircraft listed below. You will still need to locate the original aircraft. It is highly suggested (read: REQUIRED) that you have SF2NA as part of your merged installs, as several of these reference the stock 3W Tu-95 Bear destroyed model. Some reference the stock 3W An-12, Tu-16 or B-52D (SF2V) destroyed models as well. Flight Models remain "as issued"; they've not been touched by me. All New Data Inis Included in this pack are for: C-5A Galaxy C-17 Globemaster II C-141A Starlifter C-141B Starlifter G-222/C-27 Spartan E-767 KC-767 (KC-46) Nimrod MR.1 (RAF ASW/Martime Patrol) Br.1150 Atlantique (ASW/Martime Patrol) PB-1W Navy Fortress (USN 1940s/50s AEW - B-17) DC-8 * B-747 Pan Am"Jumbo Jet" *The DC-8 mods are for the package by Daddyairplanes* All aircraft have had their data inis reworked to correct, add, move, remove or generally "fix" all the hit boxes, relocate components (ie: fuel tanks, as best as possible inside the airframe) and in general clean up many things that simply escaped notice. The exception here is the Pan Am 747, which gets a partly repainted skin, with all new 100% accurate civil registration number decals (18) AND their matching "Clipper" names. Decal Randomization is "TRUE". The 747 and DC-8s also get an avionics upgrade (GM radar). Some sounds are included; you may have them alread, or not; but I like "to be sure". Please note, some of these aircraft may NOT be in the SF2 downloads section; one will need to Search the SF1/Wo* (1stGen) downloads. Equally important, is to HAVE the aircraft installed =BEFORE= installing this Upgrade Pack. Kinda makes sense, right? <gr> As is always reccomended, unzip to a temp folder or your desktop to give easy access to the rest of this readme for it's install instructions. Happy Landings! Wrench Kevin Stein ========== To Install: Another reminder: ****HAVE THE AIRCRAFT INSTALLED TO YOUR SF2 MODS FOLDER OF CHOICE =BEFORE= INTALLING THE UPDATE/UPGRADE PACKAGE.**** As always reccomended, unzip the "sf2_v2k_western_heavies_upgrade_pak" to a temp folder or your desktop or somewhere that's easy to find. Copy/Paste the /Objects folder DIRECTLY into the SF2 game install of choice's /Objects folder. It's already divided into the /Aircraft and /Decals sub-folders. You'll asked to "Overwrite?" , just say yes. It'll change nothing. Copy/Paste the included /Sounds folder DIRECTLY over you existing Sounds folder. Allow the "Overwrite". I've included sounds you may already have, but wanted to be sure that (nearly) everything was available to the End User (tm). That should cover it, go fly! ----------------------------- Credits: Veltro2k for the aircraft themselves MUE for the Lod viewer Me, for taking on the job. TMF for the destroyed 707, used with the DC-8s Sources: see original readmes ------------ Other Notes and Nonsense: Included are the original Data inis, already backed up, in case you End Users (tm) don't appriciate all the hard work that goes into creating, giving, and keeping up the Mods we do. Remember, these mostly exist for "Eye Candy" and Targets (tm), but I felt it was well worth the effort to try and correct the hit boxes. Also, remember they're really not to be Player Usable, even with cockpit, as the Game Engine has no coding for their proper usage. But, have fun anyway! A note about the destroyed model usage: While not 100%, we work with what we have, after all, it's just a burning, dead wreck on the ground. If a 3d Modeler (tm) wants to build crashed birds; go for it, I says! I know the "Clipper **" name decals are in the wrong font, but after spending an hour and half trying to FIND the correct one, just chose to use one of my script fonts. Deal with it <g>. At present, there are NO plans whatsoever to update the individual aircraft packages. End Users are on their own to locate the aircraft in the CombatAce downloads sections and apply this fix-it pack. --------------------------- If you have any problems, questions, comments, I can be reached in the usual places; CombatAce, SimHQ, or p0rn sites. Happy Hunting! Wrench Kevin Stein -------------------------------------------- Legal BS: All the aicraft herein remain the intellectual property of their respective Manufactures, Design Bureaus and Veltro2k This is freeware, it =CAN= be redistrubuted, or but =NOT= posted on other sites even if the original readmes and all other pieces of the package remain intact. The names of all contributors, modders, suppliers, etc =MUST= be listed in any new readmes. This package may =NOT= in any way, shape or form be used in any payware additions. Bribes are accepted; ask for the day's going rates... ------------------------------------------- ========== -
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 pointFor those who may be interested in the classic 1930s aircraft of the Sino-Japanese war of 1937-45, below are a few more WIPs to supplement the Chinese CR32. WIP Nakajima A4N.rar WIP Yokosuka B4Y.rar WIP Northrop 2E.rar
-
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..