pvince

Very useful. Thanks ! Great work. With those new info on stall, I've put in my todo list to reopen the Mirage F1 stall model, that is not accurate currently.

I am not 100% sure but for me the StallXXTableData are not nominal values but relative coefficients to apply to the nominal value. For example for the Stall Lift Table, the coefficient will be 1, multiplied by CLmax=1.45, which gives 1.45 in your example. I say that based on how tables are used in SF2 and actual values in data.ini. To be checked.

OK. "LIGHT" and "FULL", is it your assessment, or the IA assessment, or is it in the source ?

Very interesting With « placeholder » we have the confirmation of those that do not work. But what is the difference between full and light ? Both work.

I tried a few new functions found. For some, so far nok (tried in Avionics70 only): I tried SymbolType=MISSILE_TOF and then tried SymbolType=MISSILE_TOF_TEXT in case of ... but none displayed something I also tried the font overrides: // --- Per-symbol font overrides (optional) --- TextFontName=Arial TextSize=14 TextBold=TRUE TextItalic=FALSE TextUnderline=FALSE TextStrikeOut=FALSE TextShadow=FALSE ShadowColor=0.0,0.0,0.0,1.0 ShadowOffset=1 TextOutline=FALSE OutlineColor=0.0,0.0,0.0,1.0 OutlineSize=1 in a TEXT entry, and also added them in [RadarFont] but also no effect. On the opposite, for "SymbolType=MASTER_ARM_TEXT", I knew the simplified one, but I could test successfully the options "OnText" OffText" and "HideWithGuns=TRUE" that were unknown so far. For those that did not work I can assume they are there as provision, or leftover from the library, but not coded yet, or code removed because unused for optimization.

It's not exactly the table you described but it is a first step. All the Avionics and Cockpit functions I know, by alphabetical order. I cannot claim it is exhaustive. Those in red were captured in dll or mods but either they do not work or I have not been able to make them work. Cockpit and Avionics Functions.xlsx

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

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 !

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

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

Good to read. I wish you a complete fast recovery.

none that I know.

Yes, Idle, Cruise, Mil, Max are normalized values from 0 to 1. No RPM value in real for Jet_Engine (Prop_Engine has other entries with a real value for RPM). AB values are above 1 for Throttle and RPM for engines with afterburner (no AB entries for engines without AB). If your Hotas has "hardpoints" for idle and AB start, you have then 2 additional "throttle" parameters to align your hotas "hardpoints" on the "idle" and "max" engine settings.

I would say it’s because they are too far, out of visual range. With T you can only select target that you can see (same for Y).

And for symmetry : [RT_Light_BANK_Right] Type=ROLL_INDICATOR NodeName=RT_Light_Right MovementType=LIGHT ValueUnit=DEG Set[01].Position=0.0 Set[01].Value=65.0 Set[02].Position=1.0 Set[02].Value=65.1

Should be: [RT_Light_BANK_Left] Type=ROLL_INDICATOR NodeName=RT_Light_Left MovementType=LIGHT ValueUnit=DEG Set[01].Position=1.0 Set[01].Value=-65.1 Set[02].Position=0.0 Set[02].Value=-65.0

Not directly with "MovementType=DIGITAL_DISPLAY", but maybe some workaround, to be investigated. I can take that at the same time than avionics70, when I'll be back.

'ValueUnit=MINUTES' is not a valid entry. It is ignored and default unit is used, which is meters for this function. Valid entries: ValueUnit=KM ValueUnit=NM Scale= is a valid entry for a multiplier. In your case, you default to meters, then the multiplier, but only the least significant digits shown, the last 3 at the right, that could create the confusion. Anyway it is the distance to next waypoint, not time. For a given speed, you can get the right estimated time using "scale=" (at the value of 1/speed) but it is a constant, it will work only for that speed, therefore not really useful. In such a case, knowing it is impossible to be accurate due to SF2 limitations, I show the distance, better than nothing. (EDIT: funny but true, ValueUnit=FT is also valid for range_indicator )

I confirm, range_indicator returns distance, not time. There is nothing I know in SF2 for time to destination.

New version with another change, Animation 8 called 2 times, it works but not good. I have optimized. I left the changes visible, to be cleaned in final version. F-4E_79_PaveSpike_COCKPIT.INI

With that it works for me: [LOS_Indicator] Type=ROLL_INDICATOR NodeName=Needle_LOS MovementType=ROTATION_Y ValueUnit=DEG Set[01].Position= 160.0 Set[01].Value=-160.0 Set[02].Position=0.0 Set[02].Value=0.0 Set[03].Position=-100.0 Set[03].Value= 100.0 no other change in your file. Or I misunderstood the problem to solve. F-4E_79_PaveSpike_COCKPIT.INI

I would try: [LOS_Indicator] Type=ROLL_INDICATOR NodeName=Needle_LOS MovementType=ROTATION_Y ValueUnit=DEG Set[01].Position=+160.0 Set[01].Value=-160.0 Set[02].Position=0.0 Set[02].Value=0.0 Set[03].Position=-100.0 Set[03].Value=+100.0 my best guess, or, if not: [LOS_Indicator] Type=ROLL_INDICATOR NodeName=Needle_LOS MovementType=ROTATION_Y ValueUnit=DEG Set[01].Position=+100.0 Set[01].Value=-100.0 Set[02].Position=0.0 Set[02].Value=0.0 Set[03].Position=-160.0 Set[03].Value= 160.0

My pleasure ! Good you fixed it. You used an "indirect" way, but I am surprised the "direct" way with "Rangetexture" tgas did not work. Here is what avionics entries should look like (as an example): [TextureData] RadarTexture=[path]\AA_texture.bmp RadarAGTexture=[path]\AG_texture.bmp RangeTexture[1]=[path]\RangeGrid1.tga RangeTexture[2]=[path]\RangeGrid2.tga RangeTexture[3]=[path]\RangeGrid3.tga RangeTexture[4]=[path]\RangeGrid4.tga RangeTexture[5]=[path]\RangeGrid5.tga RangeTexture[6]=[path]\RangeGrid6.tga RangeTexture[7]=[path]\RangeGrid7.tga RangeTexture[8]=[path]\RangeGrid8.tga [AvionicsData] AvailableModes=SEARCH,ACQUISITION,TRACK,BORESIGHT,GROUND_MAP,TERRAIN_AVOIDANCE RangeUnit=NM RangeSetting[1]=7 RangeSetting[2]=15 RangeSetting[3]=35 RangeSetting[4]=60 RangeSetting[5]=7 RangeSetting[6]=15 RangeSetting[7]=35 RangeSetting[8]=60 .../... SearchRangeSetting=1,2,3,4 .../... TrackRangeSetting=1,2,3 .../... BoresightRangeSetting=1 .../... GroundMapRangeSetting=5,6,7,8 .../... TerrainAvoidanceRangeSetting=5,6

If you want to post the full avionics file I can have a look if I can find something