Jump to content

AlphaJuliet

Members
  • Posts

    377
  • Joined

  • Last visited

Everything posted by AlphaJuliet

  1. Hey, Issue reported, but could take a bit before taken a look at, it's low priority compared to our other bugs. But we'll get there Cheers, Alpha
  2. Hey, Issue reported, thanks for the report Cheers, Alpha
  3. Hey, Issue confirmed and reported. Thanks for the report, Cheers, Alpha Juliet
  4. Hey, We've seen this, it should be fixed for next update, give me a heads up if not.
  5. Hello, The gunpod indeed has quite a few limitations : As it's powered by 8th stage compressor bleed air, it cannot function below a certain number of rpm (read, under a certain bleed air pressure. This vary with altitude, but is around 70%RPM). Also, in hover, ingestion of fumes generated by a negligent discharge of any kind of weapon would drastically diminish the quality of the engine combustion and thus its performances. In these phases of flight, it can result in a crash that to lose your thrust, that's why weapon employment is limited to Nozzle angle > 30°. Cheers, Alpha
  6. Hello @Sylosis, We would have loved to make it right and spot on in the first place, but unfortunately we lacked some documents or SME's intels concerning some systems, and tried our best with whatever source we had available. Concerning your issue : As a general rule of thumb, the Harrier always need a designation on the target to give you proper delivery computing. Know that the used sensor will have an influence on the quality of the computing (for example, designating in INS mode with a drifted INS can give you wrong computation). This aircraft does not have a Radar, and can therefore not really give you continuous computation if you're not telling the system where to look. For a gun run for example, you don't really need to put the designation right on the target, putting it in the general area at the same elevation is usually enough. In the current Open Beta you can undesignate in TPOD mode, as well as any other designation mode, with the NWS button. In stable it may be different and you may need to go into INS but that's a bug, as it's fixed in the OB, it should make its way to stable in no too long. Cheers, Alpha
  7. @Penguin314 Could you also post a small track of you having the issue ?
  8. Hey, Bug reported in our internal bug tracker. Thanks for the report ! Cheers, Alpha
  9. Issue Reported in our internal tracker. Cheers, Alpha
  10. Hey, The T0 should be present in the EHSD as soon as a designation is made, and updated as the TPOD moves, in whatever tracking mode it is. The current T0 system is indeed not correctly implemented , we will work on improving it. This issue is reported in our tracker. Cheers, Alpha
  11. What in hell is that x) It's quite strange, i'll transmit it to the devs so that they can have a look. For tracking purposes, i'll move the post in the problems and bugs section. Alpha
  12. Hey @Kappa, It's the same version that was updated not long ago in our Discord.
  13. Hello, what @Vakarianis describing is the right procedure to apply to use target points. Know that you cannot erase the tgt input into the EHSD, but you can overwrite them by assigning the numbers already used in the EHSD to new lines in the RCALL page, using the USE OSB button in the CAS page.
  14. Hello ladies and gents, The Mirage III is currently going through 3D modelling to be used as an AI. It is too early to say in what asset pack or map it will be a part of, and if it will become a full module, and when. Cheers, Alpha
  15. Good afternoon (CET), This bug is known, confirmed and reported, and is in our bug priority list. Cheers, Alpha
  16. Hello, Thanks for the track, Investigating the issue
  17. We un-superposed the superposed letters so that now they are more readable because they are not superposed anymore
  18. Hello ladies and gentlemen, As you may already know, @baltic_dragonhas been working hard to deliver an updated version of the Harrier manual, and we are pleased to show you a preview of the first 15 chapters, that you can consult here : https://drive.google.com/open?id=1EgocwCHBSZN6nhcXL-r4SQH14Z8BQtDu&authuser=wojciech.danecki%40gmail.com&usp=drive_fs Bear in mind, this is still a WIP version. We are open to any suggestion of improvement or modification, and you can post them as comments to this post or directly in the dedicated channel on our Discord. Cheers, Alpha
  19. Interesting, no mention is made to that in the NFM version that I have, it just says to cycle the DATM to input the MAGVAR
  20. It is to input the local magnetic variation
  21. ED should provide this sort of functionnality with their new IR model. There is nothing we can do about it right now. Cheers
  22. Hey, You can follow this tutorial : https://wiki.hoggitworld.com/view/Exporting_MFCD_Displays And also know that there are binds for you to activate the screens export (something like "toggle HUD/MPCD export")
  23. I've also had cockpit lighting issues (especially under the clouds shadows), so don't hesitate to ping me if it comes back. Cheers
  24. Thanks for the kind words. I get what you mean, but know that I try to report even the smallest issues and bugs to iron out the Harrier the best we can. Just know the we currrently have a lot (and i mean a LOT) of small bugs to fix, some easy some not so much, and they are affecting the gameplay more than the visor issue. So, this bind will be renamed at some point when we will work on the missing or broken binds, but that's not a priority at the moment. But don't worry we'll get there
  25. Seems like a mission bug or a DCS thing, investigating.
×
×
  • Create New...