RustBelt

Look, I’m sure Heatblur wouldn’t mind if you felt like footing the build costs for a Tomcat 2.0 where they could go back and do all this stuff over differently for you. Folks just need to accept that when the project was started, certain decisions in the planning phases mean some things just can’t be changed without a full rework from scratch.

Push comes to shove though, you COULD use them though? Or were they only wired for the A-stations? With DCS we aren’t just running scenarios that DID happen. If someone planned to do something crazy, more flares is more, and if the system could do it, they should be able to do it even if it was inconvenient for maintenance. Because frankly, they’re invisible, and nobody cares what they think with their magic pixie repair and rearm technology in DCS.

You either have to engrave or emboss unless you have a multi head printer. Or you have to look at a post process like silk screening, printed waterslide decals, stickers etc. Or go all in and make laser cut clear acrylic painted and etched on top of aluminum sheet panels with back lighting. engraved would be the most ideal, as you can sand the surface, then fill in the letters. Make it print about 2-3 layers deeper than your surface.

If the AIM-54 was “competitive” than it wouldn’t have been replaced by the AMRAAM. Compete in a 1983 or earlier locked competition and see how un-competitive it is against Sparrows and old Russian medium rangers from 29As. Not all competition is SATAL crappy min/max eSport garbage.

No because they’re both different sizes, if you notice the MFD is taller than it is wide by more than 4:3 but less than 16:9. Either stack one monitor behind both screens and put both exports on it, or you’ll be buying some weirdo specialty display from lilliput or somewhere to find both fits.

Remember this is PRE pac-man level computer tech. The RIO does the actual thinking for the AWG-9.

Make the mission with the Mig’s jammer locked out. FC3 jamming is…..goofy, OP, and makes the AWG-9 do some stupid stuff as opposed to just not building a track.

Yea that’s a DCS weirdsies thing. Lighting is kind of a hit or miss nightmare in this game. Heatblur knows about it, but as with a lot of lighting “challenges” no solution has come of it yet. The game engines virtual camera is essentially night blind (and I think has either an astigmatism or a corneal scar of some sort). Get your room as dark as you can and cheat the Gamma Correction up as much as you can stand.

See that’s a whole nother thing your asking. For DCS integration you use Helios to create the export window and position it to the screen space of the display. If you look up DCS HELIOS external displays you’ll find heaps. I do this now just on a second display below my main monitor. But the principle is identical. All the monitors are treated as one big “screen space” and helios does all the sorting out where each monitor exists in the screen space, and allows you to send different stuff different places and it does all the coordinate figuring. Not connected to DCS you could use a Raspberry Pi to feed a still image of the screen onto the cockpit display. Although, that’s a bit….boring when you can just run DCS through it. The home cockpit section here that’s now hopelessly buried in the new forum layout has all the secrets! https://forum.dcs.world/forum/181-home-cockpits/

Well if the goal is for the switch to both turn on the actual screen, AND send the action input to DCS. You want to get a double pole single throw switch for the VDI and HSD. One pole (or side) connecting to the screen power, and the other pole connected to the DCS interface. Two individual isolated switch signals in one physical switch. if the screens are simple you just switch the dc power from the power supply. If they’re too smart for their own good you’ll need to make a little ground pulse from a 555 timer. When the switch closes that is wired parallel or in place of the screens on switch.

Problem is some of those IFs are the core visual model. Which is immutable for all intents and purposes. Perhaps if an F-14 2.0 gets made in the future it may be done, but like fuel pylons. If it’s baked into the mesh, it’s not changing anymore for this product. Because there’s always some chin pod, they may find a way of cheating it without remaking the mesh. But if so, assume a lot of “mesh error I can see inside the nose from outside” reports. If you funded Heatblur to make a version 2.0 of the Tomcat you can probably get whatever you want. Especially if your pockets are deep enough to get your hands on the full -1A NAVAIR sections of the B, B(U), and D. With enough money anything is possible no matter how badly conceived. Just look at Elon Musk.

But then there’s all the converted jets, and the upgrades, and the Squadron specials/franken-planes. Each it’s own deadly little snowflake.

God you need a damn astrolabe to keep track of the Tomcat production timeline. Those are some, high octane "If's" there.

Well, maybe someday you'll get that PhD and become completely disassociated with reality like most engineering PhD's with ......."opinions"

“No Patch this month, Patch Last Month, and Patch next month, but no patch this month, Never patch This month.” I firmly believe the whole of the internet and software engineering works off Lewis Carroll Wonderland logic.

Did I miss something? When was there talk of a -95? I thought the scope was Early -135 (including a mock of the Iranian exports), Late -135, and the initial “B” which is really an A+ because they probably never made a NEW B with a fishbowl TID. Our B is almost certainly a refit A.

Droppin SCIENCE!!!

Then please translate for us, because he came in halfway through some conversation nobody was having.

“Soon“

Why is this your Windmill Don Quixote? Nobody here cares or even knows what the hell you’re in about. In contemporary parlance “Sir, This is a Wendy’s.”

The thing to remember is, these are modeling actual killing machines. It’s why you fire it with a trigger. And all good trigger discipline is that you squeeze to increase pressure and maintain that pressure until the firing action is complete. Unless your controller is broken, there’s no reason to assume it didn’t register your trigger pull.

Jester is a compromise for the friendless. Be glad it works as well as it does, the other alternative is nobody at all like the vaporware Razbam Strike Eagle.

In TWS the system will produce firing solutions for ALL targets unless they are specifically marked friendly, or specifically excluded. The AWG9 can’t see if a data link matched bogey is friendly. It’s your job to be sure you aren’t firing on a friendly. It’s part of why you have a TID repeater.

Good CRM babying your pilot. The RIO has their own work to do, a crew isn’t a pilot and a backup other pilot. It’s a Pilot and a RIO. You have your call and response before takeoff, fence in/out, and Before landing checks. Besides that, your pilot needs to do their own job so you can do yours.

Instruct them to be better pilots.