Jump to content

Zeus67

3rd Party Developers
  • Posts

    3150
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Zeus67

  1. Hello folks. I hope you are enjoying the year's end festivities. Just a quick heads up regarding the AV-8B NA: Manual CAS Briefing will be enabled: This means that you will be able to enter CAS targets using the UFC/ODU. Targetpoints will be increased from 4 to 10: This means that the AV-8B NA will be able to hit 10 ground targets simultaneously with the JDAMs. EMER page will be enabled: This page displays procedure steps to be carried out during selected emergencies. Consider it an emergency pocket guide.
  2. We will enable the CAS Page editing function.
  3. Hello folks, here is the updated pocket guide with the instructions on how to use the JDAMs, including target selection. JDAMs are under testing right now but their release is approaching. :smartass: AV8BNA Pocket Guide.pdf
  4. Hello folks. Thanks for your advise. As always we need a track file so we can check the issue. Sometimes we are unable to reproduce the problem and this is where the track file comes into play.
  5. No. It is availble both in the ground and in the air. But when in the ground it will automatically assign the first four to the aircraft's targetpoints
  6. JDAM HUD Symbology Here is a sample of the HUD symbology that is used when JDAMs are selected: 1. The targets: Seven targets selected at an enemy airbase. 2. Target Selection Now we have selected four of them for JDAM strike. 3. HUD JDAM page The HUD symbology is based on real aircraft symbology. Selected targets are displayed below the range circle. The target list is always being sorted based on range, with the nearest ones being first. The center dot represents the position of the targets centroid. A centroid is the center of a geometric figure. In this case it is the center of the geometric figure formed by the selected targets. The center dot will provide steering cues for flying towards the centroid. JDAMs use a concept called Launch Acceptability Region, which is the area where the bombs can be released and expected to hit the target. LAR calculation depends on several parameters. The circle represents the Maximum LAR value. The small triangle represents the Minimum LAR value. Its position is relative to the maximum. The N indicates if terminal parameters (strike angle, heading and velocity) are not being used. If terminal parameters are being used then a T will be shown. Terminal parameters affect LAR values calculation. When there are several targets, the LAR values used in the HUD are for the first target in the list. 3. In range When the aircraft is inside the LAR the following happens: 1. Those targets that are inside the LAR are shown in a larger font. 2. An inner circle, indicating range to target appears. Its edge indicates how far inside the LAR the aircraft is Since ALL bombs will be released when pressing the circle it is best to wait until ALL targets are in range. SOP is to release the bombs when in the middle of the LAR. That is when the range cricle edge is exactly a the half position between the top of the circle and the small triangle.
  7. Hello folks. Some points on the JDAMs on the AV-8B (all versions). 1. No, It is not possible to input target coordinates directly using the UFC/ODU. 2. SOP is for the aircraft to fly with the JDAM targets loaded along with the flight plan when the aircraft starts. 3. Yes, you can attack TOOs with JDAMs. The process is a bit lengthy and do require overflying the target at least once. It also requires the TPOD. 4. JDAMs are always used in AUTO mode. There is no manual release mode. 5. JDAMs release cannot be configured by the pilot. All he can do is select fuzing method. 6. The AV-8B only releases on bomb per target. If a target needs multiple strikes, then several targetpoints will have the same position. 7. You release as many bombs as selected targets. 8. We used the CAS page because it is the only one that is documented. There are other ways to input JDAM targets on the aircraft but those are classified.
  8. The keyboard issue is solved here: https://forums.eagle.ru/showthread.php?t=245594
  9. Hello folks, The update has arrived and among the things included is the NVG. Unfortunately a mistake was introduced in the keyboard keybind file and DCS does not load this file and thus the keybinds are lost. Since this is a lua file, we can give you a repaired keybind file that you can use until the fixed on is released on next update. The file must be copied to: Mods/aircraft/M-2000C/input/M-2000C/keyboard. Overwrite the existing one. BTW, there is a small bug that was introduced at last time. When starting on the air, the GUN ARM switch is in the ARMED (Up) position now, but the guns are not armed. You must cycle the switch down and back up for the guns to be available. default.lua
  10. Zeus67

    PCA/HUD updates

    Last update about the changes. See the first post.
  11. Zeus67

    PCA/HUD updates

    I meant 10 and of course 11 is true since the radar does not change status at all.
  12. Zeus67

    PCA/HUD updates

    Our friends at the AdA made some corrections to my post.
  13. Zeus67

    PCA/HUD updates

    Hello folks, here are the news regarding the M-2000C updates: Pending review by our friends at the AdA, here are the changes to the PCA/HUD: 1. PCA and HUD are now independent of each other. So HUD mode does not depend on selected weapon nor master arm position. 2. Master Arm now just enables weapons release/fire. Setting to SAFE or ARM does nothing else. 3. HUD enters into AA mode when: Selecting CAN or MAGIC by using the HOTAS button, or by selecting Super 530D on the PCA. 4. MAG button on the PCA does NOT select Magic. It performs other functions. 5. Selecting an AG weapon will NOT set the HUD to AG ATTACK mode. Only the PCA will enter into AG mode. 6. To set the HUD, actually the entire aircraft systems, into AG ATTACK mode the pilot must click the PIP HOTAS switch forward (it is the same switch that sets the Special Modes when in AA mode). NOTE: The PCA must be in AG mode for the aircraft enter AG ATTACK mode, otherwise AA Special modes will be invoked. 7. With the HUD/Aircraft in AG ATTACK mode, clicking the PIP HOTAS switch forward again, will return the HUD/aircraft to NAV mode, but PCA will remain in AG mode. (To be confirmed) 8. With the HUD/Aircraft in AG ATTACK mode, clicking the PIP HOTAS switch back, will save the AG weapon selection and release parameters, return the HUD/aircraft to NAV mode, and the PCA will also enter NAV mode. (To be confirmed) 9. CAN and MAGIC can only be selected via HOTAS. 10. When selecting CAN or MAGIC, the radar will become active, even it the power switch is physically in the SIL position. 11. Upon deselecting CAN or MAGIC, by selecting PCA SELECT, the radar will return to SIL if the switch is in the SIL position. 12. Trying to select a weapon on the PCA when the system is in CAN or MAGIC modes is not possible (to be confirmed). Our goal is to have these changes ready for the next release. They are undergoing testing right now. Corrections to the above post: 3. Selecting POL in the PCA will also set the HUD in AA mode. 7. Unconfirmed. Clicking the PIP Forward after the system is in AG ATTACK does nothing. 8. Confirmed. The AG remains selected even if the PCA is in NAV mode. 10. Unconfirmed. Selecting CAN or MAGIC does not change radar status. Selecting SPecial Modes Forward or AFT sets the radar on EMIT if the switch is in SIL. 12. Confirmed. Final PCA/HUD updates after review by our friends at the AdA: 1. PCA and HUD are now independent of each other. So HUD mode does not depend on selected weapon nor master arm position. 2. Master Arm now just enables weapons release/fire. Setting to SAFE or ARM does nothing else. When the switch is in the ARM position the weapon code will stop blinking in the HUD. 3. HUD automatically enters into AA mode when: Selecting CAN or MAGIC by using the HOTAS button, or by selecting POL or Super 530D on the PCA. 4. MAG button on the PCA does NOT select Magic. It performs other functions: enabling the missile and starting MAV search. 5. Selecting an AG weapon will NOT set the HUD and aircraft systems to AG ATTACK mode. Only the PCA will enter into AG mode. 6. To set the HUD, actually the entire aircraft systems, into AG ATTACK mode the pilot must click the PIP HOTAS switch forward (it is the same switch that sets the Special Modes when in AA mode). NOTE: An AG weapon must be selected for the aircraft to enter AG ATTACK mode, otherwise AA Special modes will be invoked. 7. With the HUD/Aircraft in AG ATTACK mode, clicking the PIP HOTAS switch back, will save the AG weapon selection and release parameters, return the HUD/aircraft to NAV mode. The PCA will also enter NAV mode. The AG weapon remains selected. 8. CAN and MAGIC can only be selected via HOTAS. 9. Trying to select a weapon on the PCA when the system is in CAN or MAGIC modes is not possible. 10. Selecting AA Special modes will activate the radar, even if the switch is in the SIL position. Note: Selecting an AA weapon (CAN, MAGIC or S530D) will not change the radar status.
  14. Yes, that number is the altitude above the ground for which the cue must be aware of. The PUC does not appear at the selected altitude. It appears 9 seconds before you reach that altitude. It appears below the VVM and starts climbing towards it as you approach the selected altitude. When it reaches the VVM you are at the selected altitude. The PUC is used so you can plan your pull up and not go below the selected altitude. In other words, you must start climbing when you see the PUC move.
  15. Changes to chaff and flares cannot be done via rearm and refuel panel. You must use the kneeboard when in the ground and with the engine off. The reason for this is that the AV-8B NA loads the chaff and flares in packages of 30. So the kneeboard allows you to distribute these packages on the decoy bays. This is a recent update, so that is the reason why the manual does not indicate this.
  16. Yes, the fix is included in today's hotfix.
  17. How are you trying to change the amount of chaff and flares?
  18. Okay, just checked and fixed. The CTD happens when you input a number that is exactly the next waypoint to be included. If you enter a higher number you avoid the CTD. My fault. I checked [wpt number] <= [flightplan size] instead of [wpt number] < [flightplan size] I won't go into details but if [wpt number] is equal to [flightplan size] you get a CTD. So if you want to input a new waypoint, enter a number higher than the next one, the system will set the correct index.
  19. Next update. Today's hot fix only has the INS Alignment bug fix.
  20. Both the No distance to waypoint bug and the SEQ numbering bugs are fixed. The fix will be available on next update.
  21. The PULL UP warning is not controlled by PUC, which is the PULL UP CUE when dive bombing, but with the GPWS option. Click the ODU button that shows GPWS until the semicolon is not visible. Be warned that the GPWS will be disabled for 20 minutes only, it will automatically enable itself after the timer has expired.
×
×
  • Create New...