Sylosis

Only thing you don't clearly mention is locking DMT versus locking the MAV. With the DMT locked onto a target, you still need to lock the MAV after you uncaged and selected it (boxed IMAV in HUD). That being said, even if you do, doesn't mean it'll work. I'm fairly certain the MAV is glitched. Using the proper sequence, I sometimes need to press TDC Action 18 times before the MAV locks. That last step seem to not be working all the time. And also, I'm not sure about this one, but I think that unlike bombs, the MAV needs that DESIGNATE is not boxed in your EHSD.

Well I'm doing exactly this and 9 times out of the ten, I reach the final step which is "locking the Maverick", but TDC depress doesn't work. It just doesn't do anything. In 20 attempts I shot one MAV and that's it and I don't even why that time it worked.

Not sure which mission this is, but it is the one where you must take off empty from Batumi. There are fuel trucks preventing your wingmen from taxi'ing. When Batumi Tower finally moves the truck, the one in front of Nightmare 1-2 stays there. Therefore, Nightmare 1-2 never takes off. After that, you are asked to go scout where Norsemen is, with Nightmare 1-2 (you order 1-3 and 1-4 to head back to base). I flew to Norsemen (which is still at the same waypoint from the previous mission), and nothing triggered. Stayed above them until I was bingo fuel and had nothing. I wonder if Nightmare 1-2 has to be there for the triggers to work. Kinda sucks cause I was enjoying the campaign, but without knowing if I'm supposed to be able to still do it without my wingman, I prefer to just put it on hold.

Operating the A-10 and understanding how to display stuff on MFDs, selecting SOIs, etc was more or less clear and easy for me. But, for the Harrier, I am never able to do what I want. So here are my questions: - When pushing the Sensor Select Switch in some direction, for example, to go to "TV", do I need to manually open up the DMT on a MFD and only then will it do something when I push "TV"? - Another problem I have, is that when I have the TPOD on my right MFD, with the TPOD selected as the SOI (and I can actually read TPOD DES on it). If I push, for example, Sensor Select Aft twice, wanting to switch to TV, it will not behave as I would expect. It stays in the TPOD but does something else. It doesn't change the sensor. I assume this is normal but I don't understand it. - Related to the above point, that makes it very difficult for me to find a target with my TPOD in order to shoot a Maverick. Because, if I have my TPOD on the right MFD and EHSD on the left, I find my target in the TPOD, push TDC "Action" and then Waypoint Increment hold to set a point of interest on my target... Then I don't know what to do, cause I have both my MFDs used... Pushing SSS aft twice doesn't switch to the TV, as explained above. So how do I rapidly switch to the TV? Cause, correct me if I'm wrong, but I need to go through the TV in order to then uncage the Maverick, which will make the MAV feed appear. Not doing that will not make the MAV feed appear when I uncage and I won't be able to lock and shoot. So anyway... I could go on and on with other examples of stuff that don't work, but I guess you understand that I just don't get the "philosophy" of how SSS behaves. Tried reading on the subject, but couldn't find something that helped me understood. Thanks in advance for the help.

Oh well, guess it was a coincidence that everything I read and watched on AAR mentioned using yaw instead of roll... That's good to know. Maybe, on top of what I have already asked, would you guys say that once you "kinda" master it with one airplane, it is easier to "master" it for the other ones?

Hey everyone, Was wondering if anyone has had experience with air refueling with cheap rudder pedals? I'm practicing air refueling with the F14, cause I really want to be able to do it (I actually want to be able to do it with most airplane, but I start with the F14). I have a good Virpil throttle and stick, but my rudders are cheap Thrustmaster TWS. I've had them for some years now, and while they are quite cool when you begin and have nothing else, I now realize they are very cheap and kinda suck (especially after some years of usage). There is so much play in the center that I had to set a deadzone of 15 in DCS. Moreover, they are so sensitive that I have to a curvature of 40+. Add both of those and there basically isn't any precision to these. It's like using the D-Pad on a XBOX Controller. Now, it seems most people agree that you must use rudders for lateral movement and not rolling the aircraft, when you try air refueling. But again, my rudders have 0 precision. It's almost ON/OFF. Anyway, I'm still practicing, cause the other thing everybody agrees on is that air refueling in DCS is difficult and requires A LOT of practice before it starts feeling "simpler". That being said, are my cheap rudders going to make it drastically more difficult? to a point where you'd suggest I don't waste time practicing AAR until I get better rudders? Thanks in advance.

Yes, I did not confuse AFT with DOWN. Can't say why I needed 4 presses, but I can tell you what I was observing. In the TPOD MFD on my right and EHSD on the left, once I had pressed "DSGT" (might mess up some acronyms here), in the TPOD below your kind of recticle, you can read "MAP DES" (or something like that). After the first 2 presses on Sensor Select Down, it was indicating "HUD DES". And then 2 presses again, it was TPOD DES. Then I could move with TDC. What is weird, with everything else, is that in my final test I did and described briefly in my "edit" is that this was not happening in that final last test. Sensor Select down twice was going from MAP DES to TPOD DES directly. Thx for the clue about setting the EHSD on A/G, cause I never saw there was an OSB with A/G. I'll have to check it out tonight.

I am tempted to say it's probably me the problem, and this is not a bug, but I have a lot of troubles targeting something with the TPOD, since TDC Down on the TPOD often will just change Sensor. It can either switch to LST or TV. And I have no idea why, cause reading the manual and Chuck's guide, it really shouldn't, unless I don't get something? The sequence I was trying to achieve and that really didn't work for me was: - Fly to drop laser guided bombs - Activate Master Arm - Select GBU12 in stores - Set EHSD to left screen - Struggle to figure out how to enter laser code since the "CODE" symbology isn't on the EHSD and the upper left actually shows TACAN (ended up switching to LST momentarily in order to be able to enter it) - On right MFD, select TPOD and make it operational. - Push EHSD button "Designate" so that it slaves the Steerpoint to my TPOD (close to where my target is). - Push Sensor select Down twice. For some reason, it doesn't set TPOD as SOI, but HUD. I push Sensor Select down twice again, and then it works. - Using TDC, I move my TPOD onto my target - I activate the laser (push OSB button from SAFE to ARMED and also from TRLN to LASR) - I push TDC button down (Action button) : for some reason it switches to LST on my right MFD and TPOD disapears. - TPOD is now on Standby again, so I turn it back on using the right MFD. - I again, have to push Sensor Select down 4 times to have TPOD as my SOI. - It's still on my target, so I push TDC Action: switches to LST screen again.... - I turn the TPOD ON AGAIN! - Again, push Sensor Select down 4 times... - I push TDC Action once, now it switches the right MFD to TV.... - I want to kill myself at this point. - Redo all of the same shit once more, when I push TDC down, now it stays on the TPOD, for some magical reason. - However, there isn't any symbology change. It's as if, TDC Action didn't do anything. - I hold down WP Increment - Doesn't fully work. Next to DSGT in the EHSD, it is still written "STP", but where the waypoint number should be, it's written TO. - I go towards my target and I have no bombing symbology... no cue, nothing. Can't drop bombs... I'm using a Virpil joystick and I must admit that sometimes, DCS doesn't seem to quite well detect the hat switches. When using the Virpil Tester, everything is perfectly fine. But in DCS, it doesn't always work. I still don't understand why TDC Action would change the Sensor on the MFD, but then I might just fail and suck... Any help is more than welcome, cause this was a good waste of 2 hours trying to figure this out. EDIT : Just tried a quick instant action to figure this out. I did everything identical except one thing that I could not remember if I did or not. The line where I used the TV on my right MFD to enter the laser code. There is a small chance that previously, I left "CODE" selected in the MFD. Could it be the issue? Cause this time around, I didn't have all that weird behavior (of having TDC action changing sensor).

I'm actually playing the Ottoman campaign and haven't seen neither of those (TACAN and ATC frequencies) in the briefing. Yet the briefings do require to use ATC, and obviously TACAN always helps to find the ship... Therefore, if nothing is mentioned in the briefing as to using "different than default" values, I assumed it was default values. Have you tried the campaign and/or was able to talk to the Tarawa?

Probably a noob question, but I am coming back to DCS after some hiatus. I posted it in "Problems and Bugs" but nobody bothered to answer, so I figured I'd try in a non-bug related forum. So, first of all, I can't talk to Tarawa ATC. I read it's supposed to be default frequency 127.500. Tried it, using the proper Comm buton (have it set on my Comm1) and they don't reply. Also, is there a Tarawa TACAN? I've looked everywhere and can't find what it's supposed to be. Thanks

Read the briefing and didn't see if the Tarawa was set to a different frequency. I believe default is 127.5, but it just doesn't answer. So, how am I supposed to contact ATC, even just to get the start-up clearance?

I can't say which mission, maybe mission 8, but there is one with a ton of fog on ground level, which almost looks like clouds at 0 ft. It is so dense you don't see 1 foot in front of you. And it really is at 0ft, so no need to hope for better visibility as you drop altitude. What is the expectation when it comes to landing? Cause, it's essentially impossible. For this campaign, you selected an airport that doesn't have TACAN, so we can't navigate with instruments. So we have no instruments, no visibility, no runway lights. I don't mind a challenge, but at some point it needs to make some sense and be close to feasible. Flew the mission 3 times and I crashed every time. I am certain I wouldn't be able to land even if I'd try 10 more times. Tried flying over the airport to find it and can't even see it. I can't skip the mission, cause the campaign requires 100 result to go to next mission, which requires me to land. I'm curious to read what was the thought process when doing this?

At last there is a campaign for the F-5 I thought (apart from the BFM ones, which I find quite boring). But then, why would you pick Krymsk as the base of operation, when it's one of the few with no TACAN beacon (RSBN only). Meaning you essentially can't navigate the F-5 for the campaign. It's even part of the mission briefing, what RSBN to use.... but it's an F_5 campaign...!? Am I not getting something, or are there other people who think the same?

Haven't installed any mods. Not sure if I have another keyboard here, I'll have to look around. Worth trying.

I managed to finally do it, and I'm going to post what I experienced. First of all, I wrote this post after my first attempt and the 2 MANPADs on the target were just non stop shooting at me. The second time around, they were drastically more passive. I do not know why, because on my second attempt, I was not using a different strategy. The other issue I had, which was the fighter planes coming to intercept me, I was able to overcome by increasing my speed from WPT1 to WPT2. I guess I was pushing too slow, therefore getting to the target as the interceptors were already almost to me. So, for sure my mistake was to not come fly to the target quickly enough. As for the MANPADs, I have 0 idea why they were so agressive on my first attempt, even if I kept flying roughly at the same altitudes on my following tries. *shrug*

Thanks for your suggestion, but I doubt this is the issue. If it were, restarting DCS would not fix it. well the keyboard works perfectly fine with any other application. Therefore, I am tempted to say your first possible culprit might not be it. As for the second one, I just don't understand why, if it was some other application being the problem, restarting DCS fixes the it (and I reiterate that the issue is only present with DCS). And I am not saying your second potential solution is wrong, just that if it were to work, I wouldn't understand why. My reasoning is that, if I have 0 issue with anything else (including MSFS, for which I use the exact same apps and devices), then it must be DCS that is the cause of this. No?

I don't quite understand what this is, but sometimes I'll start DCS and the keyboard will not work right. Keys with modifiers are detected, but single keys are not (LCtrl+G will work, but not G). I restart DCS and then it works. Next time I use it, it might, or might not, work again. Known bug or is it just me? (never had this issue in many years of DCS)

Mission 3 of Campaign Cage the Bear doesn't make any sense. All of the other allied flights are useless. The 2 SEAD flights go kill one single SA-6 that is relatively far from the mission target (the train station), while there are 2 SAMs directly on the train station. So why aren't they going there? Also, you get attacked in the middle of that SAM dodging fest while your CAP flight is 40 miles away, shooting planes that aren't real threats... What am I not getting here?

Haha how did he do that?!

I would really like to read how you came up to that reasoning. DCS is free, yes. But, you need a joystick to play. Fortnite doesn't. Then, I doubt most people just go with the default free module. Each module is the price of a game, on its own. So... How is it a bargain? I'm not saying you're wrong, but I really don't understand how you arrived to that conclusion

Sorry, I meant "dumb" if one would complain on both occasions. That is, complaining if stuff geqts released too quickly or too late. That is dumb As far as paying for something not finish, it's not dumb, although I don't get it myself. However I do not think it is dumb. And, this is not pointed at you, but why the flying **** is everybody here getting so ****ing defensive when any kind of opened discussion is attempted? Are you all like that in real life? A colleague enters your office and ask "hey uhm, do you know why X person did Y project like this? I'm not sure I get it" "Well if you don't like it just go cry somewhere else". "OK thx, good talk" Jesus christ. You can all forget I asked anything. You would think a community where the software is relatively expensive would be more opened to discussions and debates

This is partially my bad, as I am the one who said "YouTube Reviews". I don't even think they were all titled "reviews". First impressions is more relevant. And, I'm not really debating if one should buy the F-16 or not. It might have seen like it, but I'm just discussing the business model. As somebody else pointed out, how much can you stretch the concept. I'm sure it does help them a lot in the development phase. But for sure there are disadvantages to that kind of operation

Very true. They only control what they release. Once it's released, servers admin decide.

True yes, and I indeed watched the videos with a grain of salt. They should have been titled previews, I agree. But there is no clear definition of "early access". Nothing prevents you from starting to sell it very early on and call it early acess. Which is fine. It's just that while some might have low expectations when it comes to early acess stuff, others might expect slightly more. There's no right or wrong I think

Never wrote nowhere "nobody is enjoying it" I said I based my comment on friends who have bought it and stopped using it, as well as multiple reviews on YouTube. And, the intention of the thread was to start a discussion about releasing modules in a very unfinished state. If you can't be mature enough to jump in the conversation with interesting points, and just wanna be butthurt cause you took something personal in what I said, fine.