GeoS72

For a while, I had an issue in the South Atlantic map when exiting a base capture map. I would get the following pop-up error after exiting the map in Single Player or from the Mission Editor: Can not open debriefing file (see image). After reviewing the DCS.log file, it indicated an error in the debriefing.log at a specific line item. When I looked at that line item, it pointed to a Client slot that I added to the O'Higgins airfield. The Group and Unit names included an apostrophe, O'Higgins. This is what the debriefing.log file showed: ['OV-10A Aerodromo O'Higgins'] = { time = 10.001, value = 100, }, -- end of ['OV-10A Aerodromo O'Higgins'] I concluded the apostrophe in the unit name caused problems with the LUA naming convention. I changed the Group and Unit names of this client to: ['OV-10A Aerodromo O-Higgins'] = { time = 10.001, value = 100, }, -- end of ['OV-10A Aerodromo O-Higgins'] And the problem was solved! For further safety precautions, I removed any apostrophes from all other Group/Unit names. This error no longer appears and the Debriefing screen is properly displayed.

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.

I also just got word that a Client flying a RedFor aircraft caused the RedFor CAP to spawn over the same airfield. For example, Red Client MiG-21 takes off from Khasab causes RedFor CAP wave to spawn over Khasab. For the record, that event is ONLY supposed to be triggered by BlueFor client aircraft. What was done in the last 2 updates that caused a complete failure of the trigger system? This condition makes my squadron maps (stress MULTIPLE maps) unplayable! Has the fault been isolated and how soon of a fix will be available?

Here is the same map & mission set in a Single Player environment. The debriefing shows a lot of _#### events. I presume that is related to the broken trigger system of the map. dcs.log SP-Jousters PG Map_064 Debrief.log SP-Jousters PG Map_064.trk

I cannot express how disappointed I am right now about the broken trigger system that resulted from the past 2 DCS updates. I've seen triggers act as always true (Part of Group in Zone). I also see triggers not working properly, where part of a group is in zone but does not trigger the action. This is completely UNSAT! As an example, this MP map that my squadron uses has evolved over 3 yrs. It has worked well until the Dec 19, 2023 update. It has broken a lot of my triggers! It has also caused a lot of other problems: AH-64 with invalid loadout - configured for 16 AGM-114L but the SMS page shows 12 AGM-114L plus 19 FFARs. @Flappie, please review this DCS log and MP track file. The track file is very large so please follow the Google Drive link. MP Track file corresponding to this DCS Log: https://drive.google.com/file/d/1wo0XaqV___kq3CzcerHkmoyQOEv_Ukwt/view?usp=sharing As for mods, the map has the A-4, T-45C, UH-60L, & OV-10A modules. This map worked well with these mods BEFORE the 19 Dec update. If I were to remove these mods then that would break a lot more triggers and functions that is currently broken. dcs.log

I voted for the synthetic look. But that comes with a clause: Frame rate penalties should be minimized to the greatest extent possible. As an example, Rio Grande airport suffers from large frame rate hits. It has improved over time, but the lag when on approach, taxiing, or low-level flying is still noticeable. @Raz_Specter, I firmly believe this map is exceptional beautiful. Keep up the good work!

I am disappointed to not see the skeletons return for Halloween 2023. I admired the Easter egg from last year. Maybe this year, we get to see the deck crew wearing elf hats and the Shooter wearing a Santa suit? Now that would be a cool Easter egg to see!

@MAXsenna, Thanks for the reply. The thread you referenced was one of which I provided some feedback. That crew status indicator is different than the one I'm currently referring to. This is a screenshot of what I'm talking about. This crew indicator will show clients in key positions. It should be controlled by this file: D:\Games\DCS World OpenBeta\Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\CrewIndicator\crew_indicator_page.lua All of the variables are written horizontally and don't seem to make any sense to me. It can be found on Line 7 and states: populate(5, {{41.0/128.0, -38.0/256.0}, {86.0/128.0, -38.0/256.0}, {64.0/128.0, -58.0/256.0, {{"cabin_icon_displacement", 2, -70.0/256.0*size}}}, {41.0/128.0, -88.0/256.0}, {84.0/128.0, -208.0/256.0}}, 0.9)

Bumping up this message for greater visibility. Have any Mi-8 pilots moved this overlay in the past?

Thank you all for the observations and recommendations. I will simulate the EW effects of the Prowler as suggested.

Hello all! While editing the position of the AI Gunner indicator and Controls Indicator overlays for the Mi-8, I noted this Crew Status indicator (bottom left corner of the screenshot). How would I be able to move it from its current position to the space indicated by the empty yellow box? I moved the AI Gunner Indicator & Controls Indicator overlays by modifying the following files at their respective locations: D:\Games\DCS World OpenBeta\Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\AI\ControlPanel\g_panel_page.lua (AI Gunner) D:\Games\DCS World OpenBeta\Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\ControlsIndicator\ControlsIndicator_page.lua (Controls Indicator) I was unsuccessful in editing line 7 in the crew_indicator_page.lua file located here: D:\Games\DCS World OpenBeta\Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\CrewIndicator I was moving things around because of my multi-monitor setup and thought it looked cool to see. Otherwise, it would be hidden. My search for a similar topic yielded no results. Has anyone else played with the position of this overlay? Any advice or links to share would be appreciated! Thanks in advance for your input.

After reading this thread, I have 2 questions: Does this mod perform any jamming functions or employ electronic warfare on targets? Or does it fly around, shoot HARMs, and look nice?

Minsky, Yes, you are correct. I thought it was removed but I see the floater still present. It normally hangs around the Compass. So does this make any sense: Razbam put a hidden airfield on the map but chose not to fix the one airfield that has been broken for several months?

I am disappointed. At least they removed the misplaced base object from the map. So would that be considered a partial fix?

OK, the latest DCS OpenBeta update is out and the SA map got some love. But the question still remains: Is the Cullen Airfield bug fixed? There was no mention of it in the change log.

I believe Ramstein may refer to a "happy" sock. But I could be wrong.

Little Horn, I wouldn't waste your time. The problem is on ED's side and not yours. Let them get all of their stuff into one sock first.

This "failure to login" (error 502/504) problem reminds me about the 7-P's to life: Prior proper planning prevents piss-poor performance. Right now, performance is very low. I, for one, would like to know how ED plans to mitigate such log jams in the future. Because I saw something similar when the F-15E became available for pre-order; and now we must endure the pains that come along with a large update (which also coincides with the release of the Sinai map). What's the game plan for to prevent this from happening in the future, ED? Why am I locked out from playing offline with all the modules, including the Sinai map for which you were paid?

@Minsky, thanks for the update. Good to know!

I am surprised to see this bug has not been corrected. Any word from Razbam on it?

What are the 2 spawn points you mentioned - one for Blue and second for Red slots? I believe that is a function of the Slot Blocker. For example, my base capture map has a bunch of Red Client slots. When a Red base is captured, the slot blocker script will shut off Red slots & turn on Blue slots. If a Red client is airborne then that aircraft is deactivated. That is to say, a player is flying along then suddenly will see the F2 (next plane) view.

@commiccannon, Slot blocker should be able to handle multiple road bases. For example, I define this group of slots as a fail safe point in one of my slot blocker tables: --Blue Special Slots blueSlotUnlockerTable.FARP_Dublin_Spare1 = {"AH-64D FARP DUBLIN-1 *SPARE*"} Then, I have a ME trigger that turns on that spawn point after specific conditions are met. In this instance, a group called AH-64D FARP Dublin-1 flies into a trigger zone. Afterwards, Apache spare slots become available in case of accidents. Based on my experience, it is wise to automatically lock all unnecessary slots at mission start. Then you can control which slots can be unlocked as a mission progresses. This can be done through ME triggers. Does that help?

I searched for this in the Bugs section. Didn't see it. Has this already been addressed? Cullen airport location is in the wrong location. It shows that it "floats" south of of Sea Lion Island in Grid UB58. It should be in Grid EB34, east of Estancia Cullen.

The color band is still present after the last DCS update. This band is visible in ANY aircraft while using MT. The Huey is shown in this example. Inside the red box, one can clearly see a dark band in the right margin of the screen.

The other day, I posted a displays bug in the general MT section here: https://forum.dcs.world/topic/321269-thread-for-list-of-aircraft-specific-issues-with-mt/?do=findComment&comment=5176374 Even after Friday's update, I am still encountering the same issues. Has anyone seen similar problems or have a good fix for the following graphical errors in the AH-64D? Single-Thread (ST): 1. ControlsIndicator Display is clipped from view on an external monitor. Before Friday's update & the main Multi-Thread (MT) update, I could use this area for the ControlsIndicator Overlay. Now, it's gone. When looking at the screenshots, it is normally in the area marked "External AMPCD." 2. In the ST screenshot, I edited the LUA file to display the overlay on the center (primary) display. When I "walk" the values into the External AMPCD area, I can see it getting cutoff. I can move it to the other MFDs and it still be displayed without issue. 3. Also note the message box is displayed in the upper right corner of the center (primary) display. 4. The Graphics Performance Overlay (RCtrl + Pause-Break) works on any screen. It can be seen when dragged into the External AMPCD area. ST AH-64D ControlsIndicator Overlay Example: Multi-Thread (MT): 1. ControlsIndicator Overlay problem persists. It is clipped when placed inside the External AMPCD area. As stated above, this overlay worked in the External AMPCD area of the screen before the big MT update to DCS. 2. The ControlsIndicator overlay can be moved to any other area AND be visible (see 2nd MT AH-64D Screenshot). 3. Dot labels are no longer shown. (See 1st MT AH-64D Screenshot.) Sorry, I didn't take a screenshot of it working in ST. However, dot labels DO work in ST. Let me know if proof is needed. 4. Message box is no longer shown. (See 1st MT AH-64D Screenshot). The screenshots between ST and MT were taken at the same point during a training mission. This problem extends to other aircraft; tested on the F/A-18C and UH-1H. 5. The Graphics Performance Overlay (RCtrl + Pause-Break) works on any screen. It can be seen when dragged into the External AMPCD area. 6. The last issue I experience in MT with the AH-64D is a visible narrow band along the right edge of the screen. It is not visible while on the ground but it becomes noticeable when airborne. This anomaly does not exist in ST. (See 3rd MT AH-64D Screenshot.) MT AH-64D ControlsIndicator Overlay Example 1: MT AH-64D ControlsIndicator Overlay Example 2: MT AH-64D Narrow Band Example 3: Things to consider: 1. I use 3 Cubesim monitors so screen captures show extended display. 2. Position of Controls Indicator page is custom set to Cubesim monitors: base.init_pos = {-0.78,0.63}. 3. ControlsIndicator_page.lua and Cubesim.lua (monitor setup file) attached below for review. Am I overlooking anything? Thanks in advance for advice and recommendations! GeoS ControlsIndicator_page.lua cubesim.lua