Supercarrier and F-14?

It is simple, If you do not own either F/A-18 and or F-14 then this module is of no actual use to you other than look pretty. It was developed with F/A-18 in mind primarily so expect full support for it and F-14 is compatible with the help from Heatblur.

 

Jump jets and helos can probably land on it like any other free carrier but no real simulation provided for them.

Why should HB need to do anything? Tomcat can land on current carrier and SC is no different. Deck crew does not care what ac type it launches, pattern is also the same. If someone need to actually change something, ED should add pilot salute on launch same as Tomcat has.

Deck crew does not care what ac type it launches

If we expect them to interact with the aircraft in believable ways they certainly do. They can't *see* where the plane and its components are, they have to *know*.

Well, the Tomcat is a completely different generation of aircraft so it would probably require a whole different method and interaction with the carrier. I am sure that people can just hook to them or launch like any other "basic" carrier but fully simulated and interactive landing or launching is a very different story.

 

From ED's response it seems like Heatblur needs to do more work to get it fully compatible with this module. Heatblur were probably busy developing simulation with their carrier so this just adds more work on their plate. Especially if they were coding or developing separate method of interaction between F-14 and the Forrestal carrier.

 

Let us hope it all works out in the end but I am still holding off on my purchase of the supercarrier until it is very clear what we are getting.

F-14 and F/A-18 are of the Same Generation, Just Different Programs

(Tactical Fighter Interceptor, Light Weight Fighter Attacker)

If we expect them to interact with the aircraft in believable ways they certainly do. They can't *see* where the plane and its components are, they have to *know*.

agreed. Sounds like something ED would have to code for each airframe unless there is some deck crew API that 3rd parties could use.

Exactly.

It might be as simple as putting the nosewheel location and probably wing width somewhere in a .lua. Might even already be. But considering that we have things like the Spitfire flame exhausts first moving to the wrong locations, then moving again to different wrong locations after an update, then on the third attempt to "fix" it the effect being deleted entirely, I worry.

Let's not forget, there are differences in recovery as well as launch.

One of the biggest questions I have regarding the F-14 using the Super Carrier DLC is the RIO position... What if the pilot has the DLC, but the RIO does not? I'm sure this is something that'll be considered, hopefully sooner rather than later. :thumbup:

One of the biggest questions I have regarding the F-14 using the Super Carrier DLC is the RIO position... What if the pilot has the DLC, but the RIO does not? I'm sure this is something that'll be considered, hopefully sooner rather than later. :thumbup:

The RIO is just following the Pilot's position so if the pilot has the collision model enabled, the RIO would "stick" to it.