fudabidu

The TGP will take about 2 seconds to fully zoom in or out. This is normal and also happens when using the keyboard commands. Can't tell you anything about the jitter, because I don't know which mode you were trying to use it in. The only jitter I've seen is in A2A, because the TGP doesn't slave properly to air targets yet. There might be some edge cases (ie taking off with TGP, but no A2G weapons and unable to change delivery mode), but I haven't tried those. Some more information are needed.

You want to think about the shots you take, regardless of any bugs with the 120. Right before the first launch the Hornet is notching and close to the ground to hide in ground clutter. In this kind of situation you have to expect to loose lock, meaning your 120 won't get mid-course updates and miss. It's one of the worst shots you can take at this kind of range. Missile #4 had me crying. The friendly Viper turned in to face the Hornet in a dogfight. This should have been clearly visible on the FCR and HSD (assuming datalink on and proper alignment, as it should be) and you shoot an active radar missile in that direction anyways. The missile tracks the Viper instead but luckily has to make a sharp turn, otherwise it might have been a teamkill. Please avoid doing that in the future.

TMS UP ... no matter what weapon or sensor you're using, locking something is always TMS UP. I've only watched Wags' videos and he mentions it all the time. Maybe you should watch his tutorial series from the start to get a sense for the basic controls.

For over a decade we had to manually create waypoints for all ED aircraft (unless set in ME, obviously) and I'm not expecting that to change all of a sudden. DTC is planned and setting waypoints might be the first feature to work. It's less of a pain if you're smart about your keybindings. The ICP fits almost perfectly onto a regular keyboard (see picture). If you care about the default bindings (ie camera controls) you want to set up a modifier. I've chosen my joystick's pinky button for this. All my aircraft are set up like this and it works beautifully. In the Viper I take 10-15 seconds to enter a new waypoint and I can do it blind while looking at the map. Requires practice like everything else, but I think it's very worth it.

Sounds like the INS wasn't aligned properly.

I found the original English manual from 2008 and I got pretty much the same results. It does not mention tapping the trimmer anywhere! Please, read it again and tell me where it's supposed to say that.

The Quick Editor gave me my template loadout I use online (4x AA + TGP). Seems there are no loadouts defined for the QE to pick from (yet), so it defaults to empty or the last created user loadout. For the time being you can go through Advanced -> Generate -> Edit and change your loadout this way. You flight should be the first in the group list.

All the relevant results for the search term "trim" in the manual: "“ТРИММЕР” (Trimmer) button – Cancels all force on cyclic with the trimming mechanisms. When released, the autopilot will stabilize current angles of pitch, bank and yaw [T]2" "Pressing the “ТРИММЕР” (TRIM) button on the cyclic stick cancels the autopilot’s position signals for bank (K), pitch (T) and yaw (H) and releasing it places the angular position of the helicopter in 3D space in memory" "To set a new airspeed and altitude, it is necessary to press and hold the trim button and change the speed and altitude. Then release the trim button and the current values of the airspeed and altitude are set as desired" "For changing flight parameters it is necessary to: 1. Press and hold the Trimmer on the cyclic stick. 2. Set new flight input (bearing, pitch and speed). 3. Release the Trimmer button." But I'm not supposed to hold the trimmer. Got it!

This is EXACTLY why we've been asking for a Shkval update for years and here we are talking about it again. I think it has even gotten worse since 2.5, judging by how "Deployment" plays (which I played a lot pre-DCS). Everybody is going to buy the Mi-24 anyways, so who cares, right?

Can you provide documentation about the Ka-50 that supports your claim? What would the proper trimming procedure look like? If it's such a big issue, where is your forum post about it?

Sorry, but you just don't know any better yet. I played the same mission 4 times 'as intended' (or: like most people would approach the mission) and ran into several issues we've known about for years. Some issues even date back to the original BS release in 2008 (like the analogue Shkval axis deadzone). Ask some experienced Ka-50 pilots and they will all tell you similar things...or maybe just browse the forum for 30 minutes. The Ka-50 is fun when it works. Running into some of the same issues on nearly every flight is not. Getting no response about these issues is slowly driving people away. But please continue telling us how amazing the module is.

How about a global option? Canopy reflections: - None (make the fake reflections a separate texture layer, but don't load it if disabled to save resources) - fake/static/ugly (for the people who like it) - real time reflection (for everybody with a high end GPU) It's that easy.

I understand how software development goes, but thanks for reminding me. 2.5 released years ago and we still have issues with DL targets, AI, broken missions, Shkval, ... you name it. You think this is acceptable if we don't even get feedback from the developers? Just to pick one example: was there any reply addressing the hardcoded Shkval slew axis deadzone? NO! Every 'veteran' with an analogue TDC-stick knows about it, it's easily reproduced by just flying the Ka-50, but ED chose to ignore it. It has been an issue from the very start (12 years ago) and we still have to deal with it. Good luck finding an excuse for that. I'm already telling everybody the Ka-50 is borked beyond believe and nobody should buy it in its current state. It would be a great module if you weren't required to have a list of "bugs" at hand just to see if you did something wrong. Thanks to the (lack of) communication this is what I predict for the future: 1. the Ka-50 will get some new toys, but long standing issues will not be addressed 2. every module older than ~4 years will be neglected in favor of new modules, especially helicopters (despite advertising Syria to be "perfect for helicopters") Where is ED now to tell me I'm wrong? They are in the F-16 forum section, telling people to properly align the INS or boresight the MAVs. Amazing support!

We've seen issues with the Ka-50 for years now and after testing something I think it's really urgent we talk about it. A while ago I was having issues with DL targets being saved with wrong altitude information (approx +30m), even when received from an AI wingman. Couldn't remember the exact mission, so I just took a wild guess and ended up with "Clear Tkvarcheli". It wasn't the mission I was looking for, but I did find problems. Oh boy .... Quick mission summary: Take off, turn E, destroy single AH-1, destroy ground targets Attempt 1: I kill the AH-1 with a pair of Vikhrs. No issues. I then send my WM to scout ahead 8km, exactly the range to the targets. Perfect weather, 8:30am, targets already in sight. WM goes NOE, doesn't spot a single target and gets shot down. Attempt 2: AH-1 gets hit, trailing black smoke and goes into a steep dive. AH-1 surprisingly continues the attack and knocks out some of my systems. Attempt aborted. Attempt 3: AH-1 coming straight at me, AA mode on, laser on, targeting box right over the target, target clearly visible, "lock" ... I'm getting a 6km range but no tracking. How often do we have to ask for a Shkval update??? After killing it I realize my WM went RTB and shut down for absolutely no reason. Attempt 4: AH-1 gets hit only slightly and breaks lock by maneuvering hard. I reset the Shkval to cancel the drift, re-enable AA mode, uncage, laser on, clear line of sight, way above any obstacles. I completely 'miss' the AH-1 with my first locking attempt, hit the ground behind it (good range information) and the Shkval just goes nuts. Eventually I send my WM to scout. He goes NOE which means he no longer has LOS to the targets, but he somehow sends me DL targets anyways (paused and checked in F2). At least all those targets were stored with the correct altitude, so it might depend on the area of the map, but I'm done with testing for the next few weeks. Let's recap: - AI has no sense for self-preservation - AI scouting is completely unreliable and more of a "kill wingman" function - AI can randomly break and RTB - AI LOS is inconsistent at best - Shkval tracking range is still artificially limited which can make it trash even in seemingly excellent conditions - The Shkval can start drifting randomly regardless of any obstacles and with valid range information - Even SP track files can have massive desyncs Yes, ALL of the track files were broken. Shkval looking in weird directions, missiles going dumb, AH-1 crashing when it shouldn't have ... To say that I was disappointed would be like saying water is slightly moist. I would have loved to provide all the tracks. If resources are limited and the Hornet, Viper and Hind are priority, that's cool. I understand. Not even reacting properly to long known issues I don't, unless you want people to think the Ka-50 has been abandoned. So, what's your take on the current state of the Ka-50 and what kind of genuine improvements are planned for BS3? "thanks"

With full autopilot support the helicopter will hold whatever attitude you set it to (when trimmed properly, which isn't hard at all). If the helicopter deviates the AP has reached its authority limit and you'll need to refine your trim. That's all the indication you'll ever need in regards to the autopilot. It's been almost a year now and if you're still struggling with trimming I'd suggest an online training session with a seasoned Ka-50 pilot. It's gonna be more valuable than some cryptic indications that don't actually provide any useful information.

Maybe consider an alternative: Use the 3-way switch for MRM and DGFT override modes 'as intended'. When using the special bindings the center position will bring up the last selected master mode. Incredibly useful when you're in AG and need to switch to an AA mode quickly. It has saved my life many times back in my BMS days. If you want all modes available on your HOTAS you could toggle between NAV and AG with one button (+modifier) and do A2A with the override switch. MRM and regular AA master mode are practically identical.

No, sometimes DL targets will be saved with the wrong altitude. Last time this happened I switched position by several KM just to verify this was an issue. The direction was spot on, but the elevation was way off. I've also seen this with DL points received from an AI wingman. This only seems to happen in certain areas, not everywhere. This is why I suspect it has something to do with the Shkval relying on a elevation database which is broken in some way (talking DCS code here, not IRL) No track files, because I disabled recording. I mostly play online and since MP tracks are unreliable I didn't see the point in wasting the system resources. This also means I have no memory of where the problem occurred, but it's not like we'd get a fix before BS3 anyways. Switching to manual mode has become part of my pre-flight checklist. It doesn't change anything in regards to tracking terrain / a target.

Maybe boresight BOTH pylons? Seriously, I've been flying the DCS F-16 from day one, testing every beta update (because I used to be a BMS nerd), launched over 100 MAVs by now, no mods and I've never seen this. Where are the track files showing this issue? I haven't seen one yet. I'm starting to wonder how many issues are coming from DCS and how much are coming from (a lack of) RT*M. Repeating what was said in Wag's tutorials is getting old.

No, the Shkval can indeed start drifting on its own. I've mostly encountered it hovering behind tree lines where the Shkval will get stuck on a tree 5 meters in front, even if said tree is barely within LOS. Strangely this doesn't happen everywhere and doesn't always require trees in the way. My guess is, the Shkval uses an elevation database which has issues in some areas, leading to wrong LOS calculations. This might also explain why DL targets are sometimes stored with completely wrong altitude information. We reported this already, but ED has other priorities at the moment. No point in discussing bugs if they are just getting buried and never even acknowledged (thanks ED!) I'm not even going to address the flight issues in this thread. It's about the Shkval needing an update, not basics of helicopter operation.

Or you could just hold the TDC up for a few seconds and bump the FCR range this way. No need to let go of the joystick ("HOTAS") or go heads down to find the mouse.

You can invert some symbology by pressing HOC / COH on the WPN page, or press TMS left with WPN as SOI. It would also help if ED changed the water being 'full bright' on FLIR, which we're still waiting for.

The real F-16 also has a 4-way comms switch, although left and right are used for datalink actions (which are not implemented yet). I'd recommend mapping them properly now to avoid confusion later. UHF and VHF aren't super important, so these could be bound to modifier+whatever. I do wonder what you bound to that poor stick though. I'm using the almost identical F-16 stick and the only extras I've bound are Steerpoint +/-, TGP zoom +/-, AP pitch/baro and rudder trim L/R (using pinky as a modifier). Since you can use a joystick modifier on keyboard commands I was able to map the almost entire ICP to the right side of the keyboard. It's a perfect fit!

Press OSB 18 to switch from AGC to MGC. Below that two arrows will appear. Use them to adjust the contrast manually. The picture can change when you get closer, so you might need to readjust.

I'd prefer we all stay on the same page. You pick a weapon, you have to deal with its quirks. If someone really hates boresighting it can be done on the ground (although I'm not sure it's supposed to work with weight on wheels, so this might change). Rearm before starting up the aircraft, power the MAVs as soon as possible and do it while the INS is still aligning. And yes, I'd appreciate if all aircraft needed to do this.

R-Ctrl + Pause will bring up an FPS counter in the top left corner. Everything above 30fps should be fine for refueling. Performance is usually worse in multiplayer. Also remember your engine needs a moment to reach the new RPM. If you make a large throttle change it will take longer to 'catch up', which you might perceive as delay. This is what most people seem to struggle with during the initial rejoin. I find it really helpful to listen to the engine. If the pitch keeps changing I know it's still spooling to the new RPM. Try adjusting your speed by sound, not throttle position. Once you approach pre-contact position you'll have to make tiny adjustment constantly. You will NEVER find the perfect throttle position. Make these adjustments early. Let's say you made it to contact, but you see that you're drifting backwards: Push the throttle forwards just a tiny bit (let's say 5mm), wait half a second and pull back a bit less (3-4mm). This will slightly nudge the plane forwards and increase your throttle setting. Keep focused and repeat the process. Don't wait until you've matched the tanker's speed. You'll react too late and probably overshoot. This is what you need to get a feeling for and once you do you'll make these adjustments subconciously. One of the most rewarding feelings I've ever had in a flight sim, so keep at it. If it's an older stick you also might want to check if the throttle sensor is still in good shape. Open Axis Tune and very slowly move the throttle in both directions. The dots should move smoothly. Also hold it in different positions between 25% and 75% (that's where mechanical potentiometers tend to wear out first). The dots shouldn't move at all. If you see any jumps or jitter the sensor is wearing out and it's only going to get worse. You'll either have to find a replacement sensor or switch to a new joystick.