GeoS72

Flappie, Yes, I own the Combined Arms module.

Flappie, Yes, that is one large file. It is my squadron's base cap map. On mission start, the track file is about 7.5MB and grows afterwards. I'd sure like to know the root cause of this bug. It is very frustrating. Have any Testers with AMD cards been able to replicate this error?

Here is my input on the disappearing overlays in the mission editor. It happened roughly 1hr into game play. The track file is too large so please follow this google drive link. Jousters MP Server Track File The time stamp when failure occurred was approx 15:50 - 15:55. The track file ends at 15:56. Attached are 2 screenshots that show missing icons and a new DxDiag file. DxDiag 2021-09-02.txt Here is another screenshot that shows a blank rearm-refuel screen after the icons disappeared. This screenshot is at the main menu page. Note the missing icons along the bottom edge of the screen. This too was the result of missing icons from the F10 map.

@Flappie, at what point do you want data from the dxDiag report? Do you want it run while the game is running with masked icons, before running DCS, after closing DCS, or it doesn't matter?

Attached is my DxDiag report. Hope this helps, Flappie! I normally don't see any issues within 15min of game play. It normally happens much later. DxDiag 2021-08-30.txt

@BIGNEWY, See the link to download 2 files. These show my issues with the trains. One train starts at the terminal house south of Port Jebel Ali. The second train starts at Rajaei Port, west of Havadarya. The 1st file had invisible trains. Trains not visible track The second file has visible trains. It was really strange! Trains visible now track - google drive Sorry, I couldn't attach the files as each was over 5MB.

@Pipok, I watched your track file, "Single Player - Issue with the UI.trk" and I didn't see anything unusual. No icons disappeared. I also tried your Stunt Island mission and didn't experience any disappearing icons. My experience with the disappearing icons happens randomly. It could take up to 4hrs for it to occur or as little as 30 minutes. I have an AMD Radeon graphics card.

Flappie, Thanks for the reply. I too recently updated my graphics drivers to 21.8.2 and still experienced the disappearing icons. I will do my best to post a track file when this occurs again. Expect the file within a day or two.

I am plagued by this frequently occurring problem of disappearing icons in the F10 Map, Rearm/Refuel popup window, and Main Welcome Screen while in a Multiplayer server. I'd like to stress that this problem is limited to my game while in Multiplayer. An example of the missing icons is attached. One should clearly see the lack of icons in this map of the Persian Gulf. Life bars are visible but all remaining icons disappeared. This screen shot should be filled with Red and Blue icons. Also note the lack of window frames in the lower left corner when a unit is selected. This effect randomly happens when selecting a unit. Once this occurs, the only remedy is to exit DCS completely then launch it again. This event randomly happens - it may not happen in a 6hr period. I've had it happen at least 4 times in a 2hr span. I previously read a "fix" AMD Radeon RX 5700 XT video cards. This recommendation suggested to disable the In-Game Overlay option in the Radeon preferences menu. I have this feature disabled and I'm still encountering the disappearing icons. My current setup: CPU: AMD Ryzen 5 3600 6-core processor GPU: AMD Radeon RX 5700 XT 8GB RAM: 48GB DDR4 M/B: Asus ROG Strix X570-F Gaming ATX All drivers are up to date. Has this bug been previously reported? Any help would be greatly appreciated. If there is another thread with similar complaints then please help me find it or cross-link to it.

I started playing with trains as a result of watching a recent Grim Reapers video. My experience has been mixed, see below: 1. The Train View (LCTRL + F12) has no effect. The Vehicle View (F7) does not snap to the selected train. The only way to view the train is to look at the F10 Map, select the train icon, then press LSHIFT + F11. Afterwards, I have to use the W-A-S-D to zoom in/out and pan around the map area to find the train. 2. Viewing the train is also hit and miss. One train is visible from the LSHIFT + F11 view and two others are invisible. The icons are on the map but the train is hidden, for some reason. All 3 trains were added at the same time. 3. Late activation and triggered events also do not work. For example, a second train spawns when the first train is destroyed. This mechanism does not work. I used the Group Dead conditional statement and the Group Alive Less Than conditional statement in my logical argument. The second "late activation" train thinks the first train is dead then immediately spawns. However, both trains appear on the map. 4. The Hold function in the Advanced Waypoints Tab does not work for train units. For example, a passenger train will not stop at terminals along a path. 5. These locomotives and rail cars do not require the WWII Assets Pack: Loco VL80 Electric (A twin engine setup with electrical pantographs that connect to overhead wires) Loco CHME3T (Short & stocky engine, looks Soviet by design) Loco ES44AH (Modern GE style diesel-electric engine, in a Union Pacific skin) Coach Platform Flatcar Freight Van Open Wagon Passenger Car Tank Cartinity Tank Car blue Tank Car yellow Well Car @BIGNEWY, et al: Any recommendations to get the late activation triggers working? I'll upload a track file shortly, for further examination.

Thanks, ED for fixing the bug with artillery pieces!

@Ciribob, When would the next iteration of SimpleSlotBlocker be released? I, like others, lost the ability to block slots after all the recent OpenBeta updates. This is an excellent script and would like to continue using it on my squadron's multiplayer map. Thank you for all the work put into making this script!

I also noticed "colorful light" flashes when any MLRS fires. It's very hard to screen shot the visual anomaly but it happens frequently. It is best viewed when looking at the units in an external viewing mode.

I would also like to add that all MLRS unit types have the same problem. It is not limited to the US MLRS M270.

Thanks for posting! I have the same problem. It's like the MLRS are shooting blanks. It looks like it fires something but no rounds are visible in F10 map. It is very similar to @Livers and @Pilot Ike experienced. Jiroft MLRS Shooting Blanks.trk

@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

Hi all, I would like to move the UH-1's Crew Indicator display to another monitor. Is there any tribal knowledge on this? I've searched the forum and come up empty handed. I've tried modifying the lua files with no luck either. I've tried editing the crew_indicator_common.lua file in ...OpenBeta\Scripts\Aircraft\_Common\Cockpit. The line that normally affects an overlay (like the controls indicator) is the base.init_pos value. However, when I edit this value, nothing happens to the Crew Indicator. Additionally, I've treid to edit the crew_Indicator_page.lua file in ...OpenBeta\Mods\aircraft\Uh-1H\Cockpit\Scripts\CrewIndicator with no luck either. Any help would be much appreciated! Cheers, GeoS72

Is there a way to add a list of preset radio frequency channels to a mission without hand-jamming 20 - 40 frequencies per aircraft group? Could this be achieved through a LUA file or mission template? I am aware that each aircraft has unique radio channel requirements. Could there be a master file that would be referenced? For example, I create a mission with an F-14, F-16, F/A-18, and Mirage 2000. Can I make one master list of radio presets for each aircraft type?

Is there a ControlsIndicator.lua file available for the A-4 Mod? I was unsuccessful in finding it on my own and I didn't see it popup in this thread. If someone has a link then would you kindly direct me to it? My plan is to configure the Controls Indicator pop-up to my unique multi-monitor setup. Thank you in advance for the help!

I've been using this configuration for my CH Products HOTAS for 1yr+. These controls are my adaptation of the actual F/A-18C stick & throttle inputs to the CH Products devices (which model the F-16). Please take specific note that I separated the TDC Designate function from the ProThrottle Mini stick. TDC Designate was moved to the stick. This affords me faster designation of targets using the Maverick missile or FLIR pod. Your mileage may vary.

As a follow up to my original post, I add the following recommendations for folks with additional type/model/series aircraft to the F/A-18C Hornet: 1. The location and position of the Controls Indicator box will vary from aircraft module to aircraft module. For example, the location that works best in the F/A-18C will not work in the P-47 or the UH-1. 2. The file location may not be in the ControlsIndicator sub-folder as noted in the above Step 2. However, the file should be located in the aircraft cockpit scripts folder. 3. The folder location would be ..\DCS World\Mods\aircraft\[specific Aircraft, like P-47D-30]\Cockpit\Scripts 4. The file name may be a variation, such as controls_indicator_page.lua, but the content will be very similar. 5. The line to edit the base.init_pos will be different in each LUA file. Therefore, search for that specific name. 6. Do NOT copy one LUA file from module A into module B. There are subtle differences between the scripts for each type/model/series aircraft. 7. Create a backup LUA file before making any changes! 8. Follow the quoted steps outlined above given the exceptions noted in this update. 9. To make adjustments to the LUA file, end the current active mission, do NOT exit DCS (leave it in the mission debrief screen), make the necessary changes, then press the "Fly Again" button. 10. Repeat Step 9 until the location of the controls indicator box is within the desired location.

Thanks to Loophole for providing the info in Post #6. This thread helped me restore the Controls Indicator overlay back to my primary display. I recently added a trio of CubeSim MFD panels to my monitor setup. They are an excellent companion when mated to the Thrustmaster Cougar MFD bezels. The one problem I had was the loss of the Controls Indicator overlay. In order to bring the overlay back to the primary screen, I had to play with the values noted in Post #6. The procedures below were used to restore the overlay: 1. This fix must be done for each aircraft that you fly. If you only fly the F/A-18 then modify that speficic lua file. If you fly more than one aircraft, for example, the F/A-18, the F-16, and F-14, then you must edit the file in each folder. 2. The directory is here: ..\DCS World\Mods\aircraft\[specific Aircraft, like FA-18C]\Cockpit\Scripts\ControlsIndicator 3. The file name is: ControlsIndicator_page.lua 4. Edit file ControlsIndicator_page.lua with Notepad++ 5. Edit information on Line 54 (or close to it) 6. The content to edit is called base.init_pos, as mentioned in Post #6. 7. The default information of line 54 should be as follows: base.init_pos = {0,-(1 - 2.0*size_x)} 8. I had to play with these values in Step 7 a lot to finally get it right! 9. The values that worked for my monitor configuration are: base.init_pos = {3.27,-0.75} 10. This passes integrity check (if anyone is concerned about that)! 11. The Controls Indicator overlay is tied to the TrackIR view. That means when you look around the indicator follows. My primary monitor is an msi Optix MAG127CQR (27" curved display) and video card is an AMD Radeion RX 5700XT 8GB GDDR6 1750MHz. Expect your mileage to vary because of monitor resolutions, multi-monitor orientations, locations, etc.

Grimes, Thank you for the explanation and link!

Hello all! I'm very new in the ED forums and still trying to absorb alot of info. After some searching, I have one question to ask: Is it possible to assign a laser code in the mission editor or add it to a lua file? For example, I'd like to assign a different laser code other than the default, 1688. I'm ok with a player entering the code for an LMAV or LGB when rolling onto a target. However, I'd like to set the LANTIRN pod/FLIR/TGP or JTAC/FAC/AFAC code to something else, say 1700, as part of the mission brief. Basically, resetting the default code from 1688 to a different value. Would the resident experts kindly refer me to more relevant threads or help me navigate through the vast sea of information? All I've seen thus far are problems with changing laser codes for weapon employment during a mission. Thanks in advance!

New 2 ED Forum Hello DCS World! I am George and I've been lurking on the forum for a about 2 months. Been playing DCS since Nov/Dec 2019. I've been a flight simmer going waaaaay back on other platforms *cough* C-64, and DOS. My favorite module is the F/A-18C Hornet. I have others but I am most familiar with the "baby" Hornet. I mostly fly solo but would like to dip my toe into the multiplayer arena once key skills are more refined. Anyway, thanks for reading my post in this introduction thread. If you have any relevant questions then ask.