Jump to content

pvince

JAGDSTAFFEL 11
  • Posts

    154
  • Joined

  • Last visited

  • Days Won

    2

pvince last won the day on August 28

pvince had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

pvince's Achievements

Apprentice

Apprentice (3/14)

  • First Post Rare
  • Collaborator Rare
  • Dedicated Rare
  • Very Popular Rare
  • Reacting Well Rare

Recent Badges

139

Reputation

  1. Yes, and it was not the case in our previous releases. We'll be close to that in the next release (F1C-200 update in progress) and following.
  2. Thank you ! Comparing the sections, I see the same entries and seems to work the same.
  3. I have retested with F1 and yes, I also found the slats movement consistent with speed. Then I am wondering what the difference is between "AUTOMATIC_AERODYNAMIC_LOAD" and "AUTOMATIC_SPEED" if they both use speed. I have been through many data.ini but I have not found an example of "AUTOMATIC_SPEED" use.
  4. No, I confirm it is not G, thereshold too high. Example of Mirage F1 Slats: DeploymentMethod=AUTOMATIC_AERODYNAMIC_LOAD Setting[1].Angle=25.0 Setting[1].DeployValue=102.88 Setting[1].RetractValue=154.33
  5. For a speed, yes, but what I meant is that for "AUTOMATIC_AERODYNAMIC_LOAD" the thresholds do not seem to a be speed. I have tested it and the deployment/retraction are not at the corresponding speed in m/s.
  6. One remark, there is a deployment method for "HIGHLIFT_DEVICE" that is "DeploymentMethod=AUTOMATIC_AERODYNAMIC_LOAD" that I have not found in your docs, or maybe I have not looked at the right place. That's strange, because it seems to be a regular one. I was wondering the units for "DeployValue" and "RetractValue". We also have "MANUAL_WITH_BLOWBACK". "DeploymentMethod=AUTOMATIC_ANGLE_OF_ATTACK" is also valid and could be the correct syntax for AUTOMATIC_AOA
  7. Short feedback: using your explanations of the stall spin model parameters, we’re working on the mirage F1 improvement. That will be in the next release. Thanks !
  8. Here it is a cockpit function, a display, or light, in cockpit.ini, it is something else. How do you set Max_G for a plane ?
  9. Type=RADAR_LOW_VC tested successfully, only one threshold on absolute value, eg: Type=RADAR_LOW_VC NodeName= MovementType=LIGHT Set[01].Position=1 Set[01].Value=50 ValueUnit=KNOTS Tested Type=MAX_G, returns a fast decreasing cycling value, not understood at the moment. I've quickly tested "Type=THREAT_AZ_ANGLE" but always returns 0, even with RWR warning. May need further test. What could be "MISSILE_INTERLOCK" ? Quickly tested as a lamp in missile operation (lock, min/max range) but never went on.
  10. I have tested successfully: Type=COURSE_DIFFERENCE (difference to waypoint, +/-) Type=ECM_TRANSMIT (difference with ECM ??) Type=RADAR_AZ_ANGLE (+/-) Type=RADAR_TARGET_CLOSURE_RATE Type=RADAR_TARGET_RANGE Thanks
  11. Correction: LOW_ALT_WARNING_LIGHT works, tested ok on F1CZ_late. Syntax is slightly different than RADAR_ALTIMETER (one entry for threshold). With LOW_ALT_WARNING_LIGHT: [RadarAltimeterWarning] Type=LOW_ALT_WARNING_LIGHT NodeName=LightRadarAltLight MovementType=LIGHT Set[01].Position=1.0 Set[01].Value=500 ValueUnit=FEET With RADAR_ALTIMETER: [RadarAltimeterWarning] Type=RADAR_ALTIMETER NodeName=LightRadarAltLight MovementType=LIGHT Set[01].Position=1.0 Set[01].Value=499 Set[02].Position=0.0 Set[02].Value=500 ValueUnit=FEET At first glance the 2 functions give the same functional result and I do not see the difference for using "LOW_ALT_WARNING_LIGHT". Interested to know.
  12. My personal experience (cockpit.ini functions, Type=...): Those are new for me, never seen, never tried before: CONTROL_STICK COURSE_DIFFERENCE ECM_TRANSMIT ENGINE_EXHAUST_PRESSURE MAX_G MISSILE_INTERLOCK RADAR_AZ_ANGLE RADAR_LOW_VC RADAR_OBSTACLE RADAR_TARGET_CLOSURE_RATE RADAR_TARGET_RANGE THREAT_AZ_ANGLE THREAT_INDICATOR TURN_COORDINATOR TV_DISPLAY Those were known, but operational not sure: GYRO_COMPASS (never used) HYDRAULIC_PRESSURE_INDICATOR (never worked for me) LOW_ALT_WARNING_LIGHT (seems it works, but I have failed on F1CZ test, should retry) PNEUMATIC_PRESSURE_INDICATOR (mostly not operational) THREAT_CW_WARNING_LIGHT (never got it on, but difficult to test with sure conclusion) THREAT_GROUND_RADAR_WARNING_LIGHT (never got it on, but difficult to test with sure conclusion) Open to feedback from the others ...
  13. Most of them known but some new (at list for me): NIGHT_ONLY capability, FIBERGLASS material Also the full damage scale !
  14. Amazing Impressed by what we get and the power of the AI assistance there
  15. Very useful. Thanks ! Great work. With those new info on stall, I've put in my todo list to reopen the Mirage F1 stall model, that is not accurate currently.
×
×
  • Create New...

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