pvince

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.

Just tested in W10, after so many years !! I could launch, launch a mission. Only had to run the exe in admin mode (not sure it would be needed after a new install). I am still in 1.15.2 (last release is 1.16.1). I had some hard time because I was still in realistic mode with engine start-up sequence and I did not remember it

Eagle114th, Try first by adding 'ShowAnyWeapon=TRUE' there in avionics.ini: [HUD_LCOS] SymbolType=LCOS ShowAnyWeapon=TRUE that should be enough to fix the pb of the sight being visible for rockets (and bombs, if any). Additional note: the gunsight image call in the avionics.ini NAV mode is probably redundant: [HUDModeNav] Symbol[01]=HUD_GUNSIGHT Symbol[0]= .../... [HUD_GUNSIGHT] SymbolType=IMAGE ImageFilename=cockpit\A-1CM_SIGHT.TGA //ImagePosition=0,0.0555 ImageSize=0.0675 You already have it from the call in the cockpit.ini ("GunsightName=A-1CM_SIGHT.tga"). You probably have the 2 sights superimposed in NAV mode. To be checked, I have not tested.

You can change the colors for the .tga files that are called in the cockpit.ini. For what is defined and called in the avionics.ini, it is monochrome and defined by "HUDColor=0.0,1.0,0.0,0.7", only the alpha value is used from the tga called in the avionics.ini.

It is not the same, F1EM VI is the Morocco one, RMAF.

Ok, got it now, 'taca'n are 2 sub-NodeNames of 'VertTail' and 'Nose', that are also NodeNames. I skipped too fast the initial part. Thanks !

So Hide1 section is correct but Hide2 and Hide3 have the wrong "ModelNodeName=" in the example above. Thanks for the confirmation !

For my education, what should be in the "ModelNodeName=" entry ? Same as the line before in "ParentComponentName=" entry or the one after "DestroyedNodeName=" ? Usually, in other mods, it is the one after, which makes sense because the one after is also a node name, whereas before it is a component name. Here above I see the 2 options.

Maybe I misunderstand the question but, the bomb bay opening with "O" also refers to a LOD animation, BombBayAnimationID= entry.

Congratulations Coupi !

The pilot issue here can also be that the pilot model called in the data.ini [Pilot] SystemType=PILOT_COCKPIT PilotModelName=...name... does not exist in the "Pilots" folder, and replaced by a default pilot automatically by SF2, but position then does not fit.

I have double-checked: with released files, it is ok. The problem seems to be due to another CLB4 rack used than the one released.

Actually not, not needed, just for info. What is needed is to avoid two sections "SystemType=WEAPON_STATION" with the same "StationID" number.

I take the point. With what we have released, you should not have this result, so my first immediate feedback is that you have a conflict with former files that are not compatible with the 4.0 release. Try that first please, re-download if needed, and make sure to overwrite all files (after backup if you want to keep the previous versions for reference) and check again.

Thanks and Merry Christmas to all of you CA friends !

"ReverseModelOrientation=TRUE" added should make it And depending on the expected result you may prefer the speed control with "DeploymentMethod=AUTOMATIC_MACH". This is what we use on the F1.

It is the "steering cue" (SymbolType=STEERING_CUE) in A/G mode. Some kind of emulation of the target position within SF2 limitations, better than nothing

Color is defined by 'Color=R,G,B' entry, each RGB component as a positive number between 0 and 1. For example Color=0.88,0.25,0.25 (red). If you have a picture with the color you want, you can measure the color components with Gimp 'Color Picker tool' (for example). Select the measure in RGB % then. You will get the components directly (with 1=100% of course). For 'LightSrcOffset=', I am not sure but it seems to be an offset (in X,Y,Z coordinates and meters) to the 'Position=' entry (also in X,Y,Z AC model coordinates and meters). I don't know why there is this offset instead of only the position value and I am interested to know if someone can say

Collision points are also used for contact with ground (take-off, landing) and ground objects (eg walls, buildings, not checked the details).

If I'm not wrong, "DetachWhenDestroyed=FALSE" is to be preferred, to prevent the hidden part to reappear when the aircraft is destroyed.

Sorry there was a typo in my post. maybe that. The full section as I would write it then: [Remove1] ParentComponentName=Fuselage ModelNodename=CowlFlaps DestroyedNodeName=CowlFlaps DetachWhenDestroyed=FALSE HasAeroCoefficients=FALSE With that it should work. I am not sure for the ParentComponentName but I will keep it as it is the usual case, and make sure that the parameter in this entry "Fuselage" is a real section in data.ini ([Fuselage] in data.ini, not a node in the LOD).