Jump to content

Drangoll

Members
  • Posts

    38
  • Joined

  • Last visited

Everything posted by Drangoll

  1. I've tried this but unfortunately it doesn't work for me Ngs remain at 0 (workaround tried at 6220 feet)
  2. I've tried selecting MRM , but the M function was still broken
  3. Had the same issue during the A/A pacs training mission. Left MFD was stuck on A/A radar and M (menu) function wasn't working properly Right MFD worked fine
  4. Yeah my bad , wrong photo there (adjusted now ). Anyway thanks for taking the time to collect feedback
  5. For the 3d model part imho what should be really reworked is the stick. Looks very strange and low quality in comparison to the real one and , generally speaking , to overall quality of the 3d cockpit. I understand this might not be top priority but , if you are updating the model , please consider a stick rework. In terms of texturing it would be great to have higher resolution textures on the external 3d model
  6. I agree. In general the heli's effects should be reworked. With all the desert maps we have things like brownouts should be represented as they drastically change the way you operate in such environment ( imagine landing on spot and you can't see a thing except dust. You can only rely on your instruments to touch down safely) They announced new helicopters effects a while back (2021 IIRC) but no news so far
  7. Tested right now at 46000 feet at mach 1.0. Missile reached a max of 3.27 mach at 64k feet
  8. Is it normal that the missile cannot even go beyond mach 3.1 when fired in optimal conditions ? I've read that the aim-54 achieved mach 4.3 at 24 km when fired in optimal conditions. I've seen multiple videos comparing phoenixes pre-update and post update behavior. When launched at 30k feet a mach 1.0 (sounds pretty optimal if not best conditions to me ) they reach mach 3.1 at best (reached 1782 knots at 63000 feet) Is this accurate or not ? Not trying to discredit devs work/research , just curiosity Thanks
  9. Getting the same FPS drop when underlaying tads. It happens on every map even with no other units spawned. I noticed it also happens when I'm in the CPG seat with TADS on the TEDAC Display. From the usual 50-60 fps i drop to 38-39 Will try to upload a track/video of the issue later My system : Windows 11 R9 3900X 12 cores cpu 32gb drr4 ram @3200mhz GTX 1660 DCS running on 6gb/s SATA SSD
  10. Found the issue thanks to the guys on Razbam Discord Server My TDC Axis with no deadzone were apparently wiggling imperceptibly constatly changing the position of the pod. Now with TDC Controls mapped to a POV Switch everything works fine.
  11. EDIT : Found the issue thanks to the guys on Razbam Discord Server My TDC Axis with no deadzone were apparently wiggling imperceptibly constatly changing the position of the pod. Now with TDC Controls mapped to a POV Switch everything works fine. EDIT 2 : APPLYING A BIT OF DEADZONE ON THE TDC AXIS CONTROLS ALSO WORKED FOR ME Hi guys, recently started learning the Harrier. Today I wanted to try and drop a gbu-12 on a moving target using the TPOD. I created a simple mission in the ME with an airstarted AV8B. When in the aircraft I go to the EHSD page to designate the waypoint (defined through the mission editor) and press "DESG". I then go to the right MPCD and select the TPOD page , finding the lightning correctly slaved to the waypoint. I press "Sensor Select Down" twice to go in TPODdes mode and then select MT mode. I start slewing the TPOD on the target but I immediately recognize its not picking up the moving target. Any idea why this is happening ? Am I doing something wrong ? Thanks in advance for the help. I've attached the miz mission file If you want to try it out yourself (syria map) Another video showcasing the same issue 2022-01-11 13-48-33.mp4 av8b laser guided bombs test.miz
×
×
  • Create New...