Jump to content

Rainmaker

Members
  • Posts

    1504
  • Joined

  • Last visited

Posts posted by Rainmaker

  1. 3 hours ago, VirKoV said:

     

     

    I got it!

    The problem was not in DCS and LUA files, it is the loss of focus of the active application in windows. When moving the mouse to the MFD windows, the application lost focus and that is why we could not press some keys in the UI.

     

    All you have to do is install the Microsoft Powertoys application (or similar) that allows you to make an application always on you. In this way, the entire UI is accessible while we are in VR.

    To do this, follow the following steps:

    1- Install power toys https://learn.microsoft.com/es-es/windows/powertoys/install

    2-Activate "always on top" feature

    3-Assign a keyboard combination to activate the chosen window (for example CTRL+SHIFT+Z)

    4-Enter DCS, and when you are in the main menu, press the key combination. A beep will sound, and the DCS window will be in front of the rest.

    5-Enjoy.

     

     

    Appreciate the help, but this one did not address the issue for me with my setup.  For whatever reason, on my setup, it does not allow the mouse to travel down far enough to click in the lower right corner.  It's not that it goes out of focus for me, it's that the render and the mouse cursor limits for whatever reason are different.

  2. IIRC, yes, once it sees the new spot, that now becomes the new target.  If you cease the lase, it continues to that same spot.  Don’t take that as gospel, but that’s how I remember it.  The bomb necessarily always see the new spot though as it has ai seek FOV you need to abide by. 

    • Like 1
  3. Answer is certainly ‘it depends’. Beyond that, simple things like squishing a big area into a small display screen creates easy opportunities for error. Couple that together, very easy to not score hits on small targets. Even more so when you dont really have any proximity effects in DCS.  Asking for direct hits on targets with that method repeatedly is setting a bar a lot higher than it should be.  

  4. 4 hours ago, Nickkerkwijk said:

    Is it me or does it look like the loft is not really added yet? Iirc if you go fast* in a Hornet and pull up the timer for release drops down fast, but it looks like the timer in the F15E doesnt work likt that yet

    Calculated loft cues are not in beta yet.  Everything that folks are doing to loft is just a crude method of using a climbing angle and the traditional release cue.  The ESL will give you a loaded pull cue and will be more 'proper' for lofting.  

    • Like 1
    • Thanks 1
  5. 1 hour ago, MillKris said:

    @Rainmaker there is a temp solution to fix the UFC ghosting bug.

     

    go to : DCS World OpenBeta\Mods\aircraft\F-15E\Cockpit\UFC\Indicator\UFC_Rear_init.lua

    find line : try_find_assigned_viewport("UFC")

    replace by : try_find_assigned_viewport("UFC_rear")



    Credits to this guy on reddit: https://www.reddit.com/r/hoggit/comments/16x8y49/comment/kctay6x/?utm_source=share&utm_medium=web2x&context=3

    I’ll give it a look sometime soon. Thanks for sharing that!

    • Like 1
  6. Knew a few back seaters that had them many many moons ago in the -15 world.  A few of them also would come back with busted nose bridges from them too.  After a while, I saw none of them being used.  Have heard they still do exist in the wild, but dunno how many might actually use them.  Likely not many.

    • Like 1
  7. 8 hours ago, BigBorner said:

    So were not really supposed to use it for that? Or what’s the consequence of that information? 

    It can be used, it’s just not going to be as point and shoot as people want it to be.  Positional/altitude errors are going to be a thing unless people are through on their mission planning, etc.  It has its limits on both its accuracy depending on how its used but also just in the ability to be able to accurately place the cursors exactly where needed.  I feel like people’s issues will stem more from user errors than anything as they try to do things with it for which it was not intended. 

    • Thanks 1
  8. 8 hours ago, doedkoett said:

    I have been playing around with the new JDAMs and I have noticed that bombs given their designation from the radar sometimes miss. Me and a friend tried to bomb four targets with four GBU-31's yesterday, and we designated the targets using the AG-radar. Out of four bombs only three were dropped as my wingman had the bug where the bomb disappears from the smart weapons page. All three bombs missed with quite a wide margin.

    The mission date is set sometime in 1995, so GPS should be active, and thus also EGI which should take care of any INS drift, right? Are we doing anything wrong perhaps, or does the radar lack enough precision for this kind of work, or do the JDAM´s need a bit more polish from Razbam?

    GPS should not be active in a ‘95 mission for one, so the jet is INS only. I believe the date the Zeus set is for ‘98 or ‘99. For 2, radar is inherently problematic if trying to target for JDAM for multiple reasons. 

    • Like 2
×
×
  • Create New...