Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

34 Neutral

Profile Information

  • Gender
  • Location
  1. 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
  2. Collision points are also used for contact with ground (take-off, landing) and ground objects (eg walls, buildings, not checked the details).
  3. If I'm not wrong, "DetachWhenDestroyed=FALSE" is to be preferred, to prevent the hidden part to reappear when the aircraft is destroyed.
  4. 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).
  5. Dassault Falcon 50

    Thank you for the Iraqi 'Suzanne'. I have adjusted the weapon stations, because the right could not carry the Exocet, and adjusted height relative to pylons. see below. [LeftWingStation] SystemType=WEAPON_STATION StationID=1 StationGroupID=1 StationType=EXTERNAL AttachmentPosition=-2.87,0.0,-0.490 AttachmentAngles=0.0,0.0,0.0 LoadLimit=1600 AllowedWeaponClass=ASM,EP,RP,NP,RCN AttachmentType=NATO,FRANCE,ITALY ModelNodeName=RL PylonMass=108.9 PylonDragArea=0.06 ;;LaunchRailNodeName= ;;LaunchRailHeight=0.10 ;;LaunchRailMass=22.22 [RightWingStation] SystemType=WEAPON_STATION StationID=2 StationGroupID=2 StationType=EXTERNAL AttachmentPosition=2.87,0.0,-0.490 AttachmentAngles=0.0,0.0,0.0 ;;LoadLimit=453.6 LoadLimit=1600 AllowedWeaponClass=ASM,EP,RP,NP,RCN AttachmentType=NATO,FRANCE,ITALY ModelNodeName=RR PylonMass=108.9 PylonDragArea=0.06 ;;LaunchRailNodeName= ;;LaunchRailHeight=0.10 ;;LaunchRailMass=22.22
  6. 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.
  7. I have not those aircraft on my install. But you can post the data.ini of them, I will try.
  8. 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.
  9. For Nation or AttachmentType, yes, UK is not a valid one. But for SpecificStationCode, you can use any characters string you want.
  10. Does it work if you just remove the "IRM_UK" in the aircraft data.ini and the AIM data.ini ?
  11. 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 ?
  12. 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 !

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..