LanceCriminal86

Skins can come one of two ways, either directly from the dev provided in the main install with the aircraft, or downloaded/installed from the user files in a folder that will read and display them. Right now the general goal is that the main countries that operated the F-4E and its variants will have represented skins available. HB is not going to be making separate versions of each exported F-4E systems wise but at the least skins for those operators should suffice. Once the later E comes along some skins could be shifted around to better represent the systems of those export models but we're nowhere near crossing that bridge quite yet. Some nations added dual language stencils so there would need to be some research done there, tracking down various squadron logos/stencils beyond just a plain jet with say Korean roundel on it. Probably there will be more generic/dynamic skins available for things like dynamic numbers, and separately detailed specific airframe skins, anniversary schemes, farewell jets, demo teams, etc. I'd expect basics at launch, whenever that's going to be with more schemes and squadrons added over time.

No, by the -90 and -95 those were ironed out as well as they were going to be. The screens will all still be there, you just won't have anything show up if you try to select the TCS, if the switchology will even be there. At the minimum it should be the "early" 1980s -135 but with some systems disabled, not sure if they will make a 3rd or really 4th cockpit iteration just for the Iranian jet, maybe the panels will be blanked over via some arguments. But both screens should still be there.

VF-11 and VF-31 transitioned to F-14Ds in 1992, with only a few others doing so later like VF-2 and VF-213 after their sister squadrons shut down, and 11 eventually going to Bs in the late 90s. DCS is supposed to be a "rivet counter" type sim to at least some degree, but more importantly Heatblur themselves have stated they don't want to half-bake any version or component/system. They said the same with all of the PTID questions, because little exists mapping out and showing all of the different displays and pages for the systems that were integrated, or the different piggy-back systems eventually added later for JDAMs and GPS. And yes, Bs got JDAM too. Part of the B upgrades included a digital BUS, iirc it was the As that needed a digital to analog converter for LANTIRN. VF-11 and VF-143 did the operational testing and 11 deployed with them in 2002, performing the first combat JDAM drops from a Tomcat. The guy that wrote up the F-14 JDAM article/story/whitepaper deployed with VF-11 on that cruise as he was the program officer on it. But JDAM required additional piggyback equipment to work. DFCS also didn't come until later, and was rolled out to all operational Tomcats at that time whether A, B, or D. The D didn't have DFCS from the start. DFCS testing was in 1995 with rollout to fleet As starting around 1998. Adding DFCS alone would be quite an undertaking in DCS, having to model how it interceded and did control coordination or spin recovery, we'd need details on all of that whether A, B or D. F-14Ds didn't get PTIDs until the As and Bs started decomissioning, and the PTIDs were moved across as the D's TID was digital and newer. After VF-103's testing and cruise with LANTIRN in '96 VF-154, 211, 41, and 14 received LANTIRN as well, with there being transitions from 96-99 of some jets having LANTIRN but not the PTID yet. The D also had a different jamming suite, altered external model features that would need to be done, cockpit remodeling, pilot would need changes to some of the equipment as the D had OBOGS and used different regulators. There's a lot to even just an old D, and Heatblur still don't want to cut corners. Docs have to not only be available but releasable/usable by HB without someone going to the Fed for breaching ITAR and espionage charges. Also, PTID had been a separate project due to old TIDs burning out and wasn't originally linked with LANTIRN, it just happened to enhance the capability. That's part of why As got them initially as their TIDs were the oldest and needed replacing the most from what I've seen.

Based on the previous discussions about the Phoenix, there is no API 'documentation', whitepaper, wiki, etc. as again it's still being worked internally by ED, but ED will sometimes provide values to use. The Phoenix may not even be 100% on the same "new" model as the AIM-120 if you peel further back.

All it means is that if any requests for docs ever come through, that are actually releasable to HB for use in a simulation, then they'd look towards what they could do. If you were to mind map out all the systems, displays, tests, MFD views, and all the progressive updates to the D from when they were delivered through 2006 there's a huge amount that would have to be covered. Doing a 1992 F-14D and a 2005 F-14D is a pretty big canyon of differences potentially.

You keep throwing "API" around but it's a lot more than that. ED barely even shares the "new" missile "API" with HB, nevermind the unfinished state of the SC implementation for crew, elevators, parking, comms, and LSO/IFLOLS. Yes, ED has implemented a way for the Stennis to be both SC and non-SC, which means yes, HB *COULD* add that on. But that isn't going to be done until the SC implementation/framework is more complete and nailed down, as the Forrestal itself likely needs to be "rigged" on the model side or have other reference points added and coordinates for crew, the ability to have unique/different crew skins to properly recognize the 80s-91 era of the Forrestal or later on for say the Sara, Indi, and Ranger, probably some kind of FLOLS instead of the IFLOLS of the more modern carriers, it would need internals added for the bridge/PriFly/Airboss, maybe even a briefing room skin. ED would have to have completed that themselves before a third party should even think about trying to add the same framework, and there would have to be some kind of documentation showing what is needed and how it would be done.

How do you expect it to be integrated into a module/framework that itself isn't even partway finished? Why should they burn up focus and coding effort on something that ED themselves haven't even completed and ironed out for their own ships? There's plenty for them to work on with just the F-14 itself while ED figures out exactly what they're doing on the SC module/framework. Right now we can't even access the deck crew to skin them because ED encrypted those away somewhere.

But first-person accounts are, and they stated exactly what I provided that by month 2-3 the lines were extremely obscured by tire marks, deck grime, fluids, etc. I have already provided a complete timeline of Forrestal's 1988 cruise in terms of deck photos from lots of different angles and weather, already from the pre-cruise visit to New Orleans to the first month or two at sea headed to the Suez it went from brand new to about what we see in the DCS model and just stayed that way or worse through her return. I think the issue again is how DCS is handling things like LODs, mip-maps, textures at distance, and lighting. And the latest update has impacted a lot on the lighting front, with roughmets behaving quite differently now than they used to. With the game engine performing "better" or differently the hints of the lines should be more visible further out.

{"HB_F14_EXT_INTAKERAMPS", 0, "hb_f14_ext_intakeramps", false};

HB_F14_EXT_INTAKERAMPS. If it isn't in the template you will have to grab it from the coremods/aircraft/f14/textures/diffuse_roughmet folder and use overlay or another mode to work with it.

Been asking some aircrew, by month 2-3 the decks were quite worn like we are seeing, both the markings from all the tire skids and fluids, but also the actual anti-skid wore off and the decks got slippery. IF the tempo and time and weather allowed sometimes they'd re-apply anti-skid, and sometimes touch up markings, but not always and it again would quickly get worn/beat up/grimed over again. Add to that weather, sun position, and trying to see the deck markings could be extremely hard.

Ejection seats are basically metal/plastic containers with a thin butt cushion, like wooden chair with one of those tie-on butt pads: I hacked up a cheap racing seat for now but eventual plan would be a GRU-7 repro. Racing seats aren't a bad base but most ejection seats have no bolsters and as said, the seat and backs are solid containers for survival items and parachutes and such.

Whatever you can find, it's the APR-36/37. When built most Es after the first batch through mid '68 had the APS-107, but the performance was considered to be terrible, and after VN jets were upgraded with APR-36/37. It looks like the older Phantoms had the 25/26, and really late ones had ALR-46 but I believe the APR-36/37 are currently what's planned from the release posts.

TISEO will the be the second E that comes with DMAS and factory slats etc. TISEO was on the '71+ serial jets. First released jet will be the older 66-69 serials with retrofitted slats.

So, as a friend who is a Hornet enjoyer likes to remind me, there apparently was a letter from the CO of VFA-125 to the Deputy CNO in 1982, where they noted that during a deployment to Yuma earlier in the year they were able to maneuver their F/A-18s into a rear aspect gun or AIM-9 shot on an opposing F-14 in 20 out of 34 engagements, with the F-14s unable to gain a simulated firing solution against an F/A-18 in any of those engagements. Book is "Legacy Hornets: Boeing's F/A-18 A-D Hornets of the USN and USMC by Brad Elward":

Keep telling me to "go back to school" and I'll keep reminding you to read the forum rules and responses from the devs while you attempt to "1v1 me bro" and make personal attacks.

Getting a little personal aren't we? And from the last rounds of these performance tweaks I recall that there were factors related to stores drag that are out of HB's direct hands, as the drag of the AIM-7 (and all other stores) is controlled by ED's values, which don't take into account drag differences between different pylons and airframes.

No, I read very clearly where the representative of the development team explained what is going on and you continued to insist on directing their development resources from an internet forum.

So you're the development lead now?

Yep, most of his photos were from Edwards, Nellis, and sometimes Miramar but he did have the airport code on there as I see it now. https://www.flickr.com/photos/147861202@N07/albums/72157666900357129/with/38691679272/

Coming, eventually. VX-4 F-14A+ 162911 from 1988. Same airframe would go to VF-24 as the 201 skin that currently is included (and is on the list for some fixes), then went to NFWS briefly and ended up over in VX-9 later on before ending up with VF-11 from '97-'04, and she's now on display as such: References, mainly thanks to the great Keith Svendsen's wonderful photos from Edwards and other bases/airshows from the 80s-90s, who caught her at the Edwards open house or airshow in 1988: But wait, helmets? Names? Well that took a good while, but I finally found a photo of some VX-4 crews walking to both Vandy1 black Phantoms, which dated to March of '89, and other photos from '87-'89 Point Mugu airshows showed these helmets but not clearly: Some more digging, and I found out "Edelen" was Marine Captain Russ Edelen, who worked on the F/A-18D stuff at Pax River in '86 and seems to have been around VX-4 at the right time as a back-seater, and the for the pilot, Tom Lindgren who was an F-14 project officer with VX-4 from '87-'89 and a Tomcat pilot. The pilot bodies are going to be changing at some point in the future, so I'll redo them at that time.

And some real world skins:

I can see a lot of unknown data points that would have to be known or somehow deduced to really figure out jamming and burn through and all that noise, no pun intended. Not just the actual transmission strengths of the radars and jammers but frequencies and all kinds of jazz, how the radar processes the results or discards erroneous returns, etc. I'm not sure how they'd even go about adding something like a Prowler to do protective jamming of a formation or flight, or area denial or any of that for the AI side. I understand there are some nice scripts that were done for the IADS framework/script to "disable" SAMs that were in a radius of a jet with that jammer script but trying to have more stuff like that to impact player aircraft is a huge challenge with lots of unknowns, all wrapped up in red tape.