Caput_58

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.

That makes sense, thanks so much for the explanation.

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.

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.

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.

My experience has been that those random units are only triggered during transport tasks, not during assault tasks, no matter what you're flying.

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!

I've noticed low apu pressure after repair and restart, though the engines still start.

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.

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.

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.

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.

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.

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.

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.

The MOOSE stuff is pretty slick. It lets anyone call arty by placing map markers. It's also pretty easy to setup compared to the more complicated parts of MOOSE.

On further troubleshooting, it looks like this only occurs when I try to write a profile to 'All'. Maybe there is a bad path defined for one of the module kneeboard locations?

Was there ever a solution to the "value cannot be null" error? I see a few other people have experienced it when they try to change profiles. For what it's worth, I'm running in Admin mode, my DCS installation is in the standard location, and the config process has been done correctly as far as I can tell.

Can't speak for EMC, but I'm getting the error when using the SRS specific launch button. Haven't tested launching in any other way yet.

Hey Skatezilla, I'm still having issues with launching SRS from the app. Currently I'm getting an unhandled exception error, "The system cannot find the file specified." I've correct located the SRS directory, and the launcher button isn't greyed out. I've unchecked "launch as administrator" for srs, and added it to DCS Updater in case it was a permissions issue. I've also tried moving the SRS dir to C:\. I've double checked the config file, it reflects the current SRS directory, and updates when I change it. Other external apps, like TrackIR launch without a problem. Windows 10, DCS OB, latest SRS build, AMD processor, if that's any help. Thanks!

If I didn't work 4 days on and 4 days off, I'd be there. I just need to find a squadron that trains on an 8 day cycle...... You guys have some awesome training resources up on YT, I'd love to see some operational videos to get a sense of how it comes together.

Awesome, looking forward to it!

Hi Skatezilla, thanks for all the work on your fine app. Part of my interest in it is to use it to auto-start TrackIR and SRS. TrackIR seems to work fine, but I'm getting exception errors with SRS, stating that it's unable to find the file. I've correctly located the directory. TS3 and Tacview also works fine after locating the directory. I've noticed that the check box/radio button doesn't seem to be sticky for SRS, which makes me think maybe it's failing to save config info? I've tried combinations of running your updater and SRS as administrator just in case it's a UAC issue. Also, and this is totally a minor issue, the tooltips for Tacview and SRS are both incorrect (they refer to TrackIR). Thanks for any help you can give me

In his book, Dave Baranek mentions giving his pilot speed callouts while dogfighting so he doesn't have to take his eyes off the enemy. I'd love to see that implemented so those sneaky hornets with their fancy JHMCS won't have an edge on me in energy awareness.

I have two theories on this situation. One, HB can't comment, because saying "No, we're still waiting on ED and getting very frustrated." will only poison their relationship with ED. Two, ED intends to rework the missile guidance code, but it's all wrapped up with the implementation of TWS for the Hornet, or at very least will be implemented by the same dev when he's done with TWS. ED has been improving a bunch of long broken/simplified DCS systems as they implement stuff for the hornet, so maybe missile datalink and control logic is part of what is making Hornet TWS take so damn long. My followup question (that HB also probably can't answer) is "Will we see changes in stores drag anytime soon?". My understanding is that the Tomcat doesn't sees a decreased drag penalty from the AIM54's it carries in the tunnel, but that DCS models stores drag as a fixed value, be it on the pylon, semi-recessed in the plane, or in the air.