Jump to content

Callsign JoNay

Members
  • Posts

    726
  • Joined

  • Last visited

Posts posted by Callsign JoNay

  1. 6 hours ago, rob10 said:

    How would you like them to fix it if they can't even see it themselves?  And how would they know if they fixed it if they did change any code?  So yes, you need to at least find a way to get a track of it happening so they can see the problem.  Intermittent issues really suck to fix.  And if it's some weird combination of your hardware and/or other programs that's causing it they could spend weeks trying to reproduce it (so they at least had a starting point to try and fix it) and never see the issue.

    I'm sorry but that's ridiculous. 😆  They are the devs. They have knowledge of the code and surely have tools to get under the hood and investigate. It's their job to fix bugs, not to give up because we can't figure out how to reproduce it for them. We've proven it exists as much as we have the ability to. They should investigate.

  2. 1 hour ago, rob10 said:

    How would you like them to fix it if they can't even see it themselves?  And how would they know if they fixed it if they did change any code?  So yes, you need to at least find a way to get a track of it happening so they can see the problem.  Intermittent issues really suck to fix.  And if it's some weird combination of your hardware and/or other programs that's causing it they could spend weeks trying to reproduce it (so they at least had a starting point to try and fix it) and never see the issue.

    Marlan got a track of it above, but it doesn't show in the track. So how would you suggest we do that? 

  3. 10 hours ago, BIGNEWY said:

    I can mention it to the MP team, but without a track replay or a way to reproduce it will be difficult to diagnose and report if it is a bug. 

    Ok thank you. Yes please mention it, because I have track recording turned off by default and it's unlikely I'll be able to supply a track for you. I'll make a track if I figure out how to reproduce it, but I currently have no idea what causes it.

     

    If anyone else following this thread has insight, please share. I love my AZEL page and would like it to be as reliable as the other systems.

  4. @BIGNEWY

    Here's a picture of it happening. I've got three friendly contacts ahead of me. The closest man at ~15nm is below my scan elevation, but the two contacts at my 11 o'clock ~50nm are within my scan volume as represented by the bricks in RWS. All three are also showing friendly circular HAFUs in the SA page. The AZEL is empty though. I should have two HAFU/hits at my 11 o'clock co-elevation and another showing below my yellow box scan volume at 11:30ish o'clock.

    image.png

     

    Here's another picture of it happening. I have a jamming contact coinciding with a nails-29 possibly beyond my scan limits and maybe outside of the AWACS L16 coverage so disregard him, but at my 2 o'clock right below the dugout I have a brick in RWS coinciding with a non-jamming hostile L16 HAFU in my SA page on a hot aspect. At the very least that hostile should be presenting within the yellow box scan volume on the AZEL at 2 o'clock but the entire C-scope is just empty.

    image.png

    When this bug occurs it lasts the entire flight from take off to touch down. Re-slotting is the only fix I've found. As I said above I have no idea how to reproduce it, it just happens occasionally in about 5-10% of my multiplayer flights.

  5. 15 hours ago, BIGNEWY said:

    please include a short as possible track replay example and the dcs log from the same session

    thank you 

    The problem is I don't know how to reproduce it. And I'm trying to think back if I've even encountered it in SP, or only MP. It's possible it's an MP thing, in which case I won't be able to supply a short track. I can try to get photos of it the next time it happens, but that might be the best evidence I can provide since I don't record tracks by default.

  6. There's a long standing persistent bug with the AZEL page. In about 1 in 10 of my Hornet flights I have an empty AZEL page, no DL or radar contacts. I've tried cycling AA/AG, I've trying cycling power off/on on the DL, tried changing weapons, nothing seems to jump start it's functionality. It only resolves if I re-slot.

    Does anyone know what causes this bug? Maybe some cold start switch activation order that should be avoided? I can't figure it out.

    Edit: It's happened to me in hot start too, so disregard what I asked about cold start switch activation.

  7. F-15E WSO recruitment is closed at this time.

    As of the date of this post, we are only recruiting for AH-64, other BluFor helos, and LotATC controllers. We are also still interested in standing up a Harrier squadron, and are on the lookout for an experienced Harrier driver to take lead on it, or to merge/collaborate with an established Harrier squadron. And we are still collecting RedFor freelancers to participate in our PVP events.

  8. 4 hours ago, Hulkbust44 said:

    Yeah, the other missing component is that TDC depress on a trackfile should make it the L+S, and it would be slaved via that logic.

    Sent from my moto g stylus 5G (2022) using Tapatalk
     

    I think that is working on my end. If I box L+S and TDC depress through the AZ/EL/FLIR page on something within radar range, the TGP slews and slaves to the L+S contact. My only problems are when something is out of range or if my radar is snoozed, I can't put the TGP in any area of the sky where a L16 contact exists, which is pretty dumb. Has this feature ever worked properly, or it's been this way since AZ/EL was released? I've been a Tomcat guy for the last few years, and just starting to deep-dive into the Hornet.

  9. Hey guys,

    I've been playing around with the AZ/EL's FLIR sub page, and I noticed a behavior that I suspect is not accurately modelled. I can use the TDC to move the FLIR octagon to any empty spot on the AZ/EL page, but I am unable to move the FLIR onto any Link-16 contacts. I'm not a Hornet aficionado, but this is illogical and I don't see how this could be accurate to real life, since it defeats the entire purpose of the AZ/EL FLIR sub page. What good is this sub page if we are only able to slew the FLIR pod to empty areas of the sky, but not onto anything useful?

    Video demonstration:

     

  10. Enjoy this twitch VOD of a recent A2G/CAS weekly practice session:
    https://www.twitch.tv/videos/1954595580?filter=highlights&sort=time

     

    In other news our F-16 recruitment is closed at this time, likely to re-open in the winter. 

    • We are still recruiting for F-15E driver and WSO, A-10C II, AH-64D, other BluFor helos, LotATC, and RedFor pilots.
    • We are also still looking for an experienced AV-8B pilot to stand up a Harrier squadron in the 51st VFW, OR an already established Harrier squadron operating in the North American timezone evening hours who are interested in joining our virtual wing.

     

  11. On 10/15/2023 at 10:54 AM, maxsin72 said:

    The exact quote is "We would go down to probably like 200 knots.....it took you only maybe like five seconds from those 200 knots to where you would like go super sonic".

    That's a lot of "probably like" and "maybe like". My read on Enzo is that he never actually timed it. It probably just felt like around 5 seconds to him. I believe he was just trying to make the point that the Typhoon could accelerate really fast and pulled a number out of a hat that somewhat matched his memory/perception.

  12. 11 hours ago, Fresh said:

    I've made some pictures for you.

    Basically lineup the three horizontal lights. The middle (wingtip) light tells you if you are acute (ahead) or sucked (behind). Put the wingtip light in between the nose and tail light. If the wingtip light is high, your position is low and vice-versa. The vertical light on the vertical stabilator helps to give you a sense of distance and orientation.

    See the file names for an explanation. File names got changed... editing to help...

    OK:
    
    \
      -   =   -
     
    Sucked:
    
    \
      -     = -
    
    
    Acute:
    \
      - =     -
    
    
    Low:
          
    \     =
      -       -
    
    
    High:
    \
      -       -
          =

    Today I learned... 🤯

    • Like 2
  13. 10 hours ago, FR4GGL3 said:

    Is every single Pilot in an Interview exaggerating?

    I don't think he's exaggerating, I think he's sincerely misremembering...by a lot. Spurts is right though, that kind of acceleration is impossible. You can punch it into an inertia calculator and see for yourself. It's like 2.5 Gs of acceleration. That would require about a 2.5:1 thrust to weight ratio. Even the Raptor is no where close to that.

    • Like 3
  14. 1 hour ago, MAXsenna said:

    Thanks, that's what I thought. But how to you go about when there's no AWACS or datalink? Just scan around like you'd do in a one seater?

    Sent from my MAR-LX1A using Tapatalk
     

    I guess you'd have to go off the BRAA call from the AWACS/GCI. Or just keep your scan as wide as possible (RWS mode) until you spot something.

  15. 7 hours ago, MAXsenna said:

    Hmmm, I believe I've tried it... I should revisit it?

    Sent from my MAR-LX1A using Tapatalk
     

    Yes. For example when you see a lower HAFU Link-4 contact out in front of you, but there's no upper HAFU indicating that the AWG-9 sees it, you can note it's approximate altitude represented by the single digit number connected to the HAFU, and you can approximate it's distance by comparing it to the 20nm dashed lines of the scan limits. Then you can tell Jester exactly where to look by saying something like, "Scan sector angels 10 at 30" for example, and Jester will adjust the antenna elevation to be centered on that spot. The upper half of the HAFU should come right up as long as it's not notching.

    It's much better than trying to guess the radar elevation by using the generic elevation commands like "Scan elevation low", which might scan lower than you want or not low enough.

    • Like 3
×
×
  • Create New...