ShuRugal

From DCS.Log: 00098.519 ALERT EDCORE: Can't execute Lua file D:\Users\ShuRugal\Saved Games\DCS\Scripts\Export.lua - can't open 'D:\Users\ShuRugal\Saved Games\DCS\ScriptsTacnoworld_UR_DCSW.luac'

I just wanted to chime in here and voice a problem that BSD has been experiencing. Since DCSW 1.5.5, we cannot connect in UR. The UR plugin in TS shows the red Not connected status for several of us.

What pepin said. the 9M119 is fired through the bore of the cannon, there are no shells loaded when firing missiles. If you switch from missiles to shells, you have to wait for a shell to load. Since the cannon must be fully depressed in most tanks to reload, you would also not be able to use the coax, since it is dependant upon the main gun for aiming.

Interesting rig, but I already see one serious problem with it... You have no pitch axis. Therefore, if you set it to do what you are describing, then you would end up hanging upside down in your chair after an immelman, split-s, or any other partial loop and partial roll combination. The problem isn't that DCS has invalid motion vector outputs, it's that you rig has incomplete axiis. If you had pitch and yaw gimbals to match your roll gimbal, it would work the way you want it, but with only the roll axis simulated, it has a built-in failure.

That actually makes a lot more sense. Ease of maintenance is definitely a top priority for anyone who has to import their military hardware.

According to wiki, the m-61 w/ complete feed system is 248 lbs. umm, that's kind of my point? if the M-61 w/feed is 100 lbs less than 2x m-39 with feed, then that's 100lbs more ammo you can carry (~ 175 rounds of PGU-28, probably only ~150 after expanding the drum) both are 1.8m long, and the radial bulk of a single M-61 is certainly less than a pair of M-39s on the M-39? but if it is filling a larger area with fewer rounds, then the saturation is significantly lower, thus reducing the effective range of the weapon.

hell no, Saitek software is absolute garbage. For an example of what i wanted to achieve, install the file i posted (JSGME compatible) and have a look at the "Weapon Status Panel PUI-800" section. Note how in addition to things like "master arm on/off" there is now "master arm on" and "master arm off". Or under systems, SPU-9 Radio Selector now has VHF-2, VHF-1, SW and Ground Crew as options. Eventually, I will do this for all the switches and post it to the mods section.

Does anyone know what reasoning lead Northrop to select a pair of M-39s instead of a single M-61? The two M-39s weigh ~360 lbs, and have a combined RoF of only 3,000 rounds/min. Comparatively, a single M-61 weighs ~250 lbs, with a RoF of 6,000 rounds/min. Just seems odd. With an M-61, that extra ~100 lbs saved vs 2 M-39s is over 150 rounds of ammunition, AND the M-61 will deliver more rounds on target per burst. The only drawback is higher ammo consumption rate, but that can easily be managed by using shorter bursts or programming lower rates of fire for the pilot to select.

Right, got discrete bindings added and working in all of the PUI-800 panel and the SPU-9 selector. Will do more when I feel like doing more head-smashingly dull copy-paste work. In the meantime, anyone who might want their PUI-800 and SPU-9 working correctly can have fun with this. KA-50 Discrete Switches.rar

found what i needed, i knew i'd read it on here somewhere before. now, to work! https://forums.eagle.ru/showpost.php?p=2440800&postcount=141

not trying to make a cockpit, i just want to use my X55 rotary knob as a radio selector

I have read thread on setting up toggle switches, but it describes the opposite of what I wish to do: I wish to set up commands to flip switches to discrete positions. IE, instead of "SPU-9 change position" I want "SPU-9 VHF2" "SPU-9 VHF1" and "SPU-9 Interphone" Digging at the LUA files now, but I don't even know where to begin to look to find out what the icommand for each discrete state should be

Off the top of my head: At lower approach angles the differences in height on the aircraft between laser, HUD aimpoint, and rocket pods all add up to a significantly greater percentage of angular error than at higher angles. This is further compounded by the fact that at low angles, the same percentage of angular error will generate a vastly larger ranging error. Now, take all of the above, and factor in the fact that at a low approach angle, your speed over the ground is higher. This means that the delay between when your eye sees the aimpoint line up with the target and your finger presses the trigger results in you covering more ground, introducing more angular error into a situation that is already extremely sensitive to it. TL;DR: making a low angle rocket pass is literally setting yourself up for failure. The only time you should do this is if you want to saturate an entire column in a single pass, then the range error works in your favor.

sure, if we're talking individual rounds those numbers might be more accurate, but a salvo of S-8s will easily spread out over 100m. I did screw up specifying KoM instead of OFP, though. whoops.

So, I realize that this might be a bit of a long shot, but nothing ventured etc... I will be separating from the Army in January, and I would like to find a way to use my GI Bill to obtain flight training, with the goal of earning a rotary wing commercial rating. I was wondering if there was anyone in the community who could help me locate a good school to attend which has a relationship with the VA and is approved for GI Bill benefits. Ideally I would like to find something in Virginia, which is my home state. Thanks in advance!

the real life 9K121 has a blast-fragmentation jacket around the main charge that allows it to simultaneously kill soft targets while penetrating an armored one. This jacket does a very good job of shredding aircraft. Unfortunately, DCS does not model fragmentation effects, so the effects of all explosive weapons against soft targets is vastly under-represented. For example, a shower of 30mm HE or a salvo of S-8 KoM in real life would kill every un-armored living thing within ~100m of the center of the impact area. In DCS, however, a direct hit is often required.

according to wiki "The result is that for the cost of one equivalent Western model, the Soviets could build five." Unit cost of AGM-114: $110k Estimated cost of 9K121: $22k. So, basically, you are taking out a valuable airplane or helicopter by shooting it with a Honda Civic.

Best advice is "Don't". With the current states of missiles in DCS, an F-15 can kill a flanker from safety in BVR 100% of the time if the Eagle driver knows what he is doing. Best tactic is to leverage your potentially superior SA and sneak in close. Failing this, you could try what Holimoli laid out and see if you can keep enough missiles in the air to keep him busy long enough for you to merge. However, a competent Eagle driver who keeps his cool can defeat every ER and ET fired at him without ever taking a defensive posture, while knowing that you will have to work harder to avoid his 120. IMHO, the best way to survive BVR in a Flanker is to deny that fight to the Eagle. Until the R-27 family remembers how to track targets, and until the missile drag problem is solved, the Flanker has no weapons which pose a significant BVR threat to an Eagle.

Not quite true. The Su-27 ASC will mix in some rudder with aileron, but will not hold a coordinated level turn for you. Watch the ball indicator when you turn: you will still need to step on the ball a bit to keep it centered (just not nearly as much as, say, the P-51)

at each waypoint in the fam-flight mission, you should hear your "wingman" talking to you, including instructions on when to RTB and land. If you don't you missed one.

Unfortunately, A2A target spotting has always been this sim's biggest shortcoming. The addition of the ranged-scaling option has helped, but it seems to me that it takes effect too far away to be actually useful in a knife fight.

I concur with Isegrim. I had an X52, then a Pro, Now I have an X55. I used to use SST, I had it set up so that when i pulled stage 1, it fired from the pylons, and stage 2 automatically switched to guns and fired. This worked briefly, but started causing massive framerate problems, would drop to 1-3 FPS every time i tried to fire guns. wiped it out and never looked back. With the X55, I have a profile i manually edited in notepad++ to remove all shift-state and switch modes. I bind everything inside DCS, including shift states and the switch knob. No more SST problems.

DCS: KA-52 CONFIRMED!!

yes, it is an industry standard. "An", not "The Only". :surprise: Either I've died, or PT this morning was worse than usual and I'm <still> hallucinating. :suspect:

good point, I should have considered that, since DCS relies heavily on single-thread performance. I'll tweak my numbers later this evening.