Jump to content

MYSE1234

ED Closed Beta Testers Team
  • Posts

    774
  • Joined

  • Last visited

Everything posted by MYSE1234

  1. New versions for both 2D and VR versions. A more accurate and functional version with more accurate positioning of the FOV, and the FOV now also follows the HUD glass. Also implemented a limiter for the "total FOV", anything outside 30° will be masked. Still sadly with the limited visibility with the HUD in the lower position, as I've yet to figure out a way to fix it. It's very close to being correct, but not quite. I'm personally using this mod, as the added immersion to me is well worth it. AJS37 realistic SI - 2D.zip AJS37 realistic SI - VR.zip
  2. New version (v2.85) for the people using VR. It will now change the default main menu, to a Viggen themed one. If you do not have VR you can still download this version, but you won't see any difference.
  3. Only partly, but I'll add on the "missing" bits.
  4. Try using the TRÅD button to communicate. I have a feeling it will work. The radios have gone a bit wrong ever since the radios were switched around.
  5. It's well worth it. It's going to change/help your livery making massively.
  6. I created a circular vector mask around the roundel in photoshop, and adjusted it to be just along the edge. That way you only get the roundel itself without the checkered background. After that you want to save the image as a format that can handle transparency, like .png .tga... Also did some very quick removing of the jpeg artifacts. It's not great but it's better that before.
  7. Can't remember off the top of my head. Looking video it looks like it starts from the previous fix?! Might also be that the pilot did not release to T0. If that's even a thing I'm not sure. But looking at the video one of the two is probably true, I'd assume the latter.
  8. I thought it was, but looking now I can't see anything about it. I'll get right to it
  9. It as known issue. Workaround is to set 0, on all waypoints in BANA/GRÄNS for the moment. Or just leave them there. It's for some reason loading 000 into BANA/GRÄNS by default, which results in that line.
  10. Known and tracked
  11. Looks like it's loading LS as the invisible FARP south of the aircraft. I'm guessing because it's closer than the airfield itself if that makes sense. I checked it by having LS selected, and switching to REF/LOLA and UT. There it said 903100, which is the REF code for that FARP. That together with the 000511 in BANA/GRÄNS told me it loaded the wrong code, but loaded something correctly. So to fix this I guess would be to either move it further away from the airfield, remove it or manually load 9001 as LS.
  12. Are you using "Ground start" or "Ramp start" in the mission? Ramp start seems to be working, while Ground start does not load LS correctly. Are you able to upload the missions?
  13. Reported all but No.2, as that one was already in there. Workaround is to set 0, on all waypoints in BANA/GRÄNS. Are you by chance using ground start? If so try using one of the ramp options to see if that works, I had success doing that. Workaround if that does not work is to manually set LS using the reference codes. No, does not seem to be fixed yet.
  14. There is, but it's not in DCS. Which reminds me... Give me 1 Minute It's however not for the gear itself, but for the gear lever. So it's not an emergency gear release in of itself. The normal gear lever is still used for that. The missing lever disconnects the electromechanical lock which limits the gear extension to below M0.65/ 620km/h. Which in my case the other day probably would have saved some scratches on the aircraft's belly. I had lost the pitot system so airspeed was pinned to the maximum, 1400km/h.
  15. You can indeed to this. It is now also possible to get shot such that the gear is not able to extend. I had that happen to me the other day, had to do a belly landing for the first time in a Viggen.
  16. The circle currently behaves a bit weirdly (it's in the bug tracker), and should indeed stay over the target after a fix. It should be display there until either the pilot changes destination, or prepares a new fix
  17. Get this updated, and it should alright again. Or remove the old version of it.
  18. Known and tracked. A workaround for the moment is to unsafe the trigger.
  19. Not all of them, "only" the texture for the text on the "DI" and "Data panel" is used as far as I know. Everything else is not, hence the continued work. But I like it this way tbh. I can just keep adding stuff that I find lacking or missing, at will. And if others enjoy it, I'll happily share it here. It was mainly for myself in the beginning, but saw no point in keeping it to myself. If I like it, others probably also will. Maybe not all, but some, and that's good enough for me.
  20. v2.84 Swedish NEW Sidewinder tone - now has a higher (probably more accurate) frequency of 1500Hz Dotted a few letters (Å,Ä,Ö) and some minor lighting changes. English SW tone, same as above
  21. According to THE manual, that switch should have no effect on the Bk90's. That does not however seem to be the case currently, because it very much does. I'll add this to the tracker. Below shows the switches that affect the weapon functions. .
  22. Give it a go, see if it makes the codes work. Because they definitely work for myself with that setup. Might not be correct, but that's a different problem.
  23. I think your problem here is setting it to STD. STD will set it to the standard value which is 921. I just tested it in VALB and the codes work as expected.
  24. The RWR lights not being very visible at night/ bad lighting is a known, and is in the bug tracker for the Viggen. For the moment, this mod of mine will fix it for you. And a few extra things.
×
×
  • Create New...