Leaderboard

Then it is a data issue. Get a working red SAM system, make a copy, and re-data it into blue SAM ( not just userlist.ini - separate the whole SAM system into blue), then you will see that blues are quite capable too.

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 !

I take that

As far as I can say, HUD and RWR entries are the same for Avionics60 and Avionics70. Avionics70 is different for Radar functions only. Maybe less work for the radar difference only. Avionics14A: some differences in radar functions + VDI introduction

Hello @pvince and everyone, I have finally got to complete digging the possible sections and keys, along with assoicaated keys from Avionics60.DLL. WShat is included inthe AVIONICS 60.zip (4 Folders): RTTI - CLASS + FUNC LIST RTTI - DUMP RTTI - STRING LIST SF2 INI MODDING NOTES The recent HUD.txt and other .txt posted above are insdie SF2 INI MODDING NOTES too. however, you will see files: This time, they are labelled whichi DLL file they are from, to avoid the confusion when dealing with various .txt files. The next thing I want to note: AIs, no matter how advacned they are, they are still prone to make mistakes from tim eto time, which can't be helped. That is why the DUMP file come sin handy, as well RTTI String and class / fucntion list, so you can check it. And not everything come in string, sometime the class calls another calss for sections / keys. Next, about the DUMP, I will retreat it again: It is in C Pseudocodes, NOT native codes that SF2 is written in. This C codes is decompiled from Ghidra software and they follow the logic and systems that is natively built using C++. Basically it's C folloiwng how C++ is used in SF2 engine. Keep that mind when looking at DUMP file. Here is the file: AVIONICS 60.zip Now I am moving oni to Avionics70.DLL. Cheers!

Balloon: Busted!

RTB...

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.

You all are forgetting that I've been here in SF since Day 2, and I've pretty much seen it all. I'm one of the Last of the Originals still around. By 2006 TK had done whatever was necessary, as Pasko had released the first HAWKs and Chapparals*. All the Blue SAMs work for me, so I don't know why the OP is having issues. Don't matter if it's a HAWk Nike, Rapier, Bloodhound. It could be how they're set up on the terrain. You CANNOT call them directly in the _targets ini. You have to use generic tags. *it's actually set as Mobil_AAA

I recently got back into playing and modding SF2 and was trying to solve a problem I'd been unable to solve for a long time. The Marines in my game seem to be very considerate of taxpayers, saving Uncle Sam a ton of money by not firing at the enemy. I did a lot of debugging, ensuring the EW and SAM radars were properly positioned on the map, and that the datalink between them was true. I also made sure they actually had mmunition ready. I also made sure the ECM wasn't active on the aircraft I was testing. Yes, they were not completely unable to fire, I could see those MIM-104s flying around, but their willingness to do so was quite low, especially PAC-2. I have no idea what to do yet, but I'll keep an eye on it.

Some WIP projects, because a friend mentioned this, J-11 family It's like a tree with many branches: 11A 11A (MLU) 11B 11BH 11BG 11BHG. They usually have subtle or significant differences in the layout of MWS, HUD, engine, radar, etc. This requires me to make adjustments in many aspects such as model, skin, data, avionics, etc., which is also a very tedious task.