Thank man,
You are upping the ante. If a true fan like you is going to be away and w no access it will be out then. Thanks for taking one for the TEAM.
Oh yes! Lotās of features. Did you know that it canā¦landā¦?
When I first heard about a DCS Viggen, I couldnāt believe it. It had to be FC level with some easy systems. Perhaps a mod, using the SU-25 pit. Something like that.
Heatblur (then Leatherneck), blew me away!
They reeeeally know their stuff!
Which is why I⦠I⦠This was a lot harder than I thought it would be. Which is why Iā¦AGREE with you! There! I said it.
The Tomcat is going to be awesome.
Considering how much is still missing from the Hornet I wouldnāt call it released at all.
Now if HARMs and all radar modes and everything were all there, but some of them were broken in how they worked, then I would say you could call it a beta. This isnāt a beta, itās a polished alpha allowed by the state of DCS World. I donāt think it matches the standards of āwell we got it out the door letās focus on the next release and leave just a pair working on fixing the bugsā that many early access games meet.
Downside of a multi-role aircraft is thereās so much more āstuffā to model. Conversely, HB doesnāt need to worry about Mavericks, HARMS, multiple MFD screen programs, the highly advanced SA programs powered by data link, or ground tracking radar with the F-14.
Thereās of course still A LOT of things to model on the Turkey, so Iām not trying to diminish the accomplishments of the team, but just pointing out that the Hornet is breaking a lot of new ground for DCS.
Overall, Iām glad they released the hornet when they did; Iāve been having a lot of fun with it, even in itās current state, and even then I can keep up with all the new features .
One cannot overstate this. Heatblur has been on the record that doing an F-14D would be a massive undertaking and so different that it would require another module. So while the Bug, as currently presented, has a limited capability set, in the future it will be doing far more than the Turkey.
From my own experiences, doing the systems modeling for an AH-64A wasnāt nearly as complex as they were for an AH-64D. The AH-64A didnāt have things like data sharing, target databases, multiple sensor systems, etc. The most complex piece of equipment was the IHADSS and the TADS. Further, not having to deal with the displays of the AH-64D meant that the cockpits were vastly simplified. The only reason we never got an AH-64A completed was because Nodunit had a hard drive crash and lost the model and textures.
Did you work on āCombat Heloā?
No, the AH-64D mod/addon for ArmA2/3.
I helped with Combat Help but only on the artistic side. And moral support.
A lot of bad luck happened right thereā¦
So⦠I was informed today that I need to pick out $100 worth of stuff as a Christmas present. So I chose the F-14 and two aviation related books. Canāt wait to try out the Kitty as a long range bomber.
Conversely: Minus the Maverick, HARM, and Harpoon and DBS/SAR, all of what you list actually exists in the Tomcat on primitive form or another. The TID combined with the RIOās Integrated Control Panel are essentially the mechanical equivalent of an MFD. The TID in normal operation is a direct precursor to the SA Page concept: it combines navigation and sensor information from the aircraft and rectifies it with external data link information.
Depending on the extent to which Heatblur has chosen to emulate systems rather than simulate them, Iād happily wager the F-14 is a far more complex aircraft than the F/A-18 on the inside. Weāre talking about attempting to offer functionality that would be ground breaking in the late 80s in a fighter that reached IOC in 1972. From what little you can glean from the NATOPs, the amount of integration occurring between early digital and analog computers and devices is ridiculous
I donāt know the level to which HB is attempting to actually model that, or if itās instead just black box in/out, but my point is attempting to realize any aircraft of sufficient complexity is a massive undertaking. That goes for the F-4, the F-14, the F/A-18 or what have you.
I just finished listening to episode 3 of the Alert 5 podcast, which includes the Heatblur interview, and came away very impressed with both the team and their vision for the DCS Tomcat. Much is revealed.
So⦠what about the intruder?
Thatās what Iām saying⦠Intruder alerts have gone quiet again
You could say that update news is a direct relationship to the tadpoleās speed
My home alarm sends me these regularly. I wish I knew what they mean. And where my stuff keeps going
Does āwhat have youā = F-111?
As in āwhat have you DONE with my 111???ā
In real world terms, this is true; from a coding/scripting standpoint, the Bug is a fair bit more complex to implement.
Practical example: in the AH-64A, the targeting system only had to track on sensor set and run a LOS routine on those targets visible by that sensor for a given visual distance. Once thatās done, we only needed to watch the current target and track whether or not it was visible to the sensor and whether the laser was still hitting it. That was the extent of the sensor suite, really; even though it tied into the IHADSS, the gunnerās ORT, and the pilotās VDU (his TV), there wasnāt a lot of extra stuff to track.
In the AH-64D, the system changes because we also have the TSD, which integrates the entire sensor suite, including the RWR. So now in addition to finding visual targets, we also have a radar, as well as a detection routine for ADA that might trip the RWR. So weāve gone from only caring about visual targets, but the targets weāve already seen, the targets the radar has seen, and the targets that have tripped the RWR. That all comes together and gets put into a database that must be continually maintained. This leaves a lot more going on under the hood than the A, and thatās just with sensor systems and targeting alone, nevermind stuff like moving map displays and navigation (believe it or not, these were big deals in ArmA).
In that respect, because the Bug has to be able to do more stuff ā especially with air-to-ground ā coding and scripting wise, itās got a hell of a lot more complexity. The F-14, while mimicking some of the capabilities, doesnāt have to worry about JHMCS and integrating that with missile seekers, radar modes, and the targeting pod. Further, MFDs are a royal pain in the butt to code and script in comparison to analog instruments.
I was sure glad to have figured out how to do a moving map display, but it would have been far easier to duplicate the same system I put in on the Fitter, which was just a series of waypoint coordinates in a sequential array, where the instrument in question only had to point an arrow toward the next waypoint and the distance. The data that a digital MFD puts in place makes things a lot harder, doubly so when your MFD has to do all these other things on top of that!
https://forums.eagle.ru/showpost.php?s=7e1acc8d930958272a87d8ee81d98031&p=3719863&postcount=208
Community doing the normal over reaction over Tomcat release datesā¦