pvince

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.

1 hour ago, logan4 said:

stationID-s should be seqential, not 1,28,2,3,5,6,7,10,11,etc

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

Use

ModeNodeName=CowlFlaps

BTW, F-4K is RoyalNavy right ? and your missile is RAF. Then you need Exported=TRUE, because for the game, RAF and RoyalNavy are not the same Nation.

I have the F-4M

I have not those aircraft on my install. But you can post the data.ini of them, I will try.

I have to correct: "RAF" for Nation, but "UK" code for AttachmentType is correct. Sorry for confusing.

For your problem, if the couple (aircraft,weapon) works without SpecificStationCode, it will work again if you apply the same SpecificStationCode in both. If not, make sure you have it on the right weapon_station (for example test with a "StationGroup" that has only this one in, and disable the loadout.ini, so that no doubt), or no typo.

For Nation or AttachmentType, yes, UK is not a valid one. But for SpecificStationCode, you can use any characters string you want.

Does it work if you just remove the "IRM_UK" in the aircraft data.ini and the AIM data.ini ?

9 hours ago, Menrva said:

AI makes use of guided bombs, while in the old days they wouldn't and dumb versions were required

I just tried on a stock install with F-4E and LGB and my wingman could use successfully GBU-12, on a target that I assigned, not the mission target. I have also tried with the super-etendard mod, atlis +LGB, also ok. What is the problem with the LGB and AI ?

On 31/03/2022 at 11:13 AM, mue said:

Yes, this workaround is required because the author of the LODViewer was to lazy to implement this feature into the tool. Maybe he will find some time (and motivation) in the future .

Not needed, we have to way to check without running the game, which is the purpose of your great tool.

But if you really want to go back on it , I have more needed suggestions: add pilots and seats (position adjustment) and moreover weapons (same, attachment adjustment) 

For the last one, for example, it could be according to a 'debug' [LODviewer] section in the loadout.ini !

On 22/08/2021 at 6:53 PM, pvince said:

Fill the attached file with the cockpit name you need (Filename=XYZ_cockpit.LOD) and open in LODviewer

Visu_cockpit.INI

thank you, but to be honest I am not the "inventor" of this, I have learned it from another modder in a former post, but I do not remember from who and when. So the credits go to the one who discovered this first, I am just repeating here, but I'm happy if it helps.

On 18/01/2022 at 6:54 PM, EricJ said:

I think you need SF2: NA for that to work.

Very probably yes, I confirm I have SF2:NA and I am quite sure it will not work without.

Another solution is to use those files in your [mod folder]\Terrains\VietnamSEA. Then USN will launch from carrier by default.

VIETNAMSEA.INI

VIETNAMSEA_WATER.BMP

Shift return