JIGGAwest

I'd like to add that I was able to workaround the issue by arming the weapons in the pilot seat before George did "arm" procedure. the issue doesn't seem to arise again.

@Floyd1212 you can't run reshade on your masked main screen with different settings for the unmasked areas, can you? I guess I need to decide if I want the benefit of the sharpening and contrast over more readable MPD's on export....

Yes, I can confirm GEORGE is setting the weapons to safe after a GEORGE AI MENU target selection is destroyed. George reports target destroyed, laser off, and the aircraft goes to safe. I was wondering why sometimes the weapons would be SAFE after I make a run on a target and try to PILOT WAS GUN, and it wouldn't fire.

You are seeing George SAFE the weapon system on GEORGE AI MENU short press DOWN? Do you notice GEORGE is also setting SAFE with GEORGE AI MENU long press DOWN? He shouldn't be doing that. That short press command should be only STOP LASING and TADS FORWARD, ACQ FXD(page 344 manual). I'm not clear on your methods to stop GEORGE from setting SAFE the weapons. Can you go over that again?

EDmissionNOMODS.trk

Track posted - Highlight of error: - Select target with George AI, George is lasing - Missile spools up, small dotted box, then missile ready, large box appears, then fire the missile - target destroyed, George stops lasing - George AI menu long down, select new target, George lases target, MSL NOT RDY on TADS display, Missile is spooling up, small box displayed, Missile then spools, Large box displays, Fire - target destroyed https://drive.google.com/file/d/1hH1on7QzXxHAUkAqmJKEmzGreX0IV_wc/view?usp=sharing

You may be right here. I'll watch my own track and see if the altitude being above the functional range, is the issue. I have noticed the radar altimeter bug had been reported already as not visually indicating on the FLT page even though it's a hot start aircraft.

I have like 30 hours a week in DCS... always in multiplayer and never vanilla DCS. I wish you would still have a way to look at these reported issues regardless of mods. It takes much effort to capture and describe these bugs.

Hello, I've come across this issue in several circumstances. Hot start aircraft, George is commanded to select target, George can have Hellfire WAS or Gun WAS. George menu is UP(displayed) Pilot(player) WAS for GUN, on the MPD the WPN page is selected, MAN RANGE button is pressed, A is typed on KDU, ENTER pressed. In pilot HMD manual range is still indicated. In the track file attached, I run through the AUTO RANGE several times, Then George is commanded to fire on infantry, several targets are selected and destroyed. After this round of target kills, AUTO RANGE is accepted. https://drive.google.com/file/d/1LAXEvZhtlrqjBHviO3Ddkv0wHA1aBAMU/view?usp=sharing

I believe i've found either a bug or a process issue with George AI and target selection affecting the WAS. Specifically with hellfire selected with the George AI MENU. We would go through the process of finding target, wait for spool up of hellfire missile, maneuver to fit constraints for firing, then fire. New target selection, George de-WASed the weapon, then WASed again, wait for missile to spool up, maneuver for firing constraints, then fire. I believe you should be able to rapidly fire multiple missiles after targets are destroyed and new targets are selected. When a player CPG is in the seat there isn't a process for WASing and de-WASing. You can rapidly fire multiple missiles without waiting for the hellfires to spool up in between shots. Additionally there is another issue with the player as PILOT and George as CPG when the player PILOT WASes the gun. If George is commanded to find a target, the player PILOT will lose WAS on the gun. regardless of the George AI menu selection for WAS. So if you already WASed the gun as the PILOT, set your auto range, if you command George to look for targets, you will lose your gun WAS and your auto range selection. TRACK https://drive.google.com/file/d/1hH1on7QzXxHAUkAqmJKEmzGreX0IV_wc/view?usp=sharing

My monitor config had to be changed with the new update. Otherwise all I should have had to change was the the pilot/cpg init LUAs. Not sure why I have to comment out the RIGHT_MFD and the LEFT_MFD variables that I use for other aircraft.

I believe I locked the issue down to ARMing the aircraft while the ground crew is loading weapons. attached photo shows armed aircraft and SAFE hellfires track https://drive.google.com/file/d/1yC258txP6iNJiHl4mqXInfP5YDSDz5l6/view?usp=sharing

how many different resolutions did you try? 3840x2160 main viewport, mine doesn't appear on screen either. or on screen for my second display. Binding is correct and is working. Using the updated method posted by Asto i can get the menu to show, but not in the correct position.

The update injected another issue with the PILOT DISPLAYS and CPG DISPLAYS. I now have to comment out RIGHT_MFCD and LEFT_MFCD in the monitorconfig.lua (now i can't just hop into another aircraft with MFD exports or I have to rename every aircraft to a new variable) and rename try_find_assigned_viewport line within MFD_cpg_left_init.lua MFD_cpg_right_init.lua MFD_plt_left_init.lua MFD_plt_right_init.lua to another unique variable. anyone else with the same issue?

I've noticed the issue where the airframe is armed -A/S set to ARM (this track has ground override armed as well) and the WEP page shows hellfires are still set to safe. When this is the case, you will not get a George CPG AI constraint box. This may also effect Multiplayer crews. Pressing the A/S once, will flash the ARM status and not SAFE the airframe, but GEORGE AI has an override on the ARM state and will remain armed. Pressing the A/S several times rappidly will finally unsafe the hellfires. track 20MB below https://drive.google.com/file/d/1iY6Ub1AqnbBQFytzZl5lrib-qS5m-xqK/view?usp=sharing

Only issue here is the target selection menu is appearing off screen, somewhere. I suspect we have to adjust this as well.

MPDexportISSUES.trk

not currently allowed or implemented.

There are other threads about MPD export, and it has been moved, not considered a bug. While this is possible, there is clearly framework for this to work. I'll identify a few issues I'm seeing. When customizing the Monitor Config LUA for exporting MPD's to a second display: - There is an issue with variables in the Monitor Config LUA for RIGHT_MFCD and LEFT_MFCD where the CPG MPD's exports override the PILOTs MPD's when sitting in the PILOT seat. - CENTER_MFCD variable doesn't allow for TEDAC export. There is a workaround for allowing The PILOT MPD exports not to be overridden. You have to name all the AH64 export variables to unique names, then you have to comment out or not include the CPG export variables in your Monitor Config LUA, so that only the PILOT exports will appear while in the pilot seat. Because of this, you have to have separate monitor configs for the CPG seat and PILOT seat if you want to have exports for both seats. there is either a bug or the work isn't complete for dynamic MPD export updating by the specific seat. Second screen Export BUGS or conflicts with LUA modifications: - When in the PILOT seat, when only having the PILOT MPDs exported, there seems to be a double render on the IN-COCKPIT LEFT and RIGHT MPD or the Brightness knob rates effect the exports at a multiple X%. the Exports also appear much more dim than the IN-COCKPIT. - When exporting the TEDAC, while sitting in the CPG seat, the IN-COCKPIT TEDAC, has a double rendering of a different size. Having a shadow effect. TEDAC d

there is a way to trim the apache. Wags posted a video, take a look.

I have also hit the ARMAMENT A/S safe/arm button in the pilot seat, sometimes it resets his selection

you are not getting the double TEDAC inside the cpg cockpit?

EDIT: as revealed by jonsky7, this solution is not complete and will affect the original George cpg and the george pilot interface differently. needs further work or just follow jonsky7's solution. Alright, I came up with solution, so that you can just adjust your position in your monitor config lua. (\Eagle Dynamics\DCS World\Config\MonitorSetup) locate the file Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\AI\PrestonAI_page_common.lua Line 25: local v = find_viewport("GU_MAIN_VIEWPORT", "CENTER") replace with: local v = find_viewport("AH64_GEORGE_MENU") or find_viewport("GU_MAIN_VIEWPORT", "CENTER") Add the AH64_GEORGE_MENU to your monitor config lua, example below. play around with the x an y for your position on screen, and width and height to work with your monitor. It's not a direct translation, but a little trial and error you can move it where you want. AH64_GEORGE_MENU = { x = 400; y = 800; width = 1920; height = 1080; }

Are you saying your exports work correctly for front seat and back seat? Can you share you monitor config Lua or show us the code that made it work?

I suspect the file with the code in BOLD here may be what we need to modify the the AI position. Two sections, one for VR one for NON-VR There are some commented notes in the code here. I'll experiment with this later. But, maybe someone else want to try in the meantime. \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\AI\PrestonAI_page_common.lua --for VR only! local compass_pos = {0, -0.40} local weap_control_pos = {0, 0.32} --seems okay, may be a subject to change if is_vr then SetCustomScale(1.0) else SetScale(FOV) local total_aspect = LockOn_Options.screen.aspect local total_w = LockOn_Options.screen.width local total_h = LockOn_Options.screen.height local ULX,ULY,SZX,SZY,GUI_scale = get_UIMainView() --not for VR! compass_pos = {-0.82 * total_aspect, -0.7} --relative to screen center, 1 equals screen height afaik weap_control_pos = {0.8 * total_aspect, -0.75} --viewports stuff PrestonAI_page_common.lua