JIGGAwest

Gun basically hasn't worked correctly for the last two monthly patches. In the last patch the firing would be glitchy, like the burst rate wasn't being considered. and it was fire, interrupt, fire, interrupt.... I can't get George to engage in any mode with the gun (FF or commanded), work in progress, sure I get it. But, it's clearly broken....

Following up with testing for the BOL mode on the harpoon. I have found the following. BOL mode does work. -Yes you can have separate HTTP waypoints per weapon -Harpoons seem to also track ground targets. -When rapid launching the Harpoons some harpoons seem to travel faster than others making and Pop and skim simultaneous attacks not really accurate or successful. SRCH setting by way of UFC sets the distance from firing the weapon to where it will activate the search radar. If HTTP is set, this distance will start minimum at the HTTP point. Example SRCH 1nm, Harpoon will activate after reaching the point. When Using HTTP if SRCH is set to 60nm, calculate distance from firing point to the waypoint then add in the extra distance. This is not functioning as SRCH activation from HTTP waypoint. Notes: it can be difficult to calculate the desired SRCH setting on the fly. If not using HTTP be careful of setting SRCH distance too low. It can track friendly ground targets or ships. DSTR setting is the auto destruct range from firing. Maximum is 105nm BRG is setting the attack bearing from the launch position or setting the final attack bearing from the selected HTTP waypoint

Hello, Making attempts to use the IR Mav I was experiencing some issues with locking at standard FOV. best lock range I could get was 4nm. I am not sure this is a bug, but I remember better contrast locking ability previously. With FOV increased you can get further locking distance. The issue with the FOV button is when you have the IRMAV uncaged IRMAV mode selected, if you hit the FOV button two things are shown in this track. While first targeting with the DMT in TV, The IRMAV camera will first reset to boresight then move to the designated ground point. The second issue they may be present is that when the IRMAV camera is reset to boresight, it is pulled outside of the tracking range of the zoomed mode and the ground target is no longer tracked, resulting in a bore sighted seeker camera displayed. Also at time the FOV button will not zoom on first press, you'll have to press it twice. Track file attached https://drive.google.com/file/d/1MXWmSav_wG1OB9Give7HRSldTbZQ62z0/view?usp=sharing

I having repeated issues with Harpoons in BOL mode. Although, I'm not sure if there is a bug. Maybe someone can clarify the intended behavior for this weapon. when entering a waypoint for the BOL mode using HTTP boxed, is the selected waypoint during boxing saved? I noticed when setting the waypoint for the weapon, if I were to change the aircraft selected waypoint after the boxed selection it would also update the weapon HTTP designation for all harpoons. It also doesn't look like you are able to set different waypoints for different harpoons. SRCH distance: does this determine when the missile will go into terminal mode? I'm noticing that the weapons are very late on searching. If I were to use 20nm SRCH, I'm noticing that the missiles may not be actually searching until 30 miles. The issue seems worse when using MED or HiGH modes, they need lots of distance to reach the skim terminal mode before they start tracking. I'll be doing some testing this week and will make a track with no mods.

has anyone got the TEDAC display to work after the update? using method: modify TEDAC_init.lua .....\Mods\aircraft\AH-64D\Cockpit\Scripts\Displays\TEDAC with the line at the end of the file try_find_assigned_viewport("CENTER_MFCD")

You should start a new thread. Or possibly try to get help in the Helios discord. This thread is covering MFD exports with the DCS monitor.lua.

F-18 using the RB/L mode. The first two missiles of four explodes in repeated tests(attached). Second two missiles hit target. Using RB/L Sea Radar, Flight Low, Terminal Pop and skim, Search Large. ~40nm launch Test1(RB-LHarpoon).trk Test2(RB-LHarpoon).trk

It's been reported. I believe there is a double rendering happening with the exports. Which is the reason you can see the exports still after the aircraft has shut completely down. There hasn't been comment by ED to fix this or that it is being worked on. Due to this issue, it's best to have separate monitor config files for the CPG and the Pilot. To fly the CPG you need to "un" comment out the CPG_MFD. You'll not be able to switch dynamically between front and back with working MFD exports at this point.

Make sure you have unique names for the CPG and the PILOT MFD. You'll need to comment out the CPG MFD names in the monitor config in order to get it to work. for example: PILOT_RIGHT_MFCD = { x = 5225; y = 1080; width = 535; height = 535; } AH64_PILOT_RIGHT = { x = 5225; y = 1080; width = 535; height = 535; } --AH64_CPG_RIGHT = --{ -- x = 5225; -- y = 1080; -- width = 535; -- height = 535; --}

share the file or I can't see what else might be wrong what aircraft are you testing? not all aircraft use LEFT_MFCD and RIGHT MFCD correctly show screen shots of what you have displaed make sure you restart DCS between changes you have 1024 of X position to work with. 5x + 500x = 505x(LEFT_MFCD) @ 515x leaves 10x spacing to (RIGHT_MFCD). total used X is 1015x, this should not be a spacing problem

correct hright = 500; to height = 500;

sorry fix the mistakes as noted above. you already shared it I see.

Share your updated config file Correct RIGHt_MFCD to RIGHT_MFCD UIMainView = Viewports.center to UIMainView = Viewports.Center

Is there a possibility there is another config file with the same line 2 '1 camera demo' in that folder? Try another unique name like 'mysetupv1' correct the ; on line 3

Post a screen shot shot your graphics setting page in DCS Also post a screen shot of your monitor layout in windows You are also missing ; at the end of line 3 Correct RIGHt_MFCD to RIGHT_MFCD

The above techniques didn't work. I have had mods installed for over a year without problem. A4 Hercules High Digit SAMS Military aircraft mod UH60 SU35 mod Someone looked at my log file and suggested to remove mods. There were lots of errors. I'll do more testing and report back.

In step 2 of the guide you calculate your full rendered area. There are many examples for how to do this. You have 1920 wide, since the 1280 is below, 1920 is the size needed. For vertical you are 1080+1024 = 2104 So the resolution you enter inside the DCS graphics option page will be 1920*2104 Step 3 of the guide covers the monitor config file. You have to define center and it's size Your file start with: { Center = { X = 0; Y = 0; width = 1920; Height = 1080; viewDx = 0; viewDy = 0; aspect = 1920/1080; } } at the bottom of your file make sure you ha UIMainView = Viewports.Center

I'm trying to get the units to "100% heat" by late activation. I've tried to trigger this at - mission start, no delay. - mission start, time more 10 and time more 100 - only once, time more 10 and 100 All resulting the same. No heat for units. BTR-80, ZSU-23, BMP-2, T-72B3, BTR-82A, SA-19, SA-15 The only way I have seem to get heat is to have the units contently move. For ZSU-23 I have to have them fire at a point. Any ideas? Or is the late activation work around no longer working?

I am actually seeing this too. But, its not using all my ram. But 32 GB (I have 64GB)will be used then a complete crash back to windows. the weird part is that DCS is only reporting 9GB being used in the Windows task manager. I haven't locked down the issue yet, But I will try to delete FXO and Metashaders folders in /Saved games/DCS I am also deleting mission editor folder in core DCS and running a slow repair. will report back.

mostly with mirrors on in the new south Atlantic map

yeah the black screen is back.

As of today it was mentioned in the patch notes. But, what does it do? Note: the ADM-141A TALD requires further testing and is planned to be available in the next update. Work is also proceeding on the UFC-BU page, updating the flight model and flight control system, IAM Loft cues, and finaling the INS/GPS alignment system. We are focused on completing the Hornet roadmap.

@Comrade Doge Such amazing work! Thank you for producing this! I believe you have already stated that you would try to implement waypoint labels in a future version. But, a specific question for the AH64. 1. Would you be able to implement the input of the different point types ( WP HZ CM TG ) ? - Additionally the Identity(IDENT) and Free naming options for these points? The Free isn't that important as it can be edited after. - Maybe just a checkbox or a button for the type of point that is being created at the time? ( WP HZ CM TG ) ? - Currently one issue with TG points is the threat system in the AH64 uses the majority of the TG points available if there are more than 50 targets in any given mission. 2. The ability to display a list of points already saved with their corresponding labels/point types and coordinates?

Wait, you can change your monitor config file without restarting? How exactly do you do this?

Anyone know why DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Displays\MFD\indicator\LCD (Left) MPD_LCD_*_Left.lua are set declareMFD(true) and the (Right) MPD_LCD_*_Right.lua are declareMFD(false) ?