Leaderboard

i´m back , computer is working again

I missed the "Phantom Phriday"...

Hello, my friends, I wanted to give you all an update. I saw the doctor on August 27th, and he informed me that my progress is good and looks promising. However, I still need to have another PET scan within the next two months. I'm hopeful that the results will be positive and that this will be over soon. I just returned to Kuwait on August 30th, so this is my first time on my PC in about four months. I think I need one or two weeks to fully recover from the short-term treatment side effects, and then I might start making some 3D models. Take care, Mohamad

The machine that runs mysql was nerfed after an update. I'll monitor it when I can.

PSU Mirage 2000-5F... in action ! https://theaviationist.com/2025/08/31/first-photo-ukraine-mirage-2000/

Mirage 2000C #80 with a fake cockpit I took the photo in 1995

1974... the future ! F-18 for the NAVY and the A-18 for the US MARINES CORPS !

It's been a long time since anyone posted here.

Interoperability, my good man....

RTB...

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

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

Hun over Nam.

Things have made some progress. The problem is that I first applied the S-300 data(or something else, that was a long time ago) at the beginning. So when I added ShowMissile=TRUE, I found that these missiles actually remained in a vertical upward attitude and could not be launched. After I fixed WeaponSystem data, they all returned to normal working state.

Thank you so much for your kind words, my friend! It feels wonderful to be back home again.

Original photo vs in game screenshot.

Man I just love those slow movers over 'Nam - some of my favorite flying...

I almost forgot its Sukhoi Sunday!!! Just wanting to "Fit(ter)" in, you know!!

would ask what the French are doin on an American CV, but I can think of others that belong there less

One of my most favorite things to do in the entire Universe ..... Since there's no template for the Bis B, have to make one. Simply because I don't like the brown/green camo as used by Syria for Algeria (which apparently used 2 tones of brown). Noted from several photos found the the web. Just LOVE drawing thousands of rivets ---- At least the serials will be right ....

Well, it started out straightforward. Go bomb a bridge. I'm still 22 miles from the target.... And this was at a slow point in the action.

Hello everyone! I have been working LOT on CSF Type 96 optical sight / HUD and is happy with the result. Here is screenshot of improved CSF Type 96: Navigation Mode: AA Mode: AG Mode: The Mirage 5E2's HUD also have been worked on. Navigation Mode: AA Mode: AG Mode: Eagle114th

It's been a lonnnnnnnnnnnnng time

Late 1999: Algeria accepts it's first MiG-29s

Hello everyone! The new version of SF - CAP v0.05 is finally released! UPDATE: Thank you CombatAce Admin / Mods! The files are ready for download now. So much work poured into this version, including the changes to all aircraft's following INI changes: - gun range (Minimum, Maximum, and Default) - DetectSystem, so it actually reference to the avionics.ini - Added many of aircraft avionics overhaul NOTE: In Optical folder, you will see VIEW - CAMERA SYSTEM, it includes more dynamic head movement in flight. It is still in beta stage, there is plan to improve it further. By the way, the Mirage series is the most complicated projects I have ever done up to date. This is where I dive deep into the rabbit hole and realized that various Mirage have different radars and avionics configurations. Good example is Egyptian Mirage 5SDE and Libyan Mirage 5DE, both have same airframe with different radar and optical sight / HUD. I am so relieved to be able to bring this new version out. The feedback is always appreciated, because they are helpful for me to improve the projects. For now, I want to put this project on temporary hold for now, I want to focus on digging through the SF2 dll files, so I can build the huge INI modding information library for all of us to use. You can see the projects in this link: https://combatace.com/forums/topic/100023-sf2-advanced-moddings-dll-files-editing/?page=2&tab=comments#comment-822140 When I decide to take a break from this project, will come back to work on this one, then back and fort between both SF - CAP and SF2 advanced modding projects. Thank you for enjoying the mods! Cheers

California Dreamin'

I would be very pleased if someone could create a 3ds Max exporter compatible with versions from 2010 onwards. While I am aware that Blender is an option, I am accustomed to working with 3ds Max. Ultimately, it is simply something I would be delighted to have. (I wish it would come true).

A string of MK83's at 203 feet & 487 KIAS. I suppose to everyone but me, this was BOUND to be the outcome.

Ethiopia war Eritrea 90 Eritrea Air Force MB 339

@swambast: your vietnam - which terrain is it ? looks very, very good. is it available to the general public here ? required screenie.

I'll trade you for some heavy metal over the Taiwan straits. The target was an Industrial Complex, but plans change....especially when the PLAN shows up in the straits on a Show Of Force. Just so happens, I had extra munitions to handle JUST such an occurrence.

Two seats x 2

Good reminder - thanks. Here is an old one when I was on the BOB kick for a while re-creating the London Tower Bridge, the historic port/river cranes, cargo ships, dock warehouses, barrage balloons, etc.

Hello everyone! The progress mining through the Avionics60.DLL in the language of C pseudocodes of Ghidra have been full of puzzles and it starts to make sense. Here is how it work, based on what I understand: 1) INI reads the token: "SymbolType=(NAME)" 2) Engine normalizes the token (treats "AirspeedScale", "airspeedscale", "AIRSPEED_SCALE" as the same entities). 3) Engine looks it up in a registry (Table), instantiates the matching "avnHUD(NAME)Class". 4) That class owns the **logic + drawing** for the symbol. The way SF2 handle hte string and names from class is wild! Here is list, so you can see an example: This is based on what is found inside the Avionics60 and SF2.exe dump. I want to add more informaiton about LCOS and CCIP adn why they don ot stay within the limtation of HUD rendering area (ViewportTopLeft and ViewportBottomRight): LCOS and CCIP are HUD symbols, BUT they calls the ballistic code within HUD class, resulting in not being fully integrated in HUD codes as another HUD classes do. Another wild bug I also discovered, this is from Avionics60.DLL DUMP FILE: This means if anyonoe uses "TrackMemoryTime" instead of TrackMemroyTime, wil not work. I plan on correcting it by modifying the DLL files via Ghidra and patching the DLL as first step toward modding DLL files after finishing the ini modding information library. Cheers!

Hello everyone! I am back to working on ghidra and SF2 DLL files digging. This week I am working on extracting all of available sections (Headers), key values, available values that can be used with it, especially examples how to use it. I am quite shocked to see this in Avonics60, example: UPDATE: For now, the list is removed. There was some mistakes. I am continuing to grow skilsl using AI correclty while extracting huge amounts of codes (over 60K lines of codes from Avionics60.Dll). I apologize for the mistakes. Will post more accurate list when I double check them. However, I do not promise that it do work in SF2, but it is what extracted from avionics60 dll Therefore, this week, I am going to get busy building the large database of information for each .ini sections (headers), keys (entries), and values that can be used with each keys. With that, we can experiment if they do work in SF2. Eagle114th

Hello everyone! After finishing workingon UAE and Zaire Mirage 5s / 50s series, I just realized that there are even more unique Mirage series that is locally modified based on Mirage airframe. For example, South African Cheetah C / D / E, as well the IAI Finger and IAI Dagger. Started working on South African and Ecuador Cheetah series. Here are screenshot of Cheetah E: NOTE: Cheetah C and D uses IAI Kfir C.2 cockpit and RWR while Cheetah E have modified F-15 cockpit and IAI Kfir C.7 HUD as placeholder that seem close to Cheetah E cockpit. Due to the limited information, this is based on mix of researches and an educated guess that makes sense. I am working on Argentina IAI Finger and Dagger, then I think I will finally complete the ultimate Mirage IIIs / 5s /50s series, including Nesher and Kfir. I aim to work on every mirage based aircraft, used by all nations, because of the love for the aircraft. Any aircraft that exists from any nations, deserves to be flyable in SF2! Cheers!

GOT IT FIXED! Apparently, an update switches a device security option to on. I flipped it off and we're up and flying. Now I don't know whether I'm elated or not to not have to buy a NEW HOTAS system.

Taking a peak over the Fence(r)

for half a second i thought you were giving your opinion on our advise

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

Hello everyone! I figured out what to do now. I’ve been digging through Avionics60.dll to understand how HUD and avionics are handled before any attempts to modify DLL files. By analyzing the Ghidra dump and .ini files, I created detailed notes on .ini editing for Avionics60.dll, starting with the HUD section. Here is note for a start: HUD.txt This is what I just realized from digging through Avionics60.DLL: Keys (Entries) like LCOS and CCIP are tied to the specific ballistic classes (avnHUDLCOSClass, avnHUDCCIPClass), not the generic HUD class, THERFORE is why LCOS and CIPP goes beyond HUD. Slowly will go through each DLL and extract what I can find (Sections and Keys), to build a comprehensive .ini editing library for modders here. Cheers