Jump to content

pvince

+PLATINUM MEMBER
 View Profile  See their activity

  • Content count

    108

  • Joined

  • Last visited

Everything posted by pvince

  1. 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.
  2. It is not the same, F1EM VI is the Morocco one, RMAF.
  3. 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 !
  4. So Hide1 section is correct but Hide2 and Hide3 have the wrong "ModelNodeName=" in the example above. Thanks for the confirmation !
  5. 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.
  6. Maybe I misunderstand the question but, the bomb bay opening with "O" also refers to a LOD animation, BombBayAnimationID= entry.

  7. Congratulations Coupi

    pvince replied to GKABS's topic in The Pub

    Congratulations Coupi !
  8. 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.
  9. 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.
  10. Actually not, not needed, just for info. What is needed is to avoid two sections "SystemType=WEAPON_STATION" with the same "StationID" number.
  11. 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.

  12. Merry Christmas!!!

    pvince replied to Wrench's topic in The Pub

    Thanks and Merry Christmas to all of you CA friends !
  13. "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.
  14. 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
  15. 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
  16. Collision points are also used for contact with ground (take-off, landing) and ground objects (eg walls, buildings, not checked the details).
  17. If I'm not wrong, "DetachWhenDestroyed=FALSE" is to be preferred, to prevent the hidden part to reappear when the aircraft is destroyed.
  18. 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).
  19. Use ModeNodeName=CowlFlaps

  20. Dassault Falcon 50

    pvince reviewed strahi's file in Other

    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
  21. 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.
  22. I have the F-4M
  23. I have not those aircraft on my install. But you can post the data.ini of them, I will try.
  24. 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.
  25. For Nation or AttachmentType, yes, UK is not a valid one. But for SpecificStationCode, you can use any characters string you want.
×

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

  I accept