

Hyperlynx
Members-
Posts
73 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Hyperlynx
-
Yes mate, it does. As Specter has explained, the missiles behave like that in real life, they are genuinely bad and difficult to aim. DCS faithfully, correctly simulates what is a bad missile in real life. Read his posts again, he says that real pilots also struggle to designate the target, that it's actually one of the most difficult weapons to use in the Viper's inventory
-
That's very interesting to hear that they were usually used in BORE mode! I'll have to look into practicing that.
-
As it happens, my curve was 30 something, though I had the ends chopped off. I've set it to 35. I'll also try those precision rings you mentioned, specially since they make it closer to the real thing. Cheers.
-
Because to do that you have to boresight them first, and to do that you have to get a lock, and that's hard to do with the crappy sensor and the crappy slewing. Not to mention, boresighting only works for the exact range you were at when you applied it. If you're further out or closer in, it'll be off.
-
I see. So they genuinely are crappy, and the solution is genuinely to reduce sensitivity of the axes
-
I don't remember if I was pushing the TGP as hard as I could. I feel like I was using very gentle motions for both, at least when trying to line up the target at the end of the runway. For what it's worth, I'm using a WinWing Orion 2 throttle with F-16 attachment. Anyway, the thing is, they should be slewing at the same rate regardless of what my axis settings are
-
Finished the mission, got home, parked, the logo came up and the music played, but the briefing stayed the same as before I launched. Track file is 70mb and too big to attach, so I have uploaded it: https://drive.proton.me/urls/CGZFXKAYER#7QMy5c64e0Hh edit: correction, mission 9, not mission 8. track file has the wrong name.
-
As stated: mavericks slew faster than TGP, FCR, HTS and HSD. If I adjust the axis curves, I'd be adjusting it for all of these sensors as well. There is no problem slewing those sensors. I've just recorded a short demonstration. See attached track file and video demo at Note in particular when I have the TGP on wide and zoomed all the way out. At this point the zoom level of the TGP and the mav on the WPN page are about the same. I can easily slew the TGP smoothly back and forth and over the end of the runway where the target is. On the other hand, I struggle to get the maverick to point at the same location, because the cursor is so much more sensitive (though I get there in the end). Again: please note that these are the same axes. e: actually, I noticed something a little odd. When I was slewing the TGP, without stopping the slew input, I pressed DMS to cycle to the WPN page, and the mav did seem to slew at the same rate. But, when I stopped the input and tried again, it jumped back to slewing much further than the TGP. maverick sensitivity.trk
-
Mav slewing is WAY more sensitive than TGP, FCR, datalink etc. It makes them very difficult to use, especially considering what a pain it is to boresight and use the TGP instead (which isn't your fault, that's how they are). This is trivially reproduceable, a track file should not be necessary, but I can supply one if you need.
-
Wait! I *do* have a track file, because apparently multiplayer always gets saved to track file! It's 171MB, so I can't attach it. I've uploaded it here: https://drive.proton.me/urls/C98RTVGRD0#q9yGm4Y0P3Yz Apparently the other Viper's datalink worked fine, it was just me.
-
Just had it happen again, on an exercise with some 12 odd other aircraft. I was supposed to link up with a flight of three hornets and do OCA, and had to try to go by bullseye calls alone (very difficult, I did not manage very well, admittedly had a great time trying). Of course, like a doofus, I forgot to save a track file. I'll do my best to remember, next time it happens.
-
It's still busted. Usually cycling the time on and off on the TIME page fixes it, but I've just restarted a mission and the second time out I got no datalink no matter what. (In addition, when I entered in target coordinates the sensors pointed off into the sky instead. It was fine the first attempt, but after restarting the mission it was not.) This is incredibly frustrating!
-
Mission 03 broken, -02 does not attack with guns.
Hyperlynx replied to Hyperlynx's topic in Bugs & Problems
I don't have any mods. As it happens I tried again, got the right truck this time, and things proceeded as normal. -
In other words, "SORTED" indicates that you do have a radar lock? Ok.
-
How do I see the debriefs?
Hyperlynx replied to Hyperlynx's topic in DCS: F-16C The Gamblers Campaign
Thanks. For what it's worth, it would be very helpful if the end image saying "debriefing available" mentioned to check the briefing again to access it. -
I think this was explained initially, but it's been a while since I first played and I don't remember.
-
I also use VR. I have two actual, physical kneeboards strapped to my knees, which cost me under $10 to make. I can't recommend it highly enough. Incredibly useful, even in VR. I'll admit, though, that I hit pause, went into the message log, and copied everything down. Then I hit active pause while I figured out how to enter in MGRS. Got it eventually
-
It's not really an issue since it's the wingman's target and she finds it anyway, but the 9-line for the APC reads 354 West 9.5 1574 APC 37 SDU 879605 None No factor East Note that line 6 is missing the second set of three digits. I asked the JTAC to say again, in case this was another little thing like the landing gear malfunction, but he just repeated the same thing.
-
I had exactly the same problem earlier today, and could not progress. Tacview attached. I thought it might have been because I replaced the Maverick with two 500-pound lgbus (because I hate Mavs), so I flew the mission again, this time with the standard loadout. That didn't go so well either: Tacview-20241226-110211-DCS-Gamblers M03.zip.acmi
-
We attacked the convoy, my missile hit the wrong truck but -2 hit the trailing truck fine. She's then supposed to go in and use guns on the rest, but instead she just circled in place forever. So I tried using guns and used up all my ammo. Tacview attached. Tacview-20241226-201332-DCS-Gamblers M03.zip.acmi
-
At the time I posted, I'd actually already looked through the linked brevity code doc, and seen those The Operation Room videos, but still don't know the answers to my questions. Well, ok, a related question, then: if we're doing an intercept, and lead calls "SORT left to right", how would I respond if I can see on datalink what target -1 expects me to take responsibility for, but I can't yet get an FCR lock? Would I call "2 SORTED" because I know which target is mine, even though I don't have a lock? If so, what's the correct term for when I later do have a lock (if any)? If not, what would I call to tell lead that I don't have a lock? "NO JOY"? "NO JOY RADAR"? I did see METALLICA in there as "I can't get a lock due to jamming", though that's pretty specific...
-
I know that when you want to say that you can see a target with your eyeballs you say "tally", and when you can't see a target you say "no joy". What are the equivalents for when you're using your FCR? For instance, while BVR, if I've got a datalink contact I'm trying to lock with my FCR, and my radar isn't picking them up yet, what brevity code would I use to tell my flight? As far as I understand it wouldn't be "no joy" because that's for seeing it with my eyes and that's not relevant. Likewise, when they do get in range and I start picking them up on radar what would I say? "Tally" isn't correct there, either, is it? While we're at it, are there seperate terms for just picking up radar contacts vs getting a radar lock? Eg if they're using jamming, you pick up that they're there but can't lock due to the jamming?
-
I took the Mavericks off the jet, and replaced them with 500-poundd LGBUs. I lost patience trying to get Mavericks to stop being garbage.
-
At the end of the first mission, 1 tells 3/4 and 5/6 to orbit (5 is player) while he lands. He landed, and then 3 and 4 just fly off into the wild blue yonder. I waited, waited, waited, waited, waited, waited and waited, then decided "screw this, mission's broken", switched off my radios and went in to land. Were they supposed to do that? Where were they going? IRL I could of course ask them on the radio, and I did look in the radio menus to see if there was an option there, but nothing. Also, spoilers: I can't submit a track file, it's 70mb. Tacview file attached. Tacview-20240714-145035-DCS-Gamblers M01.zip.acmi