jubuttib
Members-
Posts
457 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by jubuttib
-
FWIW I don't think expecting perfect accuracy is a realistic target, but that's not to say anything about current accuracy.
-
I guess this is in relation to the Hornet, since the F-15E doesn't carry SLAM-ERs?
-
Not on the official and common sources of the official manual or Chuck's guide. Someone has made this tho: https://www.digitalcombatsimulator.com/en/files/3335132/
-
Some questions and perhaps frustrations with this module
jubuttib replied to Typhonus2's topic in DCS: AH-64D
This is said while keeping in mind that the FM and SCAS are both WIP: The SCAS currently has a slight tendency to kind of exaggerate your movements. The white diamond on the controls indicator is your input, the green cross is what the SCAS is doing, and you can often see, that right after you push into a direction, the SCAS is pushing into the same direction, increasing your input. I feel like this is one of the reasons why the helicopter feels more twitchy and unstable, any minor movement tends to get slightly exaggerated by the SCAS. On the Hip I've generally found the opposite, the AP system pushing away from the direction where you move your cyclic, damping your inputs. Been thinking of making a proper video out of this, but haven't yet gotten around to it. It could be on purpose, to make the helicopter more responsive to inputs, I dunno. I have also managed to turn the SCAS off a few times by pressing the wrong button (how do you turn it back on?), and have noticed that this turns the helicopter into more of a Huey in a sense. It's "less stable" in the sense that it wobbles around by itself, when no input is given, more than with the SCAS on, like the Huey tends to, but it's also slightly less sensitive to stick inputs. -
Join the club... In the Ka-50 I've tested against a Ka-27 a fair bit, and on one occasion it took 3 IGLAs (4th missed) and 7 Vikhrs (all hit) to down it. AI helis are indeed just ludicrously durable atm. Wish I was as impervious to damage in my Mi-8, but a single hit from an AK-74 has been enough to incapacitate my engines a couple of times...
-
Are you sure you're talking about "km/h" and not knots? 500 km/h is barely above the speed where you can put down your landing gear...
-
FWIW I made a test mission to try these out, and have mostly been getting consistently good result on the unitary bombs, including LS-6 variants. Cluster versions (so GB-6 and GB-6 SFW) are very inconsistent, and admittedly I have had a couple of situations online where my LS-6s didn't behave.
-
Damnit, forgot to list that. Putting the TGP on a target with a helmet is one of my favorite things about HMDs on the planes that have them.
-
Heya, just trying to figure out whether this is the current expected behavior, and whether it's intended to be final. When you use the SLAM and SLAM-ER missiles on the Hornet, they do the sensible thing and point towards the target area when they're in the terminal phase. FWIW the following is with special settings as MITL Control Mode Traction, TDC Deadzone 0, DL Pod TDC Slew Rate 1, and 25 curve on my throttle's analog ministick, throttle is STECS. By contrast the CM-802AKG seems to be flying level, regardless of whether you select skim or pop-up as the terminal guidance type (probably doesn't work on purpose, being just a carryover from the anti-shipping missile days). If you're medium or high, you need to crank down the nose of the missile MASSIVELY to point at the target, and during the maneuver you basically lose all visibility. Just kinda gotta hope you can reacquire the target afterwards, and that you were pointing in the right direction overall (which thankfully is at least usually the case). Is this expected behavior? Something to be fixed? The TDC controls are also a bit weird. You need a LOT of input to create any movement (there's a huge deadzone), and then it turns very quickly, so getting it to accurately point at a target is quite challenging. In addition if you let go of the TDC input quickly (like if you were to flick the stick, for example), the input doesn't always center properly, so you can end up with the missile constantly veering to the side after inputs. So all in all you when you get control you: Can't see the target without cranking the nose down (unless you're flying very low level and are lucky), which makes you temporarily blind, and you have no guidance on how much you need to point down You have a huge deadzone to start with, so you wanna push the stick quickly to get past it If you do that, you'll very easily run over the slower section of the input range, making tiny corrections really difficult Even if your input is very gentle, the minimum amount of movement is quite a lot, so it's hard to prevent turning too much If you just let go of the TDC and let the stick snap to center on spring pressure, the TDC won't always center properly, and the missile will keep veering to the side This "minimum input is really high" problem doesn't happen with the radar, TGP or any other sensor for that matter, AND it doesn't happen when the CM-802AKG is set into "Designate" MITL Control Mode. I can move the seeker around with ease and accuracy using that mode. It's however a bit iffy when used from high altitude, since the dive down problem still exists, so you do want to be low down to use it. Again, expected behavior? Something to be fixed?
-
Yeah, and the Soviets got their kickstart from the South Africans, who (afaik) were to first to field an operational HMD with offbore capable missiles (probably not very high offbore tho) in their Mirages.
-
Yes, hence the first sentence: "The Hornet and Jeff both have datalinked man-in-the-loop cruise missiles" EDIT: Man I hate that this converts smileys into emoji, is there a way to turn that off?
-
Bah, TGP and ECM hardpoints first, way more important than the HMD. Then HMD, then forward facing MWS, you can keep the new UFC. Meh, I get more use out of the situational awareness that HMDs provide than I get from pointing heatseekers with them.
-
Huh, so I guess THAT'S why I had to bomb a command post 6 times before it blew up...
-
The Hornet and Jeff both have datalinked man-in-the-loop cruise missiles, though I'll readily admit that Hornet's implementation seems more effective. But overall I think Jeff takes the cake, because it has LS-6 glide bombs*, AND the by far most effective, at least against any kinds of units, A-G weapon in the game, the GB-6 SFW**, and you also get the GB-6 HE unitary bomb, same delivery vehicle but one big bomb (1500 pounds total, so guessing about 1000 pound bomb weight). JSOW-A in the F-15E, F-16C and F/A-18C are indeed really disappointing, and that applies to the basic GB-6 from the Jeff as well, which is effectively the same as the JSOW. *Basically winged JDAMs with potentially 40+ nautical mile range, come in 250, 500 and 1000 pound classes, or 100 kg, 250 kg and 500 kg, the two smaller ones can be dual racked for a total of up to 6 very long range bombs in the 500-1000 pound class. **Basically a winged, GPS guided CBU-97/105 with even more pucks on board and a range of 30+ nautical miles.
-
Smart weapon desync issues in multicrew still happening
jubuttib replied to jubuttib's topic in Bugs and Problems
And FWIW, wouldn't be talking about this if the 19th December openbeta changelist didn't have the following: Added: Smart Weapons MC Synch -
Ah, good call, that'd explain the two moving at different speeds.
-
Fwiw I'm the WSO, and neither of us know enough about the plane to do that on purpose at any rate, and I'm pretty sure I saw PP-EGI on the UFC during the flight.
-
Smart weapon desync issues in multicrew still happening
jubuttib posted a topic in Bugs and Problems
Tested with JSOWs, GBU-31s and GBU-54s thus far. If the rear seater hits the "XFR RDR" (or TGP etc.) button to transfer the co-ordinates to the smart weapon, the bomb still shows up as uninitialized for the front seater. Likewise if the front seater does it, it shows as uninitialized for the rear seater, there's no syncing in either direction. This also extends to the HUD, if the rear seater sets the bombs up, the front seater doesn't get any heading guidance for delivering the bombs. Rear seat HUD repeater after rear seat setting targets: Front seat HUD at the same time: Track file added. EDIT: Can't add track file because it's too big. =P -
OK, confirmed that smart weapons that get co-ordinates from the front seat don't sync with the backseat, and vice versa. So whoever sets the co-ordinates into the weapons has to also fire them. Also saw a worrying thing with regards to navigation accuracy, the front seater's TSD/moving map stayed perfectly aligned, but even on a short flight my TSD on the rear seat went completely out of whack. Some of the bombs also went off target, so I wonder if it's something like the INS drifting badly for the rear seat, not getting updates from GPS, while front seat is OK... Here's front seat TDS: And here's my rear seat TDS at the same time (roughly): They're not even in the same area code. And mine kept shifting all the time, this was taken 2 minutes an 3 seconds later (timestamps on screenshots):
-
Heya, just wondering if there's a consensus atm. on what works and what doesn't in multicrew properly. For example in today's session with a buddy we had quite a few issues, some unrelated to the F-15E itself (like FFB issues, which got sorted with a game restart), and I was just wondering whether they were supposed to work or not. Main ones that we ran into were that apparently no targeting data was being transmitted between the seats, nor were smart weapon targets synced at all. On our first run at a target I set up 3 targets for GBU-31s from the rear seat using the radar, and got all the targeting cues etc. on my HUD repeater, but the front seater got nothing. Weapons kept saying "NO ZONE" on the HUD, heading tape didn't show where to go, nothing. Eventually I requested control of the plane, dropped the bombs, and gave control back. Second run we tried to do the "rear seat designates, front seat transfers co-ordinates to bomb" method. I designated two different targets for him, and he uploaded them on his end, but they didn't actually show up on the smart weapons page for me at all, the bombs kept saying INIT. I then set a couple more targets to the bombs he didn't try to program myself, and those showed up as expected. When it came time to do the drop, he got one bomb off, then the system cycled to a station that wasn't even in the weapon profile (profile had just the CFTs, after the drop it cycled to the centerline station, which was already empty). I had to again take over, and drop the rest. Couldn't drop the second one that he had tried to program, since it was showing as INIT for me. Included images of what his HUD was showing him, and what my HUD repeater was showing me.
-
FWIW, and I don't know if it's straight up compatible with this specific implementation, but with the ALPS switches I've also been able to use Joystick Gremlin to make it so that the push-in function only sends a button press when no direction is held (four IF conditions). Potentially an option if you don't want to figure out how to get the PCBs made. EDIT: Outside of that, great job as always TSN, love your stuff.
-
Currently it seems like the radar doesn't work in Stable, need to be in OpenBeta.
-
I'll start looking into it, definitely. I sometimes visit my buddy there, so could probably pick it up from his place. FWIW I'm not going to order it for at least a month or two, so no hurry.
-
Drat. How about Denmark?
-
Sorry haven't been checking the forums: The sound was fine when just using the radio in game, there's something weird that happens in the test.
