Jump to content

GeoS72

Members
  • Posts

    300
  • Joined

  • Last visited

Community Answers

  1. GeoS72's post in Crew Indicator Relocation was marked as the answer   
    @Tanuki44,
     
    Thank you for posting and providing the knowledge. I moved the crew status indicator based on your work.
     
    I was looking at the wrong file. For those who wish to move their crew indicator then please use this as a reference. The folder & file to edit is here:
    Folder: ...OpenBeta\Mods\aircraft\Uh-1H\Cockpit\Scripts\AI\ControlPanel
    File: g_panel_page.lua (See attachment)
     
    The lines of code to adjust will be the "local shift_X", "local shift_Y", and "local size_X". These should be on lines 42 - 44.
     
    Adjusting the "local shift_X" value will move the overlay along the X-axis. A negative value will move it left and a positive value will move it right.
    Adjusting the "local shift_Y" value will move the overlay along the Y-axis. A negative value will move it down and a positive value will move it up.
    Adjusting the "local size_X" value will adjust the width of the shaded box. Use a set decimal value instead of the variable value. A positive decimal value will increase the width of the shaded box to the right. A value of 0 will remove the shaded box. A negative decimal value will increase the width of the shaded box to the left.
     
    Note: No other values were adjusted. Your results may vary because of monitor resolution and monitor configuration.
     
    The values that work for my monitor setup are:
    local shift_X          = -3.85    -- -0.65
    local shift_Y          = 0.40    -- -1
    local size_X          = 0.68    -- -shift_X + 0.02
     
    Monitor setup is msi Optix MAG271CQR (27" curved) with 3 Cubesim displays. Monitor resolution for DCS is set at 4960x1440.
     
    P.S. You can save the file as is then rename your original file to *.lua.bak or *.lua.orig. If you want to use this file then remove the ".CURRENT" file extension after you make a backup of the original.
    g_panel_page.lua.CURRENT
  2. GeoS72's post in Loading Debriefing Error-Can not open debriefing file was marked as the answer   
    I'd like to reiterate the problem and solution here.
    Problem:
    An error message will appear stating, "Can not open debriefing file" when exiting a multiplayer map in single player or Mission Editor.
    The cause:
    1. Group Name contains an apostrophe.
    2. Slot blocking script references the Group Name containing an apostrophe.
    Solution:
    1. Avoid using an apostrophe in Group Names. i.e. O'Malley, O'Higgins, O'Man, etc.
    2. Use dash (-), underscore (_), or no special character. i.e. OMalley, O-Higgins, O_Man, etc.
    Reference the above posts for examples of a MIZ file that contains a slot blocker with the apostrophe and a MIZ file that does not use slot blocker.
    Thank you, @Flappie for digesting this thread and providing the space to find the root cause of this problem.
  3. GeoS72's post in Mi-8 Crew Status Indicator Position was marked as the answer   
    OK, I finally found a way to move the Crew Status Indicator! The file that needs to be edited is crew_indicator_common.lua.
    This file is located in the main DCS install folder here:
    ...\DCS World OpenBeta\Scripts\Aircrafts\_Common\Cockpit
    Edit Line 58 to look something like this:
    base.init_pos        = {0.50,0.75} -- {-aspect, -1.0 + size + 0.0525}
    Please note, the first pair of x & y coordinates are meant for my screen dimensions. The remarked coordinates are the default values. Make sure to make a backup of the original file in case things get messed up. Additionally, make a backup of the current file to account for new updates to DCS. Yes, these values would need to be changed after each DCS update.
    This overlay also affects the UH-1H Huey or other vehicle with a similar display option.
    Here is a screenshot that shows the location of each overlay. These positions correspond to external MFD displays.

  4. GeoS72's post in Chaff Does Not Dispense was marked as the answer   
    Well, I feel silly! Thank you, @razo+r for the sanity check.
    In all fairness, an explanation of setting up chaff would have been VERY helpful in the update! I hope this unusual configuration will be addressed in later updates.
    Here are the steps to ARM the chaff dispenser:
    Armament (Or select when airborne):
    A/S Switch = ARM
    GND ORIDE = ON
    CMWS Control Panel:
    Off/On/Test = On
    Arm/Safe = ARM
    CMWS/NAV = CMWS
    Bypass/Auto = User preference (Bypass for manual control)
    WPN (Weapon) Page:
    ASE submenu:
    Chaff Safe/Arm (OSB T1) = Arm
    Chaff Mode (OSB L1) = Program or Manual (user preference)
×
×
  • Create New...