Jump to content

CaptJodan

Members
  • Posts

    230
  • Joined

  • Last visited

Everything posted by CaptJodan

  1. I'll have my pitchforks sharpened on the off chance the F-14 misses its March 20th date, because that's what was officially, and actually, promised. However, any kind of bitching prior to that is silly because, as you say, people were well informed when that end of winter was the ONLY promise being made (later refined to March 20th latest). Cobra set a very, very hard deadline and was not subtle about holding them to that deadline. And for that clarity, honesty, and acceptance of responsibility, HB gets roasted unnecessarily. It's why I hope that ED quietly works on the F-16 while continuing on the Hornet, and avoids over-hyping the Viper until it's much closer to release. The Hornet has plenty to keep people busy, with new features coming out on a regular basis. There is too much time for the hype train to get up to speed (that train likely has a couple of F135 engines to boost it up). And to be clear, ED doesn't necessarily need to have no updates. I'm personally thrilled with this update. But the more they seem to give, the more the community seems to demand. Continue the mantra "We're focusing on the Hornet, but work continues", and when we're much closer to EA release, start putting more specific info. People will likely complain about the lack of info coming out, but whatever. You're getting Hornet updates (if you have that module) so you know stuff is getting done (that will need to be for the F-16 eventually anyway). It's not like ED is sitting on their hands. Ultimately the Viper and Hornet projects are closely related. Whatever pushes the Hornet forward helps, at least in part, the Viper. That's enough for me for now.
  2. Thank you for the new newsletter info dump, including the news of including the CCIP upgrade. Super stoked about this. Also very happy to hear no release dates for now. But equally happy that there will be an EA period that starts with the basics, like you did with the Hornet. Lately so much discussion on this approach that I feared you wouldn't follow suit, but I for one have loved having the Hornet to play with and learn while systems have been integrated. Much appreciated. Also appreciated you correcting the "end of year" quote there. Unfortunate that's out there in the ether now, but at least you're on record that that was an oops and is not representative. People gotta pull the brake on this hype train. Got a long road ahead. This module is going to be VERY hard for me to not over-hype for. This is only a personal preference, not speaking for what should be, but I'd avoid over-hyping the community too soon. Best thing is to keep plugging away in public on the Hornet to show that it's a module that will be finished to silence the naysayers, while quietly getting the F-16 closer and closer to release in the background. No barrages of updates, just more Hornet goodness. Then, as release gets closer, BAM, huge news, F-16 coming out on X date.
  3. I did not. I will do this when the new card comes in. Though I will say there was an "oddity" on the first day of use where about once per day the system would "freeze" for several seconds. Wasn't sure it was the card but I now believe that it was. Broken upon arrival. The first card couldn't be tested because it was DOA. Didn't even show a picture when tested in 2 systems that worked with an older 980ti. I'll take a look at that when the new card comes. I tend to avoid overclocking as a general rule, so if the card is by default a bit OCed, I'd be fine with turning it down a touch. I'd rather save the wear and tear on it and lose a few frames than continue to go through this mess.
  4. I'll admit I did this. To be fair, it was getting to be time, and the trigger was either going to be something I really wanted like the F-16 (who knows how long away from now), another...say...space game that is in forever alpha (that I'll probably need another new system for by the time it finally is out) or pull the trigger now on the F-14. Felt like the F-14 was epic enough to deserve it. Now I just need to get each 2080ti they send me to stop failing.
  5. My graphics card has died. HB should hold release until my replacement arrives. Either that or UPS needs to pull the F-14 out of retirement to get my new card here in time.
  6. Is the Break X showing up before you pickle the weapon? I've had plenty of instances where the bomb won't explode if you do it after the break X appears on your HUD.
  7. Never know, might be a pick for the A-6 next time. :)
  8. I'm a technical writer by trade, so if needed, I'd volunteer. But something tells me ya got all the volunteers you can possibly need.
  9. I have to agree. I've watched every Tomcat video put out and while not all of them are stellar masterpieces, I've enjoyed them all and want more, even if they show the same thing other people have done. I don't really care what they're showing as usually every video shows me something new, even if the thrust of the video is air-to-air for the 15th time. Also I enjoy seeing the attention to detail and modeling effort put into the plane in the different lighting conditions people choose to go with. There's still plenty to see in every new video. Complaining there is too many videos? Sick of the hype? Hate options in loadouts that you as the player can choose to use or not? That's the problem with Heatblur. They raise the bar so high, people really do sharpen their pitchforks for the silliest things, cause gotta complain about something. Hey Heatblur, my F-14 didn't make me want some butts! Refund!! :pilotfly:
  10. At the end of the video Magz asks for comments on what you want to see next. Y'all should post and ask for a startup video. He did make mention of a cockpit tour as well as an option.
  11. Yeah, that's why I can't believe it. I refuse to. Not gonna board that hype train until there's a firm release date. But it would be nice if releases got shorter somehow.
  12. Really enjoying these looks into missile behavior. I've enjoyed all the preview videos of the Tomcat, but this series definitely touches on the big question mark that has been on my mind since this aircraft was started. Glad to be able to know a little about what to expect (if you're ready for the missile) when the module drops.
  13. I shutter to think of all the time I would have missed out on getting to know the Hornet if, even now, it wouldn't be anywhere near release if it wasn't in EA. And that's where we'd be. A Hornet that could still be at least a year away from actual release if it wasn't in EA. I'm sorry, but I'm actually aging, and I'd like to be able to play some modules before I'm dead or my body no longer can comfortably play the game. So I'm thrilled that the Hornet came out, and that we continue to see updates and new features added on a regular basis. I hope ED continues the trend with the F-16. That isn't to say I disagree with HB's approach either, per say. But I wouldn't want it to be the norm for everyone because not every developer is up to their standards. We may have to wait 5 years for a HB module, but we know when it comes out, it'll have that level of quality no one else seems to be able to match. Do I want to wait 5 years for a Mirage 2000 that, while good, will never be on the level of the Viggen or Tomcat in terms of fidelity? No, I don't really. If it's releasable at 80% from a developer that can only get it to about 90%, I'd rather they do that and continue to improve it than tack on another 2-3 years just to get to 90. HB gets you much closer to that 95-99% threshold. They've earned the respect and patience to be given the extra time, no matter how painful that wait can be. But if every dev did this, we'd have less than half the modules we have now, and probably less devs working on DCS as a whole, because they couldn't wait 5 years between new aircraft sales. At this point with the developers and third party people so far, we know which ones are trustworthy and which ones aren't. And I'm fine with those who don't want to participate in EA. But *some* (and only some) of those people also want to make sure others can't participate in EA by pressuring developers not to use early access for those who want it, even if they do it responsibly (as I feel ED has done with the Hornet so far). And that's where I have trouble.
  14. Jabbers' next videos will really tell us a lot about that. In this video he seemed to imply the next A model to be the most deadly because of it's speed, especially at <20 nmi. On several trials, he did seem to wait until the RWR went off to go defensive, even though I'm sure he saw the missile coming. If the C can be notched as easily as the A-M47, then it seems liable you can trash it almost as easily as the A-Mk47. Of course, as Jabbers says, these were optimal test conditions, where he knew where the missile was coming from and knew roughly when it would be launched. In a real scenario, all you may get is the RWR alert. I look forward to seeing the tests for both missiles.
  15. Really enjoyed this video and am looking forward to part 2. Real helpful to see the missile's capabilities and limitations broken down this way.
  16. I think the wing physics video was one of the best to see not only the wing flex, but the wing shake/vibration effects. Not sure I've seen that in any other video to that degree yet. Nicely captured, and just wow. Does HB ever get tired of pushing the envelope?
  17. Are you seeing the EW contacts on the HUD, just not the box around the contacts, or no contacts on the HUD at all? If the former, make sure to go to the EW page and select HUD on the page. That will display all EW contacts on your HUD. Not sure if it's the latter, as it seems to work for me fine.
  18. Thanks Jabbers for the very informative first look video. You answered several burning questions I had in mind, or at least gave me an idea of what to expect. Appreciated on the breadth of topics you chose to highlight.
  19. I'm with you.
  20. As one of my all-time favorite military aircraft, barely edged out only by the F-22, it would be an understatement to say I've been very excited about this coming to DCS. I keep seeing this 2019 number they keep hinting or outright almost saying, and I still won't believe it, even for EA. I mean, this is DCS....love it, but not known for accurate time estimates are they. For sanity's sake, I'm going to have to convince myself that EA happens in 2020 if we're lucky.
  21. I may not love the fact that it's not going to make 2018, but I give loads of respect to the HB team for sticking to their quality guns even knowing the pressures of releasing. Some in the community want it as perfect as possible before release, and is sick of F-18 style EA. Some like to play it as long as it's not breaking the game no matter what state it's in, ala the F-18's first release. I fall into the latter camp, but I can't help but respect HB's decision here. I also think communication like this is exceptional. Laying out the reasons there isn't a release, reasons why they won't give a hard date, and sticking to the core ideals of what they believe in as a developer that is different from other developers across the gaming industry. I may be getting really tired of waiting for this aircraft, but I know it will be worth the wait in the end, and I know they want this out in our hands as much as we do. So thank you for the clear, reasonable communication and (even though I hate the wait) thank you for sticking to who you are. I love flying the F-18 even in it's current state and very glad to have it, but I also know when the F-14 comes out, it'll be much further along.
  22. A great hype trailer. Wonder how they got that shot of the missile nearly hitting the cat right under it, with flares popping. Has to be my favorite shot.
  23. Somebody get that man a computer capable of running DCS. Great interview.
  24. That helps Wags, thanks!
  25. So just downloaded the new Friday hotfix and am not sure I am understanding how the climb FPAS climb is supposed to work. I presumed it gave optimal climb airspeed, but these numbers don't seem to add up to an airspeed I can reach. Is anyone else having this issue? Am I missing something obvious on how to read this in the HUD? Edit: I know something has changed because it's no longer just taking the vertical speed numbers (they do not match or closely match as they did in the Wednesday patch). So something was updated. So that's why I assume it's operator error first.
×
×
  • Create New...