Leaderboard

Hello everyone! It have been incredible challenging going through over 60k lines of C-pseudocodes (Decompiled in Ghidra) that follows the logic of C++ (natively written in SF2 DLL files) in Avionics60.DLL file. The interesting thing is, I have noted how each class of HUD calls another HUD class and/or uses string to handle the key and associated keys for each sections. Spent days and many hours working on both HUD and RadarDisplay key extraction that can be used in INI files. I do NOT guarantee that it works, at least it is what is found in the DUMP files. The AIs have been huge help, cutting down the intense DLL DUMP digging. Here are HUD and RaadarDisplay (WIP) INI usage guide. If some codes (INI) does not work, then I apologize. At least I tried! Here are two Avioincs60 INI information: HUD.txt RADARDISPLAY.txt Eagle114th

RTB...

I would not correct the typos bugs in the dll, because then the old XX.ini, modded but also original ones, will not work. There are other typos like that, but they are known by ini modders: Type=HUD_MODE_INDIDCATOR (cockpit.ini) NoJettisionTank=TRUE (data.ini) and maybe others that do not come to my mind now

Busy day at Nellis as F-4s head out for some Red Flag action... But they're not the only ones up there today... ...and the WSO's view...

Incredible work, amazing, this is much more complete than the databases we had so far based on accumulated experience. It seems that the outcome has HUD, RADAR, but also COCKPIT functions. For example I have not been able to get "SymbolType=LOW_ALT_INDICATOR" working for the HUD. But the "INDICATOR" part is the clue for me that it is like the cockpit function "Type=LOW_ALT_WARNING_LIGHT" (that works). I am not sure. Unfortunately, a function intended for "RADAR" does not work for "HUD" (or COCKPIT, and vice-versa). A great future outcome of the work could be to get a new "HUD" function (for example) derived from an existing "RADAR" or "COCKPIT" function (because in that case the output data is known existing from the simulation engine, so it is "just" to display it). Some Remarks: "HUD_" in Symbol[XX]=HUD_FUNCTION and [HUD_FUNCTION] entry is not mandatory, just practical legacy naming convention. Any name would work. Same for Radar_ (and most likely VDI_) SymbolType=ALT_LOW_TEXT is an interesting case (not in your list). It works, the defined text will be displayed, but whatever the altitude is. A bug I guess. BORESIGHT alone not sure, but SymbolType=BORESIGHT_CROSS works SymbolType=CLOSURE_RATE_SCALE not sure but SymbolType=RADAR_CLOSURE_SCALE works SymbolType=DEVIATION -> SymbolType=COURSE_DEVIATION SymbolType=FLIGHTPATH not sure but SymbolType=FLIGHTPATH_MARKER works (I have seen your note on alias in the previous release but not tested) G_INDICATOR not sure for HUD, but SymbolType=CURRENT_G_TEXT works SymbolType=GLIDESLOPE -> SymbolType=ILS_GLIDESLOPE SymbolType=LOW_ALT_INDICATOR does not work (see above) MACH_INDICATOR not sure but SymbolType=MACH_TEXT works MasterArm not sure but SymbolType=MASTER_ARM_TEXT confirmed yes SymbolType=MAX_G_INDICATOR -> SymbolType=MAX_G_TEXT works SymbolType=MODE_INDICATOR not sure, and not useful, as any function is called in a known mode so "SymbolType=" makes it (but "Type=HUD_MODE_INDIDCATOR" is valid cockpit function) SymbolType=RADAR_ALT_INDICATOR -> SymbolType=RADAR_ALT_TEXT SymbolType=RADAR_RANGE -> SymbolType=RADAR_RANGE_TEXT SymbolType=RADAR_TARGET_ALT -> SymbolType=RADAR_TARGET_ALT_TEXT SymbolType=RADAR_TARGET_ASPECT -> SymbolType=RADAR_TARGET_ASPECT_TEXT SymbolType=RADAR_TARGET_BEARING not HUD (tbc) but SymbolType=TARGET_BEARING_TEXT works in radar display SymbolType=RADAR_TARGET_HEADING not HUD (tbc) but SymbolType=TARGET_HEADING_TEXT works in radar display SymbolType=RADAR_TARGET_TAS -> SymbolType=RADAR_TARGET_TAS_TEXT SymbolType=RADAR_TARGET_VC -> SymbolType=RADAR_TARGET_VC_TEXT SymbolType=SCALE alone I am not sure (what on the scale ?) SymbolType=TARGET_TEXT alone ? SymbolType=WAYPOINT_ID not ok (checked) -> SymbolType=WAYPOINT_ID_TEXT works SymbolType=WAYPOINT_RANGE not ok (checked) -> SymbolType=WAYPOINT_RANGE_TEXT works SymbolType=WEAPON_COUNT -> SymbolType=WEAPON_COUNT_TEXT Again, great, very promising !

What Wrench says, it's not true that Blue SAMs don't work, they work alright. SAM launchers in the terrain's targets.ini must be added as SAM_LAUNCHER. That's the generic tag that spawns working SAM launchers. You can't tell the game to spawn a specific SAM, this decision must be left to the game engine with the generic tag. Working Blue SAMs are featured in my terrain packages and in the ODS 30AE mod; try flying an Iraqi aircraft towards Saudi/Coalition airbases and you'll be facing AAA and SAMs.

La vida...

Claro que sí amigo!!

Lamentablemente muchos de nosotros migramos a otros juegos o simplemente nos convertimos en padres y la vida diaria nos fue dejando de lado del foro. También suma mucho que el juego nunca se modernizó se quedo estatico. Yo comencé en este foro cuando tenia mas o menos 19 / 20 años , hoy ya estoy por cumplir 38, Casado y con 2 hijas. Nunca deje de modelar en 3D , hoy en dia sigo pero con otras herramientas como Fusion 360. Junto con @torno @pato poli @AleDucat Seguimos hablando todos los días , hace 17 / 18 años que somos amigos. Siempre me quedo con la nostalgia y el gran aprendizaje que este Foro y en especial esta comunidad me dio. Aprendí muchas cosas que me abrieron puertas para mejorar en mi vida personal , sobre todo en lo laboral , gracias a las tecnicas que aprendi aqui sobre modelado 3D y diseño grafico. CombatAce es y fue una gran escuela para muchos de nosotros. Saludos Marcos.

Wishlist (starting "slowly" ): - SymbolType=CLOCK_TEXT - SymbolType=WAYPOINT_TIME_TEXT (time to next waypoint at current speed)

View File SF2 MiG-17F "Fresco-C" Algerian Air Force Skin Pack SF2 MiG-17F "Fresco-C" Algerian Air Force Skin Pack 8/24/2025 -For SF2 =ONLY= (Full 4/5 Merged Recommended) Here are 2 new(ish) skins for the stock 3W MiG-17 "Fresco-C", as used by the Algerian Air Force from 1965 thru the early 1980s. Basically, slight 'rebadging' of the stock "QJJSilver1" and "QJJCamo1" (Nile Style), but with corrected serial number decals. I've =not= included any of the bits to make it flyable, but if you have, and use the "read only main ini trick", you'll have to turn that off after adding this skin, even though this does replace the stock one. See "Installation" for more details. All markings are decals, and decal randomization is TRUE. The two sets of Serial numbers are historically correct (ish). You'll have 24 for the NMF, and 18 for the Camo. However, while all the numbers are correct, they should be considered Generic in nature, as I could not find which squadron each served in. Any marked with the cross (or plus sign +) are conjectural, as I could not find any reference to them. The Post 1968 (Camo) skin uses the "FG-**" style. Both skins remain in their 'as issued' BMP format (3w Rez) When on the Loadout Page, you'll see Algerian Silver (1964) Algerian Camo (<1968) This is NOT changed from the original listing on the texture set inis, with the exception of adding specific decal randomization text, and the year tags. I have included a modified data and loadout ini. The data ini gives the aircraft some "hardening" (via aluminum armor), and the loadout ini adds the drop tank for all missions. I've also included a new pilot figure, "RedAir1". The canopy is also activated, it uses the Standard Animation Keystroke (tm), Shift/0 (zero). What I have NOT given you, are the bits and bobs necessary to make it Player Flyable (tm). If you haven't done this, you'll have to root around for the needed cockpit in the CA downloads. (cough - by Stary). I have, however given you the VK-1F engine sound. As is always recommended, unzip to a temp folder or your desktop to give easy access to the rest of this readme for it's install instructions. PLEASE read them, before installing!!! Also, the Notes section has more details on the changes. Happy Landings! Wrench Kevin Stein Submitter Wrench Submitted 08/27/2025 Category MiG-17  

If you are chasing a MiG ... you should not forget, that the MiG may have a buddy. If so, shit happens.

I had this one in my phone before I came to the UK, so this is my first unofficial comeback lol

B-61 Show of Force to deter further DMZ incursions in Korea, circa 1982. Can you spot the falling weapon? Hint: look above the hangars....

A flightline of french Thuderstreaks

View File Have Drill MiG-17F Have Drill skin for Mig-17F This is a simple skinpack for the stock MiG-17F so that you can fly as Included one skin and one decal folder for a USAF Have Drill MiG-17 Required A copy of SF2 with the MiG-17F (i beleieve thats all but North Atlantic) A pit if you want to fly it. One can be found here Credits TK for the original game and stock Syrian skin daddyairplanes skin and decals thank you for downloading this mod, i hope you have fun with it Kevin Unruh aka daddyairplanes 6 Sep 2024 ************************************************************* This is freeware; it CANNOT be distributed unless permissions are granted by myself. The original readmes, if any, and all other pieces of the package MUST remain intact. The names of all contributors, modders, suppliers, etc =MUST= be listed in any new readmes. This package and any part of it may NOT in any way, shape, or form be used in any payware additions. See the original readme documentation, if any, for further allowances and restrictions Any persons wishing to make further modifications, contact me first. Any persons wishing to make further modifications MUST remember to put everyone's name in it. ************************************************************* THIS AIRCRAFT MOD OR ANY PART OF IT MUST NOT BE HOSTED OR POSTED FOR DOWNLOAD ON ANY OTHER WEBSITE WITHOUT MY EXPRESS PERMISSION, OR USED FOR ANY OTHER PURPOSE THAN THIRDWIRE FLIGHT SIMULATORS, AND MUST NOT BE SOLD OR OFFERED FOR SALE BY ITSELF OR WITH ANY OTHER FILES OR MODS. ************************************************************* Submitter daddyairplanes Submitted 09/06/2024 Category MiG-17  

Me boy a bajar del barco por un tiempo ,tengo que mudar mi PC a Windows 10 y no se que resultará de este cambio, solo espero que no me de problemas. Esto es en lo que estaba trabajando, y mi tiempo para esto ya se cuenta en minutos en lugar de horas como en otros tiempos.