Jump to content

MYSE1234

ED Closed Beta Testers Team
  • Posts

    782
  • Joined

  • Last visited

Everything posted by MYSE1234

  1. It might be doable, but not sure if modding the module would be allowed. Very unlikely to be doable without some form of help Climb with full AB at M0.9, including acceleration from M0.55. X - time in minutes Y - Altitude in km
  2. Good to hear you got it working! Unfortunately no, it's one or the other with the cockpit mods.
  3. This is what you want your saved games folder to look like. Just dropping the folder into the DCS saved games folder should be enough to install it and enable it. If it does not work I'm not sure what could be the issue tbh.
  4. More F-4 radar! A video this time. https://twitter.com/HBSimulations/status/1667208929527382018?s=20
  5. The afterburner is already disabled when the reverser is engaged.
  6. It's not a mod. It's just a bunch of audio files so you can listen to the rwr sounds without doing it in-game; so you can attempt to learn all the sounds that mean you'll be a flaming ball of fire in the not-too-distant future. So there's not installing anything you just listen to the audio files, and enjoy the bleeps and bloops.
  7. No idea. What is this OpenMod you speak of?
  8. 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.
  9. 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.
  10. EP13 isn't collimated, if we're going after how the game actually works, vs how it should work.
  11. 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.
  12. 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
  13. Not if you're using an invisible FARP to "mark" it, then you have a reference code for it in the kneeboard.
  14. 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
  15. They're available if they want to use them. This goes for all my mods, I've made that clear to them
  16. 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
  17. Only in NAV and the landing modes it should do this.
  18. 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.
  19. 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.
  20. 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.
  21. 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
  22. 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.
  23. Yeah, that's the one. Removing that folder should fix it.
  24. Hmm. Is the livery present in the saved games folder maybe?
  25. 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.
×
×
  • Create New...