Leaderboard

in another thread, there was some discussion on decals. you know, you can have quite a bit of fun with them. things that folks never even notice, because they're in plane sight. I do this a LOT. Example below

that is what i found out when i try to get the TISEO working , for air to ground missions it can be a big help especially when you going to use the gun , it works very limited on air to air mission because the TISEO is not locking on to a target and to hold a moving target in the scope is not easy F-4E_78 with TISEO

GHOST

Spitfire over London Docks

well arent you just the little sarcastic Easter Bunny mandatory screenie, or as said on FB, MiG killer

Sunday night folks, whats your choice of music hard blues or smooth jazz?

estos últimos días regrese al tedioso trabajo de textura y cargar algunos azulejos de las islas, es un trabajo aburrido muy lento y con muchas pruebas y errores pero el resultado es muy bueno, acá algunas imágenes, pero todavía tengo mucho tiempo para terminarlo.

today update.

https://www.sas1946.com/main/index.php/topic,66864.0.html

ANATOLIAN EAGLE 2021

completed the Vickers gun 4.5 inch main gun

Silence is golden. If only hip hop/rap had been invented in those days and relegated rightly to the garbage bin before sound became a thing. Sorry, I'm off topic (again) and showing my age (again).

Hello again fellow FE2-ers, Please find included below some of the latest developmental pics. from the Bleriot XI (6-cyl. Anzani powered). Swambast has been doing magnificent and detailed work on the 3D model. He is currently busy with other duties, and I will be taking a modding break during the summer - but we hope to collaborate further on the Bleriot XI over the next few months and eventually to get to the stage where I can apply an already-tested FM to this particular model. Will post here again in a few months once more things are completed. For the most part, the external model is now largely complete - we still need to look over and complete the rigging/warping wires for the wings, also some details regarding the wheel assembly - and to look over details for the cockpit (both for internal and external cockpit views). Then the FM-application stage will follow. Eventually, we hope to have a completed model ready, which our excellent skinners can as well have fun with once it is released. Cheers all and happy flying, Von S

Bender ?

more Mod

Dropped into the 'customs' area around Tarkov. Right from the start you are on edge... no idea where the enemy may be. Scav Raiders are loose in the area and are already picking people off. You have to find an exit point, you have no compass, no waypoints to follow, scavenge or loot anything you can as you try to find a way out. Tension is high along with a deadly threat that can kill you at any moment... Can I make it out? This is Escape from Tarkov... at times brilliant, challenging, yet frustrating and will have you on edge from the minute you start your raid. I'm new to the game, still not sure what I'm doing, using a downloaded map from the internet to try and navigate myself to an extraction point which is always at the other end of the map from where you started. No compass, no waypoints, when you look at your map you are vulnerable. When you are searching a body or equipment you can be picked off at any minute... If you are giving yourself first aid it takes time, and again you are extremely vulnerable. This is no run and gun shooter... be prepared to be killed, a lot! The odds are always against you, and yet, I keep coming back for more punishment... Have to say though, applying first aid during a fight is usually where I get killed, as there is no quick fix when you are wounded. Searching a body takes time, going through pockets and equipment, examining items to see if they are worth taking... all the time you are in constant danger of being surprised and killed.

Another mission from my current Fokker DVII campaign. In which our hero Randers and his schwarm encounter some French 2-seaters. He shoots one down, then turns to deal with the SPAD XIII which has been attacking him. However, he soon realizes that his radiator is holed and that another SPAD has joined the fight. He then disengages by diving through a handy layer of cloud.

well complex shape vs regular shape does seem reasonable. still very odd, but as noted before problem solved by shifting tga location. might be showing up inside the model (have seen that plenty too over the years, esp. on transports) but anyone zooming that far in to see the inner walls of the model gets a bucket of rivets and yes, its the C-141B thank you for the input logan!

In late 1972 President Richard Nixon was facing the prospect of having the funding cut for Vietnam by congress, so took one last gamble before they could reconvene to get North and South Vietnam to terms and pull the US out of the war with its POW's. This gamble would involve for the first time large B-52 raids on actual strategic targets in North Vietnam including Hanoi and Haiphong. Now having better relations with the Soviets and Chinese the gloves were off and he duly instructed Strategic Air command ( SAC) to sort it out……. unfortunately it didn’t quite roll down the chain far enough. What ended up as a relatively short eleven-day campaign, started out and was planned for three days and those first days are really the focus of this article due to some rather strange tactics. Surprise attack All B-52 sorties were launched either from the Pacific island of Guam at Anderson AFB or U-Tapao RTAFB (Thailand), with Guam having a very long flight time to target requiring A-A refueling for the B-52Ds. The B-52s were to take off from Guam and fly right over a Soviet spy trawler sitting in international waters of the end of the runway. As the B-52 raid got closer to North Vietnam they would test all their ECM gear handily notifying the SAM operators of the frequencies being used in advance. As they neared the target the F-4 Chaff bombers would fly in front of the raid and drop chaff to provide a protective chaff corridor that the B-52s would fly through giving extra protection. However it seems that not only did the chaff present a big arrow pointing to the intended target on the Vietnamese radar scopes it then promptly blew away in the very high winds providing next to no real protection. On top of that as planned for the first three nights the B-52 waves (three waves per night) were to follow the same route as F-105s had done since 1967 and fly over the targets in level flight (to a determined point) at the same altitudes, speed, heading and times…………with a nice long pause between each wave. General Melchett: Field Marshal Haig has formulated a brilliant new tactical plan to ensure final victory in the field. Captain Blackadder: Ah. Would this brilliant plan involve us climbing out of our trenches, and walking very slowly towards the enemy? Captain Darling: How could you possibly know that Blackadder? It's classified information! Captain Blackadder: It's the same plan that we used last time..........and the seventeen times before that. General Melchett: Exactly! And that is what is so brilliant about it! It will catch the watchful Hun totally off guard! Doing precisely what we've done eighteen times before is exactly the last thing they'll expect us to do this time! There is, however, one small problem. Captain Blackadder: That everyone always gets slaughtered in the first ten seconds. General Melchett: That's right. And Field Marshal Haig is worried this may be depressing the men a tad. So, he's looking for a way to cheer them up. Captain Blackadder: Well, his resignation and suicide seems the obvious choice. General Melchett: Hmm, interesting thought. Make a note of it, Darling. (from Blackadder Goes Forth BBC) Unsurprisingly the B-52 crews, although very pleased to be finally doing something to end the war knew the tactics were dumb with comments including “like Ducks in a shooting Gallery” and “I knew it would be a turkeyshoot….....for those on the ground”. The idea of flying in level flight was to maintain Jamming integrity for the B-52 cells, also because the antenna need to be pointing down to provide the jamming coverage, thus if you turn no more protection. On the first nights some of the B-52 pilots did indeed try to outmanoeuvre upcoming SAM's not completely trusting the Jamming [and a B-52 can certainly turn at 30,000ft]. This lead to some threats of court martial for any pilot that did jeopardize cell integrity by turning (for certain waves). The threat of Court Martial reported by all sources doesn’t seem to account for the contradictory fact that the pilots were ordered to perform a Post Target Turn after dropping the payload. This meant they would turn directly over the worse concentration of SAM sites over Hanoi with no jamming protection and into the Jet Stream winds keeping them in the lethal SAM radius a lot longer. This Post Target Turn was not only unnecessary but was essentially a big cause of some of the losses. B-52s at Anderson AFB Guam December 1972 (USAF) Night One 18/19 December As an example of a raid the first night strike consisted of three waves of 129 B-52s (three waves of 48, 30 and 51). This is a breakdown of Wave One only. The Vietnamese defenders The Vietnamese were not expecting or geared up for a strategic bombing campaign of this scale, they had sent personnel and sites down to South North Vietnam and now had to recall them and everyone else on leave. The main problem was they were short of assembled SA-2B missiles. Each site (Battalion) only held six on launchers and six more on trucks in reserve. Once a truck had loaded one on the launcher it had to go to a depot and collect another, however you now had queues of trucks waiting for missiles – they could only assemble 40 per day. Luckily the pause between waves helped them somewhat. [The only way the USAF could have helped the Vietnamese more by this point was to drop fully assembled SA-2s on parachutes!! ] Even though on night one they had managed to down three B-52s (two others damaged), by Night two they had noticed the obvious use of the same tactics but were not able to capitalize on them straight away. They would launch the SA-2s unguided and when the B-52s did the Post Target Turn they would lock on and the SAM would guide in. This was not as easy as it sounds and needed practice, so they didn’t manage to down any B-52s on night two (only damaging two). From the US point of view, it seems no loss had vindicated SACs tactics, however when the Vietnamese got their tactics worked out on night three six B-52s were shot down (one other damaged) in only two waves (Second wave was cancelled by the head of SAC General Meyer after the losses in the first - but the third Wave was pushed ahead to "save face"). Some US sources seem to indicate they thought the Vietnamese had different SAMs (SA-3) but they only actually had SA-2Bs – the US were just clearly underestimating them if that was the case. B-52 window damaged from SA-2 fragments (USAF) Where did this cunning plan come from? SAC was running the show from their HQ and were very much for centralized planning - unfortunately they were detached from reality and were too arrogant to know it. WW II & Korea fighter Ace General John C Meyer was in charge and had been accused of being hesitant to make decisions by the lower Generals. [Well most would be hesitant if their expertise lay in fighters]: Richard Baughn flew as a fighter pilot in World War II and then went on to command a SAC bomber unit as a brigadier General, and recalled feeling out of place in SAC due to the mindsets driven by different cultures. “You just feel like a third shoe, a third foot” and he believed that “if a SAC guy came to a TAC base, he would probably feel the same way.” From a common base in pilot and navigator training, the major commands imprinted different approaches to their unique missions and aircraft. In the words of Baughn, “Bomber pilots and fighter pilots are two different types. Always have been. They think differently and act differently.” It was these same lower Generals who were responsible for the planning of Linebacker II - in particular General Peter Sianis. With his WW II and Korean War experience of Strategic bombing and no experience of a modern IADS he was definitely the person you wanted in charge of this [NOT]. According to Colonel Frederick J. Miranda, SAC’s logistics representative on the planning staff, General Sianis saw the map prepared by staff officers that showed routes of flight for the operation, with “several different routes leading to Hanoi.” Miranda related what next occurred: General Sianis walked out of his inner office, took a look at the map, and said, “That’s not the way we do it!” Then he removed the colored tape showing the Andersen B-52 routing from the map and rerouted that bomber stream to a route over South Vietnam into Laos and forming up with the U-Tapao bomber stream. He also changed the post-target exit routing to one requiring all aircraft to make a right turn after dropping bombs and stated, “One way in and one way out!” He then instructed his staff to go make those changes and come back with the briefing. I will never forget how the map looked after General Sianis made changes. The colored tape was hanging loosely and the general made a comment, “You guys probably have a lot of tape, don’t you?” This was a significant last-minute change resulting in replanning, additional poststrike refueling, and the now infamous “post-target turn.” He essentially took the planning function away from the majors and lieutenant colonels and straitjacketed them with the “one way in, one way out” directive. No one questioned the SAC DCS/Operations. [Doh!] The Post Target Turn is something required when delivering Nuclear bombs to avoid the blast, its inclusion at a time when Nuclear bombing was low level single ship is not really explained or justified anywhere. B-52G-125-BW (59-2582) awaiting at Anderson AFB Guam to take off on 18 December 1972 (USAF) Jamming The Electronic Warfare experts at SAC were confident that by maintaining cell integrity the B-52s would be fully protected against the SAMs, a cell was supposed to be three B-52s but sometimes a cell would include only two bombers and sometimes the cells would have degraded or failed ECM equipment due to the no abort maximum effort policy. Although SAC at the time thought the unmodified Jammers on the newer B-52Gs were the cause of some of the losses (and stopped Gs flying over Hanoi) it wasn’t the full story because they were also using the wrong type of jamming. North Vietnam was using an SA-2B SAM that was modified by the Soviets [supplied in 1971] to prevent Beacon jamming after analyzing an QRC-160-8 (ALQ-87) ECM pod found in the jungle. In the late 1960s this type of jamming had rendered the SA-2 all but useless by jamming its uplink command guidance. Now fair enough, how were the SAC EW experts to know this?……………..well they could have read reports from the US Seventh Air Force on the matter who had been aware this SAM was in use and had been reporting on it for the past year. Or they could also have tested the B-52 jammers against the modified SA-2B they had captured and was sitting in Eglin AFB! In fact it wasn’t until during Linebacker II and after the losses of the first 4 days they started testing that they confirmed that the Post Target Turn removed all jamming and the beacon jamming was not effective. B-52Ds preparing to take off for another Linebacker II mission (USAF) Aftermath Although no plan is said to survive contact with the enemy it doesn’t help when you have centralized planning and control by people that simply do not know what they are doing from the start. SAC eventually handed the planning down the 8th Air Force and with many other tactical changes things never got anywhere near as bad as Night three had been - by nights 10/11 the resistance from Hanoi had become almost irrelevant to the point they could freely fly over it. Overall Linebacker II ended up achieving Nixons objectives and the gamble paid off for him with the peace treaty being signed in January 1973. However for the B-52 flyers as always it was a very different war and by 1973 some had clearly had enough of Meyers management policies: [note B-52 Arc Light & Bullet Shot operations continued until August 1973] On January 3, those crewmembers not flying assembled in the Arc Light Center briefing room, where they first watched Meyer pin the Air Force Cross on Colonel McCarthy, who had flown two missions during the operation. Meyer then addressed the Airmen in the audience, and his message was blunt. The general elaborated on the need for cell integrity in the missions over North Vietnam, remarking that tight formations provided the greatest chance to thwart the SAM threat by using the combined jamming capability of three bombers to defeat the data-links guiding the missiles. He then stated that aircraft commanders were not to maneuver during the bomb run and repeated the court-martial threat that they had previously received at the start of Linebacker II. At that moment, the briefing room became totally silent—all whispered conversations stopped, the normal coughing that typically comes from any audience halted, and no one moved. Then, suddenly, roughly half the Airmen in attendance stood up and walked out, “like a herd of cattle,” John Allen remembered. Many of those were chagrined that McCarthy had flown only two missions, plus that he had done so from the jump-seat of G model aircraft, though qualified only in D models. Allen described what came next: Of the roughly 200 that remained, 75 to 80 people just went crazy. They picked up whatever was nearby and threw it at the stage—flight computers, briefing books, Coke cans, folding chairs, you name it. It was like if you had ever been to a burlesque house, where they’d throw tomatoes and apples at a bad act, it was just like that. It couldn’t have lasted more than 13 seconds, the assault, but [Meyer] got hit a bunch of times. I saw a Coke can bounce right off his head. I was just frozen in my tracks—I couldn’t do anything—it was mob action. He went down on a knee, and a bevy of colonels picked him up and helped him off stage. Meanwhile, the guys jumped up on stage and physically chased him down to the flight line. There were a bunch of guys running after him, including the guys that were “gone” and the others of us that just wanted to see what would happen. He was in his staff car, heading toward his airplane, a shiny silver and white VC-135. They chased him down to where they now have the B-52 [Arc Light Memorial] up on a pedestal. They ran down and they threw chunks of gravel that were next to the road, just pelting his staff car and the power cart [used to start engines],and continued to pelt him as he went up the ramp. Then off he went and we never heard anything more from CINC [commander in chief] SAC. Crews in briefing at Anderson AFB December 1972 (USAF) Sources and Further Reading To Fly and Fight: The experience of American airmen in Southeast Asia (Andrews WF, 2011) , George Mason University The 11 Days of Christmas (Michel III ML, 2002) Encounter Books Linebacker II: A View from the Rock (McCarthy JR & Rayfield RE, 1976), Office of Air Force History Maxwell AFB War From Above The Clouds (Head WP, 2002) Air Force Press Maxwell AFB Patterns and Predictability: The Soviet evaluation of operation Linebacker II (Drenkowski D & Grau LW ) Fifty Shades of Friction: Combat Climate, B-52 Crews, and the Vietnam War (Clodfelter M, 2016) National Defense University Press F-105 Wild Weasel vs SA-2 “Guideline” SAM Vietnam 1963-73 (Davies.P, 2011) Osprey Publishing The Red SAM: The SA-2 guideline Anti-Aircraft Missile (Zaloga SJ, 2007) Osprey Publishing B-52 Stratofortress units in combat 1955 to 1973 (Lake, J 2004) Osprey Publishing Quote from Blackadder Goes Forth (BBC, 1989) Title photo B-52D-65-BO s/n 55-110 weapons loading (USAF)

Thank you so much for the detailed updates. I’ll patiently wait months but updates like this really make it easier.

Dear Pilots, Summer is here and it’s very hot in both Moscow and Las Vegas, but we soldier on still working mostly from our flats and homes. This week’s DD features just a couple items, but one is quite a surprise as you will see. But first, let’s admire the upcoming 4K skins made by our steadfast ally and partner Martin “ICDP” Catney. The ugly duckling has become a swan with these new textures wouldn’t you say? With the new skins for the Hs-129, we are rapidly closing in on ALL planes in Great Battles being upgraded to the 4K standard. The Yak-1b should be next and eventually the Ju-52 will also get a refresh. The entire 4K upgrade has been a huge effort on Martin’s part as well as the previous contributions made by Francisco “BlackHellHound” Bindraban. Please join me in thanking them for their awesome contributions! A shining example of talented community members helping the developers and an effective international partnership. And now a surprise that came about very recently, but one that has a its roots in Rise of Flight history and one that should end in a positive result for Sturmovik. Today, we share extremely early WIP shots of an important fighter design that saw action against both Soviet and American air forces and late in the war, alongside them. Can you guess what plane it is? There are very few types that have this distinction. Hide contents That’s right, the Romanian designed and built IAR-80/81 is under development by a third party that we feel has the skills to make it a reality. This will take some time, but we are confident it will come to fruition. Please enjoy this little tease and when we the mesh is further along, we will offer it for pre-order as we always do. Why the IAR-80/81 exactly? Well, believe it or not, there is a lot of good reference information on this plane, so it is one that is possible to build by a single qualified modeler. A lot of what we do as a sim developer, can be described as the “art of the possible”. The IAR is indeed possible to make, so let's do it. And it’s a nice departure from our usual plane-set and is often overlooked in the history books. It will be sold as a Collector Plane, but it will certainly add some more historical flavor to the Battle of Stalingrad theater. There are some other planes we are working looking into finding a way to make. Your continued financial support is most important when we try to make new aircraft. And we continue to work on the new AQM feature, fuel systems with drop tanks, Air Marshal and even improved cloud technology. All of which I hope to show you pictures of in upcoming Developer Diaries. And Jason continues to work with talented mission makers on new mission content and Campaigns which we hope to have localized and released soon. On a serious note, the pandemic really slowed us down as we are prevented from being on our office and seeing each other face to face. Working from home is not always ideal for a collaborative effort like developing Sturmovik, but we continue to do our best and fill irritating personnel needs as soon as we can. We had hoped 2021 would bring a quick return to normalcy for us, but sadly it has brought a whole new set of challenges for us as a team beyond the usual technical ones as the pandemic sticks around. So please have patience with us and know that the team is doing their very best under less-than-ideal circumstances. See you in the skies and on the battlefield! The Sturmovik Team

I was thrilled when OBD announced they would do BoB precisely because of the above statement.

On your first pic without the patch.tga you would have 3 decals of the same type like you can see on the 3rd. The reason you can only see 2 because the patch.tga did work, but it is set for =bottom. I assume that the Left/right side tga-s show up because that matches more the parameter of the mesh/decalfacing call out and the game just overrides the other one. I think the location of the decal and complex shape of the f15 fuselage behaves a bit different compared to the round C141 (I guess that is that bird). In the 2nd pic the area marked with yellow is due to the mesh curvature is behind the other mesh section from looking from the bottom, so the patch decal would probably not "cover" that.

PZL-230F 'Skorpion' - Parani Air Force, 2006 Started in the mid-1980's the PZL-230 'Skorpion Projekt' was an ambitious attempt to provide the Polish Air Force with an affordable modern attack aircraft but in 1990 the Polish Air Force cranked in further requirements for speed, range and payload leading to a heavier and ultimately more expensive aircraft. By 1991 Poland was enduring a difficult transition from a communist to a capitalist economy and the project appeared to be heading for cancellation but the management team at PZL Okęcie were convinced that a sizeable market existed for the 'Skorpion Projekt' and actively sought a partner to develop their design eventually approaching several aerospace companies in Europe, the US and former USSR but to no avail. However, in January 1992 representatives from the state-owned Parani Aviation Company (PAC - who had developed the indigenous Piranha jet fighter in the late 1950's) contacted PZL to propose a collaboration to develop and produce the Skorpion for their respective air forces and for export. At an early stage it was agreed to have two assembly lines with PZL to be responsible for all Polish orders and subsequent European exports and PAC to be responsible for all Parani orders and all exports outside of Europe. It is understood that Paran agreed to accept a higher split on development costs because of the wider export market open to them. With heavy financial backing from oil-rich Paran the design and development moved quickly and the prototype Skorpion took to the skies in October 1995 and was soon joined by the first of a pre-production batch of 8 Skorpions eventually forming a bi-service development squadron based in Paran and taking advantage of the clear skies over the Parani desert. Paran claimed priority for deliveries and formed the first Skorpion squadron in 1998 with Poland deferring deliveries for their own air force until 2001 due to financial pressures but by this time the Skorpion had become a modest export success with PZL securing exports to many of the former Soviet Union client states but with PAC only exporting a few Skorpions to Syria. (One from 2012) https://combatace.com/files/file/8772-pzl-230-f-skorpion/

Not bad my friend ;-)

Look like the first kill in ODS of "Rico" Rodriguez... Mandatory screen from ODS 30th Anniversary

so, i was today years old when i found out the Hawaii ANG flew A and C models together from 91 until changing for teh Raptor in 09.... explains why C serials were so damn hard to find for them

SurpriseAttack=TRUE SurpriseAttack=Payback

The latest iteration of the Billion Soft Falcon 4.0 total conversion modification - Benchmark Sims 4.35 U2 - is available for you to enjoy as of RIGHT NOW! BMS 4.35 U2 requires a legit installation of a Falcon 4.0 (all older and newer versions are accepted alike, i.e. Microprose, Hasbro, GOG, Steam, Retroism). The check is performed both at setup time and every time you start BMS. If no valid installation is found, BMS will exit with a corresponding error message. U2 is an incremental update on top of 4.35 base + U1, so you need to have the BMS 4.35 Full Installer package and Update 1 available on your PC. You can both update your existing 4.35 base + U1 installation as well as perform a fresh 4.35 base + U1 + U2 installation from scratch, as you like. See the installation instructions below for details. This mod may not be used for any commercial purposes. Any such use may constitute a violation of the intellectual property of Billion Soft (Hong Kong) Limited and the non-commercial Terms and Conditions under which Benchmark Sims make this mod available to you. Generic Information & Known issues: =================================== — The build number string in the Falcon UI will read "4.35.2 (x64) Build 23835" after the update. — The shortcuts in the start menu and on your desktop will NOT be renamed to U2, they will still read "Falcon BMS 4.35" after the update, feel free to rename them manually. — The following change log is by no means complete. Its purpose is to give you a quick overview about the highlights. You can expect tons of smaller tweaks and fixes. — If you have any questions or found bugs regarding the change log items please always! reference the revision number, e.g. "(r12345)". — Note: None of the manuals have been updated yet. The 4.35.1 manuals remain valid. File Updates: ============= - Falcon BMS.cfg - IVC Client.ini - RTTClient.ini - RTTServer.ini - Key Files - Note: Please always update the files manually. Don't copy paste! Table of content: ================= 01. CTD fixes 02. Falcon BMS.cfg changes 03. Shared Memory changes 04. Tool updates 05. Key File & Input fixes & updates 06. Multiplayer fixes & improvements 07. ATC fixes & improvements 08. Weather fixes & improvements 09. Various code fixes & improvements 10. Various data fixes & improvements 01. CTD fixes: ============== - Fixed CTDs related to gndai. (r23563) - Fixed CTDs after map erase, iterator is invalided for that position. (r23591) - Avoid dangling pointer after deleting pn->subPartData. (r23592) - CTD fix when pilot nid is above hardcoded 686. (r23637) - Fixed gndai waypoint CTD. (r23646) - CTD fix in the whole ATC state machine, rule out helos from ATC entirely. (r23681) - CTD fix in landme (null ptr check). (r23702) - Locked simloop UpdateATC, since this can be called from campaign thread (race condition CTD). (r23765) - Fixes alpha CTD due to different viewports. (r23432) - Fixes nullptr PAKmap CTD. (r23348) - CTD fix, related to nullptr insertion of GroupDrawLists. (r23356) - Fix for pure virtual CTDs. (r23389) - Tons of other CTD fixes. 02. Falcon BMS.cfg changes: =========================== - Added missing lines in the Falcon BMS.cfg (r14319): * set g_nRespawnTimeforStuckAI (default 6 minutes). ReagTimer and DeagTimer adjusted accordingly. * set g_bHostDisableP2pForDubiousConnections (default 0/false). Should be activated for large MP events. Note: - U2 *does* replace your existing config file. Do *not* make a backup! - Instead, re-configure from scratch based on the new file, otherwise you'll miss new config options. 03. Shared Memory changes ========================= NONE 04. Tool updates ================ - Fixed the BMS Editor 'Model Viewer' (r23421) 05. Key File & Input fixes & updates ==================================== NONE 06. Multiplayer fixes & improvements ==================================== NONE 07. ATC fixes & improvements ============================ - Make sure DigitalBrain rWindex is aligned with the ATC / Airbase in the whole landme function. (r23681) - ATCMsg is missing a break statement. In case of lParked, info can be destroyed and default case will access it. - Fix for ATCBrain::GetOppositeRunway (r23629) - pointer in ATCBrain::ProcessQueue() gets deleted twice. (r23652) - Fix in ATCBrain: Pointer nextTakeoff may become dangling during function. (r23660) 08. Weather fixes & improvements ================================ NONE 09. Various code fixes & improvements: ====================================== Note: The following changes may include data & 3ddb updates as well. - Fixed ground Units not reaggregating and memory corruption as well. (r23506) - Fixed ObjectLOD races -> missing cockpit and model problems. (r23562) - Fixed repairing code in campaign thread. It will now send a message to SimLoop thread and all clients to repair the given feature. (r23564) - Fix Squadron stores ressuply when aircraft are coming back home. (r23580) - Added critical section during ObjectLOD::Unload.This can avoid a leak, in the case of unload/load/unload sequences. (r23593) - Fix for out of bounds access in the O_Output WordWrap function. (r23606) - Prevent accessing the team array out of bounds. (r23607) - Avoid buffer overflow write, which caused memory corrupption in SetAcLoadout. (r23611) - Fixed TGP being blocked after loosing a flight element. (r23611) - When movieClose is called, we can release the surface twice, causing undefined behavior. (r23621) - BaseBrain lastTarget is not referencing the object it points to. As a result, it may become dangling when targetPtr is dereferenced. (r23627) - Fixed UI_UpdateOccupationMap (r23637) - Fixes deadlock due to ArrestorDraw. (r23639) - Fix for SimVehicleClass::Sleep is not nulling death message. (r23661) - Make sure to call ClearTarget on SimBrain destructor, to avoid leaks. (r23664) - Fix for Weapon fire msg is converting helicopter to aircraft. (r23665) - Fixed overruns within the 3D-interpolationfunction (MissileClass::GetRMax, GetRneMax and GetRopt)when it tries to access the assumed 3D-data. (r23692) - Added precondition checks and fixes in 1, 2 and 3D-interpolation function. (r23693) - Fixed bogus values being read outside the data table array. (r23693) - Fixed memory leak in SimWeapon::launcher. (r23718) - Fixed bad cockpit text drawing outside Start and Finish frame. (r23726) - Fixed memory corruption in CameraDrawList. (r23727) - Fixed zero devision in GetRMax. (r23736) - Fix to avoid deleting any waypoint from SimVehicleClass which is shared with gNavigationSys waypoints. (r23737) - Avoid dispatcher races (UI and campaign for example) when leaving campaign or 3d (depending on game type). (r23739) - Added Copy paste functionality in edit box and chat command line. (r23755) - AIM120 fixes: That makes MADDOG shots a defensive of WVR mode as expected. (r23761) * MADDOG : goes active as soon as off the rail and scan with a limited range capability * MADDOG : does not loft anymore since has no information on range when fired * HOJ : HOJ is only capable when the missile went active - Fixed AI reacting to missile too early when missile was in HPRF instead of MPRF. (r23762) - Fixed out of bounds fix in ooutput: when SetText is called on an existing O_Output. (r23770) - Fixed Terrain loading race. (r23774) - Fixed Shadow map was not being cleared after sundown. (r23792) - Fixed race possibilities while exiting campaign/TE. (r23795) - Fixes nan values due to InJetWash computation. (r23435) - Fix Heat Blur positioning and velocity when aircraft is in Idle. (r23401) - Fix heat Blur not oriented correctly with vectoring thrust. (r23401) - And many, many more. 10. Various data fixes & improvements: ====================================== Note: The following changes may include code & 3ddb updates as well. - Updated ambiant light since we have real moon now. (r14084) - Fixed TracersGreen and TracersRed missing alpha channel. (r14141) - Fixed Al-Tariq bomb : mimic the GBU-54 instead of the GBU-12. (r14142) - Fixed F18 series totally out of control while landing. (r14186) - F-16 Cockpits updated. (r14333) * Made flight control stick move (very little) * Fixed seat adjustment switch. Now it has the washer and jam nut on the sidewall to hold the switch. * Added more switches on the 2 seater F-16s for more real life accuracy. * Textures updated. - Fixed JFS Start does not work in all non F-16 cockpits. (r14339) - Fixed Unit Flight's element for ASW, ECM, Recon and Tanker types. (r14340) - Updated American F-16 CCIP pit avionics panel to the more correct panel. (r14347) - Fixed RSAF F-16 IFF panel. Digits were not working. (r14347) - Fixed F-16 Sufa cockpit. Changed from Aux Comm to IFF panel. (r14350) - Cleaned up some texture misalignments on the night lighting and missing backlighting in some areas of some cockpits. (r14360) - Disabled the MAP switch on the PXIII F-16 since it is not used. GPS switch now moves instead of the GPS and MAP switch. Hotspot updated. (r14360) - Fixed Sufa Altimeter (6 digit). Was only showing 1/2 the digits. (r14360) - Fixed ALS for Kimhae RWY 36R that had one element in the middle of the Taxiway A. (r14365) - Updated shaders. (r14370) - All Hotas Basic key files are now available in the UI Controllers Setup "Load Keyboard". (r14375) - Fixed F-16 EAF incorrect AGM65G loadout. (r14377) - Various Texture updates.

A new Instant Action mission will be included with the next release of the ODS 30AE total conversion, complete with bonuses! Shot down a MiG-25 coming head to head, and then I shook off a pursuing MiG-29 which ultimately crashed into the terrain, trying to follow my crazy evasive maneuvers (shown in the last pic).

Grumman F-14C Tomcat - 555th Tactical Fighter Squadron, United States Air Force, 1974

348th FG

340th FS

You mean like this..?

For dog sake. Do you really need to quote the whole post with all those screenies? We have seen that nearly a year ago...While allenjb42 post was enjoyable at the time ...your quote is not. Definitely not. Really hard to see a point of copying those pictures and asking questions while you could use a private message system - which works perfectly fine on this forum. not to mention ...You did not bring anything valuable to the screenshot thread from yourself. as for screenie.. my new substitutes for the most common stock ground objects...