Jump to content

Dav IRL

Members
  • Posts

    749
  • Joined

  • Last visited

Posts posted by Dav IRL

  1. Moveable and resizable MFD exports! (Option to enable/disable)

    Option to set min/max cockpit FOV in options!

    Mirror resolution increase!

    Helmet view. 

    Time of day/weather preview in the editor, not just the preview weather screenshot or sun and moon, although it is helpful. 

    More weather effects in general.

    Busy Airport group templates in the editor.

    Way more ground troop variations with the ability to have them evacuate vehicles and buildings under attack and mount and dismount vehicle units, parachuting, and gunning from building tops. 

    Quick re-arm/re-fuel option in options, instead of waiting 170 seconds. 

     

    • Like 2
  2. On 8/2/2022 at 3:18 AM, Nealius said:

    Since George is voiced there should be an obtion to remove the subtitle messages that appear in the top right, do declutter from mission-relevant or server-relevant messages that also appear in the top right.

    Agreed, less is more as they say. 

    • Like 1
  3. 4 hours ago, davidrbarnette said:

    My main gripe with the infantry in particular is that you seem to have to hit them in the head with the 30mm or a rocket to kill them. The module itself is in a pretty decent state, the ground units that you interact with, not so much.

    From footage I have watched when the apache fires its guns on a group of infantry; you can see debris and smoke everywhere and well everything is blown to pieces, we need more of this. 

    • Like 1
  4. On 4/7/2022 at 6:31 AM, Bunny Clark said:

    Exporting displays in the Apache is a bit more difficult than other modules for a few reasons. Since there are a lot of people asking how to do it, here's a quick walk-through and some files to help you out. 

    Enabling Viewports

    First, most Apache screens are not set up for viewport exporting. The ones that are pre set up cause problems. So we need to fix that. Download the attached .zip file and extract it to your DCS\Mods\aircraft\ folder. This will overwrite all the necessary config files to enable display exporting. (These will get replaced every time DCS is updated, either use a mod manager like OvGME or manually replace them). Once this is done, you'll have the following viewports available to you:

    AH64_PLT_LEFT_MFCD

    AH64_PLT_RIGHT_MFCD

    AH64_PLT_EUFD

    AH64_CPG_LEFT_MFCD

    AH64_CPG_RIGHT_MFCD

    AH64_CPG_EUFD

    AH64_KU

    AH64_TEDAC

    Monitor Config

    These viewports need to be defined in your monitor config file. You'll find the stock ones in \DCS\Config\MonitorSetup\ and user created ones in \Saved Games\DCS\Config\MonitorSetup\. If you haven't created one yet, make a copy of one of the stock ones, place it in your user folder, and edit it. 

    Each entry in the monitor config file defines a view port. The format for these are:

    VIEWPORT_NAME = --name of the viewport you're defining
    {
         x = ###; -- distance from the left edge of the viewport to the left edge of defined space
         y = ###; -- disance from the top edge of the viewport to the top of the defined space
         width = ###; -- width of the viewport
         height = ###; -- height of the viewport
    }

    When completed, it should look like this, though your numbers will most likely be different:

    AH64_PLT_LEFT_MFCD =
    {
         x = 75;
         y = 1519;
         width = 500;
         height = 500;
    }

    In addition to the view ports, you need to define your primary game window - the one that DCS itself renders in - under the "Center =" header at the top of the file. 

    Once that is done launch DCS, go to System Settings, and define your game space. Input the resolution of the total space all your monitors take up - you can type this in, you do not need to choose an option from the list. Aspect ratio should auto populate once you've entered your resolution. Then under "Monitors" select your monitor conflict file. 

    Screenshot 2022-04-07 001118.jpg

    For a more in-depth explanation of monitor config setup, see here: https://wiki.hoggitworld.com/view/Exporting_MFCD_Displays

    Apache Problems

    Now for two problems that frequently cause people to get hung up with the Apache:

    If two viewports are defined to the same area, one will overwrite the other. This is true for most modules in DCS, but in the Apache all screens from both seats (except the TEDAC) are being exported all the time. This means if you define the Pilot Left MFD and CPG Left MFD in the same place, DCS will draw the CPG MFD on top and you'll never see the Pilot MFD, regardless of what seat you're in.

    The Apache display exports are also currently bugged and the Pilot's and CPG's left and right MFDs will always export to the LEFT_MFCD and RIGHT_MFCD viewports. If they've been assigned a new viewport in their init.lua files, they will export to both the custom viewport and the default one. This means if you have the LEFT_MFCD or RIGHT_MFCD viewports defined in your monitor config file, the Apache MFDs will show up there, no matter what. The only solution to this is to delete or comment out the LEFT_MFCD and RIGHT_MFCD viewports from your monitor config file. This will break every other module that is using those viewports.

    Hopefully ED fixes these two issues, though neither have been acknowledged yet.

    AH-64D Display Exports.zip 10.2 kB · 45 downloads

    Works perfect, have all displays on 2 screens and working! Fair play and thanks for sharing.

  5. On 4/9/2022 at 1:02 PM, Hobel said:

    How does the Harrier actually do it?  You can show and hide the mfds with a key combination?  Couldn't you do that for apache or is that hard-coded?

    I think you might be on to something, a toggle for pilot and co pilot mfd's makes sense.

  6. 23 hours ago, admiki said:

    TSD->RTE->DIR->select point you want.

    Not great, but not crazy hard

    The issue I have with this method is the waypoint location marker doesn't switch to the selected waypoint, the ETA information is incorrect too. So for example, if I select TSD>RTE>DIR and then select waypoint 2, I can see my waypoint update/(distance to) in my hud, but the waypoint indicator itself is still locked on waypoint 1. When I fly there my ETA info is also inccorrect, it is like it is calculating my distanance from WP1. 

×
×
  • Create New...