Jump to content

MYSE1234

ED Closed Beta Testers Team
  • Posts

    718
  • Joined

  • Last visited

Everything posted by MYSE1234

  1. A library with all (most) the RWR sounds, so you can attempt to memorize all of them . Link here The sound go from search -> track -> launch. Note that some radars only have one or two of those. Some are also not there due to them being outside the RWR's frequency range.
  2. A library with all (most) the RWR sounds. Link here The sound go from search -> track -> launch. Note that some radars only have one or two of those. Some are also not there due to them being outside the RWR's frequency range.
  3. EP13 isn't collimated, if we're going after how the game actually works, vs how it should work.
  4. The seeker optics are different in the B, which causes the sensor FOV to be half that of the A/T. The FOV is static and can not be changed like on the newer versions. Also it's not IR, but rather a TV (vidicon sensor) missile.
  5. It turns out it's correct in it being aligned with the horizon, it was just the illustration making it look wrong. Can be seen here in a SK37: https://youtu.be/E8Eom2shLyo?t=243
  6. Not if you're using an invisible FARP to "mark" it, then you have a reference code for it in the kneeboard.
  7. You can't. It's not coded to work like that in DCS, but it also doesn't matter for takeoff so... yeah It would be nice when landing though If you want one of the other runways you need to manually enter it on the data panel. The position of the waypoint will likely not be very accurate though, unless you change that too
  8. They're available if they want to use them. This goes for all my mods, I've made that clear to them
  9. Its due to the lines on the texture not taking into account the spherical shape of the surface they're on. It's fixed in my custom cockpit mod
  10. It's possible it's not mentioned in the DCS manual, just sounds weird if it's not, I've not really read it due to the real ones being available. The actual manuals does say it work this way though.
  11. Not a bug that the HUD symbology is hidden in NAV when the FPV is >±15°, and should be displayed again when it's <±12°. The bug here is that you can get it to display it anyway. Pretty sure the manual should say that this is how it works by design.
  12. I've not looked at the track, but you want to press 8 on the data panel not the B8 button as you seem to have pressed base on what you wrote. The waypoint indicator should say Bx8 directly after BX and 8 is pressed.
  13. U22 should emit in A and E according to the SFI. A is automatic mode - will pre-heat and emit, when hot and illuminated by radar B is pre-heat D is used when doing ground tests E is emit mode
  14. Yep, the whole thing. That folder is overwriting the default livery of the aircraft, and it's trying to find textures it's unable to find. Which is why you see the "no texture" texture on most of the aircraft. So removing the livery folder, or fixing it so it finds the correct files will fix it.
  15. Yeah, that's the one. Removing that folder should fix it.
  16. Hmm. Is the livery present in the saved games folder maybe?
  17. Looks like it's trying to find some textures named "F776_VIG_FUSELAGE_..." but is unable to find them inside the specified folder (f7 skaraborg). So looks like the "F7 Skaraborg" livery has been modified to me. The textures it's looking for is not default ones as far as I'm aware.
  18. That's what it says, no. Disregard the fact that it was edited a few minutes ago... thanks
  19. Did you wait for the mavericks to finish their warm up exercises after take off? Takes 3 minutes from when the nose gear lifts off the ground before they become functional.
  20. 760 is the QNH in mmHg, while the aircraft's altimeter is in hPa. 760 mmHg would equal 1013,25 hPa. All you need to do is convert it to hPa. I've never bothered learning how to calculate it, so not sure if you just need to convert the 760 and then do the same as mentioned above or convert the end result you got a using the above.
  21. Should be the same as far as I know. edit: There are some differences but it's largely the same. I'm not sure if it's because the aircraft was actually changed (probably not I think), their data was refined or just that the chart was remade more correctly. The AJS chart is covering a much smaller regime than the AJ's one, so I'd say the one above is accurate enough. It's unlikely the DCS AJS is that accurate anyway tbh
  22. @TOViper How does this look? I decided to color code it instead of using patterns like in the original, as we have the technical means to do so these days... I made sure to make it fairly colorblindness friendly too. If that website is to be believed.
×
×
  • Create New...