Spiceman

They had a range of motion, but no, they could not be completely folded out of the way like you see in some DCS modules. They had maybe a 20 degree range of motion.

In reality, mirrors aren’t really used to see bandits, they are pretty useless for that purpose given their narrow FOV, and the constant motion of aircraft and bandit. They’re mostly used to check the position of the wings, DLC engagement, etc. Administrative items like that. I’m not sure it’d be worth the effort to make them movable. You probably wouldn’t find yourself using them any more than you do now, would be my guess.

I know what’s happening now. As I mentioned, every time I upgraded it created a new install. So I had a bunch of installs showing. I ran one uninstall and it went well. So now I still have these remaining “ghost” installs but with empty folders. The five minutes per file is the uninstall going through some sort of lengthy timeout sequence on each file, trying to delete a file that’s not there.

Lol... turns out I was being generous on the four hours... My previous post, that was a real-time screen shot about 2.5 hours ago. It's gone from 41% to 42% since then.

Anyone else have an issue with the uninstall creeping along? It's literally taking about 4 hours.... removing one file about every five minutes. I'm running the uninstall because I noticed that each of my upgrades actually created an entirely new installation and now I've got four different installations on my system.

Chill... the A is coming. They’re hard at work on it. They’ve already posted on its progress. I’m also sure it will be a proper A which means it will have the TCS like every A did.

From 1983 or so and onward, the only time you would see a bullet fairing on a Tomcat was on a RAG jet. In my 10+ years I never saw a bullet fairing on a fleet jet. We kept one in the shop, but never had occasion to use it.

TCS was integral to the -A and was used virtually it’s entire lifespan. I can’t imagine HB’s -A wouldn’t have the TCS. The -A and -B TCS are the same system.

Once the diamond stops flashing, you should be able to designate with the same action you use to go to PAL in A/A. When designated, the diamond should become ground stabilized, and that will be the computed target point when in CMPTR/TGT bombing mode.

No you probably just need to be a little closer. Drive towards the area you want to designate and eventually the diamond will go steady. Then you can designate.

You may not be in a good position, I.e. within 8 miles or so of what you’re trying to designate, and not too shallow. It’s important to understand what is happening when you designate a target. The Tomcat has no memory. It has no terrain database. It sees the terrain in real time in A/G mode by putting the AWG-9 into 10NM pulse, freezing the antenna, and using it to paint the ground. It’s using radar range and antenna pointing angle, along with the INS, to calculate where the ground is. When you slew, you’re moving the radar antenna up and down, and when the radar has a good return, the diamond will stop flashing and you can designate. Play with that a little bit and let us know if that helps.

I see the same thing. It might be way down on a bug list somewhere and just hasn’t been addressed.

The IRST came and went so quickly, it would be a waste of development resources to model something that didn’t work and was really never used.

To clarify... TARPS jets could carry the LANTIRN, they just couldn’t carry both at the same time....

Yes.... there is/was no difference between the A and B in that regard.

I had this same issue, and noticed that it happened when I joined as Game Master first, and then joined in an aircraft slot. If I joined an aircraft slot straightaway, it worked normally. Weird.

Replay issues are a core architectural issue in DCS. Just because it’s broken on the F-14 doesn’t mean it’s the F-14 module causing it. ED says that fixing replays is on their near-term roadmap.

Of course!

I worked on the A and A+. We may have had one or two jets that had PTIDs in VF-101 when I left there in 93, but I have no experience with it. I was in a shop called Troubleshooters at the time and not in the avionics shop.

The TARPS pod itself didn’t have a navigation system. There was additional navigation information displayed on the HUD/VDI when in TARPS mode, which still came from the AWG-9. The pilot had to a bunch of “put the thing on the thing” kind of steering with a Commanded Ground Track Line and a couple additional steering error cues.

Does the new Beta use a different options setting than 1.2.3? My Options lua in my tech server folder says ‘realistic.lua’ but my client is always on Arcade.

PNG files in my kneeboard folder do not appear in-game if the .PNG extension is capitalized. I have to go into File Explorer, display the file extension, and rename it from XXX.PNG to XXX.png in order for it to show in-game. Am I the only one that has this issue?

I can tell you anecdotally... in our wing of over 50 members, we were having lots of constant complaints about performance issues in our standard training mission, built pre 2.5.6. It also included non-performance issues like the F-16 TGP HUD marker being off from where the TGP was pointing. Tried and tried to fix all the issues to no avail. Recently decided to just build a new training mission from scratch. The jury is still out, it’s only been a day, but so far it seems to be fixing our issues.

Dumb question.... in the DCS log, Tacview is making an entry every *10 milliseconds*. Is this right? I'm trying to track down some server performance issues....

Here's the log... the mission starts at 01:20 in this log. https://drive.google.com/open?id=12zNpTBrYgGIYhJkVasluB3qXcvEFo_aw