Jump to content

Ramsay

Members
  • Posts

    3744
  • Joined

  • Last visited

Posts posted by Ramsay

  1. Thx a bunch I'll have a look into this. Biggest issues right now is....see attached no A10C kneeboard files in the path as you showed :-)

    The "Saved Games" kneeboard folders aren't there by default, you need to create them i.e.

     

    • C:\Users\Carsten\Saved Games\DCS\Kneeboard\A-10C

     

    Note: If using DCS Open Beta, your save path might be:

     

    • C:\Users\Carsten\Saved Games\DCS.openbeta\Kneeboard\A-10C

     

    In the game directory..2nd attached... I have created a kneeboard folder - but it doesn't show in-game.

    DCS doesn't look there.

     

    The actual in-game kneeboard (L-ctrl+K) location is what I'm looking for - I would just add png's to that per terrain then?!

    AFAIK, yes - I've only used the "Saved Games\DCS" and Viggen specific paths in 2.5.x

     

    I'd prefer to make airframe specifik pages... e.g. excerpts from Chuck's A10C guide

    tyvm - again

     

    As you are having trouble, it may be better to manage your kneeboard pages using AlaskanGrizzly's Kneeboard Builder application.

  2. Can any1 help how to add png pages to the a10c kneeboard. I managed to do it flawlessly on the C101 - just added the png's in the kneeboard folder in the aircraft cockpit folder.

    That folder I can't find for the A10c.

    It's important to get the 'capitalisation' of the folder names correct i.e. FA-18C_hornet, Mi-8MT, etc.

     

    The DCS kneeboard can use .jpg, .png, .bmp, .dds and .tga images, the main restriction is the file extension *must* be lowercase.

     

    The Viggen is different, as it requires .lua file for each image and they need to be placed in module's folder.

     

    This is a example kneeboard folder that should help with some module names

     

    • [user name]\Saved Games\DCS\kneeboard\[module name] i.e.

     

    attachment.php?attachmentid=202756&stc=1&d=1548111135

     

    You can also add kneeboard images to a .miz mission file and make them mission specific i.e.

     

    • AV8B Sandbox, Batumi.miz\KNEEBOARD\AV8BNA\IMAGES\kneeboard_1.jpg

     

    However in game I do have a kneeboard..? Where's it located?

     

    • DCS World\Mods\terrains\Caucasus\Kneeboard

     

    I want to add some server specific pages... TYVMIA

     

    You'll need to make them part of the .miz so players download them, otherwise they'll only have access to their own pages/versions.

     

    For common images I use the mission brief.

  3. When you noted that the missiles veer left/right depending on station, were the missiles loaded on the single-rail LAU-117s or on the triple-rail LAU-88s?

    I had LAU 88 with 2*AGM-65D on Stations 3 and 9 (4 missiles total).

     

    When tested at Tonopah in NTTR, I of course expected to see the missiles veer left as they do in Peaches track.

     

    However the first AGM-65D came off the left wing and veered right.

     

    Checking the missile's HUD in Tacview, highlights the issue - some of the missiles on the LAU-88 are mounted sideways, I guess the missiles are trying to loft but instead fly sideways :lol:

     

    attachment.php?attachmentid=203181&stc=1&d=1548557946

     

    Note: Some of the missiles on the LAU-88 are "right-side up" and don't veer to the side.

     

    Tested in DCS Open Beta 2.5.4.26552

    804807954_A-10CLAU88AGM-65DTonopahTestTacview2_5_4_26552.JPG.90e7a75881217bffad608718f2be96d6.JPG

  4. TL;DR:

     

    Comparing your .trk and .acmi files to AGM-65F flight profiles, it looks like the new FM (while better) needs further refinement as the missile is under performing.

     

    Detail:

     

    The first track file is from OB 2.5.3.24984, where the missile is launched at 800 feet MSL and 6.5 NM away from the target. The missile climbs to an apex of 3,200 feet MSL by 2.4 NM away from the target and then dives in and kills the vehicle; its flight path is straight towards the target the whole flight. This behavior has been consistent for the AGM-65D for years, perhaps since the inception of DCS: A-10C.

    The loft profile in 2.5.3, while spectacular, looked unrealistic when compared to the AGM-65F profile found in the AV-8B Tactical Manual Vol 2. Not only was the apex too high but, having burnt off all it's speed to climb, the missile was now slow and took too long to reach it's target i.e. I would see +2 min flight times (at range/altitude in 2.5.3.24436), when max should be 1m45s

     

    The second track file is the same execution but on OB 2.5.4.26368. In this case, the missile, launched at 800 feet MSL and 6.5 NM away from the target immediately starts veering left, performs a slight climb to 1,100 feet MSL (apex at 5.7 NM away from target) and then gradually descends, going below 150 feet MSL while still 2.7 NM from the target and inevitably trashing itself in the trees.

    The current AGM-65D performance is less than that found reading the AGM-65F charts in the AV-8B Tactical Manual Vol 2 (interpolating between Mach 0.3 and 0.5 charts for 0.4).

     

    Using the AV-8B AGM-65F charts, range might be 34,000 ft (5.6 NM) @ 1000-500 ft/ M0.4, so a launch from 6.5 NM looks optimistic (unless in a faster aircraft).

     

    Looking at your track and tacview files -

     

    • Apex at 1,100 ft is perhaps 700 ft low

    • Time of flight at 25 sec, was 15 sec short of an expected 40 sec.

    • Distance covered was 3.8 NM (6.5-2.7) = 23,000 ft in 25 sec. The expected travel time was about 24 sec, so the DCS missile is very close but a little slower.

     

    The current FM needs further refinement as the missile is under performing.

     

    Please take the time to look into this change and correct the flight path back to its former profile, so that the Hawg can regain its key mission of pop-up attacks in high-threat environments.

    Reverting the flight model to another incorrect flight model for 'gameplay' reasons is not the correct method, providing real world data (where available) and improving the new flight model to reflect real capability is.

     

    EDIT 2: it looks like the flight profile was changed in OB 2.5.4.25729 on 20 Dec 2018, as the version notes included: "AGM-65. Search and lock ranges was increased based on launch altitude." In giving the missile potentially a little bit longer range at altitude, the change took away the low-level, pop-up ability, which is a poor trade.

    I wasn't using the A-10C at the time but FM changes to the AV-8B's AGM-65G occurred in DCS 2.5.3.24984, reducing it's excessive loft, perhaps 2.5.4 reduced it further.

     

    It also does not explain the left veer tendency introduced.

    The A-10C's missiles

     

    • veer to the left when fired off the right wing

    • veer right when fired off the left.

     

    The magnitude is about 5° before the missile tracks back towards the target (if it was directly ahead). It appears to be the same on the NTTR map, so doesn't look to be MagVar/True North related and decreases with range to target.

     

    Tested A-10C in DCS Open Beta 2.5.4.26552, Caucasus and NTTR maps at 5000-500 ft AGL.

  5. For the mission itself, I may be missing a moose thing. If I have to write lua's then that's a no-go.

    No need to worry, Moose.lua, random AI flights, range scoring, etc. are in the .miz files.

     

    When initially entering the observer slot, on screen messages appear to confirm the scripts are loaded, prior to changing to an C-101CC slot.

     

    IIRC you use the F10 radio menu to call up the range but also get feedback after each pass and a Score Total after safely landing back at Anapa.

  6. Attempting to open missions there is an error message.

    Text reading I need objects mod.

    Before opening mission I downloaded and installed the objects mod?

    Its showing in installed modules, just nowhere else. The mod came with no instructions so I had to guess where it went, showing as installed although that's all. I installed the mod with JMGSe

    I installed

     

    476th Range Objects ("Saved Games\DCS\Mods\tech\476 Range Targets\entry.lua, etc.")

    VPC Airfield Equipment ("Saved Games\DCS\Mods\tech\VPC Airfield Equipment\entry.lua, etc.")

     

    and had a requirement warning which mods were needed when opening the mission with ME but it didn't stop me editing/running the mission using the L-39C.

     

    Running my edited mission from "DCS>Missions>My Missions" doesn't give a requirement warning.

     

    VPC Airfield Equipment .zip has a number of sub folders, perhaps you've installed it to deep? The default VPC folder name is "main" but I've renamed mine to something more meaning full/less generic.

     

    Like you, I use a mod manager (JSGME) to add/remove the mods as I need.

  7. Excellent missions, you might consider making versions for the L-39 ?

     

    As I'm waiting for the C-101 to come to Steam I substituted in the L-39C for the C-101CC in

     

    • C101CC – M23 – Rocket Practice 2-MK151 (by Rudel_chw).miz

     

    and it worked really well.

     

    I'm not sure I'll take the effort to update all the documentation/instruction to match the L-39 but they look ideal missions to refresh competencies in MP/Co-op.

     

    Thank you for taking the time and effort to make and share these professional quality missions.

  8. The TOT HUD claret works backwards to the NATOPS description and is to the right when slow and left when fast.

     

    The arrow head is displayed to the left of the tick mark when the aircraft is travelling too slow and displayed to the right of the tick mark when the traveling too fast. Full displacement of the arrow head left or right of the tick mark indicates a difference of 30 knots between actual and required ground speed.

     

    i.e. when the aircraft is 15 knots fast for TOT, the claret should be half way to the right.

     

    attachment.php?attachmentid=202979&stc=1&d=1548370708

     

    Tested in DCS Open Beta 2.5.4.26552

  9. Using MBot campaign i set up a TOT on waypoint 4 (didnt set gspd), designated it as a target waypoint (waypoint 4 became boxed in). But no matter for accurate i fly, the caret on the hud does not move (i timed myself manually to be within 20-25 sec of waypoint switch)

     

    Can any1 else test TOT function in different missions to see if it works for them?

     

    TOT worked as described when tested in Open Beta 2.5.4.26552 but looks bugged as the HUD claret works backwards to the NATOP's description.

     

    • HSI Data page

    • SEQUFC Flight Plan page

    • UFC Option TOT = set to equal time on target waypoint in Zulu Time (Local - 4 Hr for Caucasus map)

    • UFC Option TGT = waypoint to select for TOT, waypoint in flight plan list is boxed i.e. 0-1-2-3-4-[5]-6-7

     

    The HUD claret works backwards to the NATOPS description and is to the right when slow and left when fast.

     

    The arrow head is displayed to the left of the tick mark when the aircraft is travelling too slow and displayed to the right of the tick mark when the traveling too fast. Full displacement of the arrow head left or right of the tick mark indicates a difference of 30 knots between actual and required ground speed.

     

    i.e. when the aircraft is 15 knots fast for TOT, the claret should be half way to the right.

     

    attachment.php?attachmentid=202979&stc=1&d=1548370708

    1823791379_FA-18CTOTHUDBug2_5_4_26552Screen_190124_221123.jpg.3eedada168e9a7818abf47f1e77e8bba.jpg

  10. With the Hornet, I set the same sort of course line through the TACAN of 250 degrees in this case.

    You haven't set a course of 250°M,you have set a course of 280°M (as shown in the bottom RH corner of your DDI pictures CSEL=280°M ).

     

    As the course line passes through the offset TACAN station (not your aircraft), you can not read the course heading off the outside compass rose (the arrow at the end of the course line shows direction, not course heading), to read the course setting, you need to read the bearing in the bottom RH corner of the HSI i.e. CSEL

    Then, it just constantly drifts away from the set 250 resulting in a huge discrepancy (20 degrees in my attachment) which results in it being a pointless exercise as I cannot use this info to make the correct heading to the runway.

    As you approach the course line, heading to the TACAN gets closer to 280°M as that is the desired course (CSEL) you have entered.

     

    As well as using the course slew switch, you can also enter your desired course directly into the UFC (after holding the course slew for a couple of seconds).

  11. The Mission time or runtime counter in either DDI under TAC/SUPT, doesnt tick over after 59m59s, it just runs from 59m00s to 59m59s and keeps looping that. Id imagine it should just continue counting minutes, so 61m32s etc?

     

    AFAIK there is

     

    • ZTOD - Zulu Time, (00:00:00)

    • LTOD - Local Time of day (00:00:00)

    • TOT - Time on Target (00:00:00)

    • ET - Elapsed Time (increments 00:00 to 59:59 and rolls over to 00:00 to continue counting)

    • CD - Countdown Time (decrements 59:59 to 00:00, defaults to 06:00 with WoW)

     

    Do you mean Elapsed Time ?

     

    I expected ET and CD to be TIMEUFC stopwatch like functions, started and stopped with ENT on the UFC.

  12. It must have been an unusual mid-flight situation , like the original target being destroyed for it to go after an aircraft.

    • The radar signature of a B-52 tail gun was misidentified by a F-4G Wild Weasel as Iraqi AAA.

    • A AGM-88 HARM was launched against the non-existent AAA and the missile tracked the B-52.

    • As the missile expected to hit a static target, it exploded behind the B-52, causing significant damage to the tail section.

    • The B-52 landed safely.

     

    The HARM didn't change target, rather it was locked onto a misidentified radar.

     

    https://bentcorner.com/in-harms-way/

  13. Why is the TDC Slew Selector on the Radar DDI page Yellow now? Is that correct?

    Yes, it's the colour on the real display.

     

    I thought DDIs could only display green and were not RGB capable?

    It depends on the display type.

     

    2.13.4.1 Digital Display Indicators (DDI).

    ...

    On aircraft 163985 AND UP the DDIs are NVG compatible and display three colors (red, yellow, and green) for stroke information. A monochrome version of the digital map can be selected on any of the DDIs.

    ...

  14. The kneeboard folder is created\found in

     

    • [user name]\Saved Games\DCS\kneeboard\[module name] i.e.

     

    attachment.php?attachmentid=202756&stc=1&d=1548111135

     

    IIRC the DCS kneeboard can use .jpg, .png, and .bmp images, the main restriction is the file extension *must* be lowercase.

     

    The Viggen is different, as it requires .lua file for each image and they need to be placed in module's folder.

     

    You can also add kneeboard images to a .miz mission file and make them mission specific i.e.

     

    • AV8B Sandbox, Batumi.miz\KNEEBOARD\AV8BNA\IMAGES\kneeboard_1.jpg

    127524790_DCSKneeboardFolder2_5_4_26368.thumb.JPG.84641b0ed3865a418c2cc49456768bab.JPG

  15. Suggestion

     

    Please include pictures of the 3D NS430 fitted to the L-39C and Mi-8 on the Steam NS430 store page, as the 'All in One' NS430 Steam pack includes the 2D pop-up and both 3D versions.

     

    Detail

     

    Currently the only pictures on the NS430 Steam page are of the 2D pop-up and some prospective buyers are mistaking :

     

    NS430 Navigation System for L-39C and Mi-8MTV2

     

    for the "NS 430 Navigation System" AKA 2D Pop-up sold on the ED store - it doesn't help that there isn't a single picture of 3D version on the store page, if they miss the significance of the "for L-39C and Mi-8MTV2" byline.

  16. What I also noticed: I have bought the Steam Version - But it seems I need to buy another module (only available in the DCS Store <-> Not compatible with the steam version) to get atleast the buildin navigation in the L-39 and Mi-8? :(

    The Steam version is more expensive than the 'standalone' versions but includes the 2D popup and both 3D versions for the Mi-8 and L-39C in one package.

     

    The 3D versions are enabled in DCS>Options>Special>NS430 using check boxes.

     

    The L-39C requires the gun sight to be disabled/removed in the mission editor (to make space for the NS430).

  17. I have bought the Steam version and there is now no option to get the building version for the l39 in steam

    ??? The Steam version is more expensive than the individual 'Standalone' versions but includes the 2D popup and both 3D versions for the Mi-8 and L-39.

     

    The L-39 option you are looking for on Steam is already included ?

  18. The airbrake is extended and retracted by pressing the key "b" once.

    Although I don't own the module - AFAIK you *must* use:

     

    LShift + 'B' for "Air brake - Extend"

    LCtrl + 'B' for "Air brake - Retract"

     

    These are momentary positions and the air brake switch returns to it's centre/neutral position, when the key combination is released.

     

    The 'B' toggle switches between Air brake switch held forward and held back and will drive the pitch trim (a feature of the real aircraft), thus using 'B' to toggle the air brake between fully open and fully closed is only suitable for 'Game' flight mode.

×
×
  • Create New...