Jump to content

Flamin_Squirrel

Members
  • Posts

    2678
  • Joined

  • Last visited

Everything posted by Flamin_Squirrel

  1. None of the information you speak of is mentioned in the news letter and mini-updates you directed me towards - there isn't even a mention of the delayed release. It's all buried in this 200 page thread. There is no one good central repository of information of the status of any module. Exhibit A: This is it I'm afraid. I wouldn't count on it coming out this week.
  2. Perhaps, if they'd actually included any up to date information on the carrier, which they don't.
  3. Straw man argument. Nowhere was a requirement for devs to spend hours on these forums mentioned in that post. Besides, that's not a dev job anyway. There wouldn't be these constant requests for info if the salient points were put in a sticky for people to easily find. That wouldn't take much time at all to do.
  4. Good points, but things have changed - in particular, pre-sale and early access. Taking people's money then not communicating, especially if dates get missed, will damage confidence and make selling subsequent EA products much harder
  5. They have options. Post information in locked stickies, for example. Its within their gift to control.
  6. Start communicating on here instead of higgit would be a start!
  7. Patience! SC will come and it will be worth the wait. ED know they screwed up (we've told them so) and I'm sure they've learnt from it. No need to throw the baby out with the bathwater. :joystick:
  8. Maybe long term we'll have persistent aircraft between missions; that would make doing checks/BIT etc worthwhile. Features that aren't well developed or have limited utility now may do in future. You've got to start somewhere, so I think there's value in introducing basic functionality now. I would agree it's a backburner item though.
  9. You're conflating an aircraft simulator with an USN officer simulator. The objective of DCS is to simulate the vehicles as faithfully as possible, not tell you how to use them.
  10. ??? I drop the gear when speed reduces below 250kts. That's the speed limit for gear, so not sure how you're doing it earlier!
  11. Understandable. I think there are reasons to be positive though: much of the modules and their weapons that they've released over the last couple of years are more complex than anything they've done before. This is a difficult time where they're developing a lot of new tech. I think it'll get better once much of that is in place.
  12. I'd have thought hindsight should make you more positive - ED are still maintaining products that are 10+ years old. Yes it might take time, but they'll get there.
  13. It takes nowhere near that long. You need to make small corrections more often.
  14. Yes. No. Constant corrections are required.
  15. No idea how realistic it is as I'm no Hornet pilot, but it is perfectly possible to fly straight and level in DCS. I expect your technique is probably lacking anticipation - your pitch is probably deviating a fair amount before you react, so you make large power corrections to catch it, which just makes things worse. You need to make frequent small corrections IMMEDIATELY at the point you see pitch move away from where you want it. As a training exercise try flying straight and level, find a point on the HUD frame in line with the horizon, and keep it at there.
  16. As long as it's logged, that's great. Thanks.
  17. A centre mounted provides enough space for a conventional stick. Any plane with a side stick I believe is also the force sensing type. The only reason you get away with a conventional stick on your desktop machine is because most desktop sticks only have a fraction of the throw of the real thing.
  18. Drop gear and flaps during the break; that way all you have to do is modulate back pressure to compensate for the additional lift.
  19. Not flow it for a while, but I'm guessing it's so the HSI is aligned with the runway, to prevent confusion.
  20. Hi BN. My bad on NATOPS. Just to point out though, damage to the launch bar wasn't what I was raising as a bug: If the L BAR switch isn't moved to RETRACT prior to launch then the nose gear won't retract with the main gear. You'd then have to move the L BAR switch to RETRACT and cycle the gear to get the nose gear to raise. Currently you can leave the L BAR switch set to EXTEND and the gear will retract fine, which it shouldn't, hence it's a bug.
  21. At the moment, you can leave the L BAR switch in EXTEND, launch from the carrier and retract the gear with no issue - I don't think is correct, as per NATOPs para 2.10.4: Although it doesn't specifically link failure to place the L BAR switch to RETRACT before launch to the L BAR light illuminating RED thereby preventing retraction of the nosewheel, reading between the lines that seems to be what would happen. Hopefully this can be investigated and confirmed in more detailed documentation. Thanks in advance for considering it.
  22. You misunderstand. That paragraph references the effect of the L BAR on the landing gear (already understood and previously mentioned in this thread), not the landing gear lever's effect on the L BAR - the latter is what SkateZilla was talking about and which I was responding to. And since you bring it up: 2.10.4. So yes there is another means, just not applicable for this LOT.
  23. Don't feel bad, I read it the same too :D
  24. I've looked into this a bit more; I can't see any reference to the gear lever having any involvement. On early models, moving the throttles to MIL or above, the L BAR switch returns to RETRACT. Later one's it does not, and it's up to the pilot to do it. I can't see anything else in NATOPs that catagorically states that failure to move the switch to retract will cause L BAR to illuminate red and prevent nose gear retraction; however one of the emergency responses is to ensure the switch is set to retract if the indication arises, so that is probably the case. Would you like me to raise as a bug, or are you happy to bring it up? Thanks.
×
×
  • Create New...