pvince

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

For the first one: You have a double "RadarTexture=", it's invalid, remove or comment the first one. For the second one: I am quite sure "RadarTexture[N]=" is not a valid entry. "RangeTexture=" is valid and can give the same if the texture is in tga. It will be superimposed to the one called by "RadarTexture=" (for SEARCH,ACQUISITION,TRACK ,BORESIGHT) or by "RadarAGTexture=" (for GROUND_MAP) in jpg.

You could try: Option 1: [TextureData] RadarTexture=cockpit\F-4E_Radar_AA.bmp ;;RadarAATexture=cockpit\F-4E_Radar_AA.bmp invalid, ignored RadarAGTexture=cockpit\F-4E_Radar_PPI.bmp RWRTexture=cockpit\F-4E_RWR.bmp Option2: use a blank texture, without any grid, and put the grids in the tgas: RangeTexture[NN]=...

I don't think you give it a name that way, it is just ignored by the game engine.

I don't remember having ever seen "RadarAATexture=...", maybe not a valid entry, because for AA the texture is "RadarTexture=".

the entries you show are for avionics60, so if you have called avionics70 in main.ini, there is something wrong.