BodyOrgan

While admittedly my examples were for the 15-20 nm range, because in my mind it's one of the most critical stages the pilot actually needs to see the other plane, it doesn't mean it's any less critical the RIO stay off the TCS while WVR. I'll tell you why, as the pilot I need to see the closure rate provided by the TID to accurately make a judgement call on whether or not to be in gate, corner speed or somewhere in between to make maneuvers to counter what the bandit is doing. The sliding bar of the HUD doesn't provide the required fidelity to make that judgement. I cannot get this information if the RIO is using the TCS, further more, during the chase the TCS let's me see the aspect of the bandit easily, and clearly, allowing me to see the vapors on the aircraft thus knowing it's pulling G bleeding airspeed, something which isn't easy to see outside the cockpit if you're slightly more than one mile separation. Even further, WVR, the RIO's head should also be out of the cockpit looking for missile launches, so they can employ the counter measures. Especially since the likelihood of a radar lock being significantly small during maneuvers to gain angles thus the TCS up on the RIO will only deny the pilot the ability to read the closure rate should he acquire PAL/VSL lock at any time. I simply cannot see how the RIO using the TCS within visual range is ever a good idea.

Thanks! Hopefully a decent solution can be found. Perhaps this is a joke, and not to be taken seriously, otherwise my techniques are not yours, and yours not mine. This statement diminishes the significance this change could bring. I disagree, the pilot has navigation cues via the TCS (VDI) the same as the HUD except he can actually see what the bogey is doing, such as, but not limited to, whether it has fired a smokeless missile, turned hot, gone into the notch, etc. IMO the RIO has other important things they should be doing such as attempting to IFF the target in which the RIO would need to ensure the STT lock hasn't dropped in order to do so. If the TCS camera is up, the RIO may be wasting invaluable time waiting for an IFF response on the DDD without ever knowing (until they flip back to the radar) they aren't going to get one because the STT lock dropped.

No, this isn't a multiplayer exaggeration. It is as QuiGon describes it "TCS LOS is being hosted on the RIO player computer and then gets transmitted to the pilot player computer, but because of network lag it's not accurate." If as the pilot you fly stable aka don't move, eventually the TCS will sync up with that of the RIO. I really wish they would reverse this and make it hosted at the pilot because as a RIO I have to give up the radar screen to VID something whereas the pilot would only have to give up the VDI which much of that information is available on the HUD too.

This could be the very first campaign I buy.

I'd like to point out the 7MH tracks for me, but the 7M does not. I have not tested the 7F.

Well, I'm not a super handy person, so cutting pipe is a pipe dream in my case. I could probably live with Jabbers solution for the weapon selector depress, but my intention was to get the curved 200mm extension, and center mount it. After having seen all the reviews for both the VKB and VPC VFX, I've decided not to buy either. Should VKB solve the two flaws, then I'll immediately pick one up.

Can the weapon selector be depressed in the sidewinder position to switch between stations? I'm reading it isn't able. Can the stick itself be canted for center position setups? I'm also reading this isn't possible without an extension, but if using the 200mm curved extension this would offset the actual position of the stick.

I don't really know much about TARPS if anything at all, but if it's essentially a reconnaissance pod I have an idea on how to actually make it useful IN GAME, and probably cause it to get heavy use. If we move to the multiplayer world for a minute, and jump on a server like BlueFlag, DDCS, or any number of servers with fog of war, then we'll quickly realize the uselessness of pre-planned target modes in the Viggen, Harrier, Hornet, etc. You can't very well mark a target via the F10 map if you can't see the target on the map to begin with, so here's the idea: If the Tomcat's TARPS pod captures intel/pictures (however this thing works), and makes it back to an allied airfield, then the captured information could be marked on the F10 map. For example, if an SA-6 is overflown, then the units could be put on the F10 map with the marker labeled as the units type. A user could then take it upon themselves to change the label to the format they need for their aircraft. For example, convert the SA-6 name to m1, m2 for the Viggen, or t1, t2 for the Harrier, etc... The user could then load up these reconnoitered targets into their aircraft's pre-planned targets, and have a field day. To me, this would make TARPS missions very valuable. I would fly them myself, so I could then go back for some sweet BK90 action :joystick:

Yes, see P-STT.

https://forums.eagle.ru/showpost.php?p=4265939&postcount=4

This isn't a Tomcat bug. It's simply how DCS works. There is a command stack queue. The AI will only complete one task at a time, so if you ask them to complete a long task like fueling, then nothing else can be completed until they finish the task they're on. You'll notice once fueling/arming is complete they will complete the next task in the queue, so if this was ground power, then they'll attach it. To get around this limitation always complete quick tasks before long tasks. In other words always ask for ground power, and air before asking for fuel.

By default Jester is set to automatically handle the radar in the manner he sees fit. Sadly, in practice this doesn't work out so well. If you fire a Phoenix in TWS radar mode, Jester is very likely to switch the radar mode to RWS, essentially trashing the shot. To prevent this command Jester to only use TWS radar mode via the Jester wheel if you want to take a TWS shot or command him to only use RWS if you want to take an STT shot. There is an additional problem with Jester if taking STT shots. He has a high probability of switching the mode from Pulse Doppler to Pulse (PD-STT vs P-STT), and vise versa. When he does this often times the lock is broken. There is an option in the special settings for the F-14 to prevent him from automatically switching pulse modes. Be default it isn't checked. I highly recommend you check this option, and command him to use pulse when you actually want it.

Agreed, but this should keep your sanity in the meantime.

https://www.digitalcombatsimulator.com/en/files/2268038/

I'm just going to link this since everyone seems to have forgotten, maybe even HB themselves. https://forums.eagle.ru/showthread.php?t=247338

Doesn't look like he's complaining about performance, rather the FOV of the 120 seeker. Notice how his RWR is still reporting the missiles even though they are quite far behind his aircraft, and not even pointed at it.

I can also report if you lose hydraulic pressure, but manage to land and repair it won't fix the lost hydraulics.

I fly as the RIO too. There is literally only one thing the RIO needs to do for the A variant Phoenix, and that's flip the cooling switch for the AWG-9 forward so it's also piped to the Phoenix, otherwise backwards as the C variant doesn't need it. All other setup is handled by the pilot. The RIO could also flip the switch on a specific Phoenix station to ensure that Phoenix is fired, but that's about it. If your RIO sees PH on the bottom right of their TID (meaning the pilot has the Phoenix selected) and the master arm is on, then they should be able to fire it. If they don't see the PH on their TID, then the pilot hasn't selected it.

A repair will not initiate unless you have sufficient damage. I don't know the threshold, but minor damage is sometimes not enough to cause it to initiate. If you want to be 100% sure, you can open the canopy before landing so that it's ripped off. This trick thus far has ensured I'm always able to repair. The Tomcat still has bugs in its repair as it doesn't always repair everything or set the plane back to its initial settings. For example, if you belly land and repair it will not lower the landing gear upon repair complete even though your landing gear lever is down, so it'll just get damaged all over again.

The lights in the RIO pit are extremely dim right now. A recent patch essentially broke them. Try firing the Phoenix yourself, if you can fire it, then they should also be able to fire it.

More than likely you as the pilot are missing something, for example selecting A/A mode, moving your weapon selector to PH (Phoenix), engaging MSL PRP (waiting the 3-5 minutes for warm-up), and setting master arm to on.

I've also been experiencing the crashes as well. It's always CTD, but after the initial Jester fixes it was somewhat rare. The recent patches however, have essentially made the aircraft unflyable. I can't get through a single flight without a CTD. Link to my lastest dcs.log file from right after the CTD: This latest crash flight took place on Blue Flag Persian Gulf. I took off from Bandar Lengeth with the typical 4 PH, 2 SP, and 2 SW load-out for CAP. I wasted one Phoenix (maddog) against incoming ordinance (JSOW I believe). A few minutes later I shot down an F/A-18 just south of Abu Musa. I used TWS and only STT locked the aircraft shortly before impact to confirm the kill with the TCS camera. Afterward I started a 270° right hand turn to create distance and come around to check the eastern side of Abu Musa from which I received 18 RWR spikes. It was during the turn in which the crash occurred.

+1 ... I really want mode toggles for these switches!

Actually, can we call it the F-16 Iron Eagle?