Jump to content

Callsign JoNay

Members
  • Posts

    733
  • Joined

  • Last visited

Posts posted by Callsign JoNay

  1. 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.

  2. 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
  3. 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
  4. 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.

  5. 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
  6. 8 hours ago, MAXsenna said:

    I've been looking myself, but no joy so far, and I'm using VAICOM. 😉
    I have luck sometimes, but I should probably look into how that RIO thing works to know what I want and when to have Jester do it. I have him scan high/low, center/left/right. But I can never find anything ever, unless the bandit is right it front of us and Jester sees him first.

    Are you using the "scan sector" command in VAICOM? That's probably my favorite feature.

  7. This mission seems broken for me as well. I'm able to destroy the APC and the outpost. Venom does a BDA, reports targets destroyed, and says they are on the move. Then radio silence and nothing after that. I even CRTZ+Zd the clock into FFW and established an orbit until I ran out of gas.

  8. Oh wait a second, I just discovered something. The work around does work if you're playing the game live, but it does not work for me if I'm viewing a track file replay. Why would they be different? 🤔

    Can you guys verify if the workaround allows you to bring the camera inside a model when you're watching a track file?

  9. 8 hours ago, The_Tau said:

    Remember you have to repeat procedure after each update

    Yeah, of course, but I haven't updated. I just tried the workaround for the first time before I posted the message 17 hours ago.

    It's working for you? You can maneuver the R.Ctrl F2 camera into the model of a jet without being stopped by the surface of the model?

  10. 1 hour ago, fagulha said:

    No issues here. The only change i´m aware of is the need to open the lua files with notepad++ with Run as administrator. Worth mention that is the View.Lua on Config Folder in your core installation folder and not in savedgames/DCS folder.

    I used notepad++ and edited the lua in my core install config folder. Hmm, I wonder why it's not working. 🤔

  11. On 11/20/2022 at 5:42 AM, fagulha said:

    Another user passed me the workaround/fix for now for this, so if someone uses this camera for first person view like i do:

    "The "camera blocking" thingy has been removed for this camera now, it should pop up in a future patch.
    In t
    he meantime, head into your "View.lua" file (under "....Config\View") , open it with notepad or something ----> find the line "CameraToUnitModelCollision = true" <--------- and change this to "false" ---> save file. "

    I tried this workaround today, but it's not working for me. My Object Free Camera is still unable to be moved inside the object I'm set on. Has something changed? Is there a new workaround?

  12. 6 hours ago, baltic_dragon said:

    Yes, this is intentional. This mission uses Dynamic Weather to be true to the book and have clear sky over the carrier, but clouds over the coast. Unfortunately, dynamic weather uses old clouds. IIRC this is the only mission having these. 

    Ahh, makes sense. Thanks for the reply.

  13. 24 minutes ago, JupiterJoe said:

    Yes, I believe it shows A2A weapon selected too.  I think that's just something left over from an early build.  The Lantirn displays weapon selected in regard to guided bombs.  Not a huge deal though.  I'd much rather time was spent getting the refuelling probe light working in a useable fashion, or implementing engine fire extinguishers properly.   

     

    It's realistic to show the A2A weapon, not the A2G. If you hover over the special option for the feature I'm talking about a pop up comes up explaining that it's a QOL consession they made for the user because the text in the RIO weapon wheel is small and hard to read.

    • Like 1
    • Thanks 1
  14. 5 hours ago, JupiterJoe said:

    Could you please name a few of those?

    Do you mean things like switches being too loud?  It makes up for a lack of haptic feedback, so makes logical sense to have that feature.  I have no problem with that.

     

    An editorial decision has to be made at some point.  You can't please all the people, all the time.

     

    Off the top of my head there is an option to display the selected A2G weapon in the TID repeater.

    • Like 1
  15. 6 hours ago, escaner said:

    The shift + left button drag for the Bingo setting does not seem to be any faster for me.

    Maybe it's shift and mouse scroll wheel. I seem to remember it making a bit of an improvement last time I tested it. It's still very slow, unfortunately. I don't know why HB insists on making us suffer with it. It should be an easy enough QOL improvement. They make QOL concessions in other aspects of the model, but for some reason they take a hard line on the Bingo knob, because apparently it was slow in real life too. 🙄 

    • Like 1
×
×
  • Create New...