Leaderboard

MATS C-135A.....when color mattered

Hopefully before summer's out.. I'm determined to get this to you guys.

Coming 2020, Microsoft Flight Simulator is the next generation of one of the most beloved simulation franchises. From light planes to wide-body jets, fly highly detailed and stunning aircraft in an incredibly realistic world. Create your flight plan and fly anywhere on the planet. Enjoy flying day or night and face realistic, challenging weather conditions. For Win 10 and XBox https://www.xbox.com/en-GB/games/microsoft-flight-simulator

Sh*t!!! I got so much love for the NF5A!!! When I was little, I would ride my bicycle to Gilze-Rijen airbase (316Sqn) to watch them take off and land!

Curtiss P-42D Twinhawk - 181st Fighter Aviation Regiment, Soviet Air Forces, 1944 Skin Credit: Charles N.B. Deliberate change in aircraft designation to P-42.

F-4G from the 561st TFS on final check before take off i know the tailnubers are still missing but so are many other small details yet

I need somebody help to update super toucan. down what needs to be done: Hit box; pivot points; Collision points; FM; He is not flying like the real one. I do not know where to set this in the files. how it should be

Always had a soft spot for this little bird.....

Technology Gap Work in progress, skins could be subject to changes. I didn't have time nor will to replicate the same black camo of the last F-22, but I will. My thanks to Krycztij for his 3View tool (https://community.combatsim.com/topic/26077-taw-3view-—-a-renderer-for-taws-3-files/) and to mue for his LODViewer.

Blue Mondays

You might wanna update your nations.ini for the proper finflash to show.

Hello Denis, May I help You to work on hit boxes and collision points ? What are the "pivot points" ? Best regards, P. Edit : Hit boxes & Collision Points.7z

D-Day... in memorian !

The following story background is from DID's F-22 Total Air War game, dated 1998. The fictional skins are based on the F-22s appearing in DID's Total Air War scenarios. Skins and 3d model are still subject to updates. In the mid-1990s, most of the military might in the Red Sea region was found in only three countries; Yemen, Saudi Arabia and Egypt. All of the other nations, dealing with constant internal pressures and sporadic social unrest could ill afford any concentrated efforts at modern militarization. So the rest of the area’s nations would bide their time and wait for their opportunity to field a national army that could stand against the might of any one of the “big three.” Although there weren’t any formal declarations of war within the region, there were also no real alliances. Each nation was kept busy dealing with internal problems of various sorts, so much so that any external issues were usually left unresolved. Border disputes erupted from time to time and were usually settled as a result of some form of military stalemate with each side claiming to be the victor. An American F-22 wing forward deployed to Djibouti, still sporting the YF-22 paint scheme, 2007 Another factor within the region stemmed from the major cultural and religious differences between the peoples of the Red Sea area nations. The population in the southwestern part of the region was largely agrarian. Trading mostly foodstuffs and other essentials for survival, farming groups clustered into tribes and lay claim to several hundred acres of land. When arguments arose between neighboring tribes, the result was often bloodshed, as tribal land holdings sometimes crossed international borders. Cities and towns within the region were often defined by the religious beliefs of the residents. Rarely, were there populations of mixed beliefs. Only the largest trading and commerce centers could tolerate such religious diversity. Religious beliefs also played a major role in state and national rule, often affecting the decision making and negotiating thought processes of the country. American F-22s in their Pac West camouflage, executing an Air Interdiction mission over the Ethiopian highlands, 2018 With all of the diverse people and religious beliefs within the area, tension was an everyday side effect. Although no formal declarations of war had occured in the recent past, that did not mean that nations haven’t fostered ill will towards each other. Outright hostilities had not developed in the past because of the lack of either a credible military force or the capital required to support it. As a nation in the Red Sea area, you were either a “have” or a “have not” in the national forces department. But all of that was soon to change. New fortunes, created by the discovery of precious metals and oil reserves within the Red Sea operations area have lead to regional unrest. International power struggles for the control of these precious natural resources now bolster nationalism and strengthen each countries desire to fight. With the new regional income, formerly poor countries now can afford to train and equip national military forces. All armed forces within the region are ready and willing to test their newly purchased hardware. It is a very dangerous time. Saudi Arabia's F-22s, with their unusual Grey camouflage, crossing the "Empty Quarter" into Yemeni territory for a strike mission, 2022 While on an international antiquities excavation in southern Sudan, a professor and his archaeological team discovered unexpected oil reserves within that region. The oil deposits extended from within southern Sudan well into northern Ethiopia. Sudan and Ethiopia exploited the oil reserves and grew rich, becoming members of OPEC. The excitement over the discovery of new oil fields gave rise to new searches throughout the area for other oil reserves. Another series of large oil deposits were found in the coastal region of Eritrea, Djibouti and Somalia. Although not quite as expansive as the fields discovered in Sudan, it was sufficient to provide these three nations with a 11% control over the world’s petroleum market. As the oil reserves along the Somali coast were being mapped out, researchers stumbled upon new gold deposits. As the initial gold strikes were quickly exploited, more were found. There were some days when the coastal nations ceased to function because almost every citizen was out with a pickax and shovel, looking for their share of the fortune. The nations of Somalia, Djibouti and Eritrea became wealthy practically overnight. After much bargaining, Egypt acquired a few F-22s; here's one in its Woodland camouflage, conducting BARCAP over territorial waters in the Red Sea, 2015 To support the new military, the old infrastructure which had supported the former way of life had to be updated. Airfields had to be modernized to allow strategic and tactical aircraft operations. A large anti-aircraft network had to be established to provide warning and protection from invading hostile aircraft. National landmarks and governmental assets had to be protected from attack and reinforced to help repel any air strikes that might get through. Across all of the Red Sea theater area, nations prepared themselves for any outbreak of hostilities.

Next project, BTR-40 closed top. I hope I will get it fast this time.

View File SF2 F-86E Sabre, 144th FIS, Alaska ANG Skin Pack SF2 F-86E Sabre, 144th FIS, Alaska ANG Skin Pack 6/5/2019 -For SF2, Any and All (Full Merged Reccomended) This is a complete revamp of a 1stGen Sabre skin by Dave "USAFMTL" Slavins from June, 2003. It is designed to be used on the SF2 KAW Sabres Pack, for the F-86E-10 available therein. The Sabres are to be found at the following URL: https://combatace.com/files/file/13604-sf2-korean-war-era-f-86-sabre-pak/ Also included is a new data ini, with updated hit and collision boxes, and some meshes now correctly named. Honestly, I'd never noticed they were 'way off' until Mue's LOD Viewer! Please note, that Crusader's fix-its have already been applied to THIS versions' data ini. A backup copy of the original (2013) data ini is supplied, so as to lessen End User (tm) workload, and provide a safety net 'just in case'. This skin repesents the 144th Fighter Interceptor Squadron of the Alaska Air National Guard from 1955 through 1957-ish, when their mission changed from Air Defense to Airlift. The skin is in jpg format, and 26 all NEW decals have been created for it. While the serial numbers are historically correct for the E model, they should beconsidered generic in nature as they don't actually repsent aircraft from this particular unit. Decal randomization is TRUE. On the skin selection menu, on the Loadout Page, you'll see: 144th FIS AK ANG (1954-58) The SF2 "date switch" is NOT active on this skin. You'll have to select this skin for your flightmates by hand. However it is easily added by a simple text edit. 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 Submitter Wrench Submitted 06/10/2019 Category F-86  

Very interesting! But let's see the requirements.

PAF

Mue, first a big thank for this wonderful tool. I also have the problem of very slow execution (menus, rotations, any interaction with the program ...), which is better after some time, or if program closed and immediately relaunched. I also had a windows memory error (not enough memory), one time. I also had a data file that could not be loaded (<no data file>), but the file was there (and loaded ok with version 0.5.2). By comparaison with a working file I have found that this was due to the character '°' (complete comment line : "// -60°, 100 meter level") that prevented the load. The data file was in ANSI (again no problem with 0.5.2). Conversion to Unicode also fixed the problem for 0.6.0. Hope this will help.

Along with the F-4C Phantom during program "Peace Alfa", Spain also received two squadrons of F-105Ds in 1971, which had been replaced by Phantoms and Aardvarks and saw action in Vietnam. While the Phantoms main task was air superiority, the Thud's main task was Strike and CAS. Republic F-105D (CA.12) Thunderchief, Ala 15, Escuadrón 151, 1972 In the 1980s, the Chiefs of the EDA received an upgrade concerning avionics and radar and was enabled to carry more modern weapons such as GBUs... Republic EF-105D (CA.12) Thunderchief, Ala 15, Escuadrón 151, 1985

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

Hanger Screen courtesy of Charles

View File P-40T Twin WarHawk There’s no record of a twin P-40 ever having been made and the only evidence is a few Pics found on the internet. There were a few variations on the design, so I took a bit from them and add lib'd a few of my own. Credits: Model: Veltro2k Textures, decals and FM (Charles). Cockpit by CAStary FNum & FLet decals: Wrench Not to be used in whole or part in anything that is payware Submitter Veltro2k Submitted 06/07/2019 Category What If Hangar

Jeeeeeez !!!!!!!!!!!!! We'll have the best F-5a with the best weapons I've ever seen ;-)))

Love those weapons!!

...and some ravenclaw_007 goodness!!

yes great choice. thank you

This vehicles are badly needed for early cold war. Good choice!!

Barcap over the Med Greeting unwanted guests...........

Damn... 'our' own cool NF-5A!!!

Homeward bound .. the sky's the limit.

F-4G , 561st TFS

Chinese Knock-Off

Dropping retards from a 2000 is SOOOOO much fun!!!

Maybe some of the flight model guys find this useful for creating, analyzing or checking flight models. Last year I had the idea for a tool that extracts the data of the debug hud and writes them into a text file: (from this post: https://combatace.com/forums/topic/91675-how-to-develop-test-flight-models/?do=findComment&comment=741238): The process steps are illustrated in the following figure: The tool "DebugHUDExtractor" I came up with is written in python and uses the optical character recognition (OCR) software tesseract. Thus to use the DebugHudExtractor you have to install python, some python packages and the tesseract software. For those who want to try this tool, here are the installation, configuration and usage instructions: 1.) Download and install tesseract: https://digi.bib.uni-mannheim.de/tesseract/tesseract-ocr-w64-setup-v4.1.0.20190314.exe Copy lucidaconsole.traineddata into tessdata directory (e.g. C:\Program Files\Tesseract-OCR\tessdata). Needs admin rights. This file contains the trained data for the lucida console font. I use this font as it gave me the best results with the character recognition. This font has to be configured for the debug hud output in the game (see. step 4 below) 2.a) Download and install python: https://www.python.org/ftp/python/3.7.3/python-3.7.3-amd64.exe While installing select "Customize installation": -optional: change the installation directory (e.g I use C:\Python37) -enable "Add Python to environment variables" 2.b) Install needed python packages. On the windows command line execute the following commands: pip install pillow pip install numpy pip install opencv-python pip install pytesseract 3.) Setting the path to the tesseract executable: In <Python_install_directory>\Lib\site-packages\pytesseract\pytesseract.py (line 35) set tesseract_cmd to the file path of the tesseract executable. Use double backslashes or normal slashes. E.g.: tesseract_cmd = 'C:\\Program Files\\Tesseract-OCR\\tesseract' 4.) Configure the game. In SF2/FE2 game set Option Hud = Normal and configure the Huddata.ini. It enables the debug hud, set the font to lucida console, sets a bigger font size (the bigger the better, but all relevant debug info should still be displayed in the screen,e.g. for my 1920x1080 resolution I use TextSize = 24) ,the normal font color is changed to red (required for text filtering), the default right info box is disabled and the default left aircraft info box is moved to the right (that gives more space for the debug info box on the left) [Debug] DisplayDebug=true [Font] TextFontName=Lucida Console TextSize=24 [InfoDisplay] //BackgroundImage=TextBackground.tga BottomLeftPosition=0.8,1.0 //BottomRightPosition=0.99,0.985 NormalColor=1.0,0.0,0.0,1.0 5.) Configure the python script debughudextractor.py : Depending on the values you want to extract from the debug hud the variables extractPitch, extractAlpha, ... have to be set to True or False, The leftRect and rightRect variables have to be configured depending on where the debug info box and aircraft info box is located on your screen (depending on your screen resolution and the entries in your huddate.ini) The format is as follows: leftRect = (top-left-x, top-left-y, bottom-right-x, bottom-right-y) The top left corner of the screen is the origin (0,0). E.g. with a resolution of 1920x1080 and the above huddata.ini, I use the following: leftRect = (56,236,1450,1080) rightRect = (1528,968,1920,1080) See this picture: 6.) Start the script from windows command line: python debughudextractor.py video_file_path time_step_in_s start_time_in_s end_time_in_s <video_file_name>.txt and <video_file_name>_error.txt will be written into the directory of the video file. <video_file_name>.txt contains the extracted data. <video_file_name>_error.txt contains what values at what time couldn't be recognized. If a value couldn't be recognized, then the very next video frame is used and analyzed.