Jump to content

Caput_58

Members
  • Posts

    50
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. From what I just read (Arab Mig-19 and Mig-21 Units in Combat), Syria retired their surviving Mig-19's after the Six-Day War, sending what was left to Egypt.
  2. That makes sense, thanks so much for the explanation.
  3. I'm either misunderstanding or the manual is incorrect about radar elevation. I had thought that E mode was elevation in degrees, whereas D mode outputted a height difference in thousands of feet at cursor location. The behavior I'm seeing for that is reversed though. In E mode, the number changes as you move the alidade closer/further, and can get very very big when you're at distant ranges (+/- 99). In D mode, the value doesn't change with distance and seems to correspond to the hard stops for elevation in degrees. The stop seems to be at +/- 48, though I gather from the manual, it should be +28 or -32. Actually, those stops are what we should see for D (+/- 48,000ft), so I'm really not sure what's going on.
  4. I had the same problem, though with just a few textures missing. I was at a loss after a repair failed to fix it. Deleted the saved games liveries file and everything is better. Thanks for the thread.
  5. Just wanted to add my +1 and say, please please let me make and use custom map files. Specify the resolution and graphic format, and let me fill a folder with image files that I can then flip through and use. This way I can have maps cut where it makes sense for the route, I can choose to have overlap between adjacent maps, and I can choose to mark up maps as I desire to indicate flight plan, or enemy concentrations, or whatever I choose. For bonus points, let me update this folder dynamically, so once I'm already playing I can swap in and out files as a mission changes.
  6. My experience has been that those random units are only triggered during transport tasks, not during assault tasks, no matter what you're flying.
  7. Any chance of making the Mi-24 eligible for transport missions? I tried to do it myself but adding them in in options.lua, but I'm obviously missing something. Thanks!
  8. I've noticed low apu pressure after repair and restart, though the engines still start.
  9. I'm seeing the same at the moment, can rearm the UH-1H fine, can rearm the MI-8 via loadouts fine, just can't rearm by station.
  10. Same problem, running with 40gig RAM, and SSD with very large page file. For what it's worth, before this, I had problems with each station having a smaller episode of lag when trying to change weapons. This one time stutter on entering rearm is tolerable, though it occasionally throws off the auto-start script for aircraft, and I can't help but wonder if it is related to the other mystery stutters I'm now seeing.
  11. That seems strange. Point tracking is a contrast lock, why would laser masking make a difference? And if the laser does matter, wouldn't I be unable to point track of my laser is off? I'd be happy to submit a track or some footage if I'm not being clear.
  12. Point track doesn't seem to work if the laser is masked, or if it does, it works under much more limited conditions. If you turn back towards the target, the moment the laser is unmasked, point track can grab on again. My experience has all been on the Syria map, just in case it's map dependent.
  13. I think it's built in to SRS since 1.9. It's called "re-transmission" or relay. I haven't toyed with it yet though, so YMMV.
  14. I get the same, in non-VR. Stutter also hits when changing loadouts in mission editor. It's been a thing for a few patches now.
  15. I came here looking for a thread just like this. Someone needs to nudge ED into making FARPs work as areas, rather than objects that aircraft need to be touching. HB seems like the best advocate for this since it's so central to the Viggen.
×
×
  • Create New...