Jump to content

AlphaJuliet

Members
  • Posts

    374
  • Joined

  • Last visited

Everything posted by AlphaJuliet

  1. Hey, That's a rounding issue in the code, it is a known issue, we have been working with ED to try and solve it. Cheers
  2. Having to choose between taking a full DITER rack of JDAMS or sidewinders is part of the constraints of AV-8B operation, IRL, and now in DCS. If you are unhappy that such a fix would happen at this stage of the module's life, I'm with you, it would've been better if we had done it right on release. Plot twist we didn't. Am I supposed to let other bugs and inaccuracies in because some among the userbase grew used to them ? If given the choice between pleasing some and having the Harrier to have realistic specs, you know what I'll choose. Our end goal is to have the Harrier as realistic as we can. It'll take time, but we'll get there.
  3. This issue is mainly encountered when designating on coords where you haven't entered any elevation, or because of hardware drift. Have you sufficient deadzones on your slew axis ?
  4. Yeah It's a known bug, annoying as hell. Has been there almost since the beginning. We're working on it. Cheers. A.J.
  5. I absolutely agree, that's why I spent weeks researching what can and can't be mounted under the wings. These modifications are documented. They are respecting what can physically and safely being loaded and released from a 2015ish USMC AV-8B N/A according to the latest USMC authorised loadouts. I know it's a downgrade in quantities of bombs you can carry compared to what was previously allowed, but the previous loadouts were incorrect for our lovely Harrier, as unsafe to carry and release. Cheers, A.J.
  6. Hey, I've reduced the volume on all RWR sounds, that should come with next update. Cheers, A.J.
  7. Hello, This is a known issue, it's already fixed and ready to be shipped on next update. Cheers, A.J.
  8. Hello ladies and gentlemen, The changelog for the AV8B Harrier did not made it to ED for this update, here is what it contains : DCS: AV-8B N/A by Razbam - Fixed: Fuel boost pumps switch should be on for cold start - Fixed: RPS switch should be on for cold start - Fixed: AFT EQUIP switch should be on for cold start - Fixed: Anti-Skid switch should be on for cold start - Improved: Minor adjustments to dry engine performance based on hover performance checks for 0 datum engine - Fixed: Water loaded/unloaded in mission editor sometimes not taking effect properly - LOADOUT REWORK : See the forum post - Fixed: Rocket rippling -Changed : Can now change GBUs/APKWS laser codes and rocket pods modes with engine hot Apologies for the inconvenience. Cheers, Alpha Juliet
  9. WARNING : The 2015 date is mentioned as a reference to the documents used to build the authorised loadouts. No load is tied to a particular date in the DCS mission editor other than Eagle Dynamics already enforced dates. -Added AIM-9L (not on the USMC authorised loadouts for 2015-ish N/A, added because compatibility is known) for station 1,2,6,7 (as for the aim-9M) -Added 19 rocket pods (station 2,3,5,6) (not on the USMC authorised loadouts for 2015-ish N/A, added because compatibility is known), as a legacy from AV-8A and AV-8C, and day attack variants, and to roleplay british Harrier II's CRV-7 rockets. -Changed the GBU-12 500lb Paveway II loadouts according to the USMC authorised loadouts for 2015-ish N/A: -2xGBU-12 on D/ITER on cheek stations only are only allowed on stations 2/6. -2xGBU-12 on D/ITER on chin and cheek stations are not authorized. -3xGBU-12 on D/ITER are not authorized. -No loads are allowed on stations 1/7 if GBU-12 are mounted on D/ITER (double racking GBU-12s means no sidewinders!) -2xGBU-12 on D/ITER is authorized on stations 2/6 with tanks on stations 3/5 -GBU-12 mounting on stations 1/7 is not authorised according to the USMC authorised loadouts for 2015 N/A, but we let that possibility in to roleplay british Harriers (and these stations are known to accept dumb bombs, and the GBU-12 is authorised there on british Harrier II's. The loading of PWII kits is probably not authorised on 1/7 in the USMC pubs because it was not tested either due to lack of funding and/or need for it) -Changed the GBU-38 and GBU-54 500lb JDAMs loadouts according to the USMC authorised loadouts for 2015-ish N/A: -FYI : The JDAMs can only be triple racked on BRU-70 D/ITER triple racks. In DCS, only the BRU-42 ITER (non digital) rack 3D model is available. However, we simulate the use of BRU-70 to enable triple racking JDAMs, which are an important loadout for modern AV8B N/As. -2xJDAM on D/ITER is authorized on stations 3/5 only in a chin and cheek configuration (D/ITER mounting location closest to aircraft is empty) -2xJDAM and 3xJDAM on D/ITER is authorized on stations 2/6 with either inboard or outboard station full. -2xJDAM and 3xJDAM on D/ITER is authorized on stations 2/6 with tanks on stations 3/5. -Changed Fuel tanks loadouts according to the USMC authorised loadouts for 2015-ish N/A: -D/ITER authorized directly near fuel tanks -Bombs are not authorized on stations 1/7 with tanks on stations 2/6. -AIM-9 is authorized on stations 1/7 with tanks on stations 2/6. -Changed ITER 500lbs with bombs loadouts restrictions according to the USMC authorised loadouts for 2015-ish N/A: -On station 2 and 6, if the outermost cheek station of a D/ITER (BRU-42 or 70) is full, only bombs with regular fin kits (so no GBU-12) can be mounted on station 1 and 7 (meaning no sidewinder with a full triple rack)
  10. HOW TO CORRECTLY MAKE A DESIGNATION AND DROP JDAMS (to avoid dropping on your current waypoint) First, get into your sensor HOTAS mode: -SSaft twice (you will go throught the LST mode upon first press first, you'll see TV in the MPCD confirming you're in the right mode) - or double tap SSDown to go into TPOD HOTAS mode (confirmed by the TPOD writing in the MPCD) Find your target and designate it. To ensure good designation, always complete a T.A.C.L. : -TDC down (designates with the current sensor) -APS (name of the throttle button on the radar bird that fires the laser to refine coords, not always applicable. In the N/A, fire the laser using the OSB button) -Cage/uncage (not always applicable ) -Long WINC (will match steering and targeting cues) So now you have designated your target with the sensor you've slewed on it. ------ Now, the JDAMS, have two modes of release : JDAMs Direct Attack : Select the JDAMs in the store or EHSD page if you are in A/G master mode. Long press on the WPInc button or on the EHSD arrows to bring up the Quick Access menu. As you have a designation with the TPOD it will select TGT on the ODU and 0 will populate on the UFC, T0 will be selected between the EHSD arrows. The T0 is a peculiar target point, it stores the coords of the current designation. The entering in the QA ( Quick Access) menu will summon the Direct Attack symbology Your JDAMs are now in direct attack mode and targeting the T0 coords. You can slew the TPOD, the coords will be what you are designating through it. Master arm, pickle, one away. JDAMs Absolute Attack : You'll need to use a targetpoint from the system (you can of course use target points you entered manually). You can make one with the TOO. Push TOO on the UFC, then select tgt in the ODU, enter a number in the UFC (or leave the one displayed, it is usually following the last one you made), press enter, you just created a target using the designation source : the TPOD/DMT/System Des. You can now select the JDAMs, it'll bring the WPN menu in the ODU. If it disappears you can summon it again with the WPN UFC button. Push on TGT on the ODU, then select the target numbers on which you want to drop. Master arm, pickle, one away.
  11. Rate was fixed, for the ammo we need to ask ED to do some for us I think.
  12. For the Master caution and warning, You can dim them with the instr/warn dimmer switch, right console, towards the back. The Flood lights are terrible IRL, pilots rarely use them when sporting NVGs. Day/Night may need some adjustments, but with a bit of playing with gain, contrast, and symbology switches you will end up with a satisfactory setting, just like IRL. In the real thing just setting it to Night does not always mean it's setup properly for a good clarity depending on the actual thing displayed. If you have more precise interrogations about the settings don't hesitate to ask. The EHSD map is indeed hard to adjust for aided flights, I'll look into what can be done. I confirm the issue for the HUD FLIR, I'll report it. Cheers, A.J.
  13. In a year I reported more than 130 issues, bugs and feature requests, and about 2/3rd of them have been solved, so unless you got better figures than me, your claim is baseless. But yeah it still has bugs, and we're commited to tackling them.
  14. Mmh. Yeah a sound rework would be nice, we are aware that the module external sounds are not great. I'll keep you guys updated when we'll have the resources to work on it.
  15. Hello, known issue. Thanks for the report. Cheers
  16. That's weird, I have no issues setting up gain and contrast with the TPOD. Would you guys have a track so I can see what you're doing ?
  17. It's not really an overhaul of the module, it's a rebuild of the designation HOTAS logic. Something that is a bit of a pain to document and explain, so I get that he wants it to be done once and for all before tackling it.
  18. Hello Ladies and Gentlemen, We made a few changes to the F10 marks import to the CAS (Close Air Support) page, the Automated Target Handling System (ATHS). In the real jet, this feature is used to transfer CAS 9 lines (including target coords) from an USMC JTAC to a Harrier. In DCS, it is enabling you to import into the jet the coords of the marks labeled " #TPn " (n being a number) you make on the F10 map. You will then find those as lines in the RCALL subpage of the CAS page in your MPCD, you can affect them target numbers using the USE button on the MPCD. If done on the ground, the lines will be automatically affected TargetPoint numbers. Contrary to previous implementation, you don't have to put an empty mark before beginning to place your marks to be imported in the jet. Contrary to previous implementation, you cannot import other peoples marks to prevent confusions when importing points on a public server. We know some of you used it to share points from a human JTAC to a Harrier player, and we're working on making so that you have this ability again in the future, while still avoiding the loading of all the other others harrier points on the map at the same time. We also know some of you used it as a workaround to create flight plans when arriving on public servers and share it within your flight, and we're also looking at ways for you to be able to create waypoints that you could share in a similar way, on the F10 map. This is not done though, and may not come before a while. Just know that we're investigating in this area. Cheers, A.J.
×
×
  • Create New...