Jump to content

dlder

Members
 View Profile  See their activity

  • Posts

    251

  • Joined

  • Last visited

 Content Type 

Posts posted by dlder

    JSTARS would be a valuable addition

    in DCS Core Wish List

    Posted

    Quote

    JSTARS, in my mind, was a huge asset. You can't begin to place a value on how much they helped us." - Capt. Jim "Boomer" Henry

    We already have attack planes and multi-role jets, but especially with the coming F-15E, this quote from the book "Flying the F-15E in the Gulf War", the "AWACS for the ground" would be immensely valuable!

    Especially with datalink and hopefully some more integrated/better communications, because the controller has to "paint a picture" for the pilot to look for the target (like outlined in the book), this would bring so much immersion to the game!

    So, the question shouldn't be IF, but WHEN.

    Thanks for the consideration,
    dlder

    • Like 2

    Is there any way to tell the max range for MAVs?

    in A-10A for DCS World

    Posted

    On 3/30/2023 at 4:26 PM, Ironhand said:

    And that’s how it used to be. If it’s changed, then that’s a problem and you should report it as a bug as well as the range launch issues for each missile. You’ll need to provide a short track file for each issue.

    EDIT: I haven’t looked into it myself but I suspect that the launch range is most probably limited by the seeker rather than the rocket motor. Something to consider, if you decide to report the bug.

    Thanks for your help and opinion. Gonna consider posting a bug report; don't know what a track file or a logfile would be good for though. Anyone can just try the Jet and see for themselfs...

    Is there any way to tell the max range for MAVs?

    in A-10A for DCS World

    Posted

    22 hours ago, Ironhand said:

    the pointing cross on the TVM would start flashing when you were within firing parameters.

    Unfortunately, no.

    It starts flashing as soon as you lock a target; even if it's beyond range. From the manual:

    Quote

    When the pointing cross flashes, it indicates a valid lock.

    A valid lock is any hard lock on a target (not the ground itself). I too read it at first like you mentioned:" within firing parameters", but that alas is wrong.

    So I guess at least with the "A", there is only eye-balling it.

    Is there any way to tell the max range for MAVs?

    in A-10A for DCS World

    Posted

    Is there any indication anywhere (which I'm not seeing), that tells you that the target is in range and can be shot? Stationary and more importantly moving targets?

    On another note, the manual is wrong with this statement:

    Quote

    The AGM-65K can lock on to a target from three nautical miles away and the AGM-65D can lock a target from eight nautical miles

    Both can lock onto truck sized targets from 20.700m (11.2nm) slant range.

    Or this one:

    Quote

    Both the AGM-65K and AGM-65D have a 3x magnification level; however, the AGM-65D also has a 6x magnification level.

    But both have 6x magnification!?

    Possible Bug - Airbrake toggle button require two presses for "off"

    in A-10A for DCS World

    Posted

    Ok, now that we've concluded that this is normal behavior for the airbrake-toggle in the A-10, there are some other things that might be wrong / not working:

    1.  The "TDC Slew Vertical (mouse)" doesn't work for the CCRP "depressible piper" (it works with MAVs though!). The piper can only be moved horizontally with the mouse, not vertically. Only with the keys, it can be moved vertically! Pretty weird...
    2. I've found a post explaining what EAC does stand for and what it does, but when pressing the default keybinds (LAlt 4 / 5), the EAC-switch (behind the throttle) doesn't move and I'm too inexperienced in the A-10 to know if it's just the switch not moving or if that function won't de-/activate

     

    Win11 / DCS - Auto-HDR also on exported displays (like USB LCD)

    in Multi-Display Bugs

    Posted · Edited by dlder

    DCS looks awesome with Win11's capability to automatically apply HDR to any Dx11 game. But the thing is: can the monitor setup be changed, so that Windows only "sees" the main - HDR capable - screen?

    So that HDR only gets applied to that and not to the SDR-USB-LCDs I have for radar/MPD/TV/... ?

    I've already checked and Windows does recognize those displays as SDR only.

    image.png

    But because the game outputs the main display along side the exported ones, auto-hdr gets applied to the entire thing (main + MPDs), rather then only the main display.

    Hope you'll get what I'm trying to say 😉

    I've tried to make pictures with my phones camera; it's not quite what it looks like in reality (it's even more white, but the camera doesn't pick that up), but one can see the white crosshair in the SDR shot, but not in the Auto-HDR one:

    SDR:

    picture-SDR.jpg

    HDR:

    picture-HDR.jpg

    PS: the problem lies in that the USB displays get a way too bright image and especially with Flir / TV images it's all pretty much white-on-white...

    F-15C cannot use new missiles?

    in DCS Modding

    Posted

    The two AMRAAM defined in "DCSWorld\CoreMods\aircraft\AircraftWeaponPack\aim120_family.lua" can be used and work. Of course.

    But if I use the code for those missiles in my own mod, I have to at least change the following code: 

    wsTypeOfWeapon     = {wsType_Weapon,wsType_Missile,wsType_AA_Missile,AIM_120C},

    to 

    wsTypeOfWeapon     = {wsType_Weapon,wsType_Missile,wsType_AA_Missile,WSTYPE_PLACEHOLDER},

    or else, DCS hangs when starting with the following error message:

    Quote

    "Error running db_scan: ?:0: attempt to concatenate a nil value"

     

    Now, with this change, the mod works; I cannot equip the new missile directly, as I have no access to the F-15C.lua, where the pylons and respective payload-IDs are defined, but I can equip them via UnitPayloads just fine.

    So I have the 120C on my own racks mounted on the pylons and can use them.

     

    BUT, as I had to figure out the hard way by testing it... the missiles don't track. Or at least not really. One might get lucky if the enemy doesn't move from it's path, or if you shoot the missile inside about 10nmi. But mostly the missiles defined by me don't kill any enemy, but the default still does (same ranges, same enemy, .... etc. -> I can provide Tacview if needed)

    => my conclusion is this: the plane (or radar) needs to "know the missile" to work correctly! (it's the same as mounting the Aim-54 onto the F-15C which works, but only STT and also has not a perfect tracking)

    -> that's why the Modern Missiles mod works, as it overwrites the (performance) data of existing missiles (120D -> 120B), so the missile ID is the same!

     

    Now to my questions:

    1. Is my assumption correct? I'm very sure, as I've tested it extensively, but it just sounds so... weird 😉
       
    2. How can I access the "F-15C" aircraft files, to (a) add the new IDs to the pylons and (b) to add the new missiles to the radar (I guess?)?
       
    3. How can I use the default missiles in my mod?
      • if I change the code in the "aim120_family.lua" from  
        local AIM_120C = 
        to  
        AIM_120C =
      • one might think I can just access that variable like so: 
        local F15_aim120c5_AA = AIM_120C
declare_weapon(F15_aim120c5_AA)

        But that doesn't work. 

      • DCS starts but logs the following error and my modded missile isn't available:
        Quote

        "?:0: attempt to index a number value"

         

    What I did instead:

    I used the new rack shape and defined the new shape+missile ID in the default "aim120_family.lua".
    So, I basically used the same code as I did in the "mod", but now inside the default file using the default missile definition and it works!

    Credits:

    I've used the "Modern Missile Mod", as well as the AMBER rack from the awesome "F-15EX Mod" (which unfortunately is using older code, thus the F-15E seems to be underpowered and it's radar is definitely worse then the default F-15C. The used missile code too is old and the included 120C-7 has a smaller range the the DCS default 120C-5)

    Because of that, I don't think I'm allowed to distribute this...

    nullimage.png

     

    _Test5 - 120c 2x def, 2x amber - 4x hit (rack definition in aim120_family.lua).acmi _Test5 - 120d 2x def, 2x amber - 4x hit (rack definition in aim120_family.lua).acmi _Test2 - 2x 120C default + 2x 120C amber (hit, hit, miss, miss).acmi _Test2 - 2x 120D default + 2x 120D amber (hit, hit, miss, miss).acmi _Test3 - 1x def, 2x amber, 1x def (hit, miss, hit, hit).acmi _Test4 - 2x amber, 2x default (miss, miss, hit, hit).acmi

    Mirrors blurred by motion blur

    in General Bugs

    Posted · Edited by dlder

    Ever since the update, the mirrors in the Su25 and Su27 (these are the ones I tried as of yet), are partly fuzzy with a "border" running through the mirror where the other side looks normal / sharp.

    I've tried checking the Steam files (I'm on stable), clearing any (shader) caches (in the dcs profile folder).

    Nothing helps.

    Here are some screenshots (with red lines showing the border):

     

    image.jpeg

    su25_1b.png

    su25_1c.png

    su25_2a.png

    su25_2b.png

    su27_a.png

    su27_b.png

    new settings in "appSettings.lua"

    in Multi-Display Support

    Posted

    Yeah, I too was thinking that maybe DCS might allow for better MFD export configuration; but I'm not sure if/how one could utilize these.

    When I enable one of my MFDs the "windowPlacement" stays the same as before, and the new "monitors" variable has 2 entries (for 2 monitors) 

    windowPlacement = {
    ["y"] = 0,
    ["x"] = 0,
    ["w"] = 4240,
    ["h"] = 1440,
}

-- added with DCS 2.8 and auto-generated:
monitors = {
    [1] = {
        ["rcMonitor"] = {
            ["top"] = 0,
            ["right"] = 3440,
            ["left"] = 0,
            ["bottom"] = 1440,
        },
        ["dwFlags"] = 1,
        ["rcWork"] = {
            ["top"] = 0,
            ["right"] = 3440,
            ["left"] = 0,
            ["bottom"] = 1400,
        },
    },
    [2] = {
        ["rcMonitor"] = {
            ["top"] = 0,
            ["right"] = 4240,
            ["left"] = 3440,
            ["bottom"] = 600,
        },
        ["dwFlags"] = 0,
        ["rcWork"] = {
            ["top"] = 0,
            ["right"] = 4240,
            ["left"] = 3440,
            ["bottom"] = 600,
        },
    },
}

    The values from the 2nd are from the 800x600 MFD display. But this is currently configured inside the "monitorsetup" LUAs.

    I haven't figured out how to use these new variables for or instead of the multimonitor LUA...

    new settings in "appSettings.lua"

    in Multi-Display Support

    Posted

    Can anyone tell me what these new settings do?

    Before 2.8.1 

    windowPlacement = {
    ["y"] = 0,
    ["x"] = 0,
    ["w"] = 3440,
    ["h"] = 1440,
}

    After the update: 

    windowPlacement = {
    ["y"] = 0,
    ["x"] = 0,
    ["w"] = 3440,
    ["h"] = 1440,
}

monitors = {
    [1] = {
        ["rcMonitor"] = {
            ["top"] = 0,
            ["right"] = 3440,
            ["left"] = 0,
            ["bottom"] = 1440,
        },
        ["dwFlags"] = 1,
        ["rcWork"] = {
            ["top"] = 0,
            ["right"] = 3440,
            ["left"] = 0,
            ["bottom"] = 1400,
        },
    },
}

    I ask, because I have different files for how many MFDs I'm running. So, if this code is needed or better yet: if I can use it for something specific, I'd like to know 🙂

    Thanks!

    Barthek's CAUCASUS REDONE 2022

    in Texture/Map Mods for DCS World

    Posted · Edited by dlder

    On 11/17/2022 at 11:33 PM, VR Flight Guy in PJ Pants said:

    Taz1004 Better Trees

    I use his trees now too; less flickering and way less pop-in. Just look at those super-low-poly trees from default (top left):

    DefTrees_summer-def.jpg

    And here's better trees v6 (medium):

    BetterMedTrees_summer-def.jpg

    True, the colors now are different, but quite ok (not enough variation imho, but maybe that's coming in v7 or so^^)

     

    • Like 3
×
×
  • Create New...