Jump to content

AvroLanc

Members
  • Posts

    1322
  • Joined

  • Last visited

Posts posted by AvroLanc

  1. I'm not 100% certain the missile is supposed to climb to the altitude. I've seen that behavior for all modes whereby if flt profile is >= current altitude it just attempts to maintain the current altitude. Definitely a SME type of question though.

     

    Yeah I suspect this is correct behaviour. You could hardly expect the missile to climb to 30000ft from, in theory 2500ft min launch altitude, and still have fuel / energy remaining.

  2. Video source linked is from an F/A-18E, Super Hornet. Can't really claim it to be inaccurate in sim as there are actual real differences in the two aircraft.

     

    Come on, seriously? The command heading bug should be wind corrected. Period. Any ounce of aviation common sense / aircraft familiarity makes this obvious.

     

    The current implementation flies you on a track downwind of the intended path, clearly illustrated by the OP.

     

    Not sure why this is in Wishlist and not BUGs.

  3. Just to revive this mater.

     

    Although the movable reticle "double D" search pattern was removed, have anyone ever wondered:

     

    Why would "Fleet Defender" producers (MicroProse), featured a movable reticle (with circular search pattern) from the start ?

     

    Haha, just when I’d got over this issue!

    Microprose probably we’re using similar reference material? This argument did occur to me months ago.

    I think we just have to go with HB now on this.

  4. Any code btw 1111 and 1788, like said below:

     

    "The entered value can range from 1111 to 1788, but the first digit of the series must be a 1 and the last three digits must be between 1 and 8."

     

    So you never forget to not use "9" or "0" in the code...and always will be any number btw 1111 and 1788!

     

    First digit always 1

    Second digit 5,6, or 7

    Third and forth anything between 1 and 8

  5. I imagine this might get move to Wish List [Coming Later] etc, but

     

    I've got doubts as to the systems accuracy of the Mav F. It seems that you can slew the seeker to a designated target (e.g. Waypoint), but then it's impossible to slew away, you can undesignate but this then removes TMR range information, which kinda feels wrong. The manual states

     

     

    In addition to manually slewing the seeker to locate and lock onto a target, the seeker may also be slaved to a target (TGT). This could be a waypoint designated target (WPDSG) or a target created witha sensor. With a TGT created, the Maverick seeker will slew to the target location. Once there, press the Cage/Uncage [C] button to uncage the seeker and allow manual slew.

     

     

    The problem is: There's no way to allow manual slew without undesignating TGT. The Cage/Uncage command does nothing. Enabling/fixing this would solve the problem.

     

    There's no track since it wouldn't help to illustrate issue.

     

    Respectfully, this doesn't seem to be related to the TGP, but rather to the cage/uncage behavior of the Mavericks. It doesn't matter if the designated target (TGT) is set with the TGP TDC Depress or via WPDSG, the missile's behavior is the same.

    Although, based on the recent AUTO bombing target elevation bug, I would expect the entire TGT designation logic to get a facelift, even if it's just in the code.

     

    Still looking into this,

     

    Just wanted to mention we do have a related bug when a MAV is used with WPDSG it will only slave once, and not afterwards.

     

    So this is something that needs to be fixed.

     

     

    I am still looking into if the MAV can be slewed or not while in WPDSG, when I find out I will pass it on.

     

    Thanks Harker for clarifying the issue.

     

    Thanks BIGNEWY for looking into it.

  6. Can't tell if it's WIP or not, but ATC approach mode works in openbeta since 4 months at least.

     

    It works in approach mode if you press ATC when flaps are on Half or Full. (it takes some seconds for ATC to stop flashing and engage, since it cuts throttle, let the plane start stalling, maybe to record min. speed according to weight, then engage and provide auto thrust for constant onspeed flying, after trimming of course)

     

    It's described in DCS f/a-18c early access guide page 62. And works like described in guide.

     

    No, it's not implemented yet. At best it's trying to hold speed, at worst it's bugged (as per your description).

  7. Yes, it is correct behaviour. Real throttles moves by themselves when ATC is engaged.

    Why it is done this way? There could be different reasons. Possibly, to indicate, that ATC is working right now.

    While developing modules, we sometimes encounter things that seem to be illogical or impractical. Without full information and years of study of different subjects it is difficult to explain every single decision made by developers of original airplane.

     

    Personally I know I would find it disconcerting if the A/T didn't move, Airbus style...

     

    In my aircraft the A/T servos move the physical throttles, and it's useful feedback to know what the systems are doing. You can also quickly override if you're not happy.

     

     

    Any ETA on the Approach mode for ATC Cofcorpse?

  8. We are planning on implementing alt call outs around the carrier at some point (no promise so far) but speed calls was not really on the RIOs checklist, as speed during landing does not really matter. what matter is the AOA and that was pilot side, the RIO does not have an AOA indicator, if at all he glanced over the pilot's shoulder.

     

    If you modelled the RIO's AVIA display (please), it would give him an AOA readout. Cheers.

  9. Hmm... based on that description, it sounds like when a TGT is designated, the Maverick slaves to it when CAGED. In other words...

     

    Current Operation

    - When caged, TGT or no TGT: slaved to boresight

    - When uncaged, no TGT: free slew

    - When uncaged, TGT: slaved to TGT

     

    Potentially Correct Operation

    - When caged, no TGT: slaved to boresight

    - When caged, TGT: slaved to TGT

    - When uncaged, TGT or no TGT: free slew

     

    This does make sense, although I can see it being correct either way. Will see what ED says.

     

    This would make sense from my understanding. Being able to designate a TGT and have the Maverick slave to it, then able to slew (while retaining the TGT) is an important capability.

     

    It does seem the IR Mav was slightly rushed out to us, and then left a little incomplete.

  10. I imagine this might get move to Wish List [Coming Later] etc, but

     

    I've got doubts as to the systems accuracy of the Mav F. It seems that you can slew the seeker to a designated target (e.g. Waypoint), but then it's impossible to slew away, you can undesignate but this then removes TMR range information, which kinda feels wrong. The manual states

     

     

    In addition to manually slewing the seeker to locate and lock onto a target, the seeker may also be slaved to a target (TGT). This could be a waypoint designated target (WPDSG) or a target created witha sensor. With a TGT created, the Maverick seeker will slew to the target location. Once there, press the Cage/Uncage [C] button to uncage the seeker and allow manual slew.

     

     

    The problem is: There's no way to allow manual slew without undesignating TGT. The Cage/Uncage command does nothing. Enabling/fixing this would solve the problem.

     

    There's no track since it wouldn't help to illustrate issue.

  11. Thanks, only noticed this report now! Guess it got buried a bit. It's tracked on our side now, should be an easy fix (famous last words).

     

    Great, took me ages to work out why I’d get it sometimes and sometimes not.Turns out it was relative nose position. Why? No clue.

     

    It was my fault, I marked it as bug, but it seems I forgot to open a tracker.

     

    Naughty, but as long as it gets squashed.

  12. Sounds interesting and when flying in IMC/IFR conditions as a RIO I already wish sometimes I would have something like that. I have asked my pilots more than once about our current AOA (yes, I sometimes don't fully trust my pilot to bring us home safely :music_whistling:)and hence would love to see that myself, as well as ILS and vertical velocity! :thumbup:

     

    Indeed, would be very useful in mp. As far as I know you get scales each side with speed and angle of attack as well as a velocity vector and ILS bars in the middle.

  13. Totally forgot about Collision Steering and NAVGRID, which are great points! :thumbup:

    What's AVIA though? Never heard of it.

     

    Attitude, Velocity, ILS, Angle of attack.

     

    It’s a display mode that projects some attitude indicator type information on the RIO’s TID. Its used I guess as a cross check against the pilots info for crew coordination during IMC / IFR. Limited use I guess for most of us on dcs, but I want it because it’s more buttons and displays to play with and for completeness sake.

  14. TWS Auto, TID BIT tests, IP Bombing with human RIO, RIO white flood lights, RIO button lighting and getting the F-14B engine instruments are things I really miss.

    And of course ED related issues like correct Phoenix guidance and RIO cockpit shaking.

     

    +1, all of that plus Collision Steering button function, NAVGRID, AVIA display , correct exterior model for BOL Chaff rails, various pilot test switch functions during cold start.

  15. Quick question...

     

    Is there a setting / config that forces the route timing, specifically the DTOT feature, take the actual flight plan legs into consideration.

     

    It appears that the DTOT / TOT readout only applies for a direct straight path route? Shouldn't it take all legs and courses into consideration too, to generate an accurate required speed to reach a planned TOT?

     

    Only had the Hog for 9 years, still digging into specifics.

  16. Right there with you!

     

    While a cockpit overhaul is in the making to make it look nicer, especially in VR, a Helmet Mounted Cueing System is more than a minor update. The A-10C Suite 3 that we have in DCS never had it. Newer suites certainly did receive it IRL. But unless ED decide to provide a newer suite A-10C, we're not getting the HMCS. And they never announced any plans in that regard, unfortunately.

     

    Yeah, I guess everyone's familar with the idea that ED were contracted for a particular Suite 3. Likewise it's been mentioned before that a payed update would attract a lot of us.

     

    Maybe some cherry picked additions, along with a relaxation of specific ANG issues, might allow a Scorpion HMD to come one day? Just a pipe dream.

  17. Well, I've had the Warthog since day 1 of early access back in 2010... It's been a while...used it on and off since then between new DCS toys and other sims.

     

    I've recently upgraded to VR with a Rift S and after being wowed by the Hornet and Tomcat decided to give the A10 a go...

     

    I have to say I've just had the most immersive 2 hours for a long time, playing through the A10 Red Flag campaign.

     

    The combination of a feature complete module, VR and a realistic mission set is amazing.

     

    I know it's been said before but I do wish the A10 could receive some kind of minor update. The addition of a helmet mounted display to point the TGP would be so so welcome.

     

    After all these years the A10C is still an awesome product.

  18.  

    Thanks. I had only seen one of those before.

     

    They’re all using AUTO mode though. Or a weird mix of Man on DDI and AUTO on HUD. But yes time of FLT and TOT looking to be in at least.

  19. D/L frequency is and will not be simulated per the latest update to the manual.

     

    This is a real shame I agree.

     

    MIDs use is pretty simple even in real thing from what I've read. As long as the MIDS data is loaded from the data cartridge the operation is pretty transparent to the pilot. He has little to set up that can't be simulated for ours needs. I was reading about it from an F-16 manual.

     

    Bascially it's:

     

    Load the data cartridge / MUMI page - which contains the preloaded channels / frequencies

    Ensure you've got a good GPS time (Non-NTR) or enter the correct time (NTR)

    Hit 'Network entry' and watch the sync status go to 'Fine Sync'

     

    I'm not sure what can't be simulated about that. Surely the Mission editor could have a additional 'MIDS channel' option for each Link-16 capable aircraft. Ensure the channels match for your mission and there you go, immersion and realism increased.

×
×
  • Create New...