Jump to content
  • Announcements

    • Erik

      2019 Drive   05/31/2019

      Can you lend a hand?  GET STARTED TODAY


  • Content count

  • Joined

  • Last visited

  • Days Won


Caesar last won the day on May 25 2017

Caesar had the most liked content!

Community Reputation

288 Good

About Caesar

Profile Information

  • Gender
  • Location

Recent Profile Visitors

27,726 profile views
  1. 2019 Drive

    Fired off a donation.
  2. DCS Weekend News: 24 May 2019

    I'll definitely be picking this one up, too. The Viper is probably my favorite behind the Turkey. I will say I'm surprised to see the price tag. I don't think the Bug was that expensive on its release, and they had to do more research on that airplane as I understand it. The Tomcat package is as expensive, but it comes with (when finished) two variants of the F-14, an AI A-6 and a Carrier. Pre-ordering, however, I can justify.
  3. The problem with discussing this graph relative to real-world aircraft performance doghouses is that the real-world charts for most of those planes shown are protected by distribution and export restrictions, so you really can't do it in an open forum without potentially falling afoul either the distro limitations or certain laws like ITAR. As to the in-game performance, there's a series of videos by The Grim Reapers which runs a bunch of the modeled aircraft against each other in terms of general performance. The F-14B has a just barely better sustained turn than the F-15C (equal payloads) on the deck, but you have to be slower in the F-14 to achieve it (20 deg/sec @ 300-330KTAS vs 19 deg/sec @ 350-450KTAS). Generally the F-15C out accelerates the F-14B in DCS against a Vmax of 650KTAS by about 4 seconds both on the deck and at 15,000 feet, while the F-14B has a better max speed on the deck, but lower max speed at altitude. The F-14B out-climbs the F-15C from 0 knots start, while the F-15C out-climbs the F-14B from 600 knots start. The two are generally comparable. What I've found is that the F-14B takes a lot more practice and understanding of its nuances, and I'm still learning a lot (have been away for a bit, and will be again shortly). A LOT of rudder work comes into play. The F-15C has the FBW and ARI and you can horse around with the stick all you want to point the nose where you want it to go without ever touching the rudder pedals, not so in the Tomcat. I've been watching some of the more competitive folks on YouTube and they've been successfully winning guns-only PvP fights against other players in Hornets, Flankers, and the like, but it definitely takes them practice and time.
  4. Have a safe and blessed holiday!

    Happy Easter, all!
  5. The way I do it is the same as nose numbers: iterative decals which are applied either left or right at the location where you want the number. An example, for the inaugural VF-1 Wolfpack skin in the Tomcat Super Pack, I made a set of .tgas "BuNoxxx" from 000 to 011. Each one matched the real-world bureau number of VF-1's F-14As from NK100 to NK114 (remember 108 and 109 aren't used), so BuNo000 matches USFtrNum000 and TailNum000, and NK100 will always be 158979, NK101 will always be 158989, etc. The call-out in the DECALS.ini look like this: [Decal007] MeshName=LeftEnginePod DecalLevel=2 DecalFacing=LEFT FilenameFormat=F-14A_74/VF1NK74/D/BuNo Position=-5.275,-0.95 Rotation=0.0 Scale=1.0 DecalMaxLOD=4 [Decal008] MeshName=RightEnginePod DecalLevel=2 DecalFacing=RIGHT FilenameFormat=F-14A_74/VF1NK74/D/BuNo Position=-5.275,-0.95 Rotation=0.0 Scale=1.0 DecalMaxLOD=4 Notice that they're the same decal, just facing a different direction. If you're using italics, it doesn't work cleanly and you have to make two different sets, but most bureau numbers I'm aware of aren't italicized. Hope this helps.
  6. Well, I brought it up against a Flanker (AI) and it went a lot better than expected. Of course, a human player would be completely different, but I'm at least building some confidence with my handling!
  7. Well, Heatblur finally released the F-14B into Early Access. If you aren't familiar with DCS, you may like to know that you need to run the module in the DCS World OpenBeta, rather than the full-up version. I hadn't touched OpenBeta and only played DCS every now and again in the past, so I was glad to find that out. I'm quite impressed with the module to say the least. The Jester AI is easy as pie to interact with, making long-range engagements very straightforward. I did three sorties tonight, after a control shakeout (DCS likes to assign axes to everything!) and basic familiarization flight. The first mission I forgot to set the time to 1200 and left it on "Random". So, a pitch-black fight against a MiG-21 it was! I have the tags on, still, in part because the monitor can slip out of my glasses field of view with TrackIR, and I can at least see a little red blob against the terrain, so that helped, but it does feel like cheating and I'll be shutting it off at some point. I was able to down the Fishbed and get back to base. This is fine! No problem at all... Second fight was in Nevada doing long-range stuff to check out Phoenix. The final fight was the included "MiG-28" fight, which was a 4v2 which sees you take a catapult shot and bring the plane back to land. Because we had an E-2 in the area, we got a vector for the bandits, ROE was splash anything that went feet-wet. I still haven't figured out how to direct the wingman, so he was effectively along for the ride. At about 25NM, TWS-A selected, I loosed both AIM-54Cs at a MiG-28 a piece, both missiles tracked and splashed their targets. Next bandit I got with my second Sparrow missile. The final guy got a shot off at my wingman, but his missile took dash-2's flares. Both AIM-9 shots I took were trashed and I had to finish him off with the gun. Plenty of gas left, but now I know I've gotta put it down on the boat, and man am I glad I went straight home, because I think it took me about 10 tries to get back on deck, and that last try, let me tell you - one of those famous "we land NOW, GOD-DAMMIT!" one-wires where I just barely missed a ramp strike. Wasn't pretty and I know I damaged the plane because little holes appeared on the port-side of the nose of the model to signify that the section had taken a beating. Funny enough, in combat, I only put 6.8g on the plane! Cat on the 'Cat "Hi, there!" No kill like a GUNS kill! I think it would come as the understatement of the century to say I was anticipating this module, but I will also say that until Heatblur did their official announcement video, I had zero confidence it would ever get done. The DCS community has been burned plenty of times in the past, and HB had run into problems and setbacks of their own while in development. My mindset became: once it's on my hard drive, then I'll believe it. As videos began to roll in, however, it became more like a kid on Christmas "oh man, I can't wait." Well, now I have it, and I can share some first impressions. The model is friggin' fantastic. The level of detail on it is stunning both externally and in the cockpit. The rivet-counters will have a tough time on this one; the models are based on laser-scanned F-14s sitting in museums, and years worth of research. The sounds are also amazing, to include a lot of clickyness to the various buttons and switches in the cockpit. The view out of the cockpit is very good, as one would expect out of a bubble canopy, but not as good in the forward quarter as an airplane without the "jail bars" splitting the windscreen. That said, with TrackIR or VR, you can simply move your head a little, or lean forward or back to keep tally. You can see clear through the tails from the front seat. In this case, I just started flying through a cloud, so it's a little blurry. The Jester AI, like I mentioned earlier, is very intuitive and easy to interact with. Even without reading the manual on how to interact, I figured it out in the first combat flight I took. The single biggest thing that will take time to learn is the flight model and handling characteristics. The F-14 is truly a stick and rudder plane, and the F-14s in Strike Fighters 2 don't even come close to simulating the adverse elements of the F-14's handling, especially wing rock and control reversal. I wouldn't consider myself a contender online at the moment, and the fact that I was able to take out the AI aircraft in a gunfight at this stage is simply because they are AI. If you hop in expecting the plane to hold your hand like the F/A-18C module, you're in for a ride. It has no g-limiter, no alpha limiter, beta (yaw) limiter, etc. It's you talking directly to the control surfaces and them doing whatever the hell you tell them to, be it to your advantage or detriment. "Need to get out of the way of that missile and put the stick in your lap? Fine! 10g ain't the worst I've been through! Boot full of rudder? I'm not stopping you! Canopy jettison followed by...oh, you son of a..." In terms of overall maneuverability (sustained/instantaneous "g", roll rate, etc.) the airplane feels good. If I didn't jack it up and start rocking the wings, I was able to turn perfectly fine and loaded as much as 9.8g on the plane in one of my fights without complaint. A major saving grace against the F-5s when I got the plane out of shape is the fact that the B adds energy quick, and I was able to stabilize the plane and quickly curl inside their turns to go from defensive, to neutral, to offensive reliably and repeatedly. I actually had to get one of them off of my dead six o'clock (he shot a missile while there, but it took my flares) and was able to reverse the situation in a manner of seconds. The F110's power also gives the plane a lot of options, such as pushing the fight vertical, or un-f*cking your carrier approach when you jack it up and almost put yourself into the back of the boat for the fourth time. AoA and airspeed are very important to pay attention to, and the rudders will make or break you in a dogfight or at slow speeds. I still haven't felt out the slow speed regime intentionally yet. I have run the plane out of airspeed during some hamfisted dogfighting moments, but honestly, it recovers itself pretty quickly, and it maintains a degree of controllability even below 100KIAS, such that I was able to point the nose where I wanted with the rudders as the plane flopped over and began regaining speed. It also allows you to go to full flaps for slow-speed flight/fighting without needing to pull the aux flap circuit breaker (of the few things not [yet] modeled, one is the circuit breakers). As I build confidence, I'll start looking to test my skills against MiG-29s, Su-27s, etc., and eventually get into multiplayer, but right now, I'm still learning the thing. Overall, it's a really amazing module. Every video I've seen talking about this module says that Heatblur set a new bar for aircraft in DCS. I agree. The plane is spectacular. You'll need to put in the time to learn it, but man, is it rewarding to fly. At some point in the future, the F-14A will be released, and the package already comes with a carrier and A-6, so its steeper asking price of $79.99 gets you more than just a single jet. In my opinion, it's well worth the asking price. I'm sure that'll buff out...
  8. I take no offense. It absolutely seems like the HB Turkey will be the most in-depth study simulation of the plane, and I can't wait.
  9. HB did say that the A will also be coming out after the B, so you will be able to fly it at some point.
  10. Heatblur announced a release date for their F-14: 13 March marks the Early Access launch date for the F-14B.
  11. This is spot-on. Rolling limits are lower than symmetrical due to torsion. It is not modeled in SF2 to my knowledge, or at the bear minimum, it won't cause early breakage if you're within the aircraft's max g * structural factor - I don't know if the airplane breaks faster if you're doing something like a 10g snap roll or whatever. As to the hard limiter on the F-16 (which the aircraft does have in reality), I know the third party F-16s and F/A-18s utilize the CAT1 G Limiter developed by one of the folks here at CA (can't remember specifically who; Fubar maybe?). We used it for our AI F-14s in the Super Pack to stop them from doing a one-and-done max G pull at the start of combat to make them slightly more survivable, but you can put it into whatever aircraft you want. [CAT1_G_Limiter] SystemType=HIGHLIFT_DEVICE DeploymentMethod=AUTOMATIC_G_loading CLiftdc=-2.7500 CDdc=0.0 Cmdc=-0.350 AreaRatio=2.000 SmoothDeployment=TRUE Setting[1].Angle=45.0 Setting[1].DeployValue=7.33 Setting[1].RetractValue=7.25 MaxDeflection=20.0 MinDeflection=0.0 ControlRate=5.0 ModelNodeName=Internal It allows you to pull up to, but not beyond the deploy value. I don't think the TW F-16 uses such a limiter, and hence why it can overshoot 9G.
  12. That's hard to say. As MB said, damaged engine mounts can mean any number of things, from no noticeable performance degradation to the engine catching fire. If you really want your aircraft to start breaking and rip off wings or damage engines, you can set the StructuralFactor= values to 1.0 and start overshooting regularly to see what happens. As to how accurate SF2 simulates the breakage, the answer is "not very".
  13. I don't think you can model something that specific. If memory serves, you can damage or set your engines on fire if the fuselage section is considered "damaged" or "destroyed" by the overstress, but that's about as far as it goes.
  14. In the data.ini, the max g is multiplied by the structural factor, so it's usually 1.2-1.5x the maximum g. I can't remember the default value, 1.2 seems to stick in my head, but you can modify each component's "StructuralFactor=" line to suit what you want. Still, the aircraft doesn't immediately break when you overshoot this, it just has a higher chance. Normally, it takes a massive overstress to outright break components off the airplane, but the more small excursions above max g*SF, the more likely something will come off. It all changes based on patch levels; I remember one of the 2012 patches was a lot more sensitive and the aircraft would break more quickly from overshooting. Currently, it seems like it happens much more rarely.
  15. Specific system damage, a-la DCS or other more in-depth simulators isn't modeled in SF2. Rather, each main component of the aircraft (wings, stabs, fuselage, etc) is taken into account and if you exceed the g-limit times the structural factor, have a chance of breaking. Normally what happens is the wings get ripped off. Sometimes the aircraft starts smoking, and if you have the debug on, you can see if the aircraft is considered "destroyed" even though you're still flying it. It's been a while since I've broken an aircraft, but I know I ripped the wings off a B-2 during SAM defense about a year ago, so it still happens at the current patch level. Way back (nearly 10 years ago) I recall ripping both wings and a stab off of an F/A-18 in a 24g pull up just to see what would happen.

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..